>The strain comes from context switching. From 9:00 AM to 5:00 PM, I had to care deeply about our quarterly goals and production stability. Then, from 6:00 PM to midnight, I had to care about inverting binary trees and system architecture design.
>This duality is exhausting. It forces you to lie by omission to people you respect. You can't tell your team, "I can't take that ticket because I need to study dynamic programming." You just have to work faster.
Guess what promo will get you? More context switching. Maybe that’s a thing to work on.
We geeks often like to go deep, and engineers who persist with shallow understanding of tech hit limits. But as you get more responsibility, getting quickly oriented to project/task/business stuff is extremely valuable. And tbh, doing the same for tech topics is valuable but harder to do.
>This duality is exhausting. It forces you to lie by omission to people you respect. You can't tell your team, "I can't take that ticket because I need to study dynamic programming." You just have to work faster.
Guess what promo will get you? More context switching. Maybe that’s a thing to work on.