Estimating quality of a codebase

Damien Cosset - Jun 9 '19 - - Dev Community

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.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .