> Spend 50% of the writing time actually writing, the rest tweaking, reading and illustrating. Details are important.
I find this true not just of blog posts, but any time I've done formal writing at all. There is an immense gulf in quality between writing that has gone through even just one heavy edit/revision process and writing that never has.
I've recently been encouraging my technical co-workers to expend more time on not-code, such as documentation, tutorials, plans, postmortems, internal RFCs, carefully worded PR/commit comments, etc. One challenge is that people sometimes think that when they "finish" a piece of writing, they're done. Unless you've been iteratively revising pieces of it in smaller chunks, I think you're really only halfway there.
I find this true not just of blog posts, but any time I've done formal writing at all. There is an immense gulf in quality between writing that has gone through even just one heavy edit/revision process and writing that never has.
I've recently been encouraging my technical co-workers to expend more time on not-code, such as documentation, tutorials, plans, postmortems, internal RFCs, carefully worded PR/commit comments, etc. One challenge is that people sometimes think that when they "finish" a piece of writing, they're done. Unless you've been iteratively revising pieces of it in smaller chunks, I think you're really only halfway there.