DEV Community

Discussion on: What is the ideal length for a technical blog post?

Collapse
 
steelwolf180 profile image
Max Ong Zong Bao

You can stop with adding more and start to edit it.

You should ask yourself these questions:

  • Have you pick a title, who will attract anyone to read it?

  • Does that article provide value to your reader be it a perspective or solving their problem?

  • Is what you are writing evergreen (It remains relevant after technology changes)

  • You can edit and keep it to 1400 - 1500.

  • How long did you set aside to write and edit it?

It's very easy to overshot when you are writing.

So focus on spending the same amount of time you write to edit your articles as well.

Collapse
 
scrabill profile image
Shannon Crabill

Good questions!

I have a working title of "Finding the Most Popular Item in a Has_Many, Through Relationship" but I am not sold on it. Will it add value? For me, yes. I learned a lot more about what was happening in my code while writing this post. Will someone else find it useful? I hope so, but it's hard to say for sure.

I spent 6+ hrs on and off writing it yesterday. I want to get faster/better at this.

Collapse
 
steelwolf180 profile image
Max Ong Zong Bao

It's alright, I started out with just setting aside time for myself to write and you get faster after multiple times.

I started out with just high-quality articles that take about 3 - 4 hrs.

My best advice is to focus on documenting with another person in mind and consistency is key by sending yourself a deadline or number of articles to write per week.

I usually use Grammarly to help me to edit my articles.

The other way is signing up for courses like Simple Programmer's blogging course which I went through it twice to get better in my fundamentals.