1. Proactive vs. Reactive Career Management
The speaker explains: developers tend to wait until they receive bad feedback or get fired before improving skills or applying for jobs, making problem-solving far more painful.
Hear it at 0:00 →Engineering video
0:59 · 7 March 2023
The speaker explains: developers tend to wait until they receive bad feedback or get fired before improving skills or applying for jobs, making problem-solving far more painful.
Hear it at 0:00 →The speaker explains: quick tips and hacks do not fix root problems, requiring developers to keep pushing themselves and improving skills regardless of how safe their current job feels.
Hear it at 0:38 →I see so many developers taking action when it's too late. It's like going to the doctor when you're already sick. For example, they improve their skills when they get bad feedback from their managers. They apply for jobs after they get fired. They're being too reactive instead of proactive. And the problem with that is that it's far more painful to fix a problem instead of preventing it. Just ask any doctor.
If you go to them when they are sick, yeah, sure, they will patch you up. They'll give you some pill here and there, and for the moment, you might even feel better. But if when you go back home, you keep doing the stuff that got you sick in the first place, eating badly, not exercising, you'll be back to the doctor in a bunch of weeks. It's the same with your developer career. A bunch of quick tips and hacks won't fix the root problem, which is choosing to push yourself when things are going well.
Keep improving your skills, no matter how safe you feel at your current job. If you take action, instead of letting your life make your decisions for you, your developer career will be much, much easier.