> Eventually all context is lost, busywork is amplified
why not fire everyone in between the top-most manager and the actual "worker" doing the work, as the report could be generated with the correct level of summary?
Mostly because there are different depths of reporting required depending who you’re creating said reports for. Often it’s unnecessary bureaucracy, but also often the ones doing the “actual work” don’t have a full understanding of how what they’re working on interacts with other parts of a system. (I mean this broadly, and not just related to software development)
Middle management can sometimes be good at this, because they may actually have the time to step back and take a holistic look at things. It’s not always easy to do that when you’re deep in the weeds with clients, managers, colleagues, or direct reports bugging you about misc things.
Overall I think (or hope) the more useless reporting will die a slow death, but I also think there’ll be a loooooong period of AI slop before we reach the point where everyone says “why are we actually doing this?”
why not fire everyone in between the top-most manager and the actual "worker" doing the work, as the report could be generated with the correct level of summary?