Jedi Knights

Jedi Knights is a small engineering practice. The work I want to do is long-horizon: platforms that hold together for a decade, ingestion pipelines that don’t fall over on event weekends, developer tools that quietly make good engineers faster instead of getting in their way. The kind of systems you can hand back to a team and walk away from, and that still make sense years later.

The way I work has a shape. I take the time to understand the problem before I commit to a build, and I write the plan down first. I choose boring, well-understood tools over anything that will need re-platforming later. I finish a small number of things well before starting anything new. Restraint is a design principle, not a compromise. And I map every consumer of a service before I change its shape.

The engagements I care about have started with a team that had already tried something twice and knew the problem was real. If you are carrying a failure mode that has resisted a couple of attempts, and you want the foundation right rather than fast — that’s the work.

Named for the discipline, not the swords.