This is not to dissuade your choice. Rather, I'm looking for similarities between myself and others, and potential pitfalls to avoid.

Generally speaking: I just don't have the energy for the amounts of bullshit that comes with being in this career anymore. No job is immune from bullshit, this much is true--but I kind of hate this cop out because it strips agency from people in minimizing the amount of bullshit they are subjected to on a daily basis.

For me, that means to hell with this career. I very much want to do something different, so that's what's going to happen.

[1] https://news.ycombinator.com/item?id=25251029

Good luck on whatever voyage and path you end up taking, I genuinely hope you find a spot of zen for you and yours.

EDIT: BY THE WAY--I will probably never stop coding, as there are always opportunities to be efficient in bookkeeping and do some low level automation (in fact I do this already). I've also got a home lab running a few local services and I enjoy tinkering. I'm just not at all interested in writing and maintaining feature/production code for another SaaS platform or "tech company". Not at all. Never again. The idea of even interviewing for one of these jobs has the heart rate ticking up and the jaw to clinch up.

It seems most people still hold their love for coding or what spawns from that coding. It is the environment in which they code, that creates most of the frustration (and doesn't seem to be stopping anytime soon).

I wish you the same luck.

Wholeheartedly agreed

Yeah, I am a little salty about the state of things. I'd prefer programming in "my basement", and can understand why communication is important. Yet I can't help but feel we've thrown out the baby along with the bathwater.

Reason I emphasize agency is that as long as it gives the best result and meets the requirements (including ethical ones), I don't care how it is done. Result being very broad: features, maintainability of the code, enjoyment of the team, etc.. Anything else that is pushed from the management layers without good reason is needless overhead.

Now what do software devs usually do when we see needless overhead? Ah right, we remove it. If only it were that simple outside software.

I don’t necessarily believe all of the points above are negative but scrum can be an exhausting way to work.

There shouldn’t be deadlines every two weeks, instead you should be working towards a sprint goal. If the goal is not achieved then you can use that knowledge in the next sprint to reduce the amount of scope you try to complete. There are no deadlines per se, because deadlines try to fix scope and time, whereas a sprint only fixes time. The process of estimation and story pointing is where things become more art than science, but provided you are consistent in your approaches this mechanism prevents our inherent lack of foresight from becoming a catastrophic prediction failure.

Meetings like stand ups, retros, and backlog refinement can be super effective tools but they have to be run properly and tightly, otherwise they become worse than nothing.

I guess in this hypothetical team the thing to do would be to raise with the Scrum Master that you’re exhausted, raise in the retro that there are deficiencies in the process etc. and get back to a more sane baseline.

Additionally, many others have already argued against both the common implementation of Scrum, and its "ideal, perfect, theoretical" version. Just the idea of preserving asynchronous communication while introducing fixed, synchronous communication strikes me as an idea by someone who does not understand how people work.

Scrum as a set of process rules should not be particularly difficult for an engineering team to learn. I submit that if a team cannot operate under such a set of rules, it will be unable to adopt any set of process rules, and in addition to that, it will perform especially poorly under a system of no rules (i.e. direct rule by edicts from kings and queens).

Good lord it is exactly this kind religiosity that has me running for the exit.

I guess my question to you is, where are you exiting to? If you know of a process or methodology that is better and can articulate the reasons why, then I will gladly follow you!

This is in my OP that began the comment thread.

I guess I won’t be following you through that exit, but all the best and good luck for the future. I admire your courage in the pursuit of happiness.

Like, sure, you can make a team decision about what goes into this sprint, and what goes into the next one. But the management makes the decision what must be done in three or six months, and there is no negotiation about that.