Do you know the concept of “code smell”? It was invented in the late 1990s (before I worked in IT, when I was just a boy, breaking computers at home) to represent “any characteristic in the source code of a program that possibly indicates a deeper problem”. What is and is not a code smell is subjective, and varies by language, developer, and development methodology. However, I often feel that there are some consistent ways to be able to review projects to understand the “smell” of them:
You can often cover up 1 or 2 but you can almost always be assured that projects that have all of these covered are likely to be better, regardless of language or framework being used. Is it because these items best show the culture around software/solution development?
Connect on LinkedIn. Follow me on Twitter. Grab the RSS Feed