4 ms·
Personally I'm a fan of writing your first draft of documentation before writing the first line of code.
by natpalmer1776 2y ago
Personally I'm a fan of writing your first draft of documentation before writing the first line of code.
- vlod 2y agoReadme Driven Development https://tom.preston-werner.com/2010/08/23/readme-driven-development.html https://tom.preston-werner.com/2010/08/23/readme-driven-deve...
- eesmith 2y agoOr from the 1990s, "User manual as spec" - https://archive.org/details/rapiddevelopment00mcco/page/324/mode/2up?q=%22user+manual+as+spec%22 https://archive.org/details/rapiddevelopment00mcco/page/324/... For example, the Excel Basic spec: https://www.joelonsoftware.com/2006/06/16/my-first-billg-review/ https://www.joelonsoftware.com/2006/06/16/my-first-billg-rev... > Then I sat down to write the Excel Basic spec, a huge document that grew to hundreds of pages. I think it was 500 pages by the time it was done. (“Waterfall,” you snicker; yeah yeah shut up.) On the page above "user manual as spec" is "point of departure spec", which would be more like the iterative prototyping style.
- tracker1 2y agoI'll often do similar if I'm exposing a library... I usually want to work out the semantics and API for how to use the library before actually writing the interface.
- natpalmer1776 2y agoInterestingly enough, my personal philosophy is to write all backend code as if it is a library for my future self. That is to say, I want to be able to forget everything about a project and still have the resources I need to use the project code as if it were a black box consumable library.