As developers, we often get requests for new features that may seem trivial at first glance, but become much more complex when we start to dig deeper. This is a story of one such example, and how we were able to work with our client to provide a more inclusive design.
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.
Legacy code is everywhere, and it's here to stay. Anything that someone else has left behind is their legacy. After a while, what they left behind might not play nicely with new code. Several key issues can come from legacy codebases, ranging from alarming security vulnerabilities to frequent bugs and plummeting developer productivity.
Nintendo started out producing handmade playing cards. Netflix was selling and renting DVDs by mail. Starbucks used to only sell high-quality coffee beans and equipment (no brewed coffee or delicious handcrafted espresso drinks!).
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.
By now we're sure that you've heard that the Python programming language is undergoing some big changes. It's true the developers who created Python 2 are no longer supporting that version of the language as of January 1st, 2020. Yes, nine months ago! They are encouraging everyone to upgrade to Python 3 but what does this mean for your business?
Ten years ago, I set out on the professional road trip of a lifetime. I had already started Corgibytes, but at that point, it was really just a name that I didn't know what to do with. I was thinking of creating products, specifically products for software developers and maybe the occasional casual game, just for fun. The vision wasn't quite there, but I was already eagerly in the driver's seat.
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.
Our work with legacy code doesn’t often put us in a position to move quickly into new or trendy tooling. And while we almost always introduce Docker very early in our projects, it is usually only for the purpose of standardizing and easing setup of developer environments. Transitioning a live environment to containers, however, can be a daunting prospect, especially for monolith applications. But, the payoffs can be huge.
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.