DEV Community

Nick Palenchar
Nick Palenchar

Posted on


The Worst Blogging Advice I Ever Received

Canonical URL:

No annoying intro here. This is it:

"When starting a blog, be sure to update it regularly"

I've actually heard or read this general "nugget" many times. It is as ubiquitous as it is terrible. One reason is that it's only applicable to one type of blog. The kind that is monetized, relying on a large group of subscribers, with aspirations of generating a livable wage for the author. Obviously, there are many types of blogs.

Back in 2018 I had set a goal to publish one post a month. I thought it was modest at the time (some authors seem to post weekly at least), but it turned out to be GRUELING. It also didn't produce work I was most proud of. The result of this goal is most of the 2018 posts on this site (you might notice there's less than 12).

The fact that I couldn't commit made me question if I should even host a blog at all. I felt like a blog with large gaps in the timeline would give the same impression a "streaky" resume gives off. As a matter-of-fact, the aforementioned terrible advice is often paired with a warning that you will look like you lack a drive for commitment, which could turn off recruiters during the job search, if you don't post regularly.

This is equally misguided. When I look at my blog, I see a collection of articles that generally represents my thoughts on coding, and general values in the industry. These are topics that are valuable to me, the topics I want to talk about. I don't want it cluttered with noise that is less helpful to readers or myself. Form the viewpoint of a recruiter, wouldn't they rather find content that supports the author's expertise in the field?

I'm not really sure what my blog is. Heck why does it matter? I just enjoy my tiny space on the corner of the internet I can call my own! Maybe it's a subtle rebellion against larger platforms (blog and social media based). But the autonomy makes me feel warm and fuzzy inside.

For me, it's helpful to write my thoughts whenever I'm moved to do so. And I hope the result is a collection of genuine thoughts and advice that others might find helpful, too.

Top comments (1)

jsrn profile image

I agree! I think it’s useful to dig into why you maintain a blog, though.

If you want to be a blogger who people recognise as a blogger, then having a track record of regular content production is probably worthwhile.

For me, if someone looked at my blog and said “you clearly lack the drive to keep this updated regularly” I think I’d just say “yes.”

Plenty of people maintain a blog because they want to get more experience in technical writing, and to them I’d suggest that writing regularly doesn’t necessarily mean you should publish regularly. Or that you could maintain a separate “best of” feed on your site if you want to keep your reputation as a prolific writer while still putting your best work front and centre.

Thanks for the post!

An Animated Guide to Node.js Event Loop

>> Check out this classic DEV post <<