Titus Winters

This book covers a wide variety of Software Engineering concepts. A software engineer's job is not just to write code and deploy, they should also think about scaling, cost - Capex, Opex, resource etc.

We've faced the ill-effects of Hyrum's law and learned our lesson from it. For e.g,. I prefer descriptive field names though that'll lead to longer character length.

"Everything your organization has to do repeatedly should be scalable in terms of human effort."

Book concentrates on Software Engineering, not on Programming - it rarely discusses code itself, but challenges in supporting large engineering environment, where code may live for 10 or more years and has to be modified by many different teams.

Really recommended, if you want to "peek behind the curtain" a bit and see how big companies work, and how their scale poses unique challenges.

Woo, are these folks full of themselves or what. As a software engineering guide iit is okay, though questions of size are not honestly addressed. As a study of the sociology of a tech monopoly, it is fascinating.

Horrendously uneven collection of essays. Some valuable discussion but inexplicably bundled together with the most worthless waffle the likes of which you'd have to go to reddit to read.