Notes on architecture, debugging, and the craft of building production software.
For years, writing clean functions and wiring up endpoints felt like the whole job. Now that AI writes code well, it's becoming obvious that was never the engineering part — it was just the entry point.
A computer engineer can hold a circuit board in their hand. A software engineer can't hold a codebase. So what does it actually mean to engineer something that has no physical form?
The real cost of a bad architecture decision on a platform that touches money is not a failed test — it is a financial edge case you discover in production. Here are the decisions that shaped Vehicash, and what each one was actually optimizing for.
Before NestJS, I spent weeks stitching together TypeScript, Express, Jest, and project structure by hand. The hard part was not the configuration — it was realising what I was actually learning.