I am quite baffled by the vibe of the comment section here.
The author explains why they do not feel like writing a technical blog, and those are (1) they have nothing interesting/new to say, (2) they are not a good programmer, and (3) it is not a good CV building.
I don't know about (1) and (2), but I respect the author's self-assessment, and I agree with (3), overall a technical blog is not a good CV builder, although there could be a confounder at play here, in the sense that who could write a popular tech blog is someone who has enough skills not be worried about having any other items to be added to the CV, like writing a blog.
But the general vibe is that somewhat the author is wrong in their self-assessment.
They should write for themselves and then publish or not publish—— similar to the love letter sent to the boy/girlfriend who dumped you that you should not send, but you should burn——or write for helping someone that in 3 years are gonna find themselves with the same problem, or that writing it down helps organize the scattered thoughts in one's mind (like people who are not writing those thoughts down are like pilgrims lost in the darkest night with no oil for their lamp) or they need a boost of confidence, because they surely have something to share.
And many are forgetting the opportunity cost: it takes time to write, and energy, and not getting any view is frustrating and maybe not a game one wants to play.
Like someone shared their thoughts on why they should not upload their salsa dancing on YT (they are not very good salsa dancers, they have nothing to teach, and nobody cares they salsa dance at Farmers Insurance where they work) and people started saying that no, you should upload to YT because maybe you are better than you think you are (why?), you may have some unique way of explaining the third step or whatever (really), it is the best way to find a romantic partner (and?) and who tells you that your skip-level manager at Farmers has a daughter who dances competitively and you may find through a common passion and through the grapevine of family a better connection with "leaders", which could give you an increase of 1k per year (before taxes)?
I, after having read the blog post and coming from a perspective of respect of the author, agree they should not write a technical blog. I don't see any reason for now, tomorrow who knows.
Author at some level would like to blog ("I would love to follow the steps of my idols") but then finds reasons to rationalize a priori why it's not worth it.
These reasons might be valid and it's perfectly fine to drop this arbitrary goal and to go pursue something else. But I think that's not necessarily easier to do, it's difficult to control what we are drawn to. And deciding what to do based on a self-assessment about your chances of success is just one heuristic from many others. Welcoming serendipity and knowing you'll get better at it should be considered too. As Steve Job said, "You can't connect the dots looking forward; you can only connect them looking backwards."
This blog post also reads like wanting the benefits of the outcome without the risk of "failing" or the efforts of the process. I'd argue there are only upsides to trying: so little to lose VS. so much to gain. You get to choose when to stop trying, worst-case scenario is having wasted time exploring some things that were interesting to you anyway.
The author explains why they do not feel like writing a technical blog, and those are (1) they have nothing interesting/new to say, (2) they are not a good programmer, and (3) it is not a good CV building.
I don't know about (1) and (2), but I respect the author's self-assessment, and I agree with (3), overall a technical blog is not a good CV builder, although there could be a confounder at play here, in the sense that who could write a popular tech blog is someone who has enough skills not be worried about having any other items to be added to the CV, like writing a blog.
But the general vibe is that somewhat the author is wrong in their self-assessment. They should write for themselves and then publish or not publish—— similar to the love letter sent to the boy/girlfriend who dumped you that you should not send, but you should burn——or write for helping someone that in 3 years are gonna find themselves with the same problem, or that writing it down helps organize the scattered thoughts in one's mind (like people who are not writing those thoughts down are like pilgrims lost in the darkest night with no oil for their lamp) or they need a boost of confidence, because they surely have something to share. And many are forgetting the opportunity cost: it takes time to write, and energy, and not getting any view is frustrating and maybe not a game one wants to play.
Like someone shared their thoughts on why they should not upload their salsa dancing on YT (they are not very good salsa dancers, they have nothing to teach, and nobody cares they salsa dance at Farmers Insurance where they work) and people started saying that no, you should upload to YT because maybe you are better than you think you are (why?), you may have some unique way of explaining the third step or whatever (really), it is the best way to find a romantic partner (and?) and who tells you that your skip-level manager at Farmers has a daughter who dances competitively and you may find through a common passion and through the grapevine of family a better connection with "leaders", which could give you an increase of 1k per year (before taxes)?
I, after having read the blog post and coming from a perspective of respect of the author, agree they should not write a technical blog. I don't see any reason for now, tomorrow who knows.