Regarding LOCOMO I have a fork that calculates an estimate based on # of commits * price per task according to Artificial Analysis benchmarks for a given model, and includes a simple overhead multiplier to pad out the estimate.
Its what I used to migrate to the 6 TB sqlite database... so yes? Depends on your definition of backup. In my case I wanted a way to restore in the case of data loss, so yes. Im sure some pedantic sql admin will disagree with me here.
Interesting, I built https://pyor.review to fix this exact issue, though it uses AI to categorize the files and groups them by complexity to speed up the review process because most AI generated code is noise, especially migration PRs.
Curious to know if this could be done in a deterministic way without the help of AI
14 comments
[ 0.23 ms ] story [ 9.2 ms ] threadRegarding LOCOMO I have a fork that calculates an estimate based on # of commits * price per task according to Artificial Analysis benchmarks for a given model, and includes a simple overhead multiplier to pad out the estimate.
Id like to see that fork. Perhaps I can fold some of it in.
- https://boyter.org/2010/08/mysql-backups-done-easily/
- is an sqldump actually a backup?
It would be intersting to combine your «attention» metric with CRAP.
If you do hook this up please let me know, id love to write about it.