Earlier quoted context omitted.
Waterfall is a straw man. Waterfall and agile are two possibilities within business-driven engineering (a euphemism for "you just code what we tell you to do, we make the decisions"). I don't think Scrum is that terrible for junior engineers, but it provides no exit. It's the terminal juniorness of it that has me bothered. I'm 31 years old and have been programming for almost a decade and I'm too old to work on "user…
How many people have you managed? How many projects have you conceived and carried through to shipping? How many of them are profitable? I suppose Fermi estimates would be fine. Those questions maybe have a snide undertone to them, that isn't my intent with asking them. You post confident rants about how businesses should operate, and I'm curious how much the above experience informs those rants.
I am slowly working towards this on my own, trying to get a personal side project to the point where I can do it full-time. I'm just starting and only spending a couple hours a week on it.
They used to be doing poorly-implemented Scrum where I work now, and I'm glad they dropped it. Having a daily 30 minute status report meeting that never started on time was killing almost an hour of productivity per day.