I will add a +1 to your recommendation as well, his blog has been my favourite way to keep up with the AI landscape over the last 18 months. Just the right level of detail and technical depth for me
I will add a +1 to your recommendation as well, his blog has been my favourite way to keep up with the AI landscape over the last 18 months. Just the right level of detail and technical depth for me
I can write fast because I've been writing online for so long. Most short posts take about ten minutes, longer form stuff usually takes one or two hours.
I also deliberately lower my standards for blogging - I often skip conclusions, and I'll publish a piece when I'm still not happy with it (provided I've satisfied myself with the fact checking side of things - I won't dash something out if I'm not certain it's true, at least to the best of my ability.)
I'm hoping to improve my overall balance a lot for 2025. Deliberately ending my at least one post a day blogging streak is part of that: https://simonwillison.net/2025/Jan/2/ending-a-year-long-post...
The writing, I understand - you do it relatively quickly because of a lot of practice. But I feel like just reading up on the AI news every week takes up a significant amount of time - time that can't be spent researching/building things.
I'm wondering how you balance that.
I've managed to balance building vs writing a lot better in the past - I lost that balance in November and December, I'm trying to get it back for January.
Having some kind of standard "I need to integrate this new thing with an existing codebase" makes a great standard project.