If you're wondering whether this blog post is really for you, ask yourself a few questions. Is my core codebase written in a language, framework, or tech stack that is 10 or more years old? Have we been struggling to hire Junior devs, seen a slide in motivation among our in-house folks, or even lost some engineers?
What if I told you that technical debt could turn out to be the grim reaper itself, jeopardizing all of your hard-earned growth and success?
The stars have aligned, and you’ve gotten the go-ahead to significantly overhaul some software. Figuring out if you should blow away the existing code and start from scratch, or if you should just rewrite parts of it instead, can sometimes be a challenging and difficult decision.
The next time you find yourself looking for an issue in code, which type of searcher will you be?
Once upon a time, there was a small business looking for help to modernize their existing software...
Is your team still using Python 2? If so, now is the time to develop a plan for migrating to Python 3. We'll walk you through our recommended upgrade approach so you can rest easier knowing your software and data are secure.
At MenderCon, we want to celebrate the software maintainers of the world and create a community where we can all learn from each other. Building on the organic community that's emerged from the podcast Legacy Code Rocks! this virtual event is a chance for menders all over the world to come together and talk about what makes improving software interesting and fun.
As a company that specializes in working with legacy code, we’ve run into our fair share of technical debt over the years. Many teams have deferred their maintenance for so long that any tiny change to the code takes forever to get out the door. But there are other things that contribute to technical debt that you won’t find in the codebase.