Start here

Start with the shape of the work.

Read these if you want the argument, not the archive. They cover operating design, platform thinking, AI without magic, and why ownership is the actual mentoring mechanism.

Work Writing

Foundational posts

Mar 2026
The engineering manager's second architecture

Software architecture is only half the job. The operating system around planning, ownership, review, and decisions is what determines whether a team can actually use that architecture.

engineering management execution architecture
Mar 2026
Writing as a force multiplier for engineering leaders

Writing is leverage. It sharpens thinking, moves context out of one person’s head, and compounds in public the same way internal platforms compound inside a company.

writing career engineering leadership
Mar 2026
Platform thinking for smaller teams

You do not need a platform org to practice platform thinking. You need a habit of turning repeated pain into reusable defaults before the one-offs become the architecture.

platform engineering developer productivity architecture
Aug 2026
AI for engineering managers without magic thinking

SpotDraft’s agentic SDLC is not a tool rollout. It is a designed loop from requirement to merge-ready PR, with agent-ready codebases, orchestration, and humans still owning the call.

ai engineering management developer productivity
Feb 2026
Manager and staff engineer partnerships that actually work

The manager and staff-plus partnership works when technical direction and operating design are explicit, shared, and aimed at leverage rather than overlapping heroics.

engineering management architecture
Mar 2026
Developer velocity without metric theater

Velocity improves when you diagnose the system — missing platforms, review bottlenecks, unclear specs — not when you celebrate the numbers that are easiest to count.

developer productivity engineering management execution

What I optimize for

01

Technical depth is one of my strengths, but engineering leadership is about converting that depth into leverage.

02

I stay close to code and architecture because it gives me better technical judgment. The goal is not to become the critical path.

03

I want engineers to think independently, make judgment calls, and learn through stretch rather than wait for perfect instructions.