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...
I recently helped a client incrementally migrate a customer-facing portal from Struts to Spring Boot. As part of the migration, we needed to consolidate five Git repositories into one. While completing the consolidation, we developed a number of scripts to follow to ensure that the change history for each repository was maintained and accessible.
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.
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.
Software systems can find themselves in a state of "rock bottom." When we encounter projects like these, we need to channel our inner monk. Start where you are. Eliminate the shame that goes with having a messy codebase. Embrace that your system is worth investing in and start making it better from where you are today.
When a JavaScript project comes our way, we’ve found bitHound to be a fantastic tool to help us understand where we can have the most impact on a project. We love them, and not just because their company also has a dog in their name. So what makes bitHound stand out from other static analysis tools out there? We’re glad you asked.