Clean Code Tip: Methods should have a coherent level of abstraction
Don't let the reader get lost in the code details!
Clean Code17 posts
Clean Code Tip: DRY or not DRY?
DRY is a fundamental principle in software development. Should you apply it blindly?
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?
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!
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.
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?
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.
Clean Code Tip: Not all comments are bad
Is it true that we should always avoid comments in our code? In my opinion, no: let's see when adding comments is not only good but necessary.
Clean Code Tip: AAA pattern for tests: why is it important?
The most important trait of Tests? They must be correct. The second one? They must be readable. The AAA pattern helps you write better tests.
Clean Code Tip: Avoid mental mappings
Mental mappings are a good way to write shorter code that you, and only you, can understand. Prefer clarity over brevity!
Clean Code Tip: Keep the parameters in a consistent order
Following a coherent standard, even for parameters order, helps developers when writing and, even more, reading code. How to do that?
Clean Code Tip: Don't use too many method arguments
When a function has too many parameters, it's clear that something is wrong. But... why? What are the consequences of having too many parameters?
Clean code tip: use the same name for the same concept
Smaller functions help us write better code, but have also a nice side effect: they help us to understand where an exception was thrown. Let's see how!
Clean code tip: small functions bring smarter exceptions
Smaller functions help us write better code, but have also a nice side effect: they help us to understand where an exception was thrown. Let's see how!
Clean code tip: Use pronounceable and searchable names
Two of the operations you often do with your code is to discuss it, or perform a search over it. So using good names will help in both situations.
Clean code tip: Principle of Least Surprise
The Principle of Least Surprise is a simple principle that helps you writing clear, obvious code: this helps other developers foresee what a component does without worrying of unexpected behaviors.
Clean code tip: How to choose meaningful names?
Choosing meaningful names takes time! Time spent finding good names is time saved trying to figure out what you meant.