#docsascode 搜索结果
Developers: do you prefer inline code comments or external docs for understanding complex systems? #DocsAsCode
Docs should be tested like code. If examples don’t run, the docs are broken. #DocsAsCode
Documentation isn’t just about transfer of knowledge—it’s about transfer of confidence. A good doc makes a user feel capable. #TechnicalWriting #DocsAsCode
Documentation is UX for developers. If your API docs are hard to navigate, your API is hard to use. They’re not separate problems. #DocsAsCode
Open-source maintainers: do you wish contributors wrote more docs, or do you prefer fewer but higher-quality contributions? #DocsAsCode
The curse of knowledge hits documentation hardest. What feels “obvious” to you took years to learn. Docs aren’t for experts—they’re for people who don’t know yet. #DocsAsCode #TechnicalWriting
Docs-as-code isn’t just putting markdown in Git. It’s treating documentation with the same rigor as production code—because for users, the docs are the product. #DocsAsCode
Open-source maintainers: do you think contributors underestimate the value of documentation, or is it just harder to motivate than code? #DocsAsCode
Developers: when you hit confusing docs, do you file an issue, try to fix it, or silently move on? #DocsAsCode
Open-source maintainers: what’s harder—keeping docs up to date, or keeping them accessible to newcomers? #DocsAsCode
Developers: what do you rely on more—official docs, blog posts, or community Q&A? #DocsAsCode
Wow! "The Ultimate Guide to Software Architecture Documentation" is highly listed on Hackernews. workingsoftware.dev/software-archi… #arc42 #c4model #docsascode #softwarearchitecture
Version control for docs = peace of mind. DeepGuide uses Git as the source of truth #git #docsascode
Over the past few years, #Pinterest has been embracing #DocsAsCode across the organization. The outcome? ✅ Improved documentation quality ✅ Higher team satisfaction ✅ A transformed culture of collaboration, quality control, and discoverability 🔗 bit.ly/4efsXCY
Clear documentation is a force multiplier. Every well-written page saves hours of future explanation. #TechnicalWriting #DocsAsCode
Docs-as-Code, Accessibility, OWASP Top Ten – wir haben neue Trainings im Programm! Ist etwas für dich dabei? socreatory.com/de/news/neue-t… #trainings #softwarearchitektur #docsascode #documention #owasp #websecurity #accessibility
Pick the right git branching strategy for your #DocsAsCode project with our handy guide (including diagrams-as-code, of course!) hubs.li/Q02Frg4w0 Documentation may need a different git strategy than code, this article will help you make an informed decision
If copy-and-paste is so bad, what are the alternatives? Find out in this post from @HeatherCloward1 about strategies for content reuse hubs.ly/Q020JzKy0 #DocsAsCode #Writing
Developers: do you prefer inline code comments or external docs for understanding complex systems? #DocsAsCode
Open-source maintainers: what’s harder—keeping docs up to date, or keeping them accessible to newcomers? #DocsAsCode
Docs should be tested like code. If examples don’t run, the docs are broken. #DocsAsCode
Documentation isn’t just about transfer of knowledge—it’s about transfer of confidence. A good doc makes a user feel capable. #TechnicalWriting #DocsAsCode
Open-source maintainers: do you think contributors underestimate the value of documentation, or is it just harder to motivate than code? #DocsAsCode
Open-source maintainers: do you wish contributors wrote more docs, or do you prefer fewer but higher-quality contributions? #DocsAsCode
Developers: what do you rely on more—official docs, blog posts, or community Q&A? #DocsAsCode
Clear documentation is a force multiplier. Every well-written page saves hours of future explanation. #TechnicalWriting #DocsAsCode
Developers: when you hit confusing docs, do you file an issue, try to fix it, or silently move on? #DocsAsCode
Docs-as-code isn’t just putting markdown in Git. It’s treating documentation with the same rigor as production code—because for users, the docs are the product. #DocsAsCode
Documentation is UX for developers. If your API docs are hard to navigate, your API is hard to use. They’re not separate problems. #DocsAsCode
The curse of knowledge hits documentation hardest. What feels “obvious” to you took years to learn. Docs aren’t for experts—they’re for people who don’t know yet. #DocsAsCode #TechnicalWriting
Keep your docs consistent with automation+linters. New lesson in our Docs as Code Fundamentals course: how tools like Vale, markdownlint, lychee, axe-core, DocsKit + EkLine help you catch issues early+save time. docskit.link/mvya7v #platformOS #DocsAsCode #DocsKit #EkLine
Contributing a verse: When users become documentation authors - Fabrizio Ferri Benedetti passo.uno/docs-contribut… #TechnicalWriting #TechnicalDocumentation #DocsAsCode #SoftwareDocumentation #OpenSource #FLOSS #SoftwareDevelopment
Version control for docs = peace of mind. DeepGuide uses Git as the source of truth #git #docsascode
Something went wrong.
Something went wrong.
United States Trends
- 1. #2025MAMAVOTE 996K posts
- 2. $ZOOZ N/A
- 3. #ThursdayThoughts 1,975 posts
- 4. #thursdayvibes 2,901 posts
- 5. Good Thursday 29.9K posts
- 6. Mila 17.9K posts
- 7. Deport Harry Sisson 19.2K posts
- 8. Ninja Gaiden 19.3K posts
- 9. Deloitte 13K posts
- 10. #TOMORROWXTOGETHER 48.9K posts
- 11. #NJCAADay N/A
- 12. Dead or Alive 17.2K posts
- 13. Happy Friday Eve N/A
- 14. No Kings 142K posts
- 15. Itagaki 21.2K posts
- 16. Jennifer Welch 6,193 posts
- 17. DuPont 2,501 posts
- 18. Starting 5 7,276 posts
- 19. Andrade 5,328 posts
- 20. Bernie 45.4K posts