1. 10
  1.  

  2. 6

    Repost prompted by https://lobste.rs/s/r20yuv/write_documentation_first_then_build

    Were I to survey the programming blog posts I’ve read in the last ten years, I would file this little blog post among my favourite ten. Every project I started this way got a better design out of it. But then, I like writing docs, so maybe this works because it gels with my usual design process.

    1. 3

      In rare flow moments at nights this past few weeks, I documented READMEs for a couple of projects. While exhausting, it was therapeutic to update these constantly. Usable, good-enough breakdown of work is much better than starting at a mountain of thoughts.

      This and the larger ‘writing is thinking’ theme is certainly a solid mental model. Everyone can verify independently and derive benefit from doing it.

    Stories with similar links:

    1. Readme Driven Development (2010) via mtn 3 years ago | 18 points | 2 comments