Microservices can help when domain boundaries are real and teams need independent deployment. More often they become a distributed monolith with expensive operations and coordination. This post lays out the warning signs and what I would do instead by default.
Read the postDeep tech makes it tempting to wait for clarity, but that usually produces demo-ware and long feedback loops. This post argues for shipping thin end-to-end slices early, and for including one real constraint in every increment so the system stays honest.
Read the postA reflection on abstraction in programming and mathematics, and on the tension between clean interfaces and performance realities. I connect this to AoS vs SoA, to optimizer placement, and to lessons learned building Qadence.
Read the postStarting a greenfield project is an iterative requirements exercise, not a one-shot design task. I share a practical approach to early PoCs, stakeholder alignment, and keeping ambition in check so the codebase stays easy to evolve.
Read the post