Answer Hazy. Ask Again Later
A little more than ten years ago, I had a somewhat similar choice. Fresh out of college, I was vying for entry-level (support) positions with two companies. Company A was local, a market leader in many categories. Company B was one of their fiercest competitors in certain areas and located some place I'd never been before.
I received an offer from Company B while Company A was still dithering about. I had to decide between taking the offer in hand or hoping that a second one would appear. I took it, partly because it existed and partly because it would involve a number of new experiences. (The second offer did come through as I was packing the U-Haul to move to the new location.)
I did well at Company B, moving quickly through the ranks until I had another choice. Accept a promotion into R&D to help develop the product we were working or one into Product Management to help lead that development. I chose the latter. A month later, I was laid off as Company B restructured, in part because they'd not been able to sucessfully compete with Company A. (None of the developers were laid off at that time.)
I was devastated, in part because I'd allowed a lot of my personal sense of self to be wrapped up in the successes I'd enjoyed at Company B.
If I'd waited for and accepted Company A's offer, I would likely have far more money than I do now, for their stock has performed admirably and they've only recently run into certain, well-publicized problems.
In looking back, I stand by my original decision for two main reasons:
As many of you know, I have a love for live theatre. While working at Company B, I was able to heavily participate in the local community theatre, doing some thirty shows in 3-1/2 years. I do not believe I would have been allowed to indulge my avocation as heavily had I waited for Company A.
Through a bizarre series of coincidences (which I'll spare you the details of) related to Company B and the product I was working on, I met the woman who would later consent to be my wife.
Without getting overly mushy, I believe she was the right person for me and I do not believe I would have met her if I'd joined Company A. Similarly, I don't believe that I'd have the pleasure of our daughter's presence in my life.
I believe that, as developers, we should take pride in our work and should strive to use craftsmanship as a guiding principle. That said, I also believe that:
There are more important things in life. In another ten years, some of my work may still exist and some of my code may still be in use, however, what will matter most is how my wife and I raise our child and the difference we make in other people's lives.
You cannot predict the future. Judge carefully, and make informed decisions, but don't invest a lot of time fretting about possibilities and what might be.
Unplanned and unexpected things will happen. Do your best to roll with those unplanned surprises. Hope for the best, but prepare for the worst.
Have backup and restoration strategies, but work on the tasks before you.
The most enjoyable journeys are those that you allow yourself to enjoy while getting to the destination.
If you make a mistake; don't stress it. You may be surprised at what happens later.
Learn from the past; don't dwell on or in it.
In short, be a Monk: Take pride in your work and your accomplishments, but not to the detriment of what really matters.
--f
In reply to Re: Permanence and Programming as a "craft"
by footpad
in thread Permanence and Programming as a "craft"
by Hero Zzyzzx
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |