OP might also like Essentialism. Very in line with YAGNI - it guides things outside of API design too!
Carl's Required Reading
31–32 of 32 posts
Re: Carl's Required Reading
#32Decent list but the ORM thing makes me suspicious. He links here as some kind of damning proof that ORMs are default bad. https://openai.com/index/scaling-postgresql/ “It’s a poor craftsmen who blames their tools.” My ORM rule of thumb: ORM for CRUD not Reports If you are joining 12 tables for operational data, you have a design flaw. That’s a reporting query pattern. Often temp tables, CTEs etc are needed as an imme…
My rule: ORMs first, if there are performance problems it's probably the db structure so don't be afraid of reworking the underlying database. In some cases though SQL gets you the specific thing you need so don't be afraid to use it occasionally in the code (fully parameterized of course and using as much of the ORM as possible for getting things like the table name rather than hardcoding).