One solution would be to write the entire article in another application (e.g. Obsidian), and then publish it "serially" simply by copying and pasting the various sections.
I as a reader (and I think many on this site) follow different tags, and also other feeds (Medium, Hackernews, etc.), so I prefer to have shorter articles, which I can possibly pre-filter already from the content (functions in Kotlin already know them? Perfect, skip the article and wait for next).
If a reader is registered to your feed, they will be notified of each new article (maybe adding links to the series' articles, I often see it done here on dev.to). With a single article instead all updates to the article itself may not be notified to followers and be lost.
About the frequency of publication, I think it depends on your productivity: do you have many articles ready? Then publish them daily. Otherwise, you could keep some "backup" articles and publish them when you have little time to delve into other topics or the "writer’s block" hits you.
This is an example of an article "part of the series": you can see at the beginning of the article a sort of index/TOC that refers to all the articles in the series
I now write most of my articles first in hashnode (blog.derlin.ch) and then crosspost on dev.to. I like your approach, I may test it on the Kotlin article*s*, thank you!
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.
One solution would be to write the entire article in another application (e.g. Obsidian), and then publish it "serially" simply by copying and pasting the various sections.
I as a reader (and I think many on this site) follow different tags, and also other feeds (Medium, Hackernews, etc.), so I prefer to have shorter articles, which I can possibly pre-filter already from the content (functions in Kotlin already know them? Perfect, skip the article and wait for next).
If a reader is registered to your feed, they will be notified of each new article (maybe adding links to the series' articles, I often see it done here on dev.to). With a single article instead all updates to the article itself may not be notified to followers and be lost.
About the frequency of publication, I think it depends on your productivity: do you have many articles ready? Then publish them daily. Otherwise, you could keep some "backup" articles and publish them when you have little time to delve into other topics or the "writer’s block" hits you.
This is an example of an article "part of the series": you can see at the beginning of the article a sort of index/TOC that refers to all the articles in the series
I now write most of my articles first in hashnode (blog.derlin.ch) and then crosspost on dev.to. I like your approach, I may test it on the Kotlin article*s*, thank you!