More code smells for your reading pleasure

What is refactoring? Why do we go through the trouble of improving code that works?

Warning: Setters Considered Smelly

In this article, I want to share my practice and tips about refactoring on Compose.

How to debug your code the easy way

Working effectively with legacy code is no easy task. I’ll try to describe the concept and my experience working effectively with legacy code.

"Don't touch it, it works" is problematic. It leads us down a bad path. How do you handle a project that held that policy for years?

It smells because there are likely many instances where it could be edited or improved.

Explore strategies to tackle technical debt and enhance code quality. Learn to balance business goals with refactoring for long-term success.

Jamal stared at his screen, perplexed by the convoluted SQL query he was trying to decipher.

In this episode, Maximiliano Contieri helps us understand the longstanding tension between academia and industry from an insider’s perspective.

Don't use metaprogramming. It is not that cool.

Discover the importance of verifying file copies to prevent silent modifications and uphold software principles like the Least Surprise and Fail Fast principles

Avoid mutable getters to protect your code's integrity and encapsulation. Learn how to return immutable copies in Java for safer and more predictable coding

Pass essential attributes during object creation to reduce mutability and eliminate getters and setters.

Overengineering complicates your code with unnecessary abstractions and complexity. Learn how to simplify your code using the KISS principle.

In this series of articles, I would like to share my practical experience implementing Domain-Driven Design to a complex legacy project.

Eliminate unused functions, constants, and "just-in-case" code.