Let’s take a look at when you should consider refactoring your codebase and how to convince your management to spend time on refactoring and technical debt.
As you push forward to create and ship the next big thing to market, you’ve probably let some things slide that just might now be catching up with you. One of these is refactoring — the process of changing a software system so that it does not alter the code’s external behaviour yet improves its internal structure.
Let’s take a look at when you should consider refactoring your codebase and how to convince your…
Many of you loved my list with the 10 Must-Have VS Code Extensions to boost developer productivity so I asked devs who use IntelliJ IDEA: what are your favorite plugins to ship quality code fast? Here are 10 plugins many of you have mentioned:
WakaTime allows you to see metrics, insights, and time tracking automatically generated from your programming activity.
You will learn exactly how long you spend coding as it automatically tracks when you start and stop typing, with detailed metrics for projects, file, branch, commit/PR, feature, and more.
As a developer, you need to organise your tasks to manage your time and successfully complete a sprint. These 6 VS Code extensions help devs get organised and work effectively.
If you like to mark sections of code with TODO and FIXME tags but keep forgetting about them then this plugin will solve your problem. It highlights TODO or FIXME phrases in the code so that you don’t forget what you wanted to fix or improve.
Software vendors are presenting a plethora of low-code software solutions to reduce the mundanity of software development. But, what are their actual advantages, how can they reduce, and also cause 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. Instead, various tools and platforms do the heavy lifting, including drag-and-drop interfaces, reusable code templates, process modeling, and SDKs, into the software development process. Thus, everything the no-code vendor thinks the user needs to build an app is already built into the tool.
According to market research…
We live in a world where progress is king — complete tasks, meet goals, commit more, deploy frequently, ship faster. But what happens when something is lurking in the codebase that’s holding you back? That’s right, legacy code. Let’s take a look at how you can deal with legacy code, once and for all.
In this guide, I will cover the following topics👇
What’s the overall performance of your engineering team? It’s a question many development teams can’t answer. However, having this information is vital to plan new features and detect problems within your team early.
Capturing different metrics will help you to measure and visualize your engineering team’s performance. This article discusses three different metrics you can measure to detect problems like lack of ownership during code reviews, technical debt, or choking points with key team members. Therefore, let’s look at how we can improve your team’s performance.
Here are three important metrics you can measure to understand your engineering team’s current…
Live Server allows you to see code changes reflected in the browser. It launches a local development server with a live reload feature both for static and dynamic pages.
Every time you save your code, you’ll instantly see the changes reflected in the browser. You’ll be much faster at spotting errors and it’s much easier to do some quick experiments with your code.
In most cases, you aren’t the only person working on the same project or codebase. That means that other people get to read your code and have to understand it. That’s also true for the code comments you leave behind. Developers often write quick and dirty comments without much context, leaving other developers clueless about what they’re trying to say. It’s a bad practice that only creates more confusion rather than clarifying things.
So, yes, you should be bothered with writing meaningful code comments to help other developers. A code comment that describes the function, the reasoning behind the function…
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.
Plenty of people have written about technical debt. They might be discussing it in the context of improving velocity, code churn, code refactoring, or it might just be an item on a very long to-do list that never gets prioritised. We put out a call out for real-world experiences of what helps when it comes to reducing technical debt and received a huge number of responses from devs across a variety…
There’s plenty of jokes around technical debt, but what happens when companies leave it to languish? I asked a bunch of developers to share some of their horror stories of technical debt.
Arthur Linum is a technology consultant. He shared some of his experiences with me:
“I was the consultant for a startup that had accumulated substantial technical debt. They had rushed to meet tight deadlines to position themselves at the forefront of the market, and this had led to code that was quick and dirty.
Unfortunately, their technical debt caught up with them. Their poorly designed code demanded a…
Building Stepsize, a SaaS company to measure and manage technical debt.