Great list. I’d just add that you should revisit these books every few years, as they read very differently each time; while you might initially read for patterns, you eventually return to them for the trade-offs, failure modes, and the nuances of why certain advice only holds up under specific constraints.
Is the role of a Senior Engineer shifting from builder to technical auditor?
With AI-assisted coding becoming common, I’m curious how Senior+ engineers are thinking about ownership, reviews, and long-term technical debt.
@Dream11
A player scored -5 and the one who made him captain got -10 ! Shouldn't he be rewarded and getting -2.5 instead ? Because that's what a captain should be getting (2x his performance, either by multiplying or dividing in case of <0)
P.s. he was not in my team though 😛