Ageism sucks. And I see older folks constantly subjected to it. But let's be clear, ageism isn't *just* towards older people. A common occurance is older people trying to pull rank on younger developers, even when the younger devs are clearly more qualified. It seems the more meaningful distinction is not age or years of experience - but whether or not you care about your work, and have continued to refine your taste and explore new ideas. Maybe we need a new metric: "Years of new experience".

Is anyone noticing more bugs across the web and in software in general? Our team’s been seeing bugs across cloudflare, GitHub UI (we’ve been seeing the pink unicorn a lot), VS Code randomly breaking. As more teams adopt AI, is this this the norm? Surely this can’t be sustainable long term.

Valuable metrics are a quiet superpower. What are some you like to pay attention to? Here are some GH metrics that have helped me: 1. PR Cycle Time — how long from PR open to merge. If this spikes, something's blocking the team. 2. Review Load per engineer — who's doing 11 reviews while others do 1? 3. Stale PRs — PRs sitting unreviewed for 5+ days are a team health signal, not just a delivery signal. 4. Deploys per week — Teams that ship frequently have fewer big-bang releases and lower stress

What’s your take on oversized Pull Requests? Knowing that it’s the norm of AI assisted development, automation hasn’t still caught up with humans reviewing the changes.. I would and still reject overly large PRs for reasons outside of testing and fixtures.

How do you handle a PM who won't stop creeping the scope after sign-off? Seriously, every single sprint it’s the same story. We agree on the goals, lock it in, and then a few days later it's "just one more small thing." Except that "small thing" completely blows up the architecture and wrecks our timeline. How do you guys manage PMs who do this without completely destroying the working relationship?