EngineeringA quiet defense of monoreposThe discourse is loud. The reality is: it depends, and here's the rubric we use.SVSachin VermaJan 18, 2026 · 7 min readGOASHINS / NOTESPart of a collectionLessons from the trenches3 of 4When to monorepo# 3 services that share types Frequent cross-cutting changes Mature CI When not to# Independent release cadences Teams that don't talk A CI you don't trust ← PreviousType tighter than you thinkNext →Five books that changed how I debugIn this collectionLessons from the trenches01What I learned from saying no for a year02Type tighter than you think03A quiet defense of monorepos04Five books that changed how I debugRelatedGOASHINS / NOTESEngineering9 minApex Governor Limits in 2026: what still bitesFive years of platform updates later, the governor limit cheat-sheet you actually need at 2am during a release.May 10, 2026GOASHINS / NOTESEngineering12 minWriting agents that don't hallucinate toolsA small set of guardrails that cut tool-call errors by 80% on our internal stack — no fine-tuning required.May 2, 2026GOASHINS / NOTESEngineering8 minType tighter than you thinkCheap TypeScript moves that catch real bugs without making your code unreadable.Mar 15, 2026