Depends on the project too. Sometimes, writing up some code as a proof of concept is the best way to _inform_ the documentation, a way to gain clarity and unde

Depends on the project too. Sometimes, writing up some code as a proof of concept is the best way to _inform_ the documentation, a way to gain clarity and understanding of the problem. In other words, writing software doesn't have to be a linear process (rarely is). Sometimes you start with documentation if the problem is well understood. Sometimes you start with code to derisk the project. Most of the time, you bounce back and forth between the two.