Distributed Systems · Cloud · Data Infrastructure · Agentic Workflows
- Building reliable backend systems with clear contracts, observable execution, and boring-by-design infrastructure
- Interested in Platform engineering, Software & Cloud architecture, and Agentic automation that stays deterministic where it matters
- Ship small → Validate → Harden
These are the projects I’m actively building and iterating on.
-
Design Cockpit — WIP workspace for making product/design decisions and turning them into clean plans.md + implementation contracts.md Repo → design-cockpit
-
Atlas Fabric — It explores whether we can systematically build a usable historical boundary dataset when none publicly exists Repo → atlas-fabric
-
IssueSight — GitHub issue context-bridge (LLM-assisted) to help juniors understand issues faster and reduce back-and-forth
Repo → issuesight -
Job Weaver — Go-based job discovery + digest system focused on startup/small-company opportunities
Repo → job-weaver -
Backenderer — lightweight deployment platform (infra-as-product) for shipping backends fast and reliably
Repo → backenderer
My default build order:
- Interfaces first (APIs, schemas, minimal UI surface)
- Execution engine (workers, queues, schedulers)
- State + data (Postgres, Redis, object storage, Iceberg)
- Observability (metrics, logs, traces)
- Hardening (tests, rate limits, failure modes, CI/CD)
This keeps complexity contained and makes refactors survivable.
- I ship small, learn fast, and iterate.
- Build → test → ship → improve.
Expect prototypes, experiments, and code that probably shouldn’t work (but sometimes does).



