https://www.code4it.dev/cleancode-tip/ Recent content in Cleancode-tips on Code4IT Hugo -- gohugo.io Tue, 15 Nov 2022 00:00:00 +0000 https://www.code4it.dev/cleancodetips/coherent-levels-of-abstraction/ Tue, 15 Nov 2022 00:00:00 +0000 https://www.code4it.dev/cleancodetips/coherent-levels-of-abstraction/ Don’t let the reader get lost in the code details! https://www.code4it.dev/cleancodetips/dry-or-not-dry/ Tue, 11 Oct 2022 00:00:00 +0000 https://www.code4it.dev/cleancodetips/dry-or-not-dry/ DRY is a fundamental principle in software development. Should you apply it blindly? https://www.code4it.dev/cleancodetips/exceptions-instead-of-null/ Tue, 27 Sep 2022 00:00:00 +0000 https://www.code4it.dev/cleancodetips/exceptions-instead-of-null/ In case of unmanageable error, should you return null or throw exceptions? https://www.code4it.dev/cleancodetips/f-i-r-s-t-unit-tests/ Tue, 26 Jul 2022 00:00:00 +0000 https://www.code4it.dev/cleancodetips/f-i-r-s-t-unit-tests/ Good unit tests have some properties in common: they are Fast, Independent, Repeatable, Self-validating, and Thorough. In a word: FIRST! https://www.code4it.dev/cleancodetips/avoid-subtle-duplication/ Tue, 28 Jun 2022 00:00:00 +0000 https://www.code4it.dev/cleancodetips/avoid-subtle-duplication/ Duplication is not only about lines of code, but also about data usage and meaning. You should avoid that kind of duplication. https://www.code4it.dev/cleancodetips/tests-should-be-readable-too/ Tue, 24 May 2022 00:00:00 +0000 https://www.code4it.dev/cleancodetips/tests-should-be-readable-too/ Should you write your tests with the same care you write the production code? Of course you should! But what does it mean? https://www.code4it.dev/cleancodetips/too-many-imports/ Tue, 19 Apr 2022 00:00:00 +0000 https://www.code4it.dev/cleancodetips/too-many-imports/ 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. https://www.code4it.dev/cleancodetips/good-comments/ Tue, 22 Mar 2022 00:00:00 +0000 https://www.code4it.dev/cleancodetips/good-comments/ 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. https://www.code4it.dev/cleancodetips/aaa-pattern-for-tests/ Tue, 22 Feb 2022 00:00:00 +0000 https://www.code4it.dev/cleancodetips/aaa-pattern-for-tests/ 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. https://www.code4it.dev/cleancodetips/avoid-mental-mappings/ Tue, 25 Jan 2022 00:00:00 +0000 https://www.code4it.dev/cleancodetips/avoid-mental-mappings/ Mental mappings are a good way to write shorter code that you, and only you, can understand. Prefer clarity over brevity! https://www.code4it.dev/cleancodetips/consistent-of-parameters/ Tue, 30 Nov 2021 00:00:00 +0000 https://www.code4it.dev/cleancodetips/consistent-of-parameters/ Following a coherent standard, even for parameters order, helps developers when writing and, even more, reading code. How to do that? https://www.code4it.dev/cleancodetips/too-many-method-arguments/ Tue, 02 Nov 2021 00:00:00 +0000 https://www.code4it.dev/cleancodetips/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? https://www.code4it.dev/cleancodetips/use-same-name-for-same-concept/ Tue, 05 Oct 2021 00:00:00 +0000 https://www.code4it.dev/cleancodetips/use-same-name-for-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! https://www.code4it.dev/cleancodetips/smaller-functions-smarter-exceptions/ Tue, 17 Aug 2021 00:00:00 +0000 https://www.code4it.dev/cleancodetips/smaller-functions-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! https://www.code4it.dev/cleancodetips/use-pronounceable-names/ Tue, 20 Jul 2021 00:00:00 +0000 https://www.code4it.dev/cleancodetips/use-pronounceable-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. https://www.code4it.dev/cleancodetips/principle-of-least-surprise/ Tue, 22 Jun 2021 00:00:00 +0000 https://www.code4it.dev/cleancodetips/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. https://www.code4it.dev/cleancodetips/choose-meaningful-names/ Tue, 25 May 2021 00:00:00 +0000 https://www.code4it.dev/cleancodetips/choose-meaningful-names/ Choosing meaningful names takes time! Time spent finding good names is time saved trying to figure out what you meant.