Have you ever tried to find the root of a problem instead of constantly fighting the consequences? When we work on eliminating the symptoms without knowing the cause – the problem comes back like a boomerang. So where is the reason for the growing technical debt and missing code refactoring? Why don’t we refactor into…
If you haven’t read the blogs about history of Refactoring Pyramid that help to keep Clean Code read below articles first. Sometimes people ask the question why I’ve chosen the pyramid as a way in which I described my approach to refactoring. There are many other concepts on how and when to refactor. Each of…
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…
Competitive refactoring definition Refactoring is nothing more than a way and a technique to keep the balance enabling the continuation of all activities. But what is the balance? Emotional one? Certainly also, because it is easier for us when the code we write is readable and testable. We are also more comfortable when the code…
Recently I wrote an article about autonomy in a nutshell. It is based on setting up boundaries of responsibilities between teams and based on trust into others that they know how to deal with their own issues the best. This entails that they do receive right to make decisions regarding their areas of responsibility in…
In case of struggling with care for code quality (most likely with lack of time to do this) then high time to ask two below questions comes Who is responsible for quality of code Who decides how or when the team can find time for quality Assuming the answer to the first question is obvious…
