3 ms·
I don't think this is only for leadership roles. If you don't stick around long enough to see how your work has evolved, your APIs have been used, how easy is i
by wreath 5y ago
I don't think this is only for leadership roles. If you don't stick around long enough to see how your work has evolved, your APIs have been used, how easy is it to adapt your work to new requirements, how you handed over ownership to someone else/another team etc etc, I think you left very valuable learning opportunities on the table.
Job hopping attitude is very visible in someone's work as well. You see them focusing on short term gains only with most of their technical decisions and leave the mess for someone else to cleanup while they move on to the next thing. Zero skin in the game.
- personjerry 5y agoAs an employee you should never think of yourself as having skin in the game. The company pays you for your time and expertise and compensates for your time. How successfully they leverage that time and expertise is on them, not on you. Job hopping is the most effective way to increase your income and position in tech.
- sean2 5y agoI think you misunderstood the parent posts. It's that your impact on a particular project doesn't become visible for a few years. If you think you quit after delivering your project near to budget and timeline, then you're left thinking you did a pretty good job, but only later is it possible to see if your architectural decisions are easy to maintain; if your API is easy to use; etc. The Senior Roles are supposed to have grown in knowledge about how all their decisions play out over a long time period, but if they've never stick around to observe the consequences of their decisions, then that might lead a recruiter to suspect whether they have learned what a Senior would be expected to know.