4 ms·
> It's frustrating to work on projects that are cancelled, I'm going to guess you're fairly junior in the profession? The more time you spend writing code, th
by zak_mc_kracken 11y ago
> It's frustrating to work on projects that are cancelled,
I'm going to guess you're fairly junior in the profession?
The more time you spend writing code, the more you realize that most of your projects will never, ever ship. That's just how the gig goes.
And it's okay. As an engineer, you should be looking forward more to the journey and how much you'll learn working on that project than anything else. Once in a while, you'll ship and you'll feel pride knowing that millions of people are using your code, but that's the exception, not the rule.
Enjoy the journey.
- ridiculous_fish 11y agoI have 12 years of professional experience. In that time, most of what I worked on shipped. It would be a serious failure if we committed to a feature and were unable to deliver it. To be fair, I have tended to work on mature products, which have predictable lifecycle. Perhaps you've had a different experience because you've worked for startups or on early development? Anyways, the way I see it, if I'm OK with my project being cancelled, I am working on the wrong project. We should not be comfortable with delivering results "once in a while."
- lmm 11y ago90% of startups fail, ergo if you're working in a startup and have a better-than-10% chance of your code shipping then you're doing it right.