Reading Feed

Articles I've read with my notes and highlights

Revised rules of engineering leadership.
  • The good news is that this means the things that were most valuable to speed up engineering two years ago are still the things that are most valuable to speed them up today.
  • Of course, the harness will miss things, but so will human reviewers, and most areas are relatively safe to make changes. Of course, there are some higher risk areas, where this doesn’t hold true. By effectively capturing these distinctions properly, we can go much faster without introducing risk.
  • High judgment individuals can wander across a company doing remarkable things, but at some point they do get hemmed in by lack of domain context, which is why durable teams are the fundamental building block, even in this era.
  • Your team and company can only benefit from this increased pace of execution if you can make durable decisions quickly, and those decisions are good. This is the primary reason, in my opinion, why the average CTO role has necessarily become substantially more technical and less bureaucratic than a year ago
  • Pretty much every PR is written by harnesses now, at least in the first pass
Quantos impostos cabem num país? França é recordista, Portugal está acima da média europeia by The DuckDB team
A Complete Guide To AGENTS.md by Matt Pocock
  • Notice the light touch, no “always,” no all-caps forcing. Just a conversational reference.
Announcing Bonsai 27B: The First 27B-Class Model to Run on a Phone by PrismML
DuckDB Extensions: The Past, the Present, and the Future by DuckDB
Can We Agree on a Storage/Workload Architecture Taxonomy? — Jack Vanlightly
  • OLTP such as the RDBMS like Postgres and MySQL use row-based storage engines. OLAP, such as Clickhouse, cloud data warehouse and the lakehouse use column-based storage.
  • HTAP is a hybrid workload system: one system -> both transactional and analytical workloads. The HTAP system therefore has specialized storage and specialized query engine to stitch together the row-based and columnar data.
DuckCon #7 – ggsql: A grammar of graphics for SQL (Teun van den Brand)
A return to two-pizza culture by
  • Within a week, Swami Sivasubramanian, our VP of Agentic AI, saw the prototype and gave the team his full support. Three engineers joined. By the second week, they had a software development manager and a few more engineers, reaching a roughly even split between science and engineering. They were deliberate about not scaling too fast. Each person who was brought on was selected because they had a specific skill, and they had to adapt to a culture that was a complete departure from how the broader organization operated. They were expected to own a problem and deliver with autonomy, and ownership meant the same thing it has always meant at Amazon: you build it, you own it.
  • Writing is still as important as ever, and it should be you doing the writing, not your AI. Writing forces you to think clearly and confront gaps in your logic.
The Coming Loop by Armin Ronacher
  • Obviously that is powerful and I cannot deny that it sounds appealing. But giving in to that idea, particularly with less and less human oversight means accepting that we may no longer understand the whole system in the same way. We treat it, we monitor it, we stabilize it, but we do not necessarily comprehend it.
New DuckDB-Iceberg Features in v1.5.3 by Tom Ebergen, Thijs Bruineman
Test-Driving the Lance Lakehouse Format in DuckDB by LanceDB team and Guillermo Sanchez
PostgreSQL 19 New Features by Neon