I agree with all points, but what if you simply don't have the time (or even the energy) for blogging? Basically I agree with you that blogging is a great idea, however I disagree with you if you say "ALL programmers should blog" (but, you didn't say that, at least not literally).
👋 Hey there, I am Waylon Walker
I am a Husband, Father of two beautiful children, Senior Python Developer currently working in the Data Engineering platform space. I am a continuous learner, and sha
No need to daily blog or make your posts super long and in depth. They can be something like notes to your future self on something you just learned that you may forget. Something you had to learn on your own becuase there were no blog posts about it. When he says everyone should blog it doesn't mean that everyone should call themselves a blogger or influencer. I think having just a couple well done blog posts (does not need to be long) can go a long way in showing your communication skills on a resume.
My goal is to make useful and helpful advice and content that will help others!
New content everyday, please leave feedback if there is something you want to see!
If you check out my video, you'll see that I too felt I didn't have time, but when i wrote down my schedule for the day, I found that a good 3-4 hours each day was spent... well, almost wasted away. It's fine to have a balance of time and enjoyment, but I optimised my day a bit more, and found I was more productive and spent less time learning when I wrote it out, if anything, blogging can help you save time!
True, agree to all of that! A lot of time goes wasted unproductively, that goes for most people, myself included ... I think once you're into a flow with a certain structure and rhythm then this will go naturally.
You do have the time. You're already documenting your work (comments, e-mails, actual documentation, commit messages, and so forth) and telling people about what's going on. Blogging isn't much different. What you might lack is the discipline to publish it where you and other people can find what you've written. But you get that discipline through practice.
My blog isn't entirely technical (I'm over halfway through my career, so I have other priorities), but every Monday is a "developer journal" going through the things I've been working on (sometimes with code samples), and when I've learned something, my notes become a Wednesday post. An occasional other post is sparked from conversation on sites like this.
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 agree with all points, but what if you simply don't have the time (or even the energy) for blogging? Basically I agree with you that blogging is a great idea, however I disagree with you if you say "ALL programmers should blog" (but, you didn't say that, at least not literally).
No need to daily blog or make your posts super long and in depth. They can be something like notes to your future self on something you just learned that you may forget. Something you had to learn on your own becuase there were no blog posts about it. When he says everyone should blog it doesn't mean that everyone should call themselves a blogger or influencer. I think having just a couple well done blog posts (does not need to be long) can go a long way in showing your communication skills on a resume.
I get your point, you're right, agree to all that ...
I usually post my readme as a blog
or vice versa
If you check out my video, you'll see that I too felt I didn't have time, but when i wrote down my schedule for the day, I found that a good 3-4 hours each day was spent... well, almost wasted away. It's fine to have a balance of time and enjoyment, but I optimised my day a bit more, and found I was more productive and spent less time learning when I wrote it out, if anything, blogging can help you save time!
True, agree to all of that! A lot of time goes wasted unproductively, that goes for most people, myself included ... I think once you're into a flow with a certain structure and rhythm then this will go naturally.
You do have the time. You're already documenting your work (comments, e-mails, actual documentation, commit messages, and so forth) and telling people about what's going on. Blogging isn't much different. What you might lack is the discipline to publish it where you and other people can find what you've written. But you get that discipline through practice.
My blog isn't entirely technical (I'm over halfway through my career, so I have other priorities), but every Monday is a "developer journal" going through the things I've been working on (sometimes with code samples), and when I've learned something, my notes become a Wednesday post. An occasional other post is sparked from conversation on sites like this.