It depends! Sometimes I work on some code and stumble on a problem, and after solving the problem I stop 5 minutes to write the solution to it.
But most of the times it's more planned work. I decide a broad topic, and I write a list of 20-30 posts I can make about that broad topic. For example recently I started a C series. I wrote 26 posts on C, and I have a list of 20+ more posts to write on it, before switching topic.
Keep in mind I do typically write short posts, but I try to explain a single topic in each one. If my usual blog post was a longer tutorial, it would not be possible to post that much and I'd lower the frequency.
Founder of Skyward Digital, the UX Jamstack agency
Showing you how to:
💻 Create excellent websites
🚀 Evaluate and improve UX
🧡 Discover loyal users
👨🏻💻 he/him
It depends! Sometimes I work on some code and stumble on a problem, and after solving the problem I stop 5 minutes to write the solution to it.
But most of the times it's more planned work. I decide a broad topic, and I write a list of 20-30 posts I can make about that broad topic. For example recently I started a C series. I wrote 26 posts on C, and I have a list of 20+ more posts to write on it, before switching topic.
Keep in mind I do typically write short posts, but I try to explain a single topic in each one. If my usual blog post was a longer tutorial, it would not be possible to post that much and I'd lower the frequency.
That's really helpful. Sounds like I need to be more proactive in my writing and not just wait for the opportunities where I run into something good.