Recent searches
Search options
I think a significant amount of organizational dysfunction (like the reading time in meetings thing) is easily explainable by people being overworked.
People aren't prepping for the meeting ahead of time so you move the prep into the meeting.
Why aren't people prepping? A totally reasonable explanation is that they've got 5 of these meetings this week plus a sprint full of coding work plus they're on call.
This also explains a bunch of "technical debt".
A pattern that repeats throughout my almost 20 year career (I old) is an engineer finds a bug that requires a non-trivial effort to fix systemically.
They make a local change to avoid (not fix) the bug.
Why? Because they don't have time. They can't take time. They don't feel like they can justify it to their manager. Maybe they're worried they won't hit an OKR.
This happens a lot with less experienced engineers but I find myself doing it.