Agreed - this is a great type of question. Being able to dive into a new codebase and read code at speed is a critical skill. Even when working on "the same old

Agreed - this is a great type of question. Being able to dive into a new codebase and read code at speed is a critical skill. Even when working on "the same old codebase", sometimes you run into weird corner cases that have you diving through a dependency, or debugging a perf issue that has you walking through other parts of the system. And reading a codebase doesn't always mean grokking the whole thing - if your goal is to figure out why some API call is failing, targeted reading is exactly what you want to be doing. FWIW: Took me 20 minutes from start to finish, without editing tests, but including ~5 minutes taken to update the codebase so my new-ish Clang would actually compile it. I didn't touch the binary protocol, though; in a real setting you'd have to make sure the binary protocol extension would be compatible with other extensions made since this version.