Coming to this post, I am assuming you already have a blog or are considering the possibility of starting one. Before you go any further, I want you to take a second and ask yourself what is your purpose behind the creation of your technical blog. Maybe it is because you are knowledgeable on a topic and want to spread your wisdom. Maybe it is because you have finally solved a problem that you could not find the answer to and are looking to help the next guy. Maybe you want to put yourself out there to help your career. Or maybe you just want your voice to be heard.
The list goes on for great reasons to begin a technical blog EVEN IF you are only a novice developer. Personally, I began my technical blog as a way to continue to learn and contribute to the tech community.
Whatever the reason, it is vital to understand that where you post your blog will have a major impact on your goals.
Personally, I have been writing technical blog posts for the last 6 months or so on Medium. You can find that here! I love the possibility that my experiences put into writing can have a positive impact on somebody. However, as I have recently finished Flatiron School and entered the job hunt, I now realize that this blog can also have a positive affect on my career.
Prior to this, I had been publishing my blogs on Medium. However, looking back I realize that this may have been a mistake. Here are the reasons why I have decided to make the switch to the Dev.to community and also why I encourage you to do so as well.
Technical Specific Blogs
One of the first things that comes to mind and something I love about publishing on Dev.to is that your blogs are written using Markdown Here. There is just a bunch of added functionality that makes your technical posts look cleaner and make more sense. I don’t want to go into it too much, but being able to essentially write code that looks clean within your blog is super neat.
var s = "JavaScript syntax highlighting";
alert(s);
Also, the ability to Preview your post before publishing is awesome to see how it looks with the Markdown.
Here is a link to a Markdown Cheatsheet to help you out!
Community
While Medium and other sites may have some sense of community, I am yet to find a developer community stronger than Dev.to. From the interactions I have had with The Practical Dev and Ben Halpern on Twitter, to the weekly newsletter I receive from Jess with featured stories, those who run the community create an easy-going environment that is fun and helpful to engage with. On top of that, the contributions on Dev.to are relevant and topical. I cannot count how many times I have found inspiration or an answer to a problem I have always had by simply scrolling through the feed.
Learning
As web developers it is our job to constantly stay in the know. While I initially began my blog to take deeper dives into topics that I had already known about, since joining Dev.to, I have been introduced to thousands more I never would have heard of. Whether it is seeing simple headlines of articles, going through a popular contributors posts, or scrolling the comments sections there is always something to pick up.
The feed that is deployed on the Dev.to community will increase the chances of your blog reaching an audience rather than being buried in the archives of Medium. The more exposure that your posts get, the more likely you will be to achieve the goal you started out with.
Welcoming to All Levels
Unfortunately, there are plenty of communities, particularly in tech, that are not as welcoming to beginners. I couldn’t count the number of times I have seen harsh and discouraging comments on blogs or questions posted in forums and communities. Speaking from experience, the belittling feeling is not only embarrassing, but can make somebody just starting out want to quit.
The people at Dev.to do an amazing job at encouraging an environment for all skillsets, levels and minds. In doing so, they bring passionate and compassionate developers to their platform. I do not want to put words in anybody’s mouth, but I firmly believe that these are values that are held high and made priorities for the community.
Career Notice
As we discussed above, the Dev.to community feed is an amazing to place to see posts by developers from all over the world. Being an active member in the tight-knit community does not go unnoticed. I have seen/heard of multiple cases where developers have been networked through the community and even ended up making a career move through the Dev network.
User Experience
Last, but definitely not least I am a huge fan of the experience you get on the site. From the simplistic interface to all of the necessary features surrounding the feed the layout is clean, organized and easy to navigate.
One of my favorite features is that you have the option of adding tags for posts that you are interested in. This means that the majority of the content you are seeing will be on topics that interest you. Not only does this help you learn, but it also makes it easier to engage with the community and others to engage with you.
Conclusion
From my experience it is an amazing idea to start a blog no matter where you do it. However, all of the reasons above and more are why contributing to the Dev.to community will maximize the potential of your blog and get you closer to your own goals. Thank you for reading and keep on blogging! Godspeed.
Oldest comments (18)
Thank You! 🙏
Woohoo! Great to have you Ryan
Thanks for your article Ryan! I'm going through Flatiron's full stack course too and had created a separate blog (wordpress) about my coding stuff. Over the past couple weeks I starting wondering if I should just move it Dev.to, instead, because of the awesome community and potential to reach more people. I think your post has convinced me :)
Well written Ryan. You've raised a couple of good points(community, user experience, career notice) and it makes sense to focus on a blog that allows sharing with the right audience.
Medium has been particularly difficult at times especially when it comes to displaying things like code snippets in a way that's readable. I've ended up creating GitHub gists and linking to them, which takes extra time bouncing back and forth. Also submitting articles for publications can take a while before they see the light of day.
I'll be considering the switch a bit more in the coming months.
Nice article, Ryan, thanks for sharing!
I agree with your points, what brought me to blog on dev.to is the developer friendliness -it's really easy to work with markdown, especially for technical articles, as you point out-, and the community -one of the most friendly I've ever seen.
I also like that the site is very intuitive and easy to use, it has most of the features you'd want in a blogging platform, but it's not bloated with features that are hard to understand, have a high noise-to-value ratio, or condition the user behaviour too much (I especially dislike the kind of gamification that you can see in Stack Exchange, for instance, where the user behaviour is highly conditioned by earning reputation and badges, I hope to never see such things here).
Hey Ryan, that's a perfect description of The Practical Dev, and of reasons to blog about tech. Your post really inspired me.
Personally, I have my own blog because I like to have a canonical place for my content. That's not a problem, though, because one of the amazing features of dev.to is publishing from RSS. This way, I can manage my content but also share it with the community. That's yet another reason to love dev.to: they do not have the walled garden mentality of other platforms.
Anyway, I have to say this community is amazing and your post was a nice tribute to it. Thank you for it :)
You nailed it Ryan, nice post!
Awesome post!
I started off on Medium as well and I still post there, but I cross post everything here (there's a tool that imports everything automatically through the RSS feed from Medium).
I find that the dev.to posts get way more views than my Medium ones (usually about 10 times as much)!
Also, 🤜 🤛 Flatiron buds!
Yes!
I'm still waiting for a few more features before moving my posts here, to be on Medium pair at least, more exactly: pre publish comment reviews, highlights, gists/external code integration, sort search results by popularity and a few other goodies.
Nevertheless, dev.to profile is on my resume/CV :))
Thanks for writing this. I actually still keep my personal blog up. However, most of my writing starts on this platform and also appears there. I also keep up a medium blog as well. However, I find this platform far easier to write for.
I agree the dev.to community is awesome but honestly having your own domain/hosted blog (free on GitHub pages) is good if you want to blog.
I like the low barrier to entry Medium and dev.to give ♥️.
This truly an amazing place for developers. I still have my own blog because I want to own my content, but it’s markdown as well so no big deal. The community is diverse and just awesome. Whenever I post something on reddit, there is so much hate amongst some useful comments. In contrast to that, dev.to is like talking to friends, colleagues or family.
Is there a tool to move from medium to dev.to?
I found a Way:
dev.to/settings/publishing-from-rss
I know I'm offtopic but since I got the URL every day I can, I read here. I have really wanted to publish something but I am overwhelmed by the advanced level of the articles and I do not want to make a fool of myself. (Who would want?), I have asked a couple of questions and I have received my lesson. Thank you very much Dev.to !!!
Greetings from Cuba!
Of course! Start on some more beginner level topics and keep pushing yourself to look into the more advanced discussions!
Some comments may only be visible to logged-in visitors. Sign in to view all comments.