TL; DR:

• Staying technical starts with knowing what "technical enough" actually means for your role
• Design reviews and code review exposure are your minimum baseline -- they keep your surface area alive
• Trust is not a weakness: as your scope grows, being deeply expert in everything is impossible and trying will break you
• Join me for the live stream (or watch the recording) on Monday April 13th at 7:00 PM Pacific!

---

The Technical Tightrope: Staying Sharp When Strategy Starts Eating Your Calendar

There's a Reddit post I came across in the ExperiencedDevs community that asked a question I've heard a hundred times: "How do you stay technically sharp when your role becomes more strategic?"

It sounds simple. It's not.

This is one of those things that sneaks up on you gradually. One day you're writing code most of your day. Then the meetings start. Then the strategy conversations. Then you look up and you're spending maybe two or three hours actually touching code out of an eight-hour day. And a quiet panic sets in: am I losing it?