A few months back, a friend asked me a question.
He was in the middle of developing several new major features for his application at his investment bank. Meanwhile, he expected layoffs within a few months. As a result, new features weren't being discussed until the layoffs occurred. Was it wise to finish off his work, even though that would leave him with nothing to do at the time that layoffs were likely? Isn't that like asking to be laid off?
Situations like these make me re-examine my motto "always put yourself out of a job." Maybe this -- a crisis of a lifetime in his industry -- was the exception to the rule.
But I told him that he should continue to work at his best rate. By pushing himself, he'd keep his mind sharp. He'd get to finish the project and understand it thoroughly. He'd burnish a reputation as a professional programmer who did excellent work. Whether or not his name ended up on the list, all of these factors would make him either a stronger developer at his current place of work or a stronger candidate for the next one.
Last week, his company did have those layoffs. But, we'll never know if he was on the list, because a couple weeks before, he accepted a great new job. Some of the experience he earned in his last project made him very attractive to his new employer.
I take no credit for his success; obviously, he did all that on his own. But it is nice to see one's personal theory get validated in real life, especially in a tough market like the current one.
No comments:
Post a Comment