Activity 31 Code Review

Design It! — Pragmatic Programmers (129 / 139)

👈 Architecture Briefing | TOC | Decision Matrix 👉

A form of peer review in which code is incrementally inspected with an eye toward architectural concerns as the code is developed. Code review is a fantastic practice that every team should do anyway. Extending code reviews to include architectural concerns makes them even more powerful.

Incrementally inspecting code as the architecture manifests helps fight architectural rot by keeping tabs on the system’s evolution relative to the planned design. Reviews are also a great time to identify design inflection points that emerge during development. Such inflection points may require further analysis.

Every review presents a potential coaching opportunity. Watch out for synchronization mismatches in mental models so you can fix them before real problems arise. Coach teammates on architectural principles as well as the specific architecture you’re developing together.

Ongoing for the life of a project. An initial code review might take as little as 10 minutes with more time needed to resolve any identified issues.

The author submits an artifact, in this case code, for review. The reviewer inspects the artifact and provides feedback. Many teams encourage multiple reviewers to participate.

Related posts:

Journalism has always been an evolving medium: It has found a place off of newspapers into radio, television, and online. But the internet has proved a completely different beast due to the fact that…

Databases are about tables, and the relationships between them. Consider the data model we’ve been working with throughout this book. Artists have many albums, and albums have many tracks as well as…

Carmen Knight is a 20- year-old college student at Alabama State University. She is a junior at ASU, involved in modeling at fashion events at the university, and part of the student group, Elite…