Yeah I agree this seems more like tech debt and possibly a shitty architecture to me, both problems that ultimately come from poor management. The codebase I’m responsible for at work was developed in a mad rush, and the levels of pointless coupling and interdependence sometimes makes it hard to change anything without spending forever tracking down all the stupid little places that piece was touching. That shit comes from management pushing you to just do the thing already and move on, which works for a while until things get so messy you have to slow down or spend some time on a refactor. Someone could easily have made a technical decision for the sake of expedience, which was then built upon and became interconnected with other things in a way that made changing it require a major change, which of course no manager will support, so the work gets broken up into 100 tiny stupid tickets trying to move toward adding the new feature without ever making a breaking change, slowing down the whole thing even more.
Yeah I agree this seems more like tech debt and possibly a shitty architecture to me, both problems that ultimately come from poor management. The codebase I’m responsible for at work was developed in a mad rush, and the levels of pointless coupling and interdependence sometimes makes it hard to change anything without spending forever tracking down all the stupid little places that piece was touching. That shit comes from management pushing you to just do the thing already and move on, which works for a while until things get so messy you have to slow down or spend some time on a refactor. Someone could easily have made a technical decision for the sake of expedience, which was then built upon and became interconnected with other things in a way that made changing it require a major change, which of course no manager will support, so the work gets broken up into 100 tiny stupid tickets trying to move toward adding the new feature without ever making a breaking change, slowing down the whole thing even more.