[patrick_haply]

> You can't write a good blog post without having already written some number of bad ones.

To add to this, I'd say: if you don't have a writing habit, the barrier to actually writing something when you do finally have something useful to say will be incredibly high.

I am willing, however, to give the GP the benefit of the doubt because they said "Engineers should blog publicly when they have something to say", not "Engineers should blog when they have something to say". Practicing writing does not mean that you have to publish everything.

[thr0waway1239]

So how do you get feedback for non-public work? On technical blogs, I always read the comments. Even for obscure/somewhat poorly written articles. Because someone who knows more than the author will sometimes leave feedback which will lead you in a better direction and expose you to more ideas.

And thankfully, technical blog articles don't attract too many comments on average. Quite often I find that a blog article on a technical point actually advances discussion on that idea.

All I would say is to make a honest effort. Try and do a basic rewrite before hitting publish.

[cookiecaper]

People have been practicing privately and only occasionally getting checkpoints of public feedback across all kinds of skillsets for centuries. It's silly to act like we don't know how to practice in private.

Yes, you need a good guide, good general principles so that you're not practicing in the wrong direction. And yes, you need occasional "recitals" where you test audience reactions. But 99% of the work involved in developing any skill is just raw, rote repetition that most audiences are not only not interested in, but actively avoid.

[thr0waway1239]

>> People have been practicing privately and only occasionally getting checkpoints of public feedback across all kinds of skillsets for centuries. It's silly to act like we don't know how to practice in private.

Fair enough. I can see why my comment came across as if I said there were no other options.

But my point is to use resources at your disposal. One of the amazing resource at our disposal today is the ability to cost-effectively publish a half-baked idea on our website knowing that a) that could still be useful for a small section of people and b) its mistakes could be corrected by another small section of people who know the topic in greater detail and c) all this happens in such a way that everyone is, quite literally, "on the same page".

[flocial]

I also find that the second I hit publish, l tend to find errors and implicit assumptions, etc. Something about going public adds extra polish.