DEV Community

Discussion on: Technical writing: how long does it take you to write a post?

Collapse
 
deciduously profile image
Ben Lovy • Edited

I've found that a) yes, it always takes several times longer than I think it will and b) both your 1 and 2 options are hard. I prefer to build the app alongside the writing, but inevitably will change my mind about something and need to make sure the post stays in sync with the actual code. When coming back to write it up after the fact, though, it's not always easy to remember what order things need to go in. I like trying to make sure my walkthrough-style posts have points where the user can pause and execute the current state to make sure things are working, but that takes extra care to get right, and often "placeholder" code along the way which doesn't end up in the final product, which makes the post even longer to write (and read).

I guess I don't have any advice, I just agree that it's harder than it looks.

Collapse
 
clarity89 profile image
Alex K.

Agree that both options are hard. What I ended up doing was to build a working app first and then build it piece by piece again while writing up to make sure the code fragments actually work. Guess that's one reason why it took much longer :D But I wanted to make sure that the code works as expected at every step of the tutorial.

Yeah, I wasn't really asking for an advice, just wondering if others had the same experiences : )