robinsamways.ca · Stack Decisions
$ I Found My Tech Stack by Auditing My Own Code
Auditing the actual dependency files across four separate projects found that one had already converged on a specific framework/ORM/database/auth combination, on its own, before that combination was ever consciously chosen as a deliberate standard.
The insight wasn't 'I decided on a stack.' It was 'I looked at what I'd already built across separate projects and recognized the decision I'd already made, independently, more than once.' The other projects are now being deliberately brought toward that same stack, on purpose this time.
Project A's real dependencies (checked directly, not assumed):
one framework, one ORM, one database, one auth library
Project B's dependencies at the time: a different stack entirely
Project C's dependencies at the time: the same underlying problem as B
The decision was already made. It just hadn't been named yet.The fix
Not a fix — an audit. Checking real dependency files directly, across every real project, rather than deciding on a stack from preference and asserting it after the fact.
Why this matters
A stack page that says 'I found this by auditing my own code' is more credible than one that just asserts preferences — it's evidence a pattern was actually followed in practice, independently, more than once, rather than a list of technologies picked because they sounded right.