I organize posts as series but I don't actually plan. It is more like me saying to myself "hey these posts relate to each other." There may be several weeks or even months between 2 posts in one of my series. Once in a while 2 posts in a row may end up in same series, in which case I may write as if it was on purpose.
One potential benefit to how I use series is that a new post may draw readers to the old related posts.
From reading perspective, it depends on how long a long article is. It also depends on whether the author is someone I've read before. I mostly browse DEV in the morning while drinking tea or coffee and in evening drinking tea. So I tend to shy away from longer articles. My attention span at those times isn't up to it. But if written by someone I've read often, and if on topic I'm interested in, then I am at least somewhat more willing to read a long post than if author is someone I've never read.
I must admit the planning is the part I find daring with Series, but your comment makes me realise all doesn't need to be perfectly planned, I should have a try and see.
Another point with Series is, I fear I will want to amend part (if not all) of the previous articles when I start writing a new one on the same subject, and I usually try to avoid editing an article once it is live. One big article written in one go is easier. What is your politic on this? Do you often amend your articles?
I haven't amended many times. When I do, it is mainly to fix a mistake. One example I can think of was when I realized I left out a step in an example GitHub Actions workflow demonstrating how to use an Action I maintain. Most of the times when I edit, it is usually not long after posting it to begin with. Reading it again and realizing I said something poorly. Or discovering a typo. I try not to go back and read older ones or else I'll drive myself nuts fixing things. If an example becomes obsolete because something changed in a library, etc, I'd rather just write something new than to continually update the old (maybe the old version is still useful to someone).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I organize posts as series but I don't actually plan. It is more like me saying to myself "hey these posts relate to each other." There may be several weeks or even months between 2 posts in one of my series. Once in a while 2 posts in a row may end up in same series, in which case I may write as if it was on purpose.
One potential benefit to how I use series is that a new post may draw readers to the old related posts.
From reading perspective, it depends on how long a long article is. It also depends on whether the author is someone I've read before. I mostly browse DEV in the morning while drinking tea or coffee and in evening drinking tea. So I tend to shy away from longer articles. My attention span at those times isn't up to it. But if written by someone I've read often, and if on topic I'm interested in, then I am at least somewhat more willing to read a long post than if author is someone I've never read.
thank you for taking the time!
I must admit the planning is the part I find daring with Series, but your comment makes me realise all doesn't need to be perfectly planned, I should have a try and see.
Another point with Series is, I fear I will want to amend part (if not all) of the previous articles when I start writing a new one on the same subject, and I usually try to avoid editing an article once it is live. One big article written in one go is easier. What is your politic on this? Do you often amend your articles?
I haven't amended many times. When I do, it is mainly to fix a mistake. One example I can think of was when I realized I left out a step in an example GitHub Actions workflow demonstrating how to use an Action I maintain. Most of the times when I edit, it is usually not long after posting it to begin with. Reading it again and realizing I said something poorly. Or discovering a typo. I try not to go back and read older ones or else I'll drive myself nuts fixing things. If an example becomes obsolete because something changed in a library, etc, I'd rather just write something new than to continually update the old (maybe the old version is still useful to someone).