In this Tech in 2, Principal Consultant Jeremy Swineheart shares three keys to learning from old code.
A lot of people will look at old code and think, “oh, this is gross” or “who would design something like this?” It’s always the go-to to blame the previous developer, but you’ve got to understand that some of these systems that we’ll get into that are like that have been doing their job for 10 years and sometimes more and that’s impressive! It’s impressive that it’s fulfilled its need and it’s doing what it needs to do. If you think about how 10 years ago the technology was so vastly different that you could really learn from how it was doing and what it was doing with limited information and limited abilities.
Understand Why Code Does Something, Not Just What it Does
If you want to find out why it’s doing what it does, like what’s the real need that it’s solving so then you can better build a system around that need more than just the raw functionality that it was completing. That’s going to leave it open for future growth.
Better Manage Technical Debt to Allow Growth
Keep in mind that there will be next steps and if they get this kind of information, what are they going to want to do with that? What kind of doors is that going to open up into? What kind of reporting or what kind of features and leave that kind of stuff open so that you don’t you don’t code yourself into a box that later on down the road requires a complete rebuild.
Use Upgrades to Rethink How You Solve Technical Problems
A big part of doing upgrades is if you’re going to go through a whole new tech stack or you’re going to upgrade from an older version of something to a newer version, that almost always comes with new features, new built-in tools and opportunities, so then if you’re already going to that upgrade, it just makes sense to try and streamline processes and leave things more dynamic and open yourself up to you know more possibilities.
Everything’s always changing and there’s always going to be a different report needed in a different way or data handled differently it’s so it’s important to try and see what’s coming but then at the same time leave it open for multiple paths.
Better Software Development Through Collaborative Communication
Collaborative communication in software development is so important, as it helps you anticipate obstacles, figure out how to resolve them and ensure you have a well-rounded product. In this Tech in 2, Senior Consultant Jennifer Butler shares three keys to collaborative communication.
Solving Common Problems in Software Development
A couple of the biggest challenges that Client Executive Hannah Stork is seeing in software development currently are capacity-based issues and speed-to-market challenges. In this Tech in 2, hear from Hannah as she shares three tips to solve these common problems.
Maximizing Efficiency, Not Productivity
In software development, efficiency is incredibly important. Perhaps even more so than productivity. In this Tech in 2, Senior Consultant Jennifer Butler explains why and shares three tips for driving efficiency in your software development teams.
Joining a New Team – 3 Tips for a Fast Start
When joining a new software development team, it can sometimes be a challenge to find the information you need or know who to reach out to for help. In this Tech in 2, learn three tips to help you hit the ground running.