Episode 458: Infinite tech debt hack and figuring out what is going on

In this episode, Dave and Jamison answer these questions:

1. Nearly every time certain developers on the team want to address technical debt, they end up just adding more technical debt. Of course, after one round of addressing technical debt, the developers in question believe that yet another round of redesigning and refactoring is in order. This stresses me out for many reasons, as you can imagine, and has led to my productivity dropping to an abysmal rate. I spend a large chunk my time resolving merge conflicts and re-orienting myself in an ever-changing codebase. Do you have any suggestions for me?

2. Hi!

   I’m a software engineer at a big tech company, and I’m starting to feel siloed in my IC role. I’m getting my work done, but I’m often lost when it comes to the bigger picture. I can’t keep up with what our internal customer teams are doing, what they need, or even what my own team’s priorities are. I’m feeling siloed, and it’s starting to worry me. I know that just being a good IC isn’t enough to advance my career here. To get promoted, I need to understand the impact of my work, be aligned with the team and customer goals, and show that I can contribute to the overall success of the company. But how can I do it? How do I stay informed about customer needs and team priorities and position myself for career growth without getting completely overwhelmed?

   Thank you for your precious advice!