| ▲ | simonw 3 hours ago | ||||||||||||||||
I had an interesting experience recently where I ran Opus 4.6 against a problem that o4-mini had previously convinced me wasn't tractable... and Opus 4.6 found me a great solution. https://github.com/simonw/sqlite-chronicle/issues/20 This inspired me to point the latest models at a bunch of my older projects, resulting in a flurry of fixes and unblocks. | |||||||||||||||||
| ▲ | small_model an hour ago | parent | next [-] | ||||||||||||||||
I have a codebase (personal project) and every time there is a new Claude Opus model I get it to do a full code review. Never had any breakages in last couple of model updates. Worried one day it just generates a binary and deletes all the code. | |||||||||||||||||
| |||||||||||||||||
| ▲ | jauntywundrkind 2 hours ago | parent | prev | next [-] | ||||||||||||||||
From the project description here for your sqlite-chronicle project: > Use triggers to track when rows in a SQLite table were updated or deleted Just a note in case its interesting to anyone, sqlite compatible Turso database has CDC, a changes table! https://turso.tech/blog/introducing-change-data-capture-in-t... | |||||||||||||||||
| ▲ | petesergeant 2 hours ago | parent | prev [-] | ||||||||||||||||
I continue to get great value out of having claude and codex bound together in a loop: https://github.com/pjlsergeant/moarcode | |||||||||||||||||
| |||||||||||||||||