- Limit opening blog spam SEO optimizations, this comes across as inauthentic. I feel we're increasingly conditioned to notice these things.

- Don't form voting cabals on hacker news / reddit. There's a lot of sophistication in detecting it. Let the natural popularity of a post be an indicator of what the audience likes. I'd further be paranoid if these sites detect a voting cabal, it could hurt the posts from the domain (to be clear, I don't know this for certain).

- Make it casual, interesting, and authentic.

- Don't put too many barriers between the author's authentic techie voice and the reader

- Find a way to give your great writers more autonomy on the blog. For example, instead of an upfront review process, give them permission to directly publish, but not share for 24 hours to allow a quick review for legal/PR reasons

- Give authors clear, consistent guidelines with what they can feel free to talk about / what they shouldn't talk about in public

- Create support for your newer writers. They're the ones who need encouragement and a writing coach. But don't take away their authentic voices, help them discover them.

- Don't get too cute with protecting IP. The in-the-weeds tech details are almost never the thing that makes a great organization or product.

- Understand the goals of your tech blog. Is it for recruiting? To get consulting clients?

- Focus on the long-game, strong community engagement, relationships, and domain authority, not short-term conversions (https://moz.com/learn/seo/domain-authority)

How do you prevent forming an awesome blog that will have <300 visits a month, out of which most visits will come from bots that will steal the content (usually on Chinese or Russian sites but not exclusively)?

Thanks, that's a really helpful list. Getting the goals right is, I agree, a bit part of the answer.

This is my favorite technical blog

https://www.righto.com/

Ken Shirriff started blogging about very average Arduino projects that he did but he taught himself how microchips work and he shares it with the rest of us.

There is a mental model for blogging that goes: "we'll submit this page to Hacker News, get 15,000 views; 12,000 of those will bounce right away; 30 will sign up for an e-mail newsletter; 3 will talk to a salesperson; 0.3 will start a trial; 0.03 will become profitable customers"

If you think that way you won't get the most out of blogging!

I'm sure every day somebody visits Ken's blog for the first time and spends the whole day reading it.

All of the content you describe is good. You need a lot of it. It has to be high quality. Some articles will be better than others and sometimes you'll struggle to get articles out the door. It will take a long time to accumulate enough articles to make a destination.

Be careful with "calls to action". On one hand you want people to take action. I've been told to add them to blog posts and really wanted to because I was just as hungry as my co-workers. Sometimes I feel like they drained all the authenticity out of the article though and were a subtraction instead of an addition.

Make it all about you and your reader. Don't let on that you are blogging because somebody else blogs, told you to blog, etc. Make it clear that you always respect yourself and the reader (e.g. watch self-deprecating remarks like "this blog is occasionally interesting".) There are many signs that make bad blogs seem inauthentic and you don't want to be that person.

Very helpful - thanks! I completely agree with the calls to action: I've found them inauthentic and jarring. It's a bit like carefully planning an outfit, then throwing some Crocs on at the last minute to serve as footwear! I'm off to spend the rest of my day reading Ken Shirriff's blog :)

Julia Evans' blog is my favorite technical blog. She has also written few posts on blogging / writing good articles:

1. Patterns in confusing explanations - https://jvns.ca/blog/confusing-explanations/

2. Blog about what you've struggled with - http://jvns.ca/blog/2021/05/24/blog-about-what-you-ve-strugg...

3. "advice" for aspiring tech bloggers - http://jvns.ca/blog/2016/05/22/how-do-you-write-blog-posts/

Date your posts!

Mention versions and dependencies where possible/practical.

Show me the code!

Point to relevant source material.

I'm a big fan of https://codeascraft.com/ which unashamedly long form writing about interesting technical problem solving. The authors do have their own voices but it's all at a really good standard.

I really like https://jrsinclair.com/web-development/. The author writes in a very easy to understand way. The subjects are always interesting and more unique. The author isn't writing, like everyone else, about the newest version of React or Typescript. There is depth to each post.

Lots of code examples and lots of simple explanations of complex ideas.

The tone is casual, like a conversation, rather than a lecture.

I try and replicate that a bit (but not nearly as well) on my own blog (sambernheim.com). The best way to get better is to keep practicing.

I like well-documented blogposts. Where the documentation / setup / code / schematics / etc. is clear and for everyone to see.

There are few things I hate more than posts where the author provides some half-assed instructions, maybe even omits very important things, and then when you try to re-create, it just fails to build halfway through.

Blogs that don't preach excessively and instead take a 'balance of opinions' or 'balance of approaches' view are more interesting. In particular a blog that states 'there is one best way to approach this particular engineering problem and all others are rubbish' is one I would avoid.

I usually blog about engineering topics on my personal blog, and at some point last year, I wrote a review of which posts seem to work better than others. Here is what I found in my specific case: https://jmmv.dev/2020/11/successful-articles.html

Here's what makes a "good" blog (of any kind) in my book:

- this is how we did what we did

- this is why you need to think about this thing, and here's a way (or ways) to think about it

- I got really bored, and did this thing - have at, Intarwebs

- here's something that I tried that didn't work, and I wish I knew why, or here is why (at least in this use case)