Estimating quality of a codebase

twitter logo github logo ・1 min read

Just how?

You've just got a new job, or a new gig. You are now working on an existing software with a codebase already in place. You start reading the code to understand the code and check its quality.

  • What do you look for when estimating the quality of the code written?
  • What are some red flags that would give you an indication that something is wrong?

Really curious about what you think.

twitter logo DISCUSS (1)
markdown guide
 

I first look at the code style

  1. is it consistent
  2. how big are the units (i.e. type/methods/files/..)
    • are they small

Then I look at the pre-commit phase of the project

  1. is there a simple and quick build/verify process
  2. is there basic static analysis
  3. how many unit tests are there

A 'no' to any of these is a red flag.

Classic DEV Post from Dec 21 '18

What is the hardest thing about learning to code?

Coding is hard. I struggled to learn for the first several years because I wasn't active within the dev community. What was the hardest thing you've experienced on your coding journey?

Damien Cosset profile image
French web developer mostly interested in Javascript and JAVA

DEV is sort of like Medium, but it's open source and 100% focused on developers.

Now reaching over 3 million visitors per month, it's the fastest growing software development community in the world.

It's free, devoted to the open web, and will never have popups or a pay wall.

Get Started Now