With a smaller pull request, it’s easy enough to keep the full context of a change in my head, and step through fairly linearly. When it comes to a larger change, especially when you don't yet understand the overall structure of the code, it becomes very tricky to navigate and gradually sign off portions of the code you’re happy with. Furthermore, if you know you're going to have to keep in your head the context of what you've already looked at and what you are still yet to, you're more inclined to put off the review until you've got a chunk of time free.
Россияне пожаловались на дискриминацию в европейской стране02:00
。关于这个话题，viber提供了深入分析
// 418: Unknown (418)
Back in 2005 I was the Xbox 360 CPU guy. I lived and breathed that chip. I still have a 30-cm CPU wafer on my wall, and a four-foot poster of the CPU’s layout. I spent so much time understanding how that CPU’s pipelines worked that when I was asked to investigate some impossible crashes I was able to intuit how a design bug must be their cause. But first, some background…