I watched a newer team member spend most of their first few months entering data into a tracking system. Not because it was a learning exercise, not because it helped them understand the domain, but because the senior they were supporting didn't want to do it themselves.
My director said something offhand on a call recently that stuck with me: promotions codify what's already been happening. By the time someone gets promoted, they've already been doing the work of that next level, and the title is just catching up.
I have more personal projects than I can realistically work on right now. A shoe rack out of plywood, a decorative fence to hide the air conditioner, low voltage landscape lighting, enclosing the patio under the back deck, smart home automation, software tools I've wanted to build for years.
I was reading a post on Hacker News - a list of rules for being a new manager. Good rules. But some of them really are rules for new managers. I've been watching Gotham Chess's "slow-run" series, and it gets at this.
Last month, Yum Brands announced that it's selling Pizza Hut to LongRange Capital, a private equity firm, for $2.7 billion. The deal splits the brand in two - LongRange gets everything outside mainland China for about $1.
I was on a team that put junior developers into the on-call rotation earlier than we should have. The reasoning made sense on paper - they needed to learn the system, and the senior engineers were stretched thin.
I wrote a while back about framing problems with proposed solutions - the idea that "this is broken and here's what I think we could try" lands better than "this is broken" on its own. I still think that's mostly right.