HN user
Still Mostly human.
At the moment eating e-mails at Lightmeter.io.
Lightmeter | YC W22 | Berlin
Senior Back-end Software Engineer: https://www.ycombinator.com/companies/lightmeter/jobs/H97vAO...
Lead DevOps Systems Engineer: https://www.ycombinator.com/companies/lightmeter/jobs/PB5qMl...
We use a wide of tools and technologies, such as Go, Python and Javascript, and SQLite, Postgres and Kafka.
Maybe a bit late in times of twitters and instantaneous replies, but I decided to spend some of my weekend refreshing my (still very basic) Prolog-fu and chose the Dog Bunny Puzzle [1].
Interestingly when one uses SQLite (or virtually any embedded/serverless[1] database engine), the code is always executed within the application process, regardless of being written in pure SQL of by the hosting language, making the dichotomy irrelevant.
Not having support for stored procedures can be used by some as an argument against SQLite, but the fact is that store procedures conceptually make no sense in embedded databases if you can extend the query language with the host code.
One big issue I've seen on SQLite is that if you add an index or view on an expression which uses code from the host process, no other application will be able to read data from the database file, unless you have such code in an extension that can be read by such applications.