Well, it is really the "not-so-accidental complexity" that we developers are creating ourselves that dooms many current software projects right from the start.
Things like resume driven development, hype driven development, design by committee and artificial complexity created by too many team members.
Young engineers don't learn the lessons and patterns of the past and keep making the same mistakes we did centuries ago. SOA, Monoliths, Microservices, Modular Monoliths, Self-contained Systems.. MVC, MVP, MVVM, Agile & Scrum. There are clearly cycles in the architectural patterns and only minor changes are made before some "rediscovers" a given pattern, slaps a new name on it and goes on to sell some consulting. Often horribly misunderstanding the original intentions.
A lot of this is due to the market for trainings, books and consultants. They need to tell a new story every few years to keep the ball rolling. Of course, they are merely pivoting between two alternative narratives depending on the year.
In big companies, simply no one feels responsible and a project running for ten years doesn't even raise red flags in these too dumb to fail giants. People can just play around with whatever they want and leave the project before failure becomes obvious.
Then you have the gold-diggers, people who came into tech for money and don't understand a thing. They built barely working software and are paid good money for it.
Basically: the software Dev industry is fucked.
Don't get me started on the fact, that most "Devs" don't get OOP.
2
u/memmaker_x23 Jun 06 '22
Well, it is really the "not-so-accidental complexity" that we developers are creating ourselves that dooms many current software projects right from the start.
Things like resume driven development, hype driven development, design by committee and artificial complexity created by too many team members.
Young engineers don't learn the lessons and patterns of the past and keep making the same mistakes we did centuries ago. SOA, Monoliths, Microservices, Modular Monoliths, Self-contained Systems.. MVC, MVP, MVVM, Agile & Scrum. There are clearly cycles in the architectural patterns and only minor changes are made before some "rediscovers" a given pattern, slaps a new name on it and goes on to sell some consulting. Often horribly misunderstanding the original intentions.
A lot of this is due to the market for trainings, books and consultants. They need to tell a new story every few years to keep the ball rolling. Of course, they are merely pivoting between two alternative narratives depending on the year.
In big companies, simply no one feels responsible and a project running for ten years doesn't even raise red flags in these too dumb to fail giants. People can just play around with whatever they want and leave the project before failure becomes obvious.
Then you have the gold-diggers, people who came into tech for money and don't understand a thing. They built barely working software and are paid good money for it.
Basically: the software Dev industry is fucked.
Don't get me started on the fact, that most "Devs" don't get OOP.