#refactoring

#refactoring

One pervasive assumption in a stubborn codebase is that there's only one way to talk to the database, limiting potential changes and upgrades.

When you write tests, you might create a large setup method that initializes various objects. This leads to unnecessary overhead if only one test uses all these objects.

"The main point of the article is to replace simplistic getters with behavior-rich methods that encapsulate the operations pertinent to the internal state."