Code Reviews

Every change we ship is reviewed by a second developer for correctness, security and maintainability before it is merged into the main codebase.

Where we use it

Code reviews are an integral part of our development process. Every piece of code is reviewed by another team member to catch bugs, improve quality, and ensure adherence to coding standards. This practice also helps in knowledge sharing across the team.

Strengths

Improves code quality and reduces bugs.
Fosters knowledge sharing and mentorship.
Ensures consistency and adherence to best practices.

Trade-offs

Can slow down the development process.
Can lead to subjective disagreements about style.
Requires a culture of constructive feedback to be effective.

Questions

We look for correctness, readability, maintainability, security vulnerabilities, and adherence to our team's coding standards and best practices.

More in Development Practices & Collaboration

Git Version Control

We use Git version control on every project, with feature branches, pull requests and reviews, so every code change is traceable and reversible.

CI/CD Pipelines

CI/CD pipelines that automatically build, test and deploy your application, so releases are frequent, repeatable and far less prone to human error.

Git

Git is the distributed version control system used to track source code changes, coordinate developers and keep a full history of every project.