4 ms·
I think you're absolutely on point. Working for an established tech company is a great way to accelerate your continued education. Just because you're not doi
by steego 10y ago
I think you're absolutely on point. Working for an established tech company is a great way to accelerate your continued education. Just because you're not doing everything yourself doesn't mean you can't develop a broad exposure to ideas. Depending on how much access to source code and documentation you have, you can stand on the shoulders of many giants.
It's also worth pointing out that you can use your industry experience to develop essential political skills, and I'm not talking about how to be a Machiavellian dick. If you want to be a good leader, work on learning how to inspire and influence people's hearts and minds to work toward a common goal. Learn how to ask good questions and really listen. Figuring out what the goal is and effectively communicating that with others is key, but if you can actually motivate others to push themselves to advance that goal, you're on your way to becoming a very effective leader. BTW, you can practice these skills on any level because it doesn't require position or power. It simply requires that you interact, listen to and conspire with your coworkers, especially the ones that hold power over you.
- jamesroseman 10y ago> It's also worth pointing out that you can use your industry experience to develop essential political skills, and I'm not talking about how to be a Machiavellian dick. If you want to be a good leader, work on learning how to inspire and influence people's hearts and minds to work toward a common goal. Learn how to ask good questions and really listen. This is another vastly understated benefit of working at a company rather than starting a start-up. You not only get to see what code at-scale looks like and deal with it everyday, but also management. You can either learn good or bad management techniques watching your own manager interact with your team. Same goes for how the org is structured and how the stresses of that structure trickle down to grievances at the Software Engineer I level.