I build software with a bias toward clarity, reliability, and finishing the job.
Most of the work lives in the space where services behave, interfaces remain readable over time, and architecture follows use instead of ego.
Start simple, make it work, make it right, keep it understandable.
I’m comfortable working inside real-world constraints, technical, organizational, or otherwise, and making the best possible outcome from them.
Good systems rarely come from freedom alone, but from thoughtful limits.
Speaking of that, limitations are also my favorite design tool in hobbies like game development, where constraints often lead to the most honest and interesting solutions.
Different medium, same idea, when something is well built, it quietly disappears and just works.
exploring small systems, quiet games, and durable ideas