Just wait until they discover “plan” mode and subagents.
08.03.2026 18:41
👍 3
🔁 0
💬 0
📌 0
Just wait until they discover “plan” mode and subagents.
alphabetizi.ng
But where do you put Tom Petty? What about Tom Petty and the Heartbreakers?
www.subaud.io/teaching-cla...
What started out as a fairly simple thought experiment has really changed the way I think about creating READMEs and other documentation for deploying projects and samples. I will likely be adding Claude Code skills to all of my projects going forward.
I created an entire state machine with UI, error handling, branching, parallel paths in ~month. I replaced it all with Claude Code skills in an afternoon. And it's better.
That looks like the making of a great setup. Thinking about doing something like this myself.
pup in her favorite dirt box
I thought you were posting pictures of my pup for a second. She gives me the same look. Usually when it's time to eat.
Spectacular
MEGAN KELLER WITH A DIRTY DRAG MOVE AND A GOLD MEDAL WINNING GOAL 🇺🇸 🇺🇸 🇺🇸 🇺🇸
This is the one I keep thinking about and don't have an answer to. Right now I'm just building stuff for me. Which is fine, but probably inefficient. But my app works exactly the way I want it to.
I like how there are two "not bad" shots in curling. One that is absolutely amazing. And one that is pretty bad. #WinterOlympics #Curling
7 miles in 25 minutes is all out sprinting.
I’ve been liking it so far. Using it through Open Code and everything is so much faster (hosting on a P5en with no users so that might help)
I accidentally filled ~200GB with cdk out artifacts the other day. Lots of things broke when I ran out of space doing that.
I just added a jetpack to my work and it’s completely changed how I work. Since last week. At least doubled (an already incredible pace)
Claude fired up Python to write a script to help parse it. “How did you know it was going to write Python?”
She had hours of work done in fifteen minutes and is completely hooked now.
I was getting a non dev set up with Claude Code. Installing all sorts of things with her. Told her to install Python. “But I don’t know Python”. “ Don’t worry, Claude does”. Ten minutes later we were getting started with CC on a CSV she was working on.
www.subaud.io/plex-collect...
www.subaud.io/orchestratin...
Finally managed to put together the follow up articles on some of the details of how the Plex Collection Creator works. Code is still all out there on GitHub. These are just some of the more detailed explanations about how it works.
Tried explaining to someone that Claude knows git way better than they do. Not sure they believed me.
For the UX piece, giving it access to "see" it with Playwright helps tremendously. It fixes things I didn't know were wrong. But then when I look at the new UX, it is clearly better. It's wild.
COULD YOU UM WORK ANY HARDER THAN THIS? Homer asking his workers to work harder.
Half the time when I'm finishing up on some UI (that I am terrible at) I'll ask Claude to "make it better".
"Sure thing boss"
Basically every software engineer in my life is obsessed with Claude Code and loves it and say it feels like an absolute step change, and these are people who've been coding for 30 years.
It was right. I gave up and removed it for good.
I created a pipeline for something similar. I had probably had an easier time with some good metadata to work with, but it was grouping reasonably well at the end.
github.com/schuettc/ple...
I’ve got one where it keeps suggesting I just remove a component because it intermittently fails and can’t really be worked around. I keep arguing with it trying to find a workaround. I’m pretty sure it’s right and I do just need to remove it :(
I think one of the most important aspects of using things like Claude Code is finding something that works for you. So far, this is working well for me. It will likely change in a few weeks when something new drops.
Besides the technical aspect of not polluting context, I've found this helps me focus on shipping meaningful improvements rather than getting lost in a maze of half finished changes. It's all set up and ready to work with multiple developers working on the same project at the same time.
It lets me easily capture bug fixes, new features, enhancements, tech debt, etc. all without disrupting my flow. Then, when I'm ready to implement, all of my notes and thoughts are ready to go.
Final holiday project wrap up. The more I work with Claude Code, the more I find myself creating different processes and workflows. Things are changing constantly and quickly but I've been very happy with this workflow so far.
www.subaud.io/building-a-h...
I've been consciously trying to do more retweeting of folks with Good And Thoughtful Takes around AI and the like lately, so here's a starter-pack thing I'll definitely not forget to keep updated later 🫡
It's always this.
