[primis]

I (Mostly) agree with you here:

> Finding and fixing bugs is a lot of fun. Incidence response is a lot of fun. Hacking on new projects is a lot of fun. Writing unit tests is fun too.

I'd agree on the first three, I'm not a huge fan of unit tests though. They seem like something a "good programmer" should do but to me it's in in the CYA lane, not programming.

> Refactoring, rewriting, sprint, agile, rearchitecting things etc aren't that fun.

I actually like refactoring code. To me it's like pruning a garden, moving stuff around to fit better. It also helps me on longer running projects to fix up crap that I wrote months/years ago. I'm always growing as a developer, and fixing foundations so they don't end up a cobbled mess is actually a pride point for me.

Agile / Sprints / Pre-Future proofing / API contract writing? Pure overhead for me. My current job is a ridiculous amount of meetings. I get like 15-20 hours of meetings weekly in my position.

This really boils down to being at a company that doesn't have technically knowledgeable management, and being on projects without a dedicated architect.

[t43562]

Unit tests allow other team members (and yourself in 6 months) to make changes with much less fear.

Sprints are supposed to be a few minutes where we spot early if someone is in trouble so we can fix it asap. The rest of the meetings should really be getting done by your product owner and maybe some kind of team lead. As you say it's usually a result of people not knowing things but sometimes that's the dev team too as in insufficiently well described requirements needing to be clarified.