Get knowledge in before the plan hardens
Late surprises are usually missing people and missing ideas, not missing slides. Lower the cost of speaking while change is still cheap, and give credit when someone else’s knowledge changes the design.
The work is people, goals, and decisions
Architecture is technical system design — boundaries, data, contracts, failure, rollout — plus the leadership to align people on those choices against a measurable goal.
AI Works Best When Engineers Lead
AI gives engineers more reach when people set purpose, direct the work, exercise judgment, and own what happens next.
How to review AI-assisted code before it ships
A practical review process for checking scope, access, evidence, and ownership when a coding agent contributes to a change.
Taking a proof of concept to production
How to turn a successful experiment into software a team can test, release, operate, and support.
Modernizing legacy systems without a big-bang rewrite
A team-centered, risk-driven approach to finding seams, preserving behavior, shipping vertical slices, and retiring old code with evidence.
Designing an asynchronous boundary that survives outages
A team case study in replacing a brittle synchronous integration with durable intent, idempotent delivery, explicit recovery, and operational evidence.