Urgent.News

One page, thousands of outlets. See who else covered it.

Editions

Tech

How Often Should I Post, and How Do I Choose Topics?

Someone sent me a message asking how often I post and how I decide what to write about. I started typing a reply, realized the reply was three paragraphs long, and realized that was the second most useful thing that had happened to me all week, the first being that they asked at all. So let me answer both halves properly. We'll do topics first, because it's the part people actually get stuck on,…

A reader asked about my posting frequency and topic selection. I replied with a lengthy explanation, realizing it was the second most useful thing that week, after their initial inquiry.

First, I addressed topic selection. You don't need to search for groundbreaking or unique ideas. Good material is often already available in your own experiences, knowledge, and interests. Look at what you already know, your areas of expertise, obvious things that others might overlook, what fascinates you, and what you are currently learning.

Problems you've faced and how you solved them are also valuable content. Additionally, questions you've been asked are pre-validated demands for information. Collect these topics by keeping a running list of ideas that come up in conversations, while troubleshooting, or when learning new things.

Regarding posting frequency, the honest answer is that consistency beats volume. Posting once a month with high-quality content will yield better results than an intense two-week period of daily posts that lead to burnout. The ideal frequency depends on your personal schedule and ability to maintain it. Avoid forcing posts when you don't have anything meaningful to say, but also don't wait for perfection.

Ship B+ content as it's better than waiting for an A+ piece. The key is to establish a sustainable rhythm that you can keep even during busy weeks, rather than focusing on the number of posts.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Security questions every senior backend engineer should handle

You are not being interviewed as a security engineer. You are being checked for one habit: whether, while describing a system, you notice who could abuse it. Security questions rarely arrive labelled.

  • Senior backend engineers must treat input as hostile
  • Focus on authorisation bugs and secure password storage
  • Demonstrate instinctual security thinking in system design

More from Sunday 16 August →