Showing posts with label technical debt. Show all posts
Showing posts with label technical debt. Show all posts

Thursday, May 29, 2025

What Running Your Application Can Tell You About Its Quality?

I mostly work with long-lived applications that undergo continuous modification. Evaluating their quality by simply glancing at the code would be rather naive—there are multiple dimensions to consider for a more comprehensive assessment. Of course, code quality matters, but there are several other checks I perform. Today, I want to share a subset of those checks—focused specifically on application execution—and what insights they can offer.

Tuesday, May 20, 2025

Do You Understand the Debt You Have to Pay?

I was fortunate to start my career with people who truly cared about code quality. Early on, I learned why this matters and how continuous attention to quality positively impacts customer satisfaction. This experience made it natural for me to improve legacy code and constantly seek further enhancements.

However, at the beginning of my journey, my perspective was narrow—I saw only the code. So, my efforts focused solely on refactoring. Fast forward to today, I've learned that there are many more ways to improve software. There are also several strategies you can explore to choose the right approach for your situation.

Friday, November 29, 2024

Friday, February 16, 2024

Wednesday, March 29, 2023

How to make good programming decisions?

I like the idea, the structure, and all the suggestions the authors shared with us. 

The book describes various problems we may face during daily work, how to tackle them, and how to decide which solution brings us the most benefits.

Tuesday, March 7, 2023

You can't stop degradation

There are a lot of patterns, techniques, and approaches that help to write understandable code and build an architecture possible to change. 

The difficult aspect of development is the fact that whatever you will do, the code and the architecture will degrade. 

The question is, why regardless of tries and efforts we cannot change that? 

Thursday, February 23, 2023

Infinite work

Improving legacy applications is something I really like to do. Sometimes it is about changing infrastructure, slicing down the monolith, establishing a better architecture for the code base(s), and sometimes it is about all these things. And the work is not only about technical aspects. You need to make sure a supportive culture is in place. A culture that helps continuously pay off technical debt. 

Both tasks are challenging and long-term in nature. You can neither change the architecture nor build an appropriate environment within a month or so. In most cases, this is a plan for years.

And this can be overwhelming.