On how I notice it:
It's the endless need of more and more resources for running xyz.
In former days, the resources where limited. So, the programmers cared for performance by good practice coding & (over) optimization.
Example: NASA was in a search of an engineer to code on their old probe flying in space. The problem: very limited resources. So the engineer needs to think like the probe's built in processor and memory - slow and with limited registers. But capable of being highly optimized in doing that. They searched for a old (school) engineer from the 60ies or something like that.
My father, too, is an old school engineer. He doesn't like to use frameworks, but rather write everything by himself. He say "why should I learn logic of others, if I can do it by myself in same time without creating overhead. I use what is necessary, but not more."
And then, I remember whole office suite fitting on a bunch of 1.44mb floppy disks - compared to now's gigabytes.
And that's the problem. There's big * debt (where * insert what ever fits)
This needs more and more resources. In the same time, programmers do not care on the optimization side anymore, as the framework can't be touched easily, or because "it works like that".
This leads to the effect that everything is getting more opaque, with difficulty to catch bugs, or the bugs are introduced by external libs or something like that..
I see the cause with the bigger and bigger frameworks and the lazyness of programmers. Why should one use ORM when one can directly connect to database? Sure. The reasons are the same as the reasons for creating a ORM lib: to make it easier. But more resource hungry and maybe buggy.
9
6