I build long-living systems — software designed to change safely over time, not pretend to be finished.
My focus is on:
- Designing foundations instead of products
- Making trade-offs explicit
- Building systems that stay understandable years later
I believe good software is less about features and more about decision hygiene, boundaries, and evolution.
I’m building and sharing common infrastructure services (auth, audit, data, foundations) that:
- Solve boring but real problems
- Are intentionally incomplete by design
- Document why decisions were made
- Expect change as a first-class concern
Everything is shared openly — code, design, and documentation — so others can learn, reuse, or evolve it.
- Designed for change, not completion
- Stable core, flexible edges
- Safety by construction (DB-level guarantees > application promises)
- Explicit trade-offs over hidden magic
- Documentation is part of the system
If a system can’t explain itself, it’s already decaying.
I work primarily across backend, cloud, and infrastructure layers, with an emphasis on reliability, scalability, and long-term maintainability.
A multi-tenant, append-only audit logging service built with Postgres RLS, Keycloak, and explicit evolution docs.
Why it exists:
- To show how to design infrastructure that survives change
- To demonstrate real trade-offs instead of idealized diagrams
➡️ Designed to evolve, not to be “done”
- Backend architecture
- Infrastructure foundations
- Systems that outlive their authors
- Simplicity that comes from clarity, not shortcuts
- Thoughtful discussions about system design
- Collaboration on infrastructure-level projects
- Reviewing or exchanging design ideas
If you care about how systems age, we’ll probably get along.