A pattern language

We started our monorepo at work roughly 18 months ago. There had already been a previous attempt with some great ideas, but it was held back by things bolted on and too many “quick fixes” without much thought. What was the underlying theme including in our “new” monorepo until only the past ~6 months was a lack of clear, mature patterns throughout the codebase. We felt like we were moving fast, but the lack of shared conventions quickly created problems. There were lots of cases like error handling which weren’t thought through properly, something that can be quite easy to do given the happy path mentality that Typescript can lead us down. So the developer experience became poor over time, and that in turn cascaded into poor user experience. Just as we were struggling as developers, so were our agents. Without established architecture to follow, our agents constantly tried reinventing the wheel or generating their own “production ready” patterns which were usually dogshit. Without it…