I kind of feel like as a human, I like reading a good blog post explaining something interesting. Can be a tutorial or just "something challenging". That helps me understand a concept, or build a mental abstraction.
I can also point an LLM to such a good blog post as a resource ("I want you do to X the way it's described in this post").
Sadly, though, I feel like people are less and less motivated to actually read the blog post. They will ask the LLM to summarise the good blog post, which may not be so constructive. Or will just completely ignore it. And if you are not used to reading good blog posts, how do you make the difference between a good one and AI slop?
A third reason I was writing blog posts was that I thought it was a portfolio. When applying for a job, I could point the employer to my open source code and to my blog, and they could judge me based on actual stuff I produced. My experience is that nobody cares: they will redirect you to their vibe-coded leetcode goddamn tool and check if you can invert a BSP in less than 4 minutes.
I have failed interviews in companies that build software on top of a library I wrote because a junior felt I was not good enough at leetcoding. Fun fact: the junior in question obviously wasn't better than me: they just had read the solution before the interview so they could feel like they knew better.
Interesting insights.
I kind of feel like as a human, I like reading a good blog post explaining something interesting. Can be a tutorial or just "something challenging". That helps me understand a concept, or build a mental abstraction.
I can also point an LLM to such a good blog post as a resource ("I want you do to X the way it's described in this post").
Sadly, though, I feel like people are less and less motivated to actually read the blog post. They will ask the LLM to summarise the good blog post, which may not be so constructive. Or will just completely ignore it. And if you are not used to reading good blog posts, how do you make the difference between a good one and AI slop?
A third reason I was writing blog posts was that I thought it was a portfolio. When applying for a job, I could point the employer to my open source code and to my blog, and they could judge me based on actual stuff I produced. My experience is that nobody cares: they will redirect you to their vibe-coded leetcode goddamn tool and check if you can invert a BSP in less than 4 minutes.
I have failed interviews in companies that build software on top of a library I wrote because a junior felt I was not good enough at leetcoding. Fun fact: the junior in question obviously wasn't better than me: they just had read the solution before the interview so they could feel like they knew better.