Pekka Enberg
@penberg
Founder and CTO of @tursodatabase. Interested in systems and low latency. Ex-@ScyllaDB and Linux.
To prove my point, turns out @glcst was able to implement ATTACH which is pretty badass! github.com/tursodatabase/…
The thing I am most proud about turso.git is that the code is so straight-forward, even @glcst is able to contribute!
My experience is different. The person who published the package probably: 1) solved for their problem 2) did not test it very well 3) does not actively maintain it Another extreme is that package is actively maintained, but keeps breaking all the because API changes.
There’s an implication thats normally true: the guy who made a repo/package and published it, probably is autistic enough to: 1) make it work well 2) make it work good 3) test it well 4) knows more about the topic than you
There are essentially two kinds of good dependecies: a framework or library that is foundational to what you are doing and small utilities at the edge of your code base that you can easily replace. Everything else often ends up just getting in the way
A general rule I have about dependencies is that if you're not an expert in what the dependency does & think it "shouldn't be hard, should it?", you should use the dependency because almost all the times, it isn't that simple. When you actually know a substantial amount about…
I wish I had the zero dependency discipline Joran and the TigetBeetle folks have because more often than not, dependencies do end up being a liability or that thing that prevents you from engineering the right thing.
TigerStyle existed before TigerBeetle was created, and was intended for software development in general, as a methodology for “higher quality software in less time”. Enjoyed this post from @LewisCTech, which gets it. lewiscampbell.tech/blog/250718.ht…
.@Keleesssss : "I am writing a paper, can you check this one paragraph for accuracy, Pekka?" Me: <writes a wall of text on random topics he did not even ask about> "Hope this helps"
Nice!
Releases: Apache Otava (incubating) 0.6.1, Nyrkiö/change-detecion v2.0.2 and git-perf 0.1.0 This is the first release of what used to be called Hunter under its new name Apache Otava. It's a big deal! blog.nyrkio.com/2025/07/18/rel…
The thing I am most proud about turso.git is that the code is so straight-forward, even @glcst is able to contribute!
If you'd like to do something great for the database community, write an easy to use implementation of the TPC-* benchmarks. Bonus points if it comes with blog posts describing what it is in a database that each TPC-* benchmark is actually testing.