DEV Community

Cover image for What I learned from writing 30 articles in a row

What I learned from writing 30 articles in a row

Steeve on May 13, 2024

This article finishes my challenge of 30 articles in 30 days... however due to unexpected life events, it took me two months to finish. The goal ...
Collapse
 
steeve profile image
Steeve

My face when I finished writing the 30th article
Image description

Collapse
 
michaeltharrington profile image
Michael Tharrington

Lol! This is made me smile... not unlike the look on this uhhh... cat?

Collapse
 
steeve profile image
Steeve

Ahahah, from the prompt, it should be a "cute animal", probably it's a mix of cat and mice

Collapse
 
jaloplo profile image
Jaime López

A lot of good advice here!!! Thanks for sharing them with the community.

Collapse
 
steeve profile image
Steeve

Thank you @jaloplo 🍻 I hope it's going to help and motivate the DEV community :D

Collapse
 
shricodev profile image
Shrijal Acharya
  1. Prepare the article title and the image cover before writing.

This is so true. I can't even start writing without building the cover image. I don't know why, tbh. 🤷

Collapse
 
jisan profile image
Jisan Mia • Edited

Hey @steeve, you just inspired me to publish my first article on DEV. I'm writing to finish it now.

Collapse
 
steeve profile image
Steeve

Bonjour @jisan 👋 I'm super grateful that it inspired you, that's what I'm living for! The writing journey is not easy, but in long term it is worth it. Let's make the best article you're proud of to help people :D I'm following you to read your future posts ;) Gogogo 🔥

Collapse
 
jisan profile image
Jisan Mia

Here you go @steeve, I just published my first article on DEV, I've been trying to finish writing this article for a long time and publish it here. But my feelings on "my article is not good enough" kept me not finishing/publishing it.

Done is better than perfect This line from your article hooked me up to finish that article and publish it here...

Article link: dev.to/jisan/20-dom-projects-your-...

You're awesome @steeve , thanks for inspiring me

Collapse
 
caillef profile image
Corentin CAILLEAUD

Congrats for this challenge 👏 DEV.to definitely needs more people like you!

Collapse
 
steeve profile image
Steeve

Thank you @caillef 🤲

Collapse
 
masteing_the_code profile image
Joel Jose • Edited

Now that's a jar full of motivation.⚡

Collapse
 
tecno-security profile image
TECNO Security

It is a great article for me, I will follow your new article!

Collapse
 
steeve profile image
Steeve

Thank you @tecno-security for your support 🙏

Collapse
 
artu_hnrq profile image
Arthur Henrique

Hey, it will help me on. Thanks

Collapse
 
steeve profile image
Steeve

You are welcome Arthur, let’s crush it 🚀

Collapse
 
dilhancodes profile image
dilhancodes.dev

Yes ,

Prepare your cover image and Headline . Before Writing

thats very important.

Collapse
 
steeve profile image
Steeve

Exactly, as soon as you get the headline, it gives you clarity on the article structure and focus

Collapse
 
fsbalbuena profile image
Fede Balbuena

thanks man

Collapse
 
steeve profile image
Steeve

You are welcome @fsbalbuena 🍻

Collapse
 
prakirth profile image
Prakirth Govardhanam

I am using your tips for my first post on DEV. Hope I get it right. Thanks a lot @steeve ! 😊

Collapse
 
steeve profile image
Steeve

Thank you @prakirth 🤲 Keep writing and experimenting 💪 that's the way you're gonna rock

Collapse
 
aungthuoo profile image
Aung Thu Oo

Thank you so much for your experiences sharing. This article allow me to get much more ideas and energy.

Collapse
 
steeve profile image
Steeve

You are welcome @aungthuoo !! Get started with something simple you already master, and feel free to share the article link here as comment, I'll take a look :D 🍻 Cheers!

Collapse
 
jojomondag profile image
Josef Nobach

Great read thx!

Collapse
 
steeve profile image
Steeve

Thank you Josef 🍻

Collapse
 
primofin profile image
Vy Nguyen Thanh

Thanks for the tips @steeve. What would you advice early-stage developers to write about?

Collapse
 
steeve profile image
Steeve

You can write about:

  • What you are learning
  • What you have mastered
  • Documenting projects
  • Reviewing frameworks/languages/patterns
  • Share your coding challenge, and ask how you can improve it
  • Interview preparation, or advises for a good job as junior dev And hundreds of subjects !

You are welcome @vynmetropolia, and keep being curious, experiment, create things and share it (On DEV for instance)! It's going to bring you a lot of value

Collapse
 
amartinez profile image
Andres Martinez Cano

Nice post, thank you for sharing those lessons 🙏🏼

Although I don't write as much as I'd like (I mostly act as a reviewer where I work), I would like to add a tip that I usually suggest:

Take a step back and read what you have written, as you progress writing your post.
I think that can help you get a sense of how the experience of reading your post is so far, and how the ideas are flowing.

Again, nice work with this post.
PS: For what it's worth, I saw your post on Daily dev and left a comment there first 🙈

Collapse
 
luciandev profile image
Lucian DEV

Nice work🥳 Thanks man!✌️

Collapse
 
steeve profile image
Steeve

Thank you Lucian 🏄✌️

Collapse
 
dariuszparys profile image
Dariusz Parys

It would be interesting to know how much time you invest per post. Maybe there is a correlation between writing more often and reduced invest of time. Do you have maybe some numbers to share?

Collapse
 
steeve profile image
Steeve

Hello @dariuszparys and thanks for your interesting questions:

  • On average 1h30 per article for the writing, image banner, and two revision max.
  • For technical article +3h: Most of the time is spent at preparing a clean code on Github to reproduce easily, and preparing diagram for explaining visually.

I've noticed that the article I've spent the most time on is the one that generates the most engagement and views.