There's this thing that happens where software teams get "stuck."You know the kinds of teams I'm talking about. There are still features the business wants from them, but all their time gets sucked away by support and maintenance and bug fixes. Changes that "should" be simple take forever. The tests suck. The build takes forever. They're stuck with weird architectural decisions made by people who left the company years ago. The code is crammed with complexity from one-off features that only one or two clients use.When I land on these teams I often find the developers on them fixated on making big changes. They need to write an entirely new system using event sourcing. They need to break the monolith into micro services. They need permission to stop all feature development for a few months. Above all, they need more staff allocated to the project.But big changes rarely help a team that's really stuck. What really helps is small changes— and a lot of them. Inline that misleading…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.