登录查看更多内容

How do you deal with technical debt and code smells that result from insufficient or ineffective refactoring?

由人工智能和领英社区提供技术支持

Technical debt and code smells are common challenges for software engineers who work on complex and evolving projects. They refer to the accumulated costs and consequences of suboptimal design and implementation decisions that affect the quality, maintainability, and performance of the code base. Refactoring is the process of improving the internal structure and readability of the code without changing its external behavior or functionality. It is a vital practice to reduce technical debt and code smells, but it can also be insufficient or ineffective if done poorly or inconsistently. In this article, you will learn how to deal with technical debt and code smells that result from insufficient or ineffective refactoring, and how to apply some best practices to improve your refactoring skills and outcomes.

此文章中的业界达人

由社区从 2 条内容中精选。了解更多

Jonah Andersson

??Inspiring tech with genuine heart? Developer of the Year ? Microsoft MVP - Azure ? Cloud DevSecOps Engineer Architect…

1 What is technical debt?

Technical debt is a metaphor that compares the trade-offs and compromises that software engineers make when developing software to the financial obligations and interests that borrowers incur when taking loans. Technical debt can be intentional or unintentional, and it can have positive or negative effects depending on the context and the goals of the project. However, if technical debt is not managed properly, it can lead to increased complexity, reduced quality, lower productivity, higher risks, and more defects in the code base. Technical debt can also manifest as code smells, which are indicators of potential problems or bad practices in the code that make it harder to understand, modify, or extend.

添加您的观点

Jonah Andersson

??Inspiring tech with genuine heart? Developer of the Year ? Microsoft MVP - Azure ? Cloud DevSecOps Engineer Architect ? Microsoft Certified Trainer ? MCT Regional Lead? Intl Speaker ? Author of Learning Microsoft Azure
举报内容
Technical debt if not handled and prioritized can lead to impacting consequences in any project. It gives the disadvantage of decreased agility by slowing development workflow of teams in an IT organization. As tech debt accumulates, it is harder to introduce new features, fix bugs, or make changes. The development process becomes more complex and time-consuming. Just like financial debt, technical debt accumulates interest over time. The longer it persists, the more effort and resources are required to maintain and improve the software. Code that is poorly designed or lacks proper documentation becomes a burden for developers. It often leads to code quality issues, increased bugs, reduced stability, and poor overall software quality.

已翻译

赞

2 What is refactoring?

Refactoring is the practice of improving the internal structure and readability of the code without changing its external behavior or functionality. Refactoring aims to make the code more consistent, coherent, expressive, modular, and testable, and to eliminate or reduce technical debt and code smells. Refactoring can be done at different levels of granularity, from small changes in a single method or class, to large-scale transformations across multiple modules or systems. Refactoring can also be done manually or automatically, using tools and techniques such as code analysis, testing, version control, and design patterns.

添加您的观点

3 Why is refactoring insufficient or ineffective?

Refactoring is not a panacea that can solve all the problems and challenges of software engineering. It may be inadequate or ineffective due to a lack of time, resources, or motivation to refactor the code regularly or thoroughly. Additionally, knowledge, skills, or standards may be insufficient to refactor the code correctly or efficiently. Furthermore, feedback, testing, or verification may be lacking to ensure that refactoring does not introduce new errors or regressions. Moreover, coordination, communication, or collaboration among the team members or stakeholders who are involved or affected by the refactoring may be inadequate. Lastly, there may be a lack of vision, strategy, or goals to guide the refactoring process and prioritize the areas and aspects that need improvement.

添加您的观点

4 How to deal with technical debt and code smells?

In order to effectively manage technical debt and code smells, a proactive and systematic approach is necessary. This includes identifying and measuring the technical debt and code smells in the code base, using tools such as code analysis, code reviews, and code coverage. It is also important to evaluate and prioritize the technical debt and code smells based on their impact and urgency. This can be done by considering criteria such as business value, technical risk, user satisfaction, and developer productivity. Additionally, refactoring activities should be planned and executed with methods such as agile development, test-driven development, pair programming, and continuous integration and delivery. Once the refactoring process is underway, it's important to monitor and control the outcomes with tools such as version control, testing, debugging, logging, and performance analysis. Finally, feedback and lessons learned from the refactoring process should be used to review and improve the refactoring practices.

添加您的观点

Dylan Brown

Software Consultant and Owner at Interfuse LLC
举报内容
Often taking this approach doesn't happen. There are many reasons, one of which being that it can take a lot more code and time to correctly prepare for good code. If the goal is to get something out the door then often best practices are considered too expensive at first. As a result there often comes the stage when technical debt has built up. In those situations it can be better to refactor in a couple different ways or build a new product altogether. 1. Piece by piece. Refactor the pieces that need new features added to them. Good for modular code. 2. Adapter: code that acts like a compatibility layer to allow new good code to interact with spaghetti code. 3. Build new product while phasing out the old. Good for large and old codebase.

已翻译

赞

5 How to improve your refactoring skills and outcomes?

If you want to improve your refactoring skills and outcomes, you need to make a conscious effort to learn and apply some best practices. Refactoring code should be done in small, frequent increments instead of large, infrequent batches. Additionally, it’s important to refactor the code as soon as possible rather than postponing or avoiding it. Every refactoring should have a clear and specific purpose, and it should be done with respect, care, confidence, and trust. Refactoring with haste or negligence or out of fear or doubt can lead to poor outcomes.

添加您的观点

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Software Engineering

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How do you deal with technical debt and code smells that result from insufficient or ineffective refactoring?

1

2

3

4

5

6

1 What is technical debt?

2 What is refactoring?

3 Why is refactoring insufficient or ineffective?

4 How to deal with technical debt and code smells?

5 How to improve your refactoring skills and outcomes?

6 Here’s what else to consider

Software Engineering

给文章评分

感谢您的反馈

更多Software Engineering相关文章

更多相关阅读内容