After reading so much content over the year (since dev.to was created), what, in your opinion, makes for a good technical blog post? What are the characteristics of strong technical writing? Are there any patterns or themes that you've seen emerge in the blog posts that you've enjoyed the most or learn a lot from?
Firstly, I think variety in styles and goals is ideal, so characteristics can vary, but here are a few thoughts:
I'm really not sure I expressed everything perfectly here, but that's what comes to mind. Thanks for the great question.
I see Dev.to mostly publishing technical posts (frameworks, concepts, techniques, etc.), but I've also seen a few of the "Programmer Life" type posts (burnout, mentoring, etc.).
Is there a particular mix of the two you're looking for? Do you want the submissions to be heavier on the technical or is it more dependent on what the community is offering?
I ask as a not entirely disinterested party - if it's the sort of thing you'd like to see, I'd like to submit a more tightly written summation of a blog series I recently started.
Think of the audience as programmers (as opposed to "tech" like startups and venture capitalists and that sort of thing) but otherwise posts do not really have to be technical at all as long as they might help someone. I wrote a post about fitness which really didn't have anything to do with code, but was directed at programmers and the things we deal with in our careers/life.
So I'd say the technical/non-tech isn't as important as knowing the audience. If you are an experienced programmer with a story to tell, it's definitely appropriate. Just use titles that express the value of the post.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.