I've been thinking the same way about myself here in dev.to.
Other than time constraints, what mostly keeps me from posting more often is that I tend to criticize what I'm about to post before doing it, to the point I end up either deleting or never finishing an article. Which I believe comes from thinking that maybe what I might be writing about isn't really that important to others.
So I recently decided to write about small things I learn along the way during my work hours and weekends to sort of "solidify" my knowledge about them.
That feels very close to home! Like I mentioned in my previous reply, I always tend to go in to deep. I start rubber ducking my problems and before you know it I'm writing a damn book while I just wanted to show-off how to do some fun stuff. Maybe I should keep things smaller and more precise indeed. Thanks for your suggestion!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've been thinking the same way about myself here in dev.to.
Other than time constraints, what mostly keeps me from posting more often is that I tend to criticize what I'm about to post before doing it, to the point I end up either deleting or never finishing an article. Which I believe comes from thinking that maybe what I might be writing about isn't really that important to others.
So I recently decided to write about small things I learn along the way during my work hours and weekends to sort of "solidify" my knowledge about them.
That feels very close to home! Like I mentioned in my previous reply, I always tend to go in to deep. I start rubber ducking my problems and before you know it I'm writing a damn book while I just wanted to show-off how to do some fun stuff. Maybe I should keep things smaller and more precise indeed. Thanks for your suggestion!