Your billing query joins 9 tables. Postgres's planner stops trying at 8. Famous last words: "It's just a 5-row lookup, the planner will figure it out." 0.3ms with 8 tables. 467ms with 9. exobench.ai/blog/how-one-ext… join_collapse_limit = 8. Default since 2005. Cross it → planner gives up → hash joins everything → 1.28s for 30 rows. I would have shipped this. 0.5ms → 5ms looks like a fluke. ExoBench found a logarithmic bomb. AI → ExoBench → real Postgres, real SQL Server, real MySQL at five scale points. No benchmark code. - SQL Server: same 9-table query → nested loops at every scale. No cliff. - MySQL: same query → no cliff. - Only Postgres has this. - The fix: SET join_collapse_limit = 12 → sub-millisecond restored. Every prompt verbatim. Emotive query plans. The cross-engine chart that should annoy you.

If you caught the article about Proteus but prefer a video format, check out @ghostdogpr's talk from Scalar 2026! 🍿 He shows how Proteus uses zio-blocks to bypass traditional Chimney/Protobuf boilerplate and speed up (slow down?) Scala compile times. youtube.com/watch?v=zTq9gdIm…

For all my Scala friends: Golem 1.5 ships with support for Scala, so I hope you join the $2.5k, three-day hackathon and built something cool on Golem with Scala 3!👇 x.com/jdegoes/status/2052778…

Claud was James Brown's funky drummer

There comes a time in your life when your son looks you in eye and says "Dad, can we go for a drive" (him driving on his provisional licence)

When your Intellij IDE contains more bookmarks than actual code you know you navigating a complex domain

Had great short break in London with the family

Just read this, looks like an awesome library we could use at work

One of advantages of having a home gym is that you get to decide the music policy. Right now I'm listening to hse.fm/

I finally pushed to button on these TYR L2's, a mere snip at £210. Expect to add a plate to your lifts by just looking at 'em tyr.eu/products/tyr-mens-l-2…

I've published the first version of Golem SDK for @moonbitlang - now you can easily write durable agents in MoonBit and run them on @GolemCloud 1.4: mooncakes.io/docs/golemcloud…

The correct way to defend against a sword

Resource.from[T](...).allocate — dependency graph resolved, scoped, finalized. One expression. One system. Ox MacWire: wire your deps with MacWire, then manually register each one with Ox's scope. Two libraries, no shared types, silent gaps.

Leaking a resource from a child scope should be a compile error. In ZIO Blocks Scope, it is — scoped requires Unscoped evidence on the return type. No evidence, no escape. In Ox? Compiles fine. Use-after-close at runtime.

What would you call a Scala library that: • Makes resource leaks a compile error, not a runtime bug • Auto-wires your entire DI graph from constructors • Almost no runtime overhead How about: Scope, in ZIO Blocks. Zero deps—works with ZIO, Cats, Kyo, or plain Scala. 👇

ZIO Schema 2 just shipped JSON schema support, courtesey of @987Nabil: ✅ get json schemas, parsers, and printers free for any Scala data type ✅ go from ZIO schema to json schema ✅ go from json schema to ZIO schema This is the foundation of powerful AI interop.

For Scala 3, derived optics just got a lot nicer in ZIO Schema 2. 👀 Unfortunately, I couldn't find a way to replicate the top-level optics for Scala 2, but at least you no longer need a type parameter in most cases. 😞 H/T @kitlangton

ZIO Schema 2 just got the best JSON interpolator. 👀 Which means you can kiss Json DSLs goodbye. 😘

Who's king of the hill? 👀 Friends don't let friends use Circe. 😉

1-2 weeks out from me doing a live coding session with ZIO Golem... this is gonna be fun. github.com/zio/zio-blocks/pu…