We've looked at the user data and carrots just aren't that popular, so it doesn't make sense to keep supporting them. We're working on a new vegetable which we hope to show off sometime new next.
You joke, but I work adjacent to biotech and by God, research groups working on engineering new genetic variants could really do with learning programming and suffering until they can do version control. I'm not saying use git (or equivalent) for the actual research, just that there needs to be some way of coordinating versions when you're working iteratively and in a team
"Why aren't our primers binding? Wait, where the hell did all those alanines come from? God damnit, we've wasted that batch now. Did you at least order some new primers from the supplier? Oh, you still need to design them? SOMEONE COULD HAVE HELPED IF YOU'D ASKED"
The client requested carrots but after delivery tells you they actually meant zucchini. You think it is strange to put zucchinis in a salad but still meticulously go through their dish and replace all carrots with zucchinis. Upon delivery they ask why it tastes weird and you realize they meant cucumber not zucchini and they got the two confused.
You wanted to add carrots to your stew, but the dependencies for carrots also pulled in a whole host of other ingredients in case you were making carrot cake with your carrots. Now you can't eat your stew because the flour has expired, and the eggs need a new major version.
You say this, but I once was trying to cook a meal in my grandmother's house and discovered that her peeler was incompatible with my body: it was left handed and I am not.
