Why I came over to dev.to

RMAG news

Since starting my career as a software engineer, I’ve also started to write development blog posts, to remind what I’ve done during work, and also thought it could be helpful when I decide to look over better opportunity.

Now more than 10 years has been passed. And during that time, I’ve changed my blogging platform several times(Blogger, WordPress, Medium, GitHub Pages, and more), for several reasons.

Until last year, I was using GitHub Pages as my blog platform. Well, it looks something cool as a developer, it can make design template as you want(as long as you have time and skill), and no limitation on registering Adsense.

But recently I’ve thought about why I’m trying to write posts spending my time. There are some profits from Adsense, but it is very small, enough to ignore if there’s other reason. And now, I’m starting to write my next post in dev.to. Here’s the reason.

Biggest reason: Deep dive into community

dev.to seems having vibrant and engaged community. In this platform, interaction with readers and other writers looks more genuine and collaborative. The platform fosters an environment where feedback is constructive, discussions are meaningful. These ambience makes it an ideal place for continuous learning and growth, and motivates like-minded people to join and communicates. This opportunity to build relationships is invaluable, and hard to find in other places.

Comfortable to write technical posts

dev.to is specifically designed with developers in mind. It excels in supporting technical content, so make it easier to share code snippets, tutorials. The platform’s markdown support is robust, and it integrates well with GitHub gists, making it a breeze to include code in your posts. Additionally, the audience here is more likely to be familiar with technical concepts. Which means, your content reaches readers who can fully appreciate and understand it.

Focus on writing

Because of comfortableness which I’ve described above, you can just focus on writing things you want, without thinking of installing, or make settings for your technical snippets.

Open Source Ethos

dev.to is built with an open-source mindset, which aligns with the values of many developers, including myself. The platform itself is open-source, meaning that anyone can contribute to its improvement. This transparency and inclusivity resonate with the principles of sharing knowledge and collaborating on projects that are so integral to the tech community. On Dev.to, you’re not just a user; you can be a contributor, helping to shape the very tool you’re using.

And now…

These are the features which makes me to start over my stories in dev.to. Well, I’m just on the starting line, and maybe I could find several disadvantages later.

But til than, I’m planning to write about my knowledge, challenges during work, and projects I’m working on.