What can you find on the list? Tech/architecture, entrepreneurship, leadership/mgmt, behavioral psychology, history and global economics, some fiction, philosophy, some classics.

If you like Tome IV, maybe you'll like this one too. I liked the first two only. Btw. tome V concludes the first "story arc" (5 huge books), the 2nd "story arc" is planned for another 5.

I'm certain my knowledge about this beautiful sport is very limited, but I know the basics of how points are awarded (TES+PCS).
I strongly believe that e.g.:
- software engineer performance does not depend on how difficult techniques (s)he uses ...
- not mentioning the artistry and presentation ...

Anyway, if you're still struggling with how to capture the idea of "maintenance" in your budgeting/planning/org. composition, you may find this No Kill Switch classic (from 2019) useful: no-kill-switch.ghost.io/the-cost-of-...

... - there's no "maintenance", but 1/ an entropy management, 2/ a cost of running software, and 3/ the concept of various debts incurred (technical, model, process, etc.).

I had this a while ago - I was kind of shocked when I heard that the "new feature development" vs "maintenance" is still a thing for many orgs. In my bliss ignorance I believed this "dichotomy" is already widely addressed by a simple mental model ...

Wyszła zdrowa godzina z kwadransem 🕰️ - ani za mało, ani za dużo. W sam raz do odsłuchania przy ubieraniu choinki, gotowaniu Wigilijnego barszczu albo innych świątecznych aktywnościach, np. rozwiązywaniu zadań "Advent of Code" 😜 ...