At 12:18 on a Tuesday, I used a 45-minute gap between meetings to pair-review already-merged validator and exception code with a mid-level engineer. The feature was live and working. We still spent the hour reading handlers together, arguing about why a generic catch-all should catch a specific exception, and trimming database setup from unit tests.

Management books tell directors to stay technical by blocking out a mythical “maker day.” Those days never survive a director’s calendar. What survives are the cracks between meetings, and choosing code over chat when one opens up.

Plumbing and pair reviews in the cracks

Thirty-to-sixty-minute calendar cracks are too short for features, which is why most directors stop trying. They fit interruptible work: CI plumbing and post-merge reviews. Two weeks earlier, I used a few calendar gaps to migrate a CI pipeline and discovered our static analysis check had been silently passing for months. A misconfigured step returned a zero exit code without scanning a file. Every dashboard was green, so nobody looked until I wandered through the plumbing.

The Tuesday pair review did different work. Reviewing shipped code without a release deadline lets you debate design instead of policing style. Near the end, I told him: “My collaboration with you will have succeeded if, whenever you next update your CV, you have more to write.” He now leads the architecture for his squad’s next major integration, and those validator patterns show up across the team’s PRs unprompted.

The catch with quiet teams

Those calendar cracks only exist because my three teams run their own ceremonies and ship without me firefighting. That quiet autonomy comes with one real catch: outward legibility. To anyone who watched the transition over six months, a quiet week means the structure is holding. To a new VP in week one, with zero accumulated context, that same silence looks like a data void. The fix was not writing top-down status digests myself; it was coaching my leads to broadcast their own delivery and risks upward as part of running an autonomous team.