I'm thinking a lot about this recently as I'm building AQ.dev (Multiplayer coding harness). My instinct is to keep it simple and not trying to do too many shenanigans with these files and let engineers maintain control.
I like this disclosure and approach. I had a very similar idea to use a label or tag to show on blog posts that I refine with help of AI. Havent gitten around ti implementing it yet. will take some inspiration from this.
But I am not sure if the book covers the mistake and later correction. It has been more than a decade since I read the book (and became a fan of the author).
It's the same show, Nova just rebranded it in the US. BTW, here's a full video of the BBC version but available everywhere. https://www.dailymotion.com/video/x223gx8
I'll check that out - I loved his "The Code Book: The Science of Secrecy from Ancient Egypt to Quantum Cryptography". Excellent introduction to cryptography.
Agreed. I bought it at the airport for a transatlantic flight the year it came out and started reading before lift off. Completed it before landing. Best flight ever.
I can attest to experiencing virtually everything the author describes here. I admire the ability to articulate these mundane-sounding challenges that greatly impact your quality of life.
Judging by the pace at which new models are released these days -- it feels like a Windows KB or VS Code patch release now.
Older models must be getting deprecated at the same (or faster) pace. So anything you built 3 months ago is probably going to break soon.
AI solutions need better insurance around model deprecation. Commercial API-only models that complete the full cycle from SOTA / gated-preview to unsupported and deprectated in a matter of months -- is no way to build serious software!
> The reasoning was in a transcript on my laptop. Claude Code deletes those after 30 days by default. Two of my projects lost their whole history that way.
Wait what? Claude Code (and Codex) transcripts are auto-deleted??
That's a treasure trove of information for all my projects and I had built some tooling and workflows tahat deal with extracting insights from them -- withut ever realizing I mightbe losing old chats. Thanks for this -- I may need to include an archival step for retention.
I will still try and include archival -- storage is cheap. A reinstall of Claude Code or buggy upgrade might still wipe history. I also ocassionally use multiple PCs -- so there is some small value in consolidating them all for analytics and insights.
(When I have a weekly quota unused and about to expire -- i task Opus with churning through these archives and surfacing learining, best practices, what's not working etc)
Is there a behind the scenes detail on Jurassic Park branding and logo? I love how well they planned it ahead and wove that into every thing we see across the park.
Somewhat like AWS CloudFormation templates start with something like TemplateVersion: 2017-10-01
But maybe that's old school thinking still.
reply