
Does Security Cross Your Mind When You Ship Code?
Four common security mistakes in development, from validation that only lives in the frontend to blind trust in JWT claims, and the excess of trust that connects all of them.
Read articleSystems architecture, technical decisions, and engineering leadership. Content built from 20+ years designing software in production.
For engineers with enough experience to know that right answers depend on context. The content assumes you already know how to program. The focus is on what comes next: architecture, long-term trade-offs, system evolution over time, and the technical leadership that sustains that work.
Three disciplines that overlap in the practice of those who design, build, and sustain complex systems over time.
System design, system decomposition, and trade-offs that define what a system can do over time. How decisions made today constrain or expand the options available tomorrow.
Code design that survives over time. Managing complexity in large codebases, how systems accumulate or reduce structural debt, and how to build software that can be changed without fear.
Technical influence, alignment of decisions across teams, and building engineering culture. How experienced engineers multiply impact beyond their own code.

Four common security mistakes in development, from validation that only lives in the frontend to blind trust in JWT claims, and the excess of trust that connects all of them.
Read article
Progressive architecture for secure storage on Azure with Java. Covers Managed Identity, User Delegation SAS, Private Endpoint, WORM, and LGPD-compliant retention. Documented incidents provide context for each decision.
Read article
How I added AI-powered semantic search to a long-form blog using SQLite, BM25, fuzzy correction and embeddings, without a vector database or paid API calls per query.
Read articleSoftware systems rarely fail because of isolated bugs. They fail because decisions accumulated over time define what a system can or cannot become.
Architecture is not about diagrams. It is about the choices that determine how a system evolves, who can change it, and at what cost.
This site exists to explore those decisions.
I design distributed systems, lead technical transformations, and develop engineers. Every article here is born from real decisions made in production systems.
How I think about engineering →