Hacker News new | past | comments | ask | show | jobs | submit login

Not really commenting on the guide, but for me, clarity of thought follows writing. Not the reverse.



Yup. For me the process is something like:

1. Think that I know something.

2. Write about it. Realize I didn't know it anywhere near as well as I thought.

3. Reflect on and actually understand thing.

4. Edit writing now that I actually know what the hell I'm talking about.


And further than that, even if when do know most the pertinent details, the best way to communicate them is probably not the jumbled order it appears in your head, nor is it even some "logical" order (such a timeline or logical argumentation).

Writing for clarity often involves careful consideration of how to sequence the information such that it can be consumed given the audience and knowing when to elide details or otherwise footnote them.


Same, I usually end up writing anything important twice because the first draft is when I realize all of the things I hadn't thought through.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: