I generally aim for around a "three minute read" divided into four to five paragraphs, an intro and conclusion. People like to skim over a post so I aim for bite-sized posts.
Any more than that and I consider splitting it into multiple posts. Sometimes this makes sense, other times it doesn't but that's what I aim for. This sometimes makes a nice series that I can post over a few weeks and build on.
I use this tool (wordcounter.net/) to get an idea of my reading time and other stats. Looks like 1600 is a six minute read. I'd consider dividing it into two but it completely depends on the content. My last post was an eight minute read but there was no logic split point so I left it as it was.
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.
Great topic!
I generally aim for around a "three minute read" divided into four to five paragraphs, an intro and conclusion. People like to skim over a post so I aim for bite-sized posts.
Any more than that and I consider splitting it into multiple posts. Sometimes this makes sense, other times it doesn't but that's what I aim for. This sometimes makes a nice series that I can post over a few weeks and build on.
I use this tool (wordcounter.net/) to get an idea of my reading time and other stats. Looks like 1600 is a six minute read. I'd consider dividing it into two but it completely depends on the content. My last post was an eight minute read but there was no logic split point so I left it as it was.
What are your thoughts Shannon?
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.
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