In the last 2/3 years, our market has been facing great changes. Not even the big firms are having a good time; rather, it is quite the opposite. Their payment times have become even longer than their decisional times. For them, not taking any action has become a sort of strategy, given how much they fear making a mistake.
It’s better to look for new markets as soon as possible. We will search for clients abroad, although keeping here our production. In the meanwhile, however, there has been a market which found us, without us actually looking for it. It’s the start-up market. If the former one didn’t take any decision at all, the latter does it too much, and too frequently. And as we all know, haste makes waste.
The outcome, is usually a solution that by now gets called, even in an euphemistic way, quick & dirty. The most mean ones do call it the spaghetti code, with reference to the whole software architecture.
Since long time ago, we had adapted to work in an Armageddon Team environment. We always privilege package contracts and this forces us to be strongly efficient in the management of any possible variation that might occur as we go. To be able to sustain the possibility that some start-up might succeed, and if they do, it will be on an international level only, we have to pre-think our sw (software) in terms of horizontal scalability, of which I know the actual meaning, but I like to extend it to the concept of sw.
Which sw does scale horizontally? The one that allows me to change or add components with simplicity and therefore with formal “neatness” at every level of the software architecture. Thus, here comes our asymptotic goal regarding the proceeding through successive approximations: quick & clean. We need to render clean what is usually dirty, while respecting an important commitment: quick