Earlier quoted context omitted.
Paperwork. I swear, it's paperwork. My mom is a (retired) preschool teacher. By the end of her career, she was working for a school affiliated with a large chain, and maybe 1/3 of her time was spent on filling out all the paperwork required by management. That was time she absolutely was not spending with the kids. My dad is a (retired) doctor. Similar story there. His hospital ultimately ended up associated with a r…
> The same thing happens at my own job, software. The bigger a company I'm at, the more of my job consists of filling out paperwork about the work I'm doing, rather than doing the actual work. There's some irony here considering software has been promising for decades to help businesses scale information sharing.
Concrete example:
15, 20 years ago when we tracked user stories, the status of the sprint, etc., with sticky notes on a wall. We didn't have to record a lot of information on them because they only needed to track status at a high level. Details were communicated through conversations. That did mean that a lot of that information was tribal knowledge, but that was actually fine, because it was of ephemeral value, anyway. Once the work was done, we'd throw the sticky notes in the trash can and forget the tribal knowledge. Reporting out happened at a much higher level. We'd report status of projects in broad strokes by saying what big-picture features were done and what ones were in progress. We'd fill operations in on the changes by telling them how the behavior of the system was changing, and then let them ask questions.
Nowadays, we put it all in Jira. Jira tickets are extremely detailed. Jira tickets live forever. Jira tickets have workflow rules and templates and policies that must be complied with. Jira rules make you think about how to express what you're doing in this cookie cutter template, even when the template doesn't fit what you're actually doing. Jira boards generate reports and dashboards that tell outside stakeholders what's happening in terms of tickets and force them to ask for help understanding what it means, almost like you're giving them a list of parameters for Bézier curves when what they really wanted was a picture. Jira tickets have cross-referencing features, which creates a need to do all the manual data entry to cross-reference things. Jira tickets can be referenced from commits and pull requests, which means that understanding what changed now means clicking through all these piles of forever-information and reading all that extra documentation just to understand what "resolves ISSUE-25374" means when a simple "Fix divide-by-zero when shopping cart is empty" in the commit log would have done nicely. etc.
We communicate so much more these days. Because we can, because we have all this communication technology to facilitate all that extra communication. What we forgot is that, while computers can process information at an ever faster pace, the information processing hardware inside our skulls has remained largely unchanged.