
When we started building Codocly, the problem looked simple.
Developers write code, but documentation is often treated as something that comes after the real work is finished.
You build an API.
Then you document it.
You change the API.
Then you update the documentation.
A new developer joins the team.
Someone has to explain the architecture.
The codebase becomes larger.
Understanding it becomes harder.
We started Codocly to solve this problem.
But while building it, we realized something much bigger:
Documentation is only one part of the developer workflow.
And that realization changed our vision for Codocly.
The Original Problem: Documentation Is Always Behind
Technical documentation is important, but maintaining it manually is difficult.
A typical development workflow looks something like this:
text
Write Code
↓
Build Feature
↓
Deploy
↓
"Someone should update the documentation"
↓
Documentation gets delayed
↓
Code changes again
↓
Documentation becomes outdated
Top comments (0)