> Validate your strategy before building it. If there's a senior engineer in your team who nitpicks your code, get their buy-in before writing it. I think this

> Validate your strategy before building it. If there's a senior engineer in your team who nitpicks your code, get their buy-in before writing it. I think this hits the nail on the head. Code reviews have been adopted by most of the orgs I've worked at as a way to reduce any technical barrier to starting a project. Technical planning is moved from the start of a project to the end (or more accurately, to what has now become the middle). I'm certain there are code review processes that are done well, but they don't appear to be common.