I made two important changes this morning for my automation-related operating environment:
My first bad experience: the code generated by Claude Code made my dashboard unresponsive in my browser. Eventually, the data stopped updating. After a ten-minute debugging session, I asked Claude Code to revert the change, and it did so promptly. But then I started getting execution failure notices on Discord. A lot of notifications. Then I started investigating…
It appears the browser was making frequent refresh requests to one of my workflows, which depleted my Claude pay-per-use credits. Bummber. Looking at my n8n dashboard, I saw that one of my workflows was failing because of that. Logs were confirming the problem with the interaction with Claude AI. As shown on the graphs below, my instance CPU usage went through the roof. Ouch. Now I know what happened, and the problem was fixed. Now, I should find a way to rate-limit this type of behaviour. That’s for tomorrow, I guess. 😅
Ten days into 2026, I have achieved much more than I anticipated. If I maintain this pace, I will complete my list of wild ideas soon. It’s not just about checking items off the list, but also about learning a lot along the way. It’s very fulfilling.
I’m making good progress on my personal dashboard idea. While people may criticize LLMs and enjoy coding for fun, for me, it opens up possibilities I couldn’t have imagined before.
One of the frustrating aspects of LLMs is their lack of consistency unless you develop specific skills, which can take time to implement effectively. For example, I wanted to generate documentation for my most recent n8n automation workflow, but Claude was unable to do it, and I can’t remember the prompt that finally made it possible. I should have saved it somewhere for easy retrieval. I’m wasting precious credits. 🤦🏻♂️
Simon Willison on AI-assisted programming:
The more time I spend on AI-assisted programming the less afraid I am for my job, because it turns out building software - especially at the rate it’s now possible to build - still requires enormous skill, experience and depth of understanding.
Changes from the last edition are in bold. ✉️ Mail Client: Fastmail 📨 Mail Server: Fastmail 📝 Notes: Craft + Apple Notes ✅ To-Do: Things 3 📷 iPhone Photo Shooting: Camera.app 📚 Photo Management: Photos.app + Photomator 🗓️ Calendar: Calendar.app 🗄️ Cloud file storage: iCloud 📰 RSS: Reeder connected to Inoreader 📇 Contacts: Contacts 🕸️ Browser: Mobile Safari + ARC Browser on Mac + ChatGPT Atlas 🧠 AI: ChatGPT + Claude AI 🔎 Search: Kagi Search 💬 Chat: iMessage (WhatsApp when abroad) 🔖 Bookmarks: AnyBox 👓 Read It Later: Inoreader 📜 Word Processing: Ulysses, Craft 📊 Spreadsheets: Numbers 🛝 Presentations: Keynote 🛒 Shopping Lists: Reminders 🧑🍳 Meal Planning: None 💰 Budgeting & Personal Finance: Numbers 🗞️ News: La Presse (Apple News for English news) 🎶 Music: Apple Music 🎧 Podcasts: Apple Podcasts 🔐 Password Management: iCloud Keychain & Apple Passwords 👨🏻💻 Blog hosting: Ghost, Micro.blog, Scribbles.page 🌐 Web Services: Cloudflare, Chillidog Hosting, DigitalOcean
In today’s world, with LLM, Claude Code, etc., is Apple’s Swift Playground still relevant, even for younger aspiring coders? A few years ago, it seems we were hearing much more about it than today.
I’m building a Dashboard. 😎
Apparently, people are barely using Stack Overflow to ask questions, thanks to LLMs and AI. I expect a similar trend among people in a community like this one on Micro.blog. Some questions would be super easy to answer by asking ChatGPT or the like. I do understand that many people still want this human touch, though.
