The fact the Musk called this a"code review" itself is bit odd, if not downright ludicrous. This is more like the outcome of an architecture review, and a very high level one at that. That Musk would call this a "code review" leads me to wonder how much he actually knows about building secure, reliable, and maintainable software.
In short, I don't think Musk has a clue about what a code review is, let alone how is supposed to work.
@justinhendrix Anytime I see an architecture diagram, I can't help but think of the classic microservices video.

it's because of the way our backend works // merch: https://merch.krazam.tv// https://www.instagram.com/krazam.tv // https://twitter.com/krazamtv
@justinhendrix @canadiancharity
Reading through this thread, this post exemplifies what I used to use the Quote feature for. It was perfect to say an "aside"; that is, a comment relevant to the main thread but not precisely about the heart of the thread.
When I found people who used the tool to disparage, I'd usually just scroll on by, or block.
And, I agree about the micro board! It reminds me of mind-mapping to take notes.
@justinhendrix What's missing from this high-level overview are the infrastructure components. What's doing the orchestration and launching/restarting/deploying all of the dozens/hundreds of application instances? Simple stuff like DHCP servers, DNS servers, load balancers. How does the horizontal scalability work for each of these components? It's the interdependencies that are often the most interesting and brittle.
"Doors and corners kid. That's where they get you." #TheExpanse