Our engineering workflow revolves around our code review process. Code reviews are more than just a way to make sure we don’t introduce new bugs into the codebase. They have become pillars of our team’s engineering culture—ensuring code quality, encouraging collaboration and providing valuable teaching and learning opportunities.
We’ll look at the ways your code review process can define, reflect and reinforce your team's culture. These methods can be useful whether you're building and managing engineering teams at startups, large companies or even open source communities. We’ll then walk through the process with actual Pull Requests and identify best practices for more productive code reviews.
Creating code reviews that reflect your team's culture
Process

Related content
The role of developer advocacy in driving innovation

Introducing a career framework as your organization scales

CONTENT SPONSORED by SPLIT
Stop working on islands as engineers

Navigating competing priorities as an engineer

CONTENT SPONSORED by SPLIT
How feature measurement promotes productivity and happiness

CONTENT SPONSORED by SPLIT
Coding with clarity to improve developer experience

What is developer experience? Your route to better productivity

Mastering large-scale migrations

Using experiments to bring security into your software development life cycle

Is agile still the way forward?
.png)

Communicating quickly, effectively, and inclusively

CONTENT SPONSORED by SWARMIA
Improve planning and ideation with divergent thinking

What McKinsey got wrong about developer productivity

Introducing new processes to your team

CONTENT SPONSORED by JELLYFISH
5 best practices for annual budget planning

CONTENT SPONSORED by JELLYFISH
Overcoming the challenges of annual budget planning


CONTENT SPONSORED by JELLYFISH
Working with leadership to plan for a successful new year

How to design (and listen to) a developer survey

CONTENT SPONSORED by PLURALSIGHT
Why support and belonging are the final key to developer thriving

A prioritization framework for uncertain times

Setting goals and using metrics that motivate

3 strategies for driving organizational change

Building an onboarding plan for engineering managers

Managing the chaos of context switching

CONTENT SPONSORED by LINEARB
What the top 10% of dev teams look like in 2023

How AI changes engineering management

Using high-quality questions to unlock innovation

If agile isn’t dead, why is it still not working?

Building a prioritization framework

Introducing processes where none exist

Focus on outcomes over outputs

How to get leadership buy-in on your tech strategy

Growing an experiment-driven quality culture

CONTENT SPONSORED by CODE CLIMATE
Keep your delivery in balance with these metrics pairings

CONTENT SPONSORED by PLURALSIGHT
Why motivation and self-efficacy drives thriving software teams

Incorporating organizational values into your agile process

CONTENT SPONSORED by SPLUNK
Building a more effective DevSecOps culture

CONTENT SPONSORED by LINEARB
Why elite dev teams focus on pull-request metrics

Four key steps to take for an effective project handoff

CONTENT SPONSORED by JELLYFISH
What recent data tells us about developer productivity and team health

How to plan your next product feature using a six-week cycle

Platform engineering for engineering managers

How principal testers can improve company processes

How to protect your calendar against unnecessary meetings

How to build a strong culture with ensemble programming

CONTENT SPONSORED by VERCEL
Removing roadblocks to faster iteration

CONTENT SPONSORED by DATADOG
Practicing engineering transparency

CONTENT SPONSORED by SPLUNK
Running human-focused postmortems

How engineering leaders can promote urgency in teams

How engineering leaders can better organize their day

Managing complex organizational change

DevOps for engineering managers

Context switching strategies to preserve your focus

CONTENT SPONSORED by SWIMM
Documentation is broken

CONTENT SPONSORED by PAGERDUTY
Keep your digital ops thriving through 2023 uncertainty

How to break the “get me everything” cycle

CONTENT SPONSORED by CHRONOSPHERE
On-call is a necessary function for any organization

How to make plans for an uncertain future

CONTENT SPONSORED by DEEPSOURCE
How to bake quality into your teams’ coding process

When, not if: The playbook method for managing risk

CONTENT SPONSORED by PLATFORM.SH
Three ways to reduce the cost of DevOps

Navigating complexity as an engineering leader

How to build an effective code review process for your team

Why business context is important for technical decision-making

CONTENT SPONSORED by ROOKOUT
Why traditional observability tools aren't cutting it anymore

CONTENT SPONSORED by CHRONOSPHERE
How to reduce stress for on-call engineering teams

Empowering engineering teams to perform code reviews

CONTENT SPONSORED by CODESIGNAL
Optimizing the time you and your team spend on hiring


Bringing together a social model of open source

What is a developer experience team?

CONTENT SPONSORED by CHRONOSPHERE
How to create sustainable on-call rotations

CONTENT SPONSORED by PAGERDUTY
Want to accelerate incident response? Empower customer service teams.

CONTENT SPONSORED by HONEYCOMB
What is the business case for observability?
.png)
Why the most advanced technology solution isn’t always the correct one
.jpg)
Born-left security: The new approach taking over shift-left

Want to promote knowledge-sharing in your teams? Standardize the way you take notes.

How to communicate the state of your open source project

CONTENT SPONSORED by JELLYFISH
How to scale decision-making in your organization with Circles

CONTENT SPONSORED by CODE CLIMATE
How to level up your reporting as an engineering director
 (1).png)
.jpg)
CONTENT SPONSORED by JELLYFISH
Four engineering leadership trends you need to know

CONTENT SPONSORED by HONEYCOMB
Why on-call pain is a sociotechnical problem
.png)
CONTENT SPONSORED by CODE CLIMATE
Five engineering KPIs to consider for your next board meeting


CONTENT SPONSORED by PLIVO
Want to deliver more value to users? Bring engineers and customers together

CONTENT SPONSORED by CODE CLIMATE
Reporting to the board as an engineering leader: Secrets to success

Dynamic Reteaming: The Art and Wisdom of Changing Teams: Heidi Helfand in conversation
.png)

Just Work: Kim Scott in conversation


Engineering Management for the Rest of Us: Sarah Drasner in conversation


CONTENT SPONSORED by PAGERDUTY
Four things you need to know about managing toil as you scale
.png)
CONTENT SPONSORED by PLIVO
How to drive a customer-focused engineering team

CONTENT SPONSORED by PAGERDUTY
What is toil and why is it damaging your engineering org?

CONTENT SPONSORED by CODE CLIMATE
Four best practices for leveraging data responsibly

CONTENT SPONSORED by PAGERDUTY
Three steps for managing toil as you scale

Effective Remote Work: James Stanier in conversation


How to run a progressive ERG


CONTENT SPONSORED by JELLYFISH
Why engineering teams should stop counting Agile story points

CONTENT SPONSORED by CODE CLIMATE
Reporting effectively to the board

.png)
How to turn an engineering incident into an opportunity

CONTENT SPONSORED by CODE CLIMATE
Four ways to empower your team through data

CONTENT SPONSORED by HONEYCOMB
Using SLOs to align business and engineering goals

Setting a vision, mission, and strategy for your team

CONTENT SPONSORED by SHIFTLEFT
A guide to open source for the traditional enterprise

CONTENT SPONSORED by STACKHAWK
Shifting left on security: Five steps to transformation

CONTENT SPONSORED by AIRBRAKE
Five mistakes to avoid when setting OKRs for your team

CONTENT SPONSORED by SHIFTLEFT
Who is responsible for open source security?

CONTENT SPONSORED by SHIFTLEFT
How open source maintainers ensure projects are safe, friendly, and thriving
.png)
Running your first internal hackathon

Understanding the role of a Distinguished engineer


Balancing delivery speed with engineering health

How to drive decisions as an engineering leader

Getting your engineers engaged with OKRs

Why open source projects should embrace operational transparency

Do successful products prioritize familiarity over uniqueness?

Getting big changes implemented at the staff+ level

Five steps for making data-informed decisions

Top 10 ideas to take into 2022
.png)
How to cultivate a great engineering process
 (1).png)
CONTENT SPONSORED by HONEYCOMB
How Netflix, Teachers Pay Teachers, Honeycomb, and more used observability in 2021


CONTENT SPONSORED by STACKHAWK
Overcoming security hurdles to push engineering velocity


A vision for a social model of open source

Delegation is a superpower

CONTENT SPONSORED by EPSAGON
An introduction to Real User Monitoring (RUM)

CONTENT SPONSORED by LINEARB
Communicating engineering priorities to your CEO

CONTENT SPONSORED by CODE CLIMATE
Learnings from ‘The engineering leader’s guide to data-driven leadership’
.png)
CONTENT SPONSORED by EPSAGON
An introduction to issue management

CONTENT SPONSORED by CODE CLIMATE
Introducing OKRs to your team: From general alignment to measurable results
.jpeg)
CONTENT SPONSORED by HONEYCOMB
The rise of OpenTelemetry

Technologists: how to make decisions for your organization and our society

CONTENT SPONSORED by CODE CLIMATE
Using metrics to communicate the state of your engineering org

.jpg)
Creating open source projects for your community
.jpg)
CONTENT SPONSORED by CODE CLIMATE
Running more effective standups


CONTENT SPONSORED by CODE CLIMATE
Engineering metrics at every level: An engineering director’s guide
.jpg)
 (1).png)
CONTENT SPONSORED by MOOGSOFT
Making the most of observability
 (1).png)
CONTENT SPONSORED by HONEYCOMB
Why people are at the center of systems

CONTENT SPONSORED by CODE CLIMATE
How managers can use metrics to improve planning and run better standups

.jpg)
CONTENT SPONSORED by HONEYCOMB
Breaking down knowledge silos between engineering teams


CONTENT SPONSORED by LINEARB
Are daily standups still adding value?

CONTENT SPONSORED by PELOTON
Working across teams to champion accessibility

How keeping accessibility front of mind benefits everyone

CONTENT SPONSORED by SLACK
How enterprise organizations can respond when engineering goes wrong

.png)
CONTENT SPONSORED by MOOGSOFT
Thoughts on kickstarting observability

CONTENT SPONSORED by MOOGSOFT
The difficulties of observability
.png)
The culture of process

CONTENT SPONSORED by CODE CLIMATE
How Netlify, Splice, Code Climate, and more use engineering metrics
.png)

Developing a product-led innovation strategy for a software company

CONTENT SPONSORED by CODE CLIMATE
How to foster data-driven tech leadership
.png)
Outages are coming for you

Decision Making for Software Engineering Teams: Francesco Strazzullo in conversation


How to break out of the thread of doom

Every decision creates a policy

CONTENT SPONSORED by HAYSTACK
Preventing burnout while shipping faster
.png)
When planning long-term, favor accuracy over precision

CONTENT SPONSORED by LAUNCHDARKLY
Learnings from 'Weighing up the pros and cons of build vs. buy'

Finding your acorn: How to drive the change you want as an engineering leader

CONTENT SPONSORED by LOHIKA
Why the first two weeks are essential when building great software products

Leveling up your machine learning product by taking the leap to third-party
 (1).png)
CONTENT SPONSORED by DUFFEL
Write things down: transparent culture in minutes
.png)
Guiding principles for build vs. buy decisions
 (1).png)
CONTENT SPONSORED by ROLLBAR
How to make a build vs. buy decision for a new software solution
 (1).png)
CONTENT SPONSORED by LAUNCHDARKLY
Addressing the challenges of build vs. buy


CONTENT SPONSORED by CODE CLIMATE
What engineering leaders should be measuring

 (1).png)
The search for the best solution: third party or open source?
.png)
140,000 lines of code: why we built our own licensing system
.png)
Utilizing invisible forces to make better decisions in software design
.png)
Build vs. buy: know what you need, and know what you want

Reliability and more: preventing a crisis in engineering production

Making the perfect meeting
.png)
CONTENT SPONSORED by LAUNCHDARKLY
Ten things you need to know before making a build vs. buy decision


CONTENT SPONSORED by SLACK
Building a culture of quality in engineering teams

CONTENT SPONSORED by LAUNCHDARKLY
The long tail of product features
.png)
Making your meetings more effective
 (1).png)
.png)
Debugging engineering teams: Groundhog Day

CONTENT SPONSORED by EPSAGON
Using observability to accelerate the Engineering Flywheel

A thorough team guide to RFCs
.png)
CONTENT SPONSORED by LAUNCHDARKLY
Abandoning the build: when investing is the only way to scale

Demystifying the software engineering test pyramid

.png)
How to have meetings that don't suck (as much)

Don’t cross the Rubicon: engineering practices you don’t want to delay
.png)
CONTENT SPONSORED by LAUNCHDARKLY
To build, or to buy, that is the question

Empowering your engineering team with an effective decision-making process

CONTENT SPONSORED by PLURALSIGHT
Learnings from 'Deconstructing engineering velocity'

Running efficient, effective, and engaging retrospectives


The ‘flawed five’ engineering productivity metrics

The importance of effective status reports

CONTENT SPONSORED by PLURALSIGHT
Optimizing micro-feedback loops in engineering
.png)
CONTENT SPONSORED by SKYSCANNER
The art of self-organizing engineering teams

How to run a great incident post-mortem

Mapping the immovable objects in engineering projects

CONTENT SPONSORED by LAUNCHDARKLY
Software platforms: DIY vs. buying it

Leading your engineering team through an unexpected product pivot

CONTENT SPONSORED by LIGHTSTEP
A primer on the OpenTelemetry collector

How to avoid the growing pains of communicating at scale

CONTENT SPONSORED by LIGHTSTEP
What is observability and why should you care?

Estimating your way to success

Leading your engineering team with ‘experiments’ not ‘processes’

CONTENT SPONSORED by PLURALSIGHT
Recognizing and removing project bottlenecks


Designing cultural transformations

Accentuate the negative: making the non-perfect decision

Managing expectations on time estimates with probabilistic forecasting
.jpeg)
CONTENT SPONSORED by WORK & CO
Learnings from ‘Inspired: How to Create Tech Products Customers Love’

CONTENT SPONSORED by HONEYCOMB
Learnings from 'Observability in action'

CONTENT SPONSORED by CODE CLIMATE
Understanding your team’s velocity

 (1).png)
How to affect change without losing your job

CONTENT SPONSORED by LAUNCHDARKLY
Feature management: a low-risk way to deliver software faster
.png)
Embedding observability into your engineering culture
.png)
 (1).png)
CONTENT SPONSORED by CODE CLIMATE
How to measure and improve success in your engineering team

Sending gifts to future-you

CONTENT SPONSORED by CODE CLIMATE
Development metrics you should use (but don’t)
 (1).png)
Strategies for creating cultures of innovation in engineering teams

.png)
Observability and your business
.png)
Minimizing risks in code deployment


CONTENT SPONSORED by HONEYCOMB
Observability at scale

CONTENT SPONSORED by CODE CLIMATE
The health of your business depends on the health of your engineering team

CONTENT SPONSORED by CODE CLIMATE
The toolbox of engineering metrics for distributed teams

CONTENT SPONSORED by PEPSICO
Trusting the instincts of engineers to foster a culture of innovation

How to avoid alert fatigue

Career ladders aren't enough – you need a thoughtful promotion process, too

CONTENT SPONSORED by CODE CLIMATE
Using metrics to remove bottlenecks and support your team

CONTENT SPONSORED by OPTIMIZELY
Adopting an experimentation philosophy

CONTENT SPONSORED by PEPSICO
Assign problems (not work) to your teams to build extraordinary products

How to adapt your UI testing strategy to your product's stage

CONTENT SPONSORED by HONEYCOMB
Tell better stories with observability
.png)
CONTENT SPONSORED by CODE CLIMATE
How to develop engineering metrics with people, process, and tools in mind

CONTENT SPONSORED by GITLAB
The power of visibility to unblock collaboration
.png)
.png)
CONTENT SPONSORED by OPTIMIZELY
Building stronger teams with AB testing
Preventing process deadlock

CONTENT SPONSORED by TWITTER
Accessibility from the start

Imperfect Processes: Navigating the fuzzier parts


What makes a good process?

Scaling up sustainably through better processes

CONTENT SPONSORED by OPTIMIZELY
Establishing experimentation as a core part of your project workflow
.png)

A process is never done
.jpg)
.png)
Engineering with empathy
.jpg)
CONTENT SPONSORED by WORK & CO
Team Topologies: Manuel Pais in conversation
 (1).png)

CONTENT SPONSORED by OPTIMIZELY
The challenges of introducing product experimentation


A resignation can be an opportunity

Hypothesis-driven development

Creating efficient, accurate, software estimations
.jpeg)
.jpg)
Debugging engineering velocity and leading high-performing teams

Finding your groove: how to build your team’s operational cadence

Minimum Viable Business Continuity Management
.png)
Taking risks in production
 (1).png)

On Postponing Lead Dev New York and London
.png)
Designing effective OKRs


Learning from incidents: from 'what went wrong?' to 'what went right?'

Breaking down silos for better collaboration

.png)
Writing effective technical documentation

Strategies for making impossible decisions

Handling security issues as an engineering team

Scaling performance at the scale of Slack

Applying software engineering practices to improve people management

Building blocks for architecture governance with autonomous teams

Unlocking success: the components of high-performing teams

The race to Mach 2.0 at scale
 (1).png)
Using an 'architectural North Star' to align your engineering team with your organization

Observability that matters (and avoiding the kind that doesn't)
 (1).png)
Driving architecture alignment across a fully-distributed engineering workforce


Clear, concise and consistent: how to communicate and prioritize risks from the engineering team to the wider organization

Bridging the gap between engineering and customer success teams

The benefits of delivering imperfect software

Solutions for creating and managing inclusive projects

Travel through time and break free from rigid working cultures


How synergy between product and engineering can solve the problem of software estimation

Business as usual vs. innovation: how to get the balance right

Effective meeting facilitation techniques

Engage your engineers by giving them 10% time

Creating an effective process for on-call engineering teams

Taking a fresh look at setting objectives and key results for your engineering team

Planning for black swan events: how to create an effective panic team

Guiding your engineering team to self-organisation

Engaging your engineering team to achieve high performance faster
 (1).png)
Documenting and communicating architectural decisions
.png)
Principles for managing product quality

How to lead your engineering team through a period of change
.jpg)
Engineering teams work better remote-first

Using observability to detangle and understand production
.png)
Designing software to maximize developer productivity

Reclaiming the Spirit of Agile

Tackling Big, Impossible Projects

Using Agile Techniques to Build a More Inclusive Team

CI/CD For Humans: Empathy as the Foundation for Effective Deployments

Strategies for reducing the fragility of your systems

Building a culture of continuous delivery

Collaborative debugging on engineering teams
.png)
How to Design Systems and Processes Teams Actually Follow

Crafting fun and productive Sprint retrospectives

Failing smarter and learning faster in engineering

How to estimate as as an engineering leader
.jpg)
Engineering retrospectives - Look back, move forward
.jpg)
Creating processes that don't impede autonomy

Working backwards from the customer

Dealing with overheads as an engineering leader
.png)
Seven key considerations in early development

Adapting testing for engineers

How performance is everyone's job

Plug in to LeadDev
Want to get regular updates on all things LeadDev? Sign up to our mailing list
To find out more about how your data is handled check out our Data Promise

