Live data from Hacker News

sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25)

simonwillison.net

51–60 of 93 posts

Re: sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25)

#51
I'm kind of surprised that there is no test case that would have identified the fact that delete_where() leaves the state corrupted. There would be no need to ask Fable if the problem gets identified by the test. And having a test will also catch all future problems that might arise in the same function. So maybe instead of asking Claude what is wrong it would be wiser to invest in test coverage.

Re: sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25)

#52
Great to see such write ups in particular with money.

At least 2 things the random LinkedIn post will ignore, on purpose or not :

- price today remains low (even though they might feel higher than before), Uber is the business model, no secret there, it's a VC classic

- $150 spent by an expert, a software engineer with significant practical knowledge in AI, is not equivalent to the exact same amount spent by a novice.

Yet now that a number is out, you bet it will be used. Expect alarmist posts tomorrow morning in your feed claiming building software is now as cheap as diner at the restaurant.

Re: sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25)

#53
post #52

Great to see such write ups in particular with money. At least 2 things the random LinkedIn post will ignore, on purpose or not : - price today remains low (even though they might feel higher than before), Uber is the business model, no secret there, it's a VC classic - $150 spent by an expert, a software engineer with significant practical knowledge in AI, is not equivalent to the exact same amount spent by a novice…

It's also about variance in the number.

Expert software engineers will still accidentally burn $500 or $5000 on tasks that don't work, or are not efficient. Amateurs will accidentally spend $100 to get something great.

So part of the change is a change in the risk structure of using frontier models. Before, you'd burn your quota; now, you can burn uncapped (less-capped) money.

Re: sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25)

#54
post #8

Earlier quoted context omitted.

You didn’t do it enough. They stop finding bugs eventually. Also, different models can find different bugs (though they do find the same ones, too, which is good and expected). For best results you want to run multi model reviews in loops. If you had multiple people look at your PRs multiple times on different days results would be very similar.

No, depending on the complexity of the issue models can be into loops, where they go "this is definitely an issue and must be fixed", and then the resulting fixed code gets "this is definitely an issue and must be fixed", and then the resulting fixed code has the original 'issue'.

I've ran into this in the before times with linters and static analyzers. Nothing new.

Re: sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25)

#56
> I went out to enjoy the Half Moon Bay 4th of July parade, occasionally checking in and prompting the next step for Fable from my phone.

This intensification of work will not be good for workers’ health. Like, put your phone down man. You can’t be modeling this behavior to young people.

Further, the intensification of work is probably not even good for productivity in the long term. This periodic half-thinking about things without stepping away from the problems you are working to solve will lead to more half-assed solutions. Ideas need room to breathe and dedicated focus.

Re: sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25)

#57
post #43

I'm a big fan of sqlite-utils, but I really don't like how Python (particularly 3.12+) changes how sqlite's transactions work -- the native behavior explained in the sqlite docs is much better IMO. I understand why Python had to change it (to be compatible with other databases) but I don't think it's a good model for sqlite. Therefore, I created apsw-utils, a port of sqlite-utils to the amazingly-awesome apsw lib --…

> changes how sqlite's transactions work What specifically are you referring to? The apswutils website also does not explain.

They're probably talking about the addition of the autocommit flag, which hides more fine-grained transaction control in favor of more uniform behavior across multiple databases:

https://docs.python.org/3/library/sqlite3.html#sqlite3.Conne...

You can still use previous behavior with "legacy" mode that lets you control when transactions are opened in which isolation level.

Re: sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25)

#58
post #43

I'm a big fan of sqlite-utils, but I really don't like how Python (particularly 3.12+) changes how sqlite's transactions work -- the native behavior explained in the sqlite docs is much better IMO. I understand why Python had to change it (to be compatible with other databases) but I don't think it's a good model for sqlite. Therefore, I created apsw-utils, a port of sqlite-utils to the amazingly-awesome apsw lib --…

> changes how sqlite's transactions work What specifically are you referring to? The apswutils website also does not explain.

Pythons options are here: https://docs.python.org/3/library/sqlite3.html

SQLite behavior is here: https://sqlite.org/lang_transaction.html . The regular implicit transactions there plus explicit where needed aren’t supported in any python mode.

Re: sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25)

#59
post #3

The problem I have with this workflow is that the models are still too eager to please. If I ask it to scan a release and note possible issues, it absolutely will find issues. If I keep running the same prompt, it will keep finding issues. I’ve spammed GitHub PR reviews and it just keep finding (or inventing?) new issues. There is never a “Nothing found, good to go!”. I have to keep reminding myself that the model wi…

[dead]
Post reply on HN