small-batch software always looks calmer on day one. one app does one thing, and that feels clean right up until you have to move data, teach someone else the workflow, or remember which tool owns what.
that’s the part i keep running into. the giant all-in-one app is annoying in a different way, but at least the mess is in one place. what do people actually prefer once a team has to live with it for a year or two?
The “remember which tool owns what” problem turns into an incentives problem fast: nobody wants to be the person updating three systems.
I think it depends on the environment and task at hand. What I have found to be helpful for teams that are running automated or ad-hoc scripts to extract or manipulate data, interact with API’s of COTS proucts, or any other operational task is to create a terminal based wrapper that handles extensibility. Everyone can use what’s there in the base and “bolt on” new functionality. That way the list of commands/capabilities can grow without impacting the others and the use of each is relatively similar aside from the unique flags of each extension.
There is always more than 1 way to solve a problem, just sharing what’s worked for my teams at multiple companies.
:: Copyright KIRUPA 2024 //--