By Nick Pettit
What is good code?
We know when we spot bad code. But because good programming is harder to define, it’s difficult to know you’ve actually created quality.
In my experience, there are two great questions that can indicate code quality:
- When you’re working on a team, do others easily understand your code’s logic?
- When changes are required, is it a quick and straightforward process?
If it’s difficult to explain code to others or if lots of things break when making changes, then chances are the code is bad. Fixing these problems often involves finding sensitive solutions in the context of a particular environment.
Read more here: Treehouse
