Getting ready for 1-2 weeks of LinkedIn posts discussing the U.S. ban on Fable / Mythos for foreign nationals… 🫣😂

Pelzerhaken

BREAKING: CEO discovers tokens cost money

Northern Sea

The $2500 MacBook Pro I bought in 2012 that I used to write every single hashicorp 0.1 release. Arguably turned that $2500 plus some internet into like a billion dollars. Good trade.

Today I’m launching QuackLake, a @duckdb DuckLake catalog service via the new quack protocol on top of @CloudflareDev Durable Objects github.com/tobilg/quacklake

In my novel Wohpe one chapter is the pope encyclical about AI. The novel is from 2022 (pre chatgpt). Here we are in 2026 with the actual pope writing an encyclical about AI.

Went outside 😀

Today, we are releasing DuckDB v1.5.3. This is not an ordinary patch release – it packs many new features as extensions. First, DuckDB v1.5.3 ships our new Quack client-server protocol as an autoloadable core extension. Second, Quack can now also work as a DuckLake catalog. And finally, the AWS and Iceberg extensions made huge strides, along with changes in the HTTPS extension for better proxy support. We wrote a blog post about all these changes and improvements: link in the thread 🧵

crying

The v0.2.0 release of my @duckdb quack protocol TypeScript client now also supports Apache Arrow as inputs/outputs: github.com/tobilg/quack-prot…

Recommended read if you use Codex

Launching latlng, an open source geospatial object engine written in Rust. latlng.cloud

Is there an API to query the running @CloudflareDev Container instances of a specific application, or lifecycle event notifications? Load balancing example seems to not do any of this, so there will be cold starts eventually? github.com/cloudflare/contai…

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.

Documentation of the new DuckDB Quack protocol from its sources gist.github.com/tobilg/9ced9…

„Extremely lean“ meaning $1.3m token spend/month