Name: Figuring Out What Matters In A Codebase
Uploaded: 2024-03-18T17:55:49+00:00
Duration: 5 min 48 s
Description: In a large codebase, the code will follow the Pareto Principle (the 80/20 rule): 20% of the components account for 80% o

Figuring Out What Matters In A Codebase

In a large codebase, the code will follow the Pareto Principle (the 80/20 rule): 20% of the components account for 80% of the impact. So your goal as the engineer is to spend most of your time on the 20% of code that matters to the business and matters to your coworkers.

How do you figure out where that 20% comes from?

- Talk to people
- Use blames to find hotspots
- Look for patterns in code reviews
- Look at past alerts and what triggered them

In a large codebase, the code will follow the Pareto Principle (the 80/20 rule): 20% of the components account for 80% o

Code review is one of the most common and powerful ways for software engineers to learn. On top of increasing code quality, it builds engineering culture within a team.

Code review can catch coding mistakes and design flaws before the code reaches production

A good code review process is needed to catch bugs, increase maintainability, and guarantee a high velocity future contributors.

Code review ensures high quality software that is maintainable for the lifetime of the code

With how often software engineers change teams, it's crucial to be efficient at this. Learn how to get coding within a new codebase fast, build the proper relationships, and hit the ground running in general.