I've only been in the industry 13 years, and I'm not using a single tool today that I used back then, but I'm still using the lessons I learned: How much time

I've only been in the industry 13 years, and I'm not using a single tool today that I used back then, but I'm still using the lessons I learned: How much time should my team spend on testing vs. code review vs. building new features? How risky is this feature, and how much QA does it need? Which of the brand-new engineers on my team needs a careful eye on their code so they don't blow everything up? When is it time to say screw it, we have to ship? Which new hip framework is likely to have staying power, because of the people and the commitment behind it? How do I convince open-source maintainer X to accept my new feature, so I'm not maintaining patches into eternity? Those are the important questions I deal with every day. I couldn't answer them as well 10 years ago, and I bet I can answer them better 10 years from now.