Jira and the ticketization and subdivision of work into trivial units, removing real ownership of a feature. It's not that I'm against planning work over time,

Jira and the ticketization and subdivision of work into trivial units, removing real ownership of a feature. It's not that I'm against planning work over time, but there should be a minimum level of a granularity that's more than a few lines of code at a time so that a single person can effectively design, implement, debug, polish, and ultimately ship a meaningful chunk of work -- at the feature level, ideally -- rather than some minor subsystem that then gets integrated into a bunch of other subunits of work by three or four other people and then tested by yet more people who had no prior contact with the body of work. This sort of divide-and-conquer, IME, leads to terrible user experiences and unmaintainable code because no one person or team or has oversight or ownership into the final integrated product. I only had this problem at companies with heavy middle management and not enough engineering input into processes, often with no engineering leadership at the top or upper middle. I eventually quit that job because I was so frustrated by the stupid bureaucracy and my micromanaging direct manager, who wasn't very experienced in the frontend world and kept suggesting (nay, insisting) on inappropriate solutions based on his prior knowledge from 10 years ago in a different field. I got 10x more work done before they implemented the new system and brought on the new manager. This sort of system was intended to bring up the bottom performers and help them stay accountable, but as one of the higher performers on my team (according to my reviews, anyway), it constantly hampered me and prevented me from getting meaningful work done. I spent way more time fighting the bureaucracy and shuffling Jira tickets between like 8 columns and more subcolumns (that nobody really followed anyway) than coding. Quit soon after that, after complaining to our VP with a detailed report about why the new system wasn't working and was actually hurting productivity. All he did was ask me to hide the report so I wouldn't embarrass anyone =/ All my best work was done in the opposite situation: small teams with high autonomy and minimal managerial interference. We still had frequent checkpoints and demos, but the engineers did the actual design and coding, and we were measured by our outputs, not our processes.