In the past few years, many blog posts and articles have been written that present the Clean Architecture, as it has been presented by Robert C. …

In a previous post, we discussed the importance of writing expressive code. Expressiveness makes our code easier to follow and understand. New developers can add new features or fix defects without spending too much time trying to decrypt what the original authors had in their mind or why they ended…

A year ago I had an interesting discussion with my best friend Alex about code reviews. He said that when he does a code review, he always starts with the tests. …

In this post, we will discuss a possible problem in the code that can be identified from the history of the source code. We call this “smell” cumulative code. The term cumulative code is used in this post to describe the code that changes mostly by additions and rarely by…

What is a flaky test? Don’t you hate when things are not deterministic? A test should constantly pass or fail if no code changes are applied. We should run our tests against a controlled environment and make assertions against an expected output. We may use a test fixture as a baseline for running tests. A…

Have you ever seen code like this? I bet you have (or you will see at some point in your career). Code like this exists in some legacy systems and is often very old. Most likely, you don’t feel very good when you see code like this. The problem…

In most projects, the amount of work is so large that one person alone cannot handle. Thus, we form teams to handle the workload. A team is more than just a group of people. It is an organization. The team members are the components of this organization and usually affect…

The problem Let’s assume that we have three components: A, B and C. Another component, Main, has a dependency to A and wants to call a method foo that belongs to component C: a.getB().getC().foo(); The previous snippet is equivalent to: B b = a.getB(); C c = b.getC(); c.foo(); The problem…

Testing is one of the few ideas that really changed my perception about software. It has become part of my everyday coding routine and is something that once you learn using it, it affects the way you write software. Developing a software without testing is the same as developing software…