Things are done different ways for a reason, sometime. The heavyweight process that essentially disrespects the individual contributor (agile et. al.) has a place in a corporate, accountability ecosystem where reporting is required. But it definitely turns the individual into a factory worker, on a line, putting screw A into slot B.
Yet so much got done, for decades, without agile's help. Even at large companies, sometimes. Even on large projects.
I imagine the vitriol above was a response to the dehumanizing effect that agile has on the individual contributor. They become, by design, a replaceable unit. "Hey get me a 6-pack of programmers for this project!"
I've worked on more than just crud apps. And at this point, with the front-end/back-end false dichotomy, nobody works on simple crud apps anymore. Single page js frameworks have made interaction design so bloated, it's kind of a little bit awful.
But the real loss of traction is in third-party services, authorization and inter-departmental warfare over favor and jurisdiction. Who's on top? Who tops from the bottom?
Y'all have your way, and I have mine. Getting up at seven in the morning, to commute to a nine o'clock stand-up that goes nowhere, and does nothing is a waste of my fucking time. Grooming sessions? Planning sessions? Retrospectives? When the fuck am I going to get a chance to sit and fucking think?
Oh, this is supposed to be an eighty hour work week, isn't it?
Look, my setup works for me. Just add an option to disable agile/scum.
I just try to be fair and balanced. But I feel with you.
Handle process in a case-by-case basis. If something needs changing, change it, but move on and GET SHIT DONE. That's the only way to go. I don't care what people say, good programmers don't need to be babysat.
However, the point of the process is to enforce consistency. If you have no process, then everything is dependent on the whims of the programmer in charge of the project.
No code review? Then I have to trust your code is spotless.
You want to be left alone in a library until the project is done? Then I have to trust you understand the product owners requirements perfectly.
You want to be in charge of the project? Then I have to trust you can handle that.
If I just hired you, why should I trust you?
Based on your comment, I wouldn't trust you at all. You sound like the kind of person who only learns lessons the hard way.