What a night & day difference between Claude Sonnet 4.5 and Opus 4.5 models. The latter is much more effective at working through my MCP connection to Craft. But boy this baby consumes a lof of credits. 😅

I’m trying something new this year for my year-in-review blog post. Using all my monthly post digests stored in Craft1, I’m using ChatGPT to look at those digests, take into account last year’s year-in-review article, plus this year’s document personal milestones to suggest ideas. This is now possible because Craft now supports MCP. Using the best ChatGPT models, I get a lot of material to consider but somehow I feel this is really overwhelming. I should be more directive like limiting the number of possible scenarios, their length, etc. I’m still exploring this workflow.

  1. I subscribe to my own blog post digest newsletter for archival purposed. ↩︎

Time to renew Kagi Search. I’m on the starter tier. Upon examination, I’m doing about 45 searches per month. The trend is decreasing. I use their Article Summarizer on the iPad and iPhone much more often. I want to support them because I believe we need diversity when it comes to searching the web. But it’s not cheap, and my search requests trend is going downward, thanks to AI. Decisions, decisions, decisions. Any Kagi users in the room?

I always feel like I’m losing the time-saving benefits if I spend time improving an automation (an Apple Shortcut, for example). 🤦🏻‍♂️

Thinking out loud here: one way Apple could retain more talent could be to start innovating again, maybe? 1

  1. Recent departures to OpenAI, a company working on a new class of devices might doing just that: trying to innovate for real. ↩︎

I spent the last few days putting together a workflow to help me write those year-in-review articles. As we get closer to the end of the year, it’s the right time to start working on this. I documented my workflow in this Craft document and submitted to the #winter_challenge on Slack. Hint: my first real use case for MCP.

On Tony Fadell For Apple's New CEO

Parker Ortolani on taking a chance of Tony Fadell to replace Tim Cook. At first, Tony Fadell seems like the obvious candidate, but I worry that we may be under the spell of a certain nostalgia in thinking he would be the perfect choice, as Parker points out. The world is no longer what it was in the days of Steve Jobs and his close collaborators. Apple is no longer what it once was either, and that is partly what many people criticize the company for. John Ternus is a product engineer, not a designer, and putting design back at the center of the process as it was in the Steve Jobs era may be a more restorative idea—and in that sense, yes, perhaps Fadell would be a good choice.