This week has been full of annoyances. Changes in operational behaviour which have presented themselves as weaknesses in automation and tooling. I’m not talking about things we were too lazy to think about during design and development, I’m talking small paradigm shifts: 8-fold increases in data (mostly noise); new data combinations; and repeated execution of a human initiated process more than once a minute (for the last two years once a week).
We were actually quite prepared for the data increase. Our original design allows for scaling out. However, part of the data source is temporally sensitive and out of sequence handling is not an option.
We’ll get over these once we understand the reasons for the operational changes and what the new requirements are.
In a rash moment I thought it would be a good opportunity to totally reimplement one of the applications. Bad idea. The application is used by Project Managers, touches business partners (represented by our Supply Chain group) and involves our Accounts Team.
It turns out that not only do all these people have an opinion on the operational requirements for the application but also how it should be implemented.
I’m pretty sure I don’t mind producing a new application but I have no patience for the endless debate and lack of a view towards a common good. People are spoilt by software these days. They all want their own workload reduced to zero. In a world of tight budgets this is difficult to do.
Agile allows you to manage backlogs but they become endless. Every feature is essential.
We’ll eat the elephant one bit at a time and who knows perhaps end up with more than a series of compromises.
Bring back the single feature command line application.