The Accuracy of Code, the Wisdom of the Samurai: Mastering the Path of Software Development
Programming, encompasses a diverse range of topics and discussions related to the art and science of computer programming. It serves as a platform to explore programming languages, development methodologies, coding best practices, and emerging technologies. It provides insights into programming concepts, techniques, and tools used to create innovative software solutions. Through tutorials, code snippets, case studies, and industry trends, the programming category aims to educate and empower readers, whether they are beginners seeking to learn programming fundamentals or experienced developers looking to expand their knowledge.
Fluent interfaces are a term coined by Martin Fowler and Eric Evans. It’s a design approach in software development that aims to create an object-oriented API. The goal is to make the API more readable by making method calls more expressive and easier to understand.
Writing unit tests correctly is as important as coding features. To achieve this, certain principles help ensure that unit tests are easy to use and modify when adding new test cases. The FIRST principle, which stands for Fast, Independent, Repeatable, Self-validating, and Timely, is a guide for us in this endeavor
Clean Code is the set of principles for writing code that is easy to understand, maintain, and modify. Below, we will explore the most important principles that are vital to know as the foundational skills of every good samurai developer.
Mike Cohn introduced the concept of Testing Pyramid in his book “Succeeding with Agile.” It is a visual metaphor used to categorize tests into different layers, each with specific characteristics.
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.
