You can do it like this:

Why? Because writing on dev.to suggests some important things about you to potential employers:

You do more than the bare minimum - you're thoughtful about your work.

You enjoy sharing knowledge. When you change jobs, you probably leave documentation behind for the person who will take your place.

You're a good writer. If you ask me, technical writing is 2018's most undervalued skill for software developers. Communication is at least half of what we do, and with remote work growing in popularity, writing clearly is becoming essential throughout the industry.

You're part of a large and active professional community. This is a force multiplier when you're working on obscure scaling problems or difficult bugs.

You might be shy about including this on your resume because you haven't gotten a hundred ❤️s or been mentioned in the dev.to newsletter. Don't worry about it. Some of the most useful and well-written posts I've seen on this site never got a lot of attention. But they helped me when I needed them, and that counts for a lot.

Oh, and while you're at it, do you have a GitHub #graveyard? Add that too. You're doing cool stuff. Make sure people know it.