I quickly read through the `sqlite-history-json` project and it's only a few hundred lines of code and the code doesn't use transactions which means that it can fail and leave the state of the code and database in an inconsistent state.
Being only a few hundred lines of code is a pro, not a con (it's 2,800 including tests: https://tools.simonwillison.net/sloccount?repo=https%3A%2F%2... - lines counted by my vibe-coded port of the classic Perl SLOCCount tool to run in a browser using Perl-in-WebAssembly.)
I lead with sqlite-history-json because I think it's the most impressive of the bunch - it solves a difficult problem in an elegant way with code I would have been proud to write by hand.
Props for your work on these but they’re toys mate. These are things you built for yourself that other people happened to find useful. That’s great! I’m not shitting on that, but it doesn’t really convince me that AI coding really is this amazing productivity booster in all cases. It’s good for small greenfield projects, I’ll admit that.
Six useful small greenfield projects in two weeks is pretty good, especially when they weren't my primary focus for those two weeks.
I wouldn't call these toys either. If you want toys take a look at most of https://tools.simonwillison.net/ - these six are all real projects on GitHub with tests and documentation and release notes.
- https://github.com/simonw/sqlite-history-json
- https://github.com/simonw/sqlite-ast
- https://github.com/simonw/showboat - 292 stars
- https://github.com/simonw/datasette-showboat
- https://github.com/simonw/rodney - 290 stars and 4 contributors who aren't me or Claude
- https://github.com/simonw/chartroom
Noting the star counts here because they are a very loose indication that someone other than me has found them useful.