Do more experimentations with local models people! vickiboykis.com/2026/06/15/r…

Chevy's New Silverado Doubles Down on V8s as Truck EVs Retreat suspension.news/p/chevy-s-ne…

Tesla Pushed Its Own FSD Safety Data to European Regulators. Researchers Called It Misleading. suspension.news/p/tesla-push…

Swearing way too much at Claude today, but it's putting em dashes in file names now. Really?! autocomplete is not happy.

Honda's Former CEO Told Its Current CEO to Quit. The $15.7B EV Write-Down Is Why. suspension.news/p/honda-s-fo…

Honda Recalls 1M Accord Hybrids and CR-Vs Over a Tire Repair Kit That Has Injured 8 People suspension.news/p/honda-reca…

If we want to build software factories (still an if for me), how can we build good ones? I think that’s the biggest gap in how people use LLMs right now. And I don’t know about you, but I think it all comes down to verification. 👇 germanvelasco.com/blog/draw-…

The BMW M3 going electric is why 21 outlets covered the reveal in one morning. M built its reputation on character: inline-six sound, sharp steering, pure mechanical engagement. Does an electric M still feel like an M without the engine?

BMW's Quad-Motor Electric M3 Concept Is a 100 kWh Sedan Built to Silence the Skeptics suspension.news/p/bmw-s-quad…

Claude migrating a prod (personal project) db from SQLite to PostgreSQL live?! What could go wrong?

Frustrating that LinkedIn broke cmd click to open in tab on external links?! But I guess one less tab to process is probably a good thing in the end anyway.

Postgres 19 is in beta, and whew is it a doozy of a release. Each Postgres release is a bit different. Sometimes there is a single marque feature, sometimes there is a bunch of small quality of life improvements, often there is something around performance. Postgres 19 seems like it has really some of everything in it including marque areas. I'm going to spend some time over the coming weeks highlighting some of whats coming. And today I want to start off with a bang, built in REPACK! If you have operated Postgres for long enough, you have probably had a moment where you wanted to reclaim table bloat, rewrite a table, or reorganize data, but you very much did not want to take the lock that came with VACUUM FULL. There has long been an extension ecosystem around this problem, most notably pg_repack. That alone tells you something: users had a real need, and the ecosystem filled the gap. And even then pg_repack came with a few caveats in running it. Postgres 19 brings a new REPACK command into core, including support for REPACK CONCURRENTLY. That's right, not just REPACK in core, but being able to run it CONCURRENTLY just like we do for index creation! This is the sort of feature that may not excite someone building a toy app locally, but it matters a lot once your database is large, busy, and important. The difference between "yes, we can clean this up online" and "we need to schedule a maintenance window" is not a small difference. It is the difference between routine maintenance and a project plan. I expect REPACK CONCURRENTLY to be one of those features that production Postgres users care about more than the average release-note reader might expect.

I have a nice routine to share: We commonly communicate technical architecture/proposals in docs. Each night, I load new ones in either a notebookLM or prepare to play the doc in audio. In the morning I go for a walk & listen. Walking and thinking is cathartic. It’s nice to be in nature.