In software development, I believe engineering health is a term that deserves attention and strategic focus. Sustainable software development is not just about the code we write or the features we ship; it’s about a proactive commitment to the underlying health of our engineering processes. Allocating 20-25% of our resources to engineering health has always been my preference. At this point, I feel like it is a…
Leave a CommentTag: software maintenance
Legacy software often comes with historical decisions, prior mistakes, and previous successes. Engaging with these systems isn’t merely a journey through old code, but a rich learning experience waiting to be unwrapped. Let’s go into the not-so-obvious perks of working with legacy systems. Gaining Insights Mistakes, they say, are the portals of discovery. When we venture through legacy systems, we’re exploring the mistakes of the past. They…
Leave a CommentThroughout the years I have worked on many software projects. In most of them, the code header included the author’s name. At first, it seemed natural to have the author’s name. In time I realized having a code author in the header is irrelevant, discouraging, and often negative. In many projects, the header file is dictated by the coding style for the company or the project itself.…
Leave a CommentDuplicate code isn’t something we want in our code for various reasons. Clearly, the straightforward reason is changing the duplicate code. You need to find the same code piece everywhere it’s used and replace them all. A more complicated reason is the proper use of design principles [1]. Although it’s hard to argue against any of the reasons, I still think duplicate code can be fine. Duplicate…
1 Comment