What I use to build software.
The setup behind the work — the AI-assisted workflow I lean on, the editors and languages I reach for, the infrastructure I ship on, and the machines it all runs on.
AI-assisted workflow
- Claude CodeMy primary agent — it drives most of the day-to-day work.
- CursorIDE-native edits when the change is small and local.
- PiWhen a more flexible, configurable setup than the others fits the task better.
- The principleAI to move faster on prototyping, testing, and review — without lowering the bar for what “done” means.
- Building for agentskomust is an example of building for agents — it emits
survivors.jsonfor them to act on.
Editor & terminal
- IntelliJ IDEAJVM work.
- VS CodeEverything else.
- GhosttyTerminal.
Languages & frameworks
- Kotlin / JavaWith Spring Boot, Micronaut, and Ktor as the leading frameworks.
- GoFor services where it earns its place.
- TypeScriptNest.js on the backend, Next.js / React on the front end.
- PostgreSQLThe default datastore.
Infra & services
- Kafka, Docker, KubernetesThe runtime backbone.
- GitHub ActionsCI.
- VercelHosts this site.
- AWS and AzureCloud, depending on the client.
Hardware
- MacBook ProThe main machine.
- PC running OmarchyAn Arch-based Linux setup for everything else.