It takes me 2 hours.
I am not joking. Usually, I don't have it "planned" before I started to write. Sometimes I do when it comes to technical related topics, but anything usually comes down to me jotting it down on dev.to and refining it from there.
When it comes to writing anything but technical, I tend to have an idea of what I want to write during the weekend, but nothing written down. I just hope I remember it in a couple days. If not, oh well I figured something out lol.
For curiosity, in this case, I decide to write this piece since @ben release some news on AI Disclosure for dev.to. It gave me a thought: "How long yall have taken to write one dev.to article?"
For Technical topics, I do write things down during the week. For example, on my article on "Git Gud", I write a list of git commands I tend to use more often on a sticky note. Then, I documented it on dev.to and go from there. This is more of a straightforward example, but overall, it takes me a week to have a technical piece finished. Compare to anything but technical piece, it's 2 hours lol.
Sometimes, I refined my article by me re-reading it (just like right now) or have my friend peer review it. My friend enjoys what I have written on dev.to and probably will join, even though he is not a tech person.
I don't use AI on my writing (as mention many times before), mainly because I want to improve on my writing and not falling into the habit of relying on AI tools. Trying to get out of the habit as a developer since I have notice I used AI more than I should for learning sake.
How long does it take for you?
I am curious since I notice some people publish everyday or once a while. I am wondering about your process of writing an article on dev.to and how long it takes you? Would love to hear your experience and your thoughts about the use of AI to help you on the process!
As a side note, this took me 40 mins to write this whole thing out, including finding images for this post lol.
