2 ms·
> The root of the problem is the uncontrolled complexity of modern software products. > Because of this complexity responsibilities are diluted, most of your co
by magicalhippo 8y ago
> The root of the problem is the uncontrolled complexity of modern software products.
> Because of this complexity responsibilities are diluted, most of your code is in your dependencies nowadays.
That doesn't resonate much with me. Yes maybe in terms of LOC most of our code is in dependencies. But most of our _important_ code is our own, in the business logic.
The reason our product is unreliable is mostly down to complexity as you note, but that complexity is driven by our users who want better integration and automation. Add one more optional behavior ("when X I need to do this tedious task Y, could your program do this for me?") and you've increased the testing surface exponentially.
On the other hand those additions is what sets us apart from our competition, and what makes the eyes pop when we show off our product to potential new clients.
So it's a balancing act. The complexity makes our users extremely productive[1], but it also makes our software more fragile[2].
[1]: For example, one client went from almost an entire day of manual data entry for certain orders to less than half an hour due to a "smart" Excel importer I wrote.
[2]: Users now want the Excel importer to behave in conflicting ways, and trying to cater to that without breaking one of the use-cases is very difficult.