Programming is an art of mathematical precision - Sotiris Fanou.

The Importance of Code Comments and Documentation: A Pillar of Software Engineering Throughout my professional life, I have encountered thousands upon thousands of lines of code with no comments at all. A growing number of developers today believe that code comments and documentation are outdated practices, relics of an earlier era in programming. Some argue that well-written code should be self-documenting and that comments are redundant or even misleading. While there is some merit to the idea of writing expressive, clean code, the notion that comments and documentation are unnecessary is seriously flawed. It disregards one of the foundational principles of software engineering: abstraction . Abstraction and the Role of Comments In software engineering, abstraction is the purposeful hiding of certain details of a system in order to highlight others. According to Liskov and Guttag (2001), abstraction simplifies systems by modeling complex be...

The Most Common Mistake Software Development Organizations Make Over the course of my career as a software engineer and consultant, I have worked with a wide variety of organizations, from nimble startups to sprawling enterprises. Despite differences in size, industry, and tools used, I have noticed a recurring and troubling pattern: a majority of these organizations consistently neglect one of the most fundamental aspects of software development, maintaining structured, well-designed, and well-documented code. I estimate that at least two-thirds of the organizations I have worked with make this same critical mistake. They focus almost exclusively on output and delivery deadlines, often under the umbrella of Agile methodologies, but fail to ensure that the code being produced is clean, maintainable, and well-understood. The Consequences of Neglecting Code Quality When teams skip esse...

Bottom-Up Design: The Best Way to Refactor Messed-Up Code Throughout my career in software development, I've encountered a recurring challenge: inheriting codebases that are messy, disorganized, and fragile. The common impulse in such situations is to suggest a full rewrite. While this might sound appealing at first, it is usually the wrong move. The smarter, more sustainable approach is to introduce design to the existing mess. Not by imposing a grand vision from above, but by letting the code itself guide you. This is what I call bottom-up design , and it is, in my opinion, the best way to refactor a problematic codebase. Why Rewriting Often Fails Rewriting an existing system from scratch is a massive undertaking. You lose all the small decisions and hidden logic that exist in the current system. Even worse, you now have to develop and maintain two systems in parallel: the old one that’s still in use, and the new one trying to catch up. As...

Keep It Simple, Stupid (KISS): Why Simplicity in Code is a Sign of Great Engineering As software engineers, we often face a dilemma: should we showcase our skills by writing intricate, highly optimized, and sometimes cryptic code, or should we prioritize clarity, simplicity, and ease of understanding? Too often, developers lean toward the former, believing that writing complex code demonstrates sophistication and intelligence. However, true craftsmanship in software development lies in simplicity, maintainability, and empathy for the next person who will read your code, which might be you six months from now. The Essence of KISS The KISS principle, originally coined by the U.S. Navy in 1960, stands for "Keep It Simple, Stupid." It advocates for simplicity as a core design principle, warning against unnecessary complexity. In software development, this translates to writing code that is straightforward, easy to read, and easy to modify. Code si...

  Author: Sotiris Fanou Many software development teams jump directly to implementation skipping design. This practice produces inflexible code with no structure, which is difficult to change and maintain. For example, if someone wants to fix a bug or add a new feature it is like trying to reach an unknown destination without a map. It is very difficult to know where to change the code and if this will be affecting something else elsewhere. Additionally, numerous programmers disregard the readability of the code they write. One reason could be the fact that most developers work within tight schedules and their priority is to finish by the deadline rather than write clean code. Unfortunately, many programmers think that if their code is unreadable this will be a problem for someone else in the future and it will not affect them. Therefore, a lot of code out there is not structured, difficult to read and difficult to be amended and maintained. Very few developers work on creating bra...