80K views · Oct 9, 2007 · 51:02 · 1 HN recommender · 3 mentions · discussed 2011–2018
A 2006 Google TechTalk in which SQLite's author Richard Hipp introduces the embeddable, zero-configuration C database library. He covers its history, strengths and weaknesses, and where it beats client/server databases.
Why Hacker News points people here: Recommended as a first-hand intro from SQLite's creator that also teaches how a database engine is built.
“is actually a pretty good intro on to how to build your own DB engine.”HN comment, 2016
“is actually a pretty good intro on to how to build your own DB engine.”
Intro by SQLite's author that doubles as a guide to building a DB engine.
"An Introduction to SQLite" by Richard Hipp (who wrote the library) is actually a pretty good intro on to how to build your own DB engine. this video
“Here's the Google Tech Talk on SQLite from 2006”
Google Tech Talk introducing SQLite from 2006.
I've also worked with SQLite, and one project was the using the C API. It's also why I really liked Google Gears. Here's the Google Tech Talk on SQLite from 2006 this video
“They've talked about being able to refactor the core of their engine in a weekend”
SQLite cited as example of test coverage enabling big refactors.
First start writing automated tests, for example Selenium & unit tests. You'll learn what all the code does, you'll learn a new skill, you'll have a safety net of regression tests for rewriting the code, and you'll be adding value to the company. If you have good test coverage, you'll be able to rewrite the code very quickly. There are a ton of resources for how and why to do testing. One that stands out in my mind is SQLite. They've talked about being able to refactor the core of their engine in a weekend, only because they had the test coverage to know they did it right. link link this video
