Thanks. And no worries. Stil, I'm curious, why publish on dev.to if no aiming at a more general developer audience? Not least stuff already published ... what's the draw to republishing on dev.to? I'm just curious, and keen to understand. That's all. Not critical.
He is aiming at advanced Spring developers as target audience, dev.to is as good of a place for this as any other platform. Majority of posts here are for some specific target audience and not for general developer audience (apart from posts about architecture, most of posts are not for general audience). Tags are for denoting what kind of audience is this written for (java, kotlin, spring)
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.
Thanks for your detailed explanation.
The gist of my answer is: my point here is not to appeal to a broader audience. If you happen to be interested in the post, great, if not, great too 🙂
In all cases, I'm happy it made you look a bit more into the concepts I mention.
Thanks. And no worries. Stil, I'm curious, why publish on dev.to if no aiming at a more general developer audience? Not least stuff already published ... what's the draw to republishing on dev.to? I'm just curious, and keen to understand. That's all. Not critical.
He is aiming at advanced Spring developers as target audience, dev.to is as good of a place for this as any other platform. Majority of posts here are for some specific target audience and not for general developer audience (apart from posts about architecture, most of posts are not for general audience). Tags are for denoting what kind of audience is this written for (java, kotlin, spring)