can we talk about how code review is not just about pointing out syntax errors and typos, but also about understanding the thought process and design decisions behind the code? it's not just about "is this technically correct?