[gamedever]

For me, the #1 reason I don't blog more, especially about tech topics, is that they take too long. Maybe you can bang out a useful blog post in 20 minutes. For me it's more like 4 to 8 hours.

I have to make samples. Since I do mostly web tech I want the samples to actually work, no "here's some code, trust me". I also need diagrams. And, I have to proofread since I'm terrible at getting it right in one or even 5 checks. I write once, add samples, write some more, add images, write some more. Every time I write I add errors, so it always takes multiple passes.

[gpjt]

Proofreading is one place that AI can actually be a friend rather than a foe. If you give Claude your draft and tell it explicitly to call out misspellings and grammatical errors only, it does a really good job.

[zabzonk]

Much like (say) MS Word does? In real time.

[arvinsim]

Proofreading is easily done with an editor. I think AI is much more useful for giving critic and advice on how you write your sentences. Setting the tone, refining the main idea, pointing out redundancies are some of the things that I find very useful.

[lawn]

My drafts usually live for days, weeks, or even months before I publish them. (And sometimes I throw them away after having worked on them for many hours.)

My advice is to "chill": focus on the process instead of the result and let the posta take the time they take.