What are Clean Tests? The Clean Code rules apply equally to the production code and the test code. Therefore you should clean your test code every time when you write or modify tests. As a result, you will begin to notice opportunities for performing refactoring right after adding a new test into your legacy code.…
What style should Clean Code be written in? Clean Code is not always object-oriented. Sometimes it will be written in procedural style. So what style is better: procedural or object-oriented? We should perform the choice under given conditions which facilitates its development and readability – in accordance with the principles of Clean Code. Below is…
This time I would like to take a look at how teams support code quality in their software development processes. I will analyze some stages of such processes and check how the explicit presence of individual steps in Kanban Board / Scrum Board can supports the maintenance of Clean Code in teams and organizations. Below…
This article complements the subject of cleaning code by explaining connections between the Refactoring Pyramid and Uncle Bob’s SOLID principles. We will see how each of SOLID rules acts as basement for each level in the pyramid. We will end up at the top level of architectures. In my previous post I explained levels of…
In this post I would like to show you “Refactoring Pyramid in Practice” to clean your code. In order to do so, I will follow the sequence of small transformations like in one of refactoring examples in “Refactoring to Patterns” book by Joshua Kerievsky. The sample will show refactoring to Interpreter. Anyway I’ve experienced the…
General principles, patterns – at one side allow us to tidy up knowledge, use common approach when solving certain kind of problems. On the other side they might impede our creativity and inspiration. But even then we have something we can base on even if we want to reject it and invent something better. Pyramid…
