loading...
Cover image for You should write that blog post

You should write that blog post

helenanders26 profile image Helen Anderson Originally published at helenanderson.co.nz ・2 min read

What can you blog about?

Plenty.

If you can write release notes or a page full of useful technical documentation, it’s just as easy to write a blog post with some commentary about your project, something you’ve learned recently or some top tips you can share.


Project Releases

Blog posts go hand in hand with Project Releases as timely commentary or an announcement that the feature you’ve been working so hard on is available. Write about why it’s so useful and how someone can get started.

It doesn’t have to wait until your release. You can provide regular updates on how things are going, but remember to think about the “why” and not the “how” to avoid repeating what you’re putting into your technical documentation or readme.


Tips and Tricks

People love lists of quick, readable tips for languages they’re learning about or tools they are new to. You will be surprised how many things you think are obvious, that others have not considered.

Have you been studying something in your spare time? Working on your professional development? You have a unique point of view, so get writing and share it in a blog post.


Get writing

The best way to get started is to get started.

  • Open a google doc and start writing.
  • Keep it brief with lots of headings
  • Add Grammarly to your Chrome browser and get another pair of eyes across it.

The Nerves

It can be nerve-wracking to put yourself out there, so I’ll reiterate what has been said in posts before:

  • You’re reinforcing your learning or understanding of your chosen technology or tool. So even if you only get a handful of views, you have still done something worthwhile.
  • This is all about your unique point of view. Which doesn’t mean you have to know everything on a topic. That’s why you are writing a blog post, and not rewriting technical documentation.
  • Everyone makes mistakes, that’s why there is an ‘edit’ button if you spot a typo once you have published your post. So don’t worry too much about it being 100% perfect.

Be prepared for friendly comments and questions … and start thinking about the next blog post.


This post originally appeared on helenanderson.co.nz

Posted on by:

helenanders26 profile

Helen Anderson

@helenanders26

Making applications go faster at Raygun, AWS Data Hero, and tag moderator on Dev.to. Database concept you don’t understand? Let me know, I’ll write a post!

Discussion

markdown guide
 

I'm writing one right now!

Another thing that I wanted to add here is don't worry about the word counts. As long as your post is helpful, then your blog is already great and that's all that matters.

You need 300 words to get your point across quickly? Do it! You need 2000 words to teach someone about the programming tool? Do that too!

 

I love seeing successful writers encouraging others to write. Writing is so rewarding (even if no one reads it!).

With your reach and following I know you will inspire a bunch of devs to give writing a try and experience the rewards for themselves 💪👍🙏.

 

Great article with plenty of encouragement and an awesome breakdown on where to get started. Love it!

 

YES!! Its so easy to overthink a post or think that a topic is overdone when it is not.

 

You inspired me to document my "call centre -> web developer intern" journey. Thanks! 🥰

 

Ditto the grammarly tip, it is so amazing. I now use it for everything to write with confidence.

 

I don't know how I've lived without it, to be honest.

My only problem is that in New Zealand we use 'UK English' but at my workplace, we must write in 'US English'. Switching gears between words like color/colour, program/programme, organisation/organization is extra mental overhead.