About

Background

I'm a software development team lead and hands-on engineer building and evaluating AI systems for software development. I work directly with coding agents, developer tooling, model experiments, evaluations, and the systems that help teams ship reliable software.

Over the years, I've worked across the full lifecycle of software delivery — from architecture and cloud infrastructure to developer tooling, documentation, and team culture. What ties it all together is a belief that the best outcomes come from investing in the systems and practices that help teams work more effectively.

My leadership experience provides context for that work: how a tool fits into a team, what evidence supports it, where its limits are, and whether people can maintain and improve the surrounding system.

Engineering Philosophy

I believe software teams should work in ways that are sustainable, transparent, and grounded in practical reality. Here are the beliefs that shape how I approach engineering work:

  • Evidence over AI novelty. I evaluate what a system can do, where it fails, and when human judgment or a more capable model is required before promoting it into a workflow.
  • Bounded experimentation over broad claims. Local and open-weight models are useful learning and evaluation tools for bounded work, not production solutions or replacements for frontier cloud models. I escalate when a task's complexity, reliability, or stakes exceed the evidence.
  • Documentation as a first-class artifact. Good documentation is not a side project — it's the difference between knowledge trapped in one person's head and knowledge the whole team can build on.
  • Practical systems over theoretical purity. The best architecture is one the team can maintain, evolve, and explain to a new hire on day one.
  • Developer experience is a team multiplier. Investing in tooling, onboarding, and local development environments pays compounding returns across every project and every new team member.

Leadership Approach

Leading engineering teams is about creating conditions where good work happens. My approach centers on three themes:

  • Mentoring and growth. I invest in helping team members develop the skills and confidence to take on increasingly complex work. The measure of good leadership is a team that doesn't need you.
  • Engineering culture. Culture isn't perks — it's the daily practices around code review, incident response, documentation, and how we treat each other when things go wrong. I lead by example in those moments.
  • Driving outcomes, not activity. Busy teams are not necessarily effective teams. I focus on clear goals, measurable progress, and removing the obstacles that slow delivery.

Interests

The areas I focus on most and enjoy writing about:

Coding agents and workflowsEvaluations and reliabilityCloud infrastructureDevOps and CI/CDDocumentation and knowledge managementDeveloper toolingEngineering leadershipLocal AI and open-weight models