The Accuracy of Code, the Wisdom of the Samurai: Mastering the Path of Software Development
Domain Driven Design, also known as DDD, is a software design technique that employs the Business Domain as a guiding principle and models it as a means of communication between business experts and technology professionals.
As Tolkien wrote, “One Ring to rule them all, One Ring to find them, One Ring to bring them all and in the darkness bind them”. Software architecture arise when creating a project with the intention of addressing all current and anticipated code organization problems. However, some programmers tend to use the same architecture that worked for them in previous projects, assuming it will work in the current one, but that is not always correct.
One of the skills a samurai developer must develop is knowing how to apply refactoring in their day-to-day work. When starting the software development journey, one tends to follow the axiom “If it works, don’t touch it, or it might break.” This fear naturally arises from inexperience and the context in which one works. However, I believe that as professionals, we must pursue the ideal of continuous improvement, and to achieve that, we must overcome that fear. It’s good to have a protocol on how and when to act to produce better code.
SOLID is an acronym for a set of object-oriented programming principles described by Robert C. Martin.
These are not immutable rules or absolute truths; rather, they are good advice. They serve to name concepts and not just rely on the “feeling” of bad code. They aim to categorize these “feelings” into specific recommendations.
As a junior programmer in object-oriented languages, I learned that extension (or subclassing) eliminates duplicate code. Two subclasses with the same parent and common behavior move that code to the parent, removing it from the children. It became a code reuse mantra, but also one of my early programming vices.
