Post

Developers love to build. We chase features, fix last-minute bugs, and move mountains of code—but documentation? That's for later!

Personally, it’s not that writing docs is hard—it’s the psychological, organizational, and technical hurdles in fast-paced dev cycles that push documentation to the bottom of the backlog. “We’ll do it next sprint,” we say, knowing deep down we might never get around to it. The fix? start small.

Oh i missed the link www.coderabbit.ai/blog/challen...

I imagine someone has written extensively on this, but my personal process is "TDD": Test Driven Documentation. Comments and Confluence pages can grow stale. But 100% test coverage with well-explained unit tests, plus a document generator like TSDoc, helps enforce documentation matches function.

Oh, 100%. But then, see, we are talking about a whole new topic. I love writing tests and then code, but it is not the default choice for many people. Infact, some do coverage as a covering the branches :(