Today we start off a series of bytes about code review, perhaps the most important process to master for a company in terms of soft and hard skills, that when done right can foster better engineers and a better codebase.
When writing a large, or even small feature, it's important to have the approach you're going to take - before almost any code is written - heard by and approved by a colleague or senior. That way, if you've got the wrong approach, you can adjust then and there, without having to redo a lot of coding. Once you've started on the right track, you should then review every now and then to make sure you're doing what you agreed on and you're on the right track. This will save time and stress when it comes to code review - which should really be a final check, not a first look.
This approach may sound only suitable for junior developers, by it applies to developers at all levels. You are a team working on a codebase, so don't code alone.
Heads up: As with any terse bit of advice, there will be exceptions of course, and subtleties and nuance that can't possibly be captured in a Byte of Wisdom. This has been what I've experienced, I'd love to hear yours in the comments too!
You can catch up with all the other bytes at http://bytesofwisdom.com/