Clean Code Tip: Methods should have a coherent level of abstraction

Don’t let the reader get lost in the code details! Continue reading

Clean Code Tip: DRY or not DRY?

DRY is a fundamental principle in software development. Should you apply it blindly? Continue reading

Clean Code Tip: throw exceptions instead of returning null when there is no fallback

In case of unmanageable error, should you return null or throw exceptions? Continue reading

Clean Code Tip: F.I.R.S.T. acronym for better unit tests

Good unit tests have some properties in common: they are Fast, Independent, Repeatable, Self-validating, and Thorough. In a word: FIRST! Continue reading

Clean Code Tip: Avoid subtle duplication of code and logic

Duplication is not only about lines of code, but also about data usage and meaning. You should avoid that kind of duplication. Continue reading

Clean Code Tip: Tests should be even more well-written than production code

Should you write your tests with the same care you write the production code? Of course you should! But what does it mean? Continue reading

Clean Code Tip: Avoid using too many Imports in your classes

Having too many ‘using’s, or imports, is a good indicator that your class does too many things. You should work to reduce the number of dependencies of a class. Continue reading