those were precious super el niño years
this one is shaping up to be uh, especially super, though
3cats
@rachel.supply
480 followers 1.2K following 2.8K posts
firmware engineer likes: photo, rustlang, meshtastic, books of color swatches dislikes: the neverending search for frutiger retro Sony Style aesthetic 31 she/her fox boston glass.photo/3cats signal: threecats.14
![Screenshot of https://news.ycombinator.com/item?id=49850929
> [I work on Claude Code] I broadly agree with the author’s point: plan mode was useful, and is no longer useful.
In Claude Code, all plan mode does is add a little reminder to every user message along the lines of “you’re in plan mode, please don’t code yet”. It’s something I came up with late on a Sunday night many months ago, when I got tired of asking Claude to plan with me first before coding in each new session. Something people might not realize is plan mode has always been a prompt — it has never changed the toolset because doing so would break the prompt cache, and so would be expensive for users.
This worked well for a while, until a few months ago, using early versions of Fable, I realized that I wasn’t using plan mode anymore because the model just got it, and because for the increasingly complex work I asked the model to do, planning had become interactive and iterative. With Opus 5.5, I feel Opus has gotten to that point too.
For codebase understanding, I sometimes ask Claude to generate an artifact that explains some aspect of its changes. For complex diffs to core parts of the system, I will often ask it to make diagrams or even interactive demos so I can better understand the change and alternatives considered. I don’t do this very often, but it’s a useful way to explain code when you need it. I ask Claude to attach these artifacts to its PRs also, so others can understand and future Claudes have the context.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:mxru2537dtgh4lbrodvsj7sx/bafkreif7ncv45oadg2cqdwllbqfu62opdy7xqqeios4eypqscjxjltmyyu)
