"Why programmers like cooking: You peel the carrot, you chop the carrot, you put the carrot in the stew. You don’t suddenly find out that your peeler is several versions behind and they dropped support for carrots in 4.3" -- Randall Koutnik
@tastytronic
IMO some carrot peelers should be updated. 😏

@manuelcaeiro @tastytronic can I quietly recommend one of these?

https://amzn.eu/d/1OdKdNf

(You can obviously buy them from other places than Amazon. I should add I've no connection to the company that makes them or indeed to Amazon other than as a user)

Amazon.co.uk

@Geoff @manuelcaeiro this is actually what we always had growing up!
@tastytronic I’m a programmer and I don’t like cooking precisely because of that: the peeler hasn’t had an upgrade in a thousand years, and the carrot in a million. Unmaintained.
@ankitpati there's always Soylent, if you're interested in running alpha version nutrition in production...
@tastytronic Just wait till they tell you about their new smart fridge. Get that shit outta my KITCHEN
@tastytronic That's true. Programming is a lot like cooking. You peel the carrot. Your chopping knife has gone dull. It was made of some kind of super-hardened steel that's pretty much infeasible to sharpen. So now, not only do you need a new chopping knife, you need a different chopping knife, because they stopped making this one several years ago.
@tastytronic Yeah but then I make a very human mistake. You can't really debug your carrot nor put it back to previous versions in case you make a mistake! And knowing myself, I would peel my own fingers too!
@tastytronic I finished the stew but then I decided to refactor it so now dinner will be ready at 2:30am.

@tastytronic You do sometimes find out that your peeler saw fit to rust since you last used it because you can't have nice things.

Then you have to repurpose a knife to peel the carrot with greater inefficiency and loss of edible mass.

@tastytronic when I taught a friend, a fellow programmer, to bake, he said his problem with baking is that unlike cooking you can't debug baking at runtime :-D
@tastytronic It's like project management, because I can use a knife and be done.
@tastytronic I'm worried some techbro will find this post and use it to ruin cooking for everyone forever.

@tastytronic Defect report: Root vegetable is actually hemlock, entire village dead.

Cooking is a discipline thousands of years more mature than programming. All the stupidity was deprecated a long time ago.

@tastytronic The way I see it, ingredients don't use semver, they use year.month.day and your body drops support for ingredients that are too old, ingesting them is an undocumented behavior where things can go fine or it can dump the entire contents on stdout or stdin.
So you need to have a garbage collector disposing the old ingredients, and on the day you decide to cook you might find that your carrots have been collected.
But sometimes you can freeze the dependencies, so that's good.
@tastytronic Yes!! We went to all the trouble of inventing semantic versioning, then switched to releasing a new major version every six weeks. I hate it so much.
@tastytronic But you might discover the knife is unusably blunt, cut your finger when it slips off the carrot, and have to go to urgent care for stitches. So swings and roundabouts. ☺️

@tastytronic I’ve never prepared a meal that later told me there was a syntax error or undeclared variable.

Most cooking (aside from baking, that shit is wizardry) is very forgiving when it comes to variances in components and quantities - a stew with more potatos and less carrots won’t refuse to cook.

I’ve also never managed to get a meal into an infinite loop. ;)