203
Your Engineers Aren't Lazy, Your Codebase Is Punishing Them
(piechowski.io)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
We used to do retrospectives at one of my old jobs, because everywhere loves cargo-culting agile and scrum stuff.
I quickly realized that a lot of the problems were largely outside the team's control. It was shit like "The CEO doesn't believe in designers or UX, so he won't hire one, so we spend a lot of time doing that work badly ourselves." Or, "management is making us spend all this time in 'planning meetings' so we don't get anything done"
Stuff that has easy solutions, but we can't do because some idiot or powerful cry-baby is in the way.
Retrospectives are great for finding and sharing a consensus on these kinds of issues. The team can weigh their options. Known limitations are much better than unknown ones. And often, some bandaids and workarounds are possible to diminish negative effects, at least to a degree.
I've definitely had things we had to wait for, or are still waiting for. At least we don't usually get outright rejections.