Engineering design docs can be a huge time saver and a cultural pillar when done right, especially for remote teams. Most teams have adopted them in some form, yet very few teams will suggest they're nailing it. Also, writing design docs can be intimidating without experience. Building a tool for writing technical design docs, we were surprised to find a lack of online resources and guidelines on this topic. So we put together a community resource of the best design doc examples and templates that we could find on the Internet. We're excited to share this labor of love. Check out DesignDocs.dev if you want to: 📑 Emulate design doc writing from 40+ leading engineering orgs and OSS projects 💡 Get inspired by 1000+ real examples of design docs 📠 Copy templates used by real-world teams 🤔 Understand the why, when, how of design doc writing

I was just with a technical co-founder who has an engineering team across 4 time-zones. When I asked about their collaboration — their immediate answer without prompting was "we've always used design docs and hardly ever have the need for meetings". Thanks for the collection @shin_kim1.