DEV Community

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

Collapse
 
scrabill profile image
Shannon Crabill

Yup, I'm using Grammarly as my editor and it's saying 6-8 mins for a read time. I probably have more fluff than I need (clarifying that something can be done this way or that way, with code examples) but I do not see a logical split at this time either.

I'm doing a write up on finding the most common item in a has many through model association in Ruby.

A shorter version could be, this is the code you need, here's some quick points on what's happening, but that doesn't seem helpful. There are some small tangents that clarify what's happening within some functions (like .inject. It's sort of mysterious, so it felt important to explain what is doing what. I learned a lot in the process).

I could end is as is, and do a second post on implementing the method, what you can do with it, but that seems less relevant since the how/what would vary depending on someone else's app/model set up.

Collapse
 
helenanders26 profile image
Helen Anderson

Sounds like it makes sense to make it a long read. There's nothing wrong with that and it sounds like a great topic to cover all in one go.

Looking forward to reading your post :D