4 ms·
I fear this is great advice. I too avoid writing documents. Or even reading them. I want to have my hands in the code, but it's increasingly clear to me that I
by mcv 7y ago
I fear this is great advice. I too avoid writing documents. Or even reading them. I want to have my hands in the code, but it's increasingly clear to me that I need to write more stuff down.
- xinau 7y agoI had/have the same problem, what helped me a lot was to write down what I've learned (roughly bi-weekly). Another booster was to stick to the same document structure for example NABC for proposals and ideas. NABC: https://nielschrist.wordpress.com/2012/07/13/the-nabc-method-standford-research-institute-sri/ https://nielschrist.wordpress.com/2012/07/13/the-nabc-method...
- deleted 7y ago[deleted]
- gonzo41 7y agoI don't fear writing documents, but i do work with a lot of people who do fear reading! I've found a really good trick is to highlight key figures or a few standout grabs in the early paragraphs of the text and then to have more substantial higlights towards the meaty parts of the document. Essentially it's like having the bullet points and full document in one. It;s resulted in a lot of people getting interested up top and being tricked into reading down the bottom. Give it a try sometime.
- squeed 7y agoFor sure. Part of being a successful writer is communicating in a way that is most effective for your audience. Rarely is a wall-of-text the right answer. Bullet points, flow diagrams, and examples are all helpful techniques when writing for engineers.
- larrywright 7y agoWriting would be valuable to me even if nobody else ever read the documents. I find that writing helps me think through a problem much better, and in the end I have a better solution.