DEV Community

Discussion on: What are your best tips for writing technical blog posts?

Collapse
 
ssimontis profile image
Scott Simontis

Whenever I write something, I set a timer I feel is appropriate. For example, I try to respond to all e-mails in under five minutes. If I cannot do that, I'm overthinking things and not conveying my ideas clearly enough.

I think that attitude of staying out of the weeds is very important...no one is going to take about the issues you are presently overthinking for hours. And sometimes if I am slowly struggling along and failing to make satisfactory progress, I just delete everything and start over.

Sometimes I outline things. When inspiration hits me, I record the idea as an outline, and if detailed enough, I basically end up with an article minus some glue sentences by the time I am finished.

Collapse
 
danielplust profile image
Daniel

Sometimes I outline things. When inspiration hits me, I record the idea as an outline, and if detailed enough, I basically end up with an article minus some glue sentences by the time I am finished.

This articulates the process I've come to use almost exactly. Except I don't outline things just "sometimes"—I have to all the time.

Thanks for sharing.