The Archieve of AC LAB

AC Lab was a program I developed for older equipment, adapting its software to fit the needs of the people using it.

Equipment and software don’t necessarily age in the same way. A machine may still perform its function while its application reflects an earlier way of working, with steps and assumptions that no longer fit current requirements. Treating the whole setup as a single, ageing asset can obscure where the limitation actually sits and lead to a larger replacement than the problem requires.

My contribution was in the software, working within the equipment’s constraints while reconsidering what the program could allow people to do. That required respecting the existing setup without treating every decision in the original application as a permanent requirement.

What interests me about this work is the distinction between a necessary constraint and an inherited decision. A fixed sequence might protect an important dependency, or it might reflect how someone preferred to organise a task years ago. They can look identical on screen, but changing them has very different consequences, which makes understanding why something exists an important part of deciding whether to keep it.

There is also an economic question behind the technical one. Keeping an application unchanged avoids the immediate effort of development, but may preserve recurring manual work, reliance on particular people for support, or limitations on what the company can do. Changing it introduces development, testing, transition, and maintenance costs. Both sides deserve examination, including the costs that have become familiar enough to disappear into everyday operations.

For me, a worthwhile improvement needs a clear connection between the restriction being addressed, the outcome it enables, and the effort required to maintain it. That gives development a purpose and provides a basis for preserving the parts that already work well.

I also care about how today’s change affects tomorrow’s options. A useful update should leave its assumptions and dependencies understandable, so the next requirement can be assessed without someone having to reconstruct why everything was built that way.

AC Lab reflects the kind of development I want to pursue where understanding what an existing system still has to offer and finding where software can give it room to evolve. A company can have good reasons to keep its equipment without being committed to every decision that came with it.