@paulg I tried something similar for a product aimed at marketers and found a name I really liked. Couldn't get a good .com, though. Thanks for sharing the trick.
@arvidkahl@podscanfm@audiohook Congrats, Arvid! I've been following you and listening to your podcast for quite some time. Really glad to see this happen for you.
@dhh I can get pretty far from a prompt to a working app. It's the deploy, operate and grow part that makes me wonder how much of the stack can really disappear.
@lika_build Exactly. Once a run can change state, retries need more than 'try the model again.' Give each step an idempotency key, record what actually committed, and let a resumed run skip completed effects. Otherwise a timeout can quietly become two writes.
@Postgres_Daily Good default for teams already on Postgres. The win isn't just one fewer database: you can join vector matches to permissions and business data in the same query. I'd still benchmark recall and latency on the real workload before treating it as a universal replacement.
@sutarabhiii The evaluation piece gets skipped too often. I'd test retrieval separately from generation: for a set of real questions, did the right source even make it into the top results? If not, a better prompt won't fix the answer.
@pathikghugare I havent hit the quota for that. Once I asked how is it working it uses a proxy mechanism to send the same request claude code would send.
@HarshitMaurya_ What worked for me are two things
I keep agent memory off and keep decisions in files that agent re-reads.
I also use compact command with a description everytime for the context I think must not be lost.
Somehow ChatGPT has been running multiple compacts without losing context
@charliejhills Good list. I'd push back on 4.
Correcting it once doesn't mean it never repeats. What I kept hitting is that the correction lands as a new and the old one both stay, with nothing marking either as superseded. Retrieval surfaces whichever matches the query. Both are in there.
@acatovicx https://t.co/ek6BU3tI0Y
most probably the regression could be the issue
Claude Code removed no time estimates rule in 2.1.111. It restored and strengthened the rule in 2.1.152
Either way I use CLAUDE.md to specify not to give estimates. It was a huge issue earlier for me as well.
@acatovicx Claude Code is not measuring execution time.
It is the pattern it has learned from human documents. Those documents use sprints, days, and weeks.
Also there was a regression on system prompt of Claude Code as per reverse engineered prompt tracker.
I recently spoke to a marketer who ran a $40M brand with just two designers and ONE AI process:
He gave me and my team a masterclass on using AI to scale marketing and creative.
He chains 7 different tools together for: ideation, image creation, video editing, and iterating based on performance.
I paid him 6-figures to build these systems for my companies.
Now, Iโm giving them away for free.
Repost + comment โGAโ to get the guide in your DMs.