📢 Time for an update on my workflow. This one's a 23 min read, so buckle up. 100% organic and hand-written, like an animal. steipete.me/posts/just-talk-…
Oct 14, 2025 · 7:00 PM UTC
Jupp.
Interestingly enough, the workflow you describe is 98% the workflow I have with Claude.
I don't get how we both can have the opposite experience.
This is good stuff, and I appreciate the feedback about Amp! If a single model house has all the best coding models, then yes, they will win. But if it ends up being valuable to use a variety of models, then things like Amp can win. We'll see.
Incredible, very detailed and opinionated, thanks!
I think the main things I probably think of a bit more are using the testing out model SDKs as part of the workflow, trying to design agentic workflows and feedback loops with other models.
>IMO most are something for the marketing department to make a checkbox and be proud. Almost all MCPs really should be clis.
Lots of great knowledge in this post (and things that needed to be said out loud), thanks for writing this
coming soon:
"Just talk to her; the no-BS way of improving your relationship with your AI girlfriend"
Very cool- interesting point about clis - for my tool (ck (“seek”) a sidecar local embedding hybrid vector bm25 code search) - I found it was pretty good just calling it directly rather than using the MCP version github.com/BeaconBay/ck
Brilliant read, and you've convinced me to finally try codex. I've just been too impressed by Claude code to bother so far tbh
This is really good stuff Peter. Couldn't agree more with the "just talk to it" takeway. I cringe at the amount of context poisoning I see some people suggest.
