I have a similar list I like to share, had a few from Carl's list, will probably add a few from it.

http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom... https://www.parsonsmatt.org/2017/10/11/type_safety_back_and_... https://lwn.net/Articles/336262/ https://tomasp.net/blog/2015/library-frameworks/ https://ratfactor.com/cards/not-quite-the-same https://matklad.github.io/2023/11/15/push-ifs-up-and-fors-do...

Pleasant to hear about the Object-Relational Impedance Mismatch [1], haven't heard about that concept for a long time - maybe a decade!. The reason I like Dapper [2] is that it makes you use your own sql.

Edit "lets" -> "makes".

[1] https://en.wikipedia.org/wiki/Object%E2%80%93relational_impe...

[2] https://github.com/DapperLib/Dapper

> PostGIS is a great database and its foundational data type is geography.

Hate to "well ackchyually" the author here, but I'm gonna. The foundational data type in PostGIS is not geography, but geometry. geography is geodetic layer on top of geometry. I honestly don't use geography that much because it only supports a subset of the geometry functions.

The Grug Brain article is fantastic, and even better if you run it through an LLM to convert from caveman. This thing is a gem.

Thanks for a drop of humanity in this place. I feel saner

I personally hate YAGNI, because it so often leads to balkanized APIs that only implement the "needed" features and omit things that a reasonable person would expect because they weren't needed initially. Far better to have a clear and explicable model that is fully and consistently implemented.

DDIA is great. I read and re-read the small section about LSM merge tree in the first and second edition of the book and got interested in this stuff. It is always a pleasure to read about internals.

Grug.