With @tursodatabase's Limbo announcement, I decided to read a bit more on SQLite and its creation and came across an amazing transcript from @corecursive's interview with Richard Hipp.
Some interesting stuff that I learned🧵
Richard was a contractor working on battleships, where the DB issues he ran into became the inspiration for SQLite
Interestingly, most of his experience was building compilers, not databases, and so he approached it from a compiler-problem perspective
Holy cow, he brought up SQLite to 100% MCDC coverage during his work with safety-critical aviation products at Rockwell Collins
Lol they were able to segfault every DB engine, including SQLite, but not Postgres
"when I set out to write it, I went around looking, is there a reference on how to write an SQL database engine, I found nothing, and so I just had to kind of invent it myself, so it was a completely independent mission"
He implemented covering indexes for SQLite on a flight after listening to one of the original MySQL developers, David Axmark
You can just do things! Crazy to see how an insanely cracked dev does JIT-learning while building one of the most incredible software products of all time
You don't have to reinvent the wheel for everything but if you want to make something amazing, you may be better off building many parts yourself
Taking inspiration from Linus and Git, SQLite built their own version control system, called Fossil
Incredible advice
"I think, maybe, just don’t listen to the experts too much and do what makes sense. Solve your problem."