66 Stories To Learn About Technical Debt

Let's learn about Technical Debt via these 66 free stories. They are ordered by most time reading created on HackerNoon. Visit the /Learn Repo to find the most read stories about any technology.

1. Badly Designed Authorization Is Technical Debt

Hard-coded authorization leads to technical debt. Decouple your authorization decisions to be a more effective business.

2. Fight Technical Debt With These 10 JetBrains Extensions

I see many Engineering teams under huge pressure to build fast and often lacking time to fix and clean up their codebase.

3. How To Manage Technical Debt With the Barbell Strategy

The barbell strategy is a valuable approach for companies looking to balance the need for innovation and stability in their software systems.

4. Bad Codebases Shoo Developers Away

In this software engineering survey, we learn about the state of technical debt and technical hiring.

5. Check Out This Panel Discussion on Technical Debt

Tackling technical debt is a challenging, yet integral part of every engineer and engineering leader’s role.

6. Technical Debt and the Obfuscation of Truth

"Tyranny without the tyrant" - Hannah Arendt

7. 5 responsibilities of a Tech Lead and 17 Metrics to Track Their Performance

Tech lead, team lead, software architects, and engineering managers — as any developer already knows, naming is hard. Throughout the industry, those roles are as fuzzy as their responsibilities.

8. Engineers Spend 33% of Their Time Dealing with Technical Debt

There are many ways in which technical debt costs us money: lost deals, customer churn, employee churn, lawsuits, and more. However, there are a couple of issues that are more important than others: engineering time, morale, and the missed revenue from software delays.

9. Technical Debt Isn't Technical at All; It's Not Even Debt

People assume they know what technical debt is, however, almost no-one understands it.

10. Technical Debt: Where it Comes From and How to Manage it

Technical debt, approaches to its rapid repayment, and minimization on previous and current projects.

11. Is Technical Debt Actually Bad Debt?

Release early, release often — just don’t forget to refactor ;)

12. Technical Debt Horror Stories Shared by Developers (Part 1)

I asked a bunch of developers to share some of their horror stories of technical debt.

13. How to Lead Your Team's Technical Debt Management

Delivery speed results in cost reduction; confidence enables speed; confidence requires quality.

14. 6 Examples to Differentiate Desirable Technical Debts From Undesirable Ones

Technical Debts have been in the center of software engineers debate for quite some time. Not only its analogy to financial terms has been discussed, but also the different contexts and aspects a debt contains.

15. The Bus Factor Score: How Many Team Members Can get Hit By a Bus Before the Team Fails?

What happens if your development team is hit by a bus? A short explanation of the Bus Factor and how to hold its score at safe levels and why you should.

16. How To Improve Developer Effectiveness With Feedback Loops

At it's heart, software engineering is a series of feedback loops.

17. 3 Main Types of Technical Debt and How to Manage Them

The 3 main types of technical debt are: deliberate, accidental/outdated design, and bit rot.

18. Get Rid Of Technical Debt In 10 VS Code Extensions

Many engineering teams get stuck and cannot ship quality software fast because of technical debt. The best engineering teams I've talked to use the right tools.

19. 7 Signs You Need Help With IBM i Application Modernization

Every company needs to make sure its apps can keep up with the modern-day technological requirements and market expectations through application modernization.

20. Product Managers Can Avoid Delays By Reducing Technical Debt

PMs are ideally placed to create a workplace culture around preventing and responding to technical debt. Here are 7 actionable strategies to help PMs.

21. The Upcoming Low Code Disaster That No One Is Talking About

You can't today browser any well-known tech news website or open YouTube without seeing Low Code Article or Ad.

22. 6 Resources That'll Make You Better at IBM i Modernization

While the launch of the IBM i in 1988 seems like a lifetime ago, it is still responsible for powering mission-critical business applications.

23. Debunking The Myths of Application Modernization

Before the pandemic, businesses sought ways to innovate and become more agile, without increasing costs, as an advantage over competitors. But, COVID-19 has made these outcomes a prerequisite for survival in any competitive market.

24. Hit That Technical Debt, Now

It probably comes as no surprise many are facing furloughs and lay-offs. If you are in an affected industry, but work in their IT departments or otherwise support tech for some entity, you may have dodged the first wave. The remote work exodus generated a lot of work.

25. Technical Debt is Eating The World

The concept is simple: due to a lack of resources, people sometimes do not address a problem correctly when shipping a new feature or fixing a bug. This debt must be repaid (e.g. the problem needs to be addressed correctly) or the debt will accumulate and impact the software development in the future.

26. DevOps and Technical Debt: A Guide for Businesses

Let’s see how organizations should entwine some essential practices into various phases of the DevOps lifecycle to address the technical debt challenges.

27. Technical Debt Management is Important: You Can’t Keep Building on a Broken System

Every software company has some amount of technical debt, which is additional development work created in the long-term by taking a shortcut in the short-term to get code out the door. Technical debt can take the form of poor design decisions, much-needed refactorings, technology upgrades, and outstanding bugs.

28. Tackling The Technical Debt in Five Steps

Recognizing that you have technical debt is easy. And if you don’t recognize it already, one of your engineers will likely tell you:)

29. 4 Tips on How to Refactor Code in Visual Studio Code

This article looks at how you can refactor your code using Visual Studio Code (VS Code) and Visual Studio Code plugins.

30. 10 Ways to Prevent and Manage Technical Debt—Tips from Developers

Developers deal with technical debt every day, and they know how to prevent and manage it better than anyone else. Here’s just some of what they had to say.

31. An Essential Guide to Code Quality

Just like quality assurance is done in manufacturing, testing code quality is also done in software development. While developing software or if you're inspecting code written by your team, you need to make sure you verify its quality at every level of development before it gets more complex. In the world of software, the phrase code quality can be interpreted in different ways by different industries and teams.

32. Reducing Time Spent on Refactoring 3 Tips from a Dev

Recently, I had to deal with an old codebase that was difficult to maintain and scale. In this article, I'll share how my team and I decided to deal with maintenance and the best practices we implemented to reduce time spent on refactoring.

33. Is Low-Code the Solution to Technical Debt?

Low-code is a means to develop applications with visual, intent-driven development tools reducing the need to create lines of custom code.

34. The Early Velocity Trap

With much of the DevOps stack having matured and good practices becoming more mainstream, the need for quality in software has quickly become a central issue

35. Technical Debt and Prioritization

This week Product School Slack's community members discussed issues regarding technical debt when it comes to prioritization. Check it out!

36. Demystifying Tech Debt: An Overview of the 4 Types with Actionable Fixes

Learn how to manage technical debt in your codebase with this guide on the 4 types of tech debt, with examples. We'll look at how to fix each type of tech debt.

37. Code Churn: How it Relates to Refactoring and Technical Debt

Code churn is a measure or indication of how often a file changes. It typically refers to how often a developer throws out code

38. How To Improve Code Quality With Code Reviews and Refactoring

Originally published at Managing Technical Debt.

39. How Does Technical Debt Drive Up Business Expenses?

How does tech debt cost you? Here are 6 reasons why managing technical debt should be part of your business plan.

40. How to Write Meaningful Code Comments

In this guide, you will learn why it is important to write code comments, what are different code comment types, and the 4 best practices.

41. What Product Managers Can Do to Minimize Technical Debt

Product managers are able to help in tech debt closing. Is it myth or reality? In the article, we'll discover what it may look like under the hood.

42. 6 Practices Of How To Use Linters For Reducing Technical Debt

Technical debt is a common term in software engineering management. It has been the target of debates for many years. The name comes from a financial analogy because some people defend that developers buy time by shipping faster (and with lower-than-expected quality).

43. The Engineer's Complete Guide to Backlog Grooming📝

Without organization, backlogs get messy quickly, and issues can’t be prioritized.

44. Low-Code Platforms Don't Work Well with AI, But Here's How We Can Fix That

Low-code platforms might be booming, but are they ready to lift the power of AI as well? Read on to find out why low-code might not be a fit for AI.

45. How Engineering Leaders Can Prioritize Code Quality

Learn why code quality matters, the most important metrics you need to manage quality, and how to track and manage code quality issues.

46. Software Engineering Best Practices + The Best Resources to Save🚀

The reality is, tech moves fast, and it's easy to get distracted by the latest software, tool, or trend.

47. The Engineer's Guide to Creating a Technical Debt Proposal

This article will guide you through the process to craft a technical debt proposal to justify the time spent solving technical issues.

48. Kill Technical Debt Before it Kills Your Project

49. How to Measure Your Technical Debt: 8 Metrics to Consider

Technical debt metrics help you to monitor deficiencies in your current codebase. We decided to look at how they work, and pick out the best tracking tools.

50. Effective Sprint Planning: How To Not Get Overwhelmed By Technical Debt

My aim is to offer practical strategies to make planning a sprint less painful so that you'll feel organized rather than overwhelmed by your technical debt.

51. A Video Game, a Fighter Plane, and a Story to Explain Technical Debt – Even to Non-Technical People

Imagine you are a project manager building a historic fighter plane in a video game. A technical debt story about white stripes on a fighter plane.

52. 7 VS Code Extensions for Frontend Developers

As a developer, you’re always looking for cutting-edge tools, tricks, and extensions. Here are 7 tools that'll improve your productivity and efficiency.

53. 200+ Software Engineers Taught Me The Best Way To Manage Technical Debt

Over the last six months, I’ve learned how the best software engineers and leaders manage technical debt. I've interviewed more than 200 experts, to understand how tech debt is handled at growing software companies.

54. What Do Engineers Really Think About Technical Debt?

My team at Stepsize has surveyed 200+ Engineers and published the State of Technical Debt 2021 Report that explores the impact of tech debt on companies.

55. Code Refactoring: A Comprehensive Guide for Engineers

In this guide, you’ll learn all about refactoring source code: the benefits, challenges, tools, and best practices, and what is the difference between refactoring and technical debt.

56. Technical Debt and How to Prioritize It: An Interview with Adam Tornhill

Last week we hosted a webinar where I interviewed Adam Tornhill, CTO & Co-founder of CodeScene, about technical debt: what is it, why is it important, and how to manage it effectively.

57. How To Manage Technical Debt Properly

We're used to thinking that you cannot deliver fast and maintain a healthy codebase. But does it really has to be a trade-off?

58. The Technical Debt Illusion: From The Trenches

Originally, the metaphor of technical debt was introduced to help us explain the need for refactoring software systems to upper management.

59. ClojureScript Macros: A (Not So) Long Journey [Part I]

I’m learning the Clojure and ClojureScript craft and I must say, I enjoy it. This article explains what leads me on the track of learning Clojure/Script macro. This is the first part of my journey on this topic.

60. Technical Debt Management Best Practices for Software Engineers

Technical debt exists on each project if it’s more than 1–3 months old. Having technical debt doesn’t necessarily mean that software engineers are not performing well. Technical debt can appear because of business pressure, lack of requirements, lack of interaction between team members etc. However, good software engineers know how to manage the technical debt and do that. Bad software engineers simply hide the tech debt from managers and customers, hoping that the project will be completed before it gets out of hand.

61. 4 Ways Software Engineers Organize Their TODOs

TODOs are a tricky subject for developers. Many codebases are guilty of having TODOs linger around while nobody knows who’s responsible for a TODO or even has the required context to tackle it. Yet, should we feel ashamed for our lingering TODOs?

62. Track & Manage Your Technical Debt To Make Better Strategic Decisions

If you are looking for a tool to start managing technical debt this article will help you make the right decision.

63. An Engineer's Guide to TODOs: How to Get Things Done

A lack of focus, lack of visibility into our codebase problems, and context switching decrease developer productivity. Here are the best ways and tools that'll help you get things done.

64. Five Big Myths Surrounding Technical Debt

In a software company, people often talk about tech debt, usually blaming it for something bad that is happening, such as

65. ClojureScript Macros: A (Not So) Long Journey [Part II]

The writing of Clojure/Script macro may seem as a wizard senior programming craft, but this article will show you that it's not the case. This is the second part of my journey to learn Clojure/Script macro and this article will deal with Clojure macro.

66. Understanding Technical Debt As A Software Engineer

What is tech debt? How to manage it effectively? In this Engineer's Complete Guide to Technical Debt, you will learn metrics, statistics, and tools that help engineering teams accelerate the software development process.

Thank you for checking out the 66 most read stories about Technical Debt on HackerNoon.

Visit the /Learn Repo to find the most read stories about any technology.