While I agree with the sentiment, my impression is that the GP's point is about memory safety rather than performance. So yes, this applies for common patterns like per-frame memory in games, in which case the "it" is the arena. Otherwise, as a general rule, profile first, then optimize.
The latest edition (7th ed, 2015) actually uses 4.5 as well. AFAIK OpenGL hasn't changed too much since 3.3, certainly not to the point of being irrelevant for learning.
Hard to talk about code comments without mentioning 'antirez's article [0] about this where he goes in depth on the different kinds of comments he used throughout Redis.
Are you referring to snapshot testing[0][1]? i.e. you first "snapshot" the output of the function and commit it to VC, and each test run will run the same input and compare it against the "snapshot", failing and giving a diff if it differs.
I'm about to try it soon, seems like a good ROI as you said.
Hey folks, this is my internship project at Supabase, which you may have heard from its HN thread that got popular recently. We lean heavily on PostgREST, which is a Haskell tool (a wildly successful one!) that turns a Postgres database into a RESTful API.
We use PostgREST through our own client library as it's much easier to use. But it's in JavaScript, and I'm part of the Rust Evangelism Strikeforce myself, and the rest is history. ;)
I don't know how many people FB actually allocates for their main app, but this reminds me of a chapter in The Mythical Man-Month. It is said over 1000 people and 5000 man-years went into OS/360. I don't see it anywhere today.
Instead, the book proposes The Surgical Team, i.e. about 10 people taking specialized roles, with the system being the product of the mind of a few key people. I wonder how well this aged.