Kinda understand in the old days developers were engineers, we solved it, by code and by machines / computers. You had a good idea of the problem, had experienc

Kinda understand in the old days developers were engineers, we solved it, by code and by machines / computers. You had a good idea of the problem, had experience, knew the best ways to to visualize a gui around it. Then companies got addicted to scrum, micro management, only minimal changes allowed, nothing radical to change, and old code got over engineered, to complex for what a user realy wants, driven by marketing selling points that never got sold anyway. I've seen this so many times, while all side projects where you were in that old full control went great. Then you get blamed "you dont fit the company..." Companies rarely take a look in the mirror, has the main project become a nightmare sinking ship instead of you (only a few believe in it). The problem is I think scrum to many people involved, to many people want to say, (not knowing the engine), good software usually has good dictators leading it positively without needs for scrum (or minimal). Good coder (i noticed) usually are intelligent people to have nice conversations with, will write elegant code, and love to share their ideas, as if it were readable books you would like to talk about. The poor coders are extreme focused on "their" code knowing it all and there is no argue about it, they feel talking about code is a waste of time, see sorry about their faults and laugh about others people misstakes. Above all they protect their position in the company, (it might be better if they changed jobs) but on every company we have those people, not open to ideas, new aprouches new solutions.. you just dont fit in they say... If the WHOLE scrum process takes a coder more than hour a day, its gone wrong IMO (and yes most often this goes wrong because their so "experienced", while you've seen way more companies failing just like them)