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
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.
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.
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
Congratulations on the release boyter! scc has been a really useful tool for probing projects. Looking forward to the new features.
Thanks mate.
Very interesting. This reminds me a lot of the CRAP metric - a combination of cyclomatic complexity and code coverage.
It would be intersting to combine your «attention» metric with CRAP.
Not one I have come across. Now in my list of reading.
Neat tool. Wondering if this has a place helping to gate PR’a that should require human review.
- saw this other post on your blog
- https://boyter.org/2010/08/mysql-backups-done-easily/
- is an sqldump actually a backup?
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.
if sqldump isn't a backup, what is?
they say pg_dump isnt a backup hence my question
Thanks for developing scc!
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.
You are welcome.
Id like to see that fork. Perhaps I can fold some of it in.