> Now, we need to be spending all of our time off, which if you work for a startup isn’t as much as you’d think, developing a blog
If you read my post, you'll see that I'm not advocating for that. I'm suggesting the bare minimum: "Start a blog. Post an interesting technical article to it once or twice a year—something you’ve learned, or a bug you’ve fixed, or a problem you’ve solved. After a few years stop bothering entirely, but leave the blog online somewhere."
The point of my piece is that you don't need to dedicate huge amounts of effort to doing this kind of work. Do a little bit, stick it online somewhere and it will still give you a huge benefit compared to other candidates who don't have any public evidence of their work.
I think what can be confusing to people who receive this advice at a time when they are already searching for a job, is that this is potentially a bit too late. If you publish something once or twice a year (like you suggest in the post) it all adds up and in a few years you have a body of work to present. If you're applying for a job next week there's not much you can do in this one week (although I've seen some exceptions to that too, where people did something cool and heroic in a few days to draw attention to what they have to offer before or while going for a job).
If you read my post, you'll see that I'm not advocating for that. I'm suggesting the bare minimum: "Start a blog. Post an interesting technical article to it once or twice a year—something you’ve learned, or a bug you’ve fixed, or a problem you’ve solved. After a few years stop bothering entirely, but leave the blog online somewhere."
The point of my piece is that you don't need to dedicate huge amounts of effort to doing this kind of work. Do a little bit, stick it online somewhere and it will still give you a huge benefit compared to other candidates who don't have any public evidence of their work.