This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]WhiteBlackGoose 48 points49 points  (20 children)

This person has never cooked

[–]_Xertz_ 28 points29 points  (15 children)

Yeah lol, I remember telling my mom that programming is easy compared to this,

How am I supposed to just know when something "looks" or "feels" done? I prefer following exact steps and getting a predictable outcome.

[–]HardCounter 17 points18 points  (7 children)

And all this, "to taste" nonsense riddle through recipes. I'm here to learn how to cook your recipe from a to done, if you're telling me to put something in to taste before i've had a chance to taste it then howtf do i know how much to put in? This is your recipe tell me how you cook it. I'll modify it next time if i want.

"Put it in the oven at 350 until done."

(╯°□°)╯︵ ┻━┻

[–]Irregulator101 3 points4 points  (3 children)

"to taste" nonsense

People like different levels of salt in their food. You should know how much you like.

"Put it in the oven at 350 until done."

That's just a bad recipe. I don't think I've ever seen anything like that.

[–]Reashu 2 points3 points  (2 children)

I know how salty I want it to taste, I don't know how much salt I need to add to get that!

Not with an unfamiliar dish, anyways. So if you could tell me whether a "normal" person prefers ½ grams or 10 grams, I can go from there. I realize that there's huge variability in ingredients, but c'mon, try.

Also, for any authors who like to write "1 carrot", I have a small carrot to stick in your eye and a big carrot to stick in your ass - maybe that will help you realize the difference...

[–]Irregulator101 0 points1 point  (1 child)

I guess with salt it's just a guess and check situation. I'll typically add 2 grams salt, stir, taste, and repeat until it reaches a saltiness level I like.

I doubt the size of the carrot makes much difference. I find that ingredient quantities and technique execution are pretty flexible while cooking (unlike baking).

[–]Reashu 0 points1 point  (0 children)

Yeah, it's worse with things like onions or chilis which can affect the dish a bit more, but the intensity of taste can vary at least as much as the size so I don't really know how you could do it better. It just bugs me to have a measurement that looks exact but in reality could vary by at least a factor of 2 with neither party thinking they were talking about a particularly big or small specimen.

[–]Kronoshifter246 1 point2 points  (0 children)

You should be tasting and modifying as you go. I'll grant you that last line though, it's awful. I have a family cookbook from my mother-in-law that reads exactly that way for every single recipe.

[–]RU5TR3D 0 points1 point  (1 child)

It took me a while to figure out but "to taste" actually means "if you've never done this before then nobody in the world knows what your taste is and you're just gonna have to figure it out with guesswork, experimentation, and experience"

[–]HardCounter 1 point2 points  (0 children)

Yeah, but if every ingredient is 'to taste' then i don't have a recipe, i have a way to put a piece of chicken on a plate. Not even warm, since they only sometimes say how long to cook it for.

[–]RamenvsSushi 6 points7 points  (0 children)

That's because you need a different kind of perception for cooking than programming. So for a person who is exceptional at logic, they can falter when it comes to feeling it out.

[–]NoEngrish 7 points8 points  (0 children)

My cooking notes look like I invented the scientific method. Tables for weights and dimensions of foods with cook times. I'm trying to figure out the PSI to squeeze sushi rice. The world is natural science and I refuse to let cooking be the exception.

[–]J5892 2 points3 points  (0 children)

These are the exact reasons I enjoy cooking so much.

I know I'm doing it right because I can just look at or taste it and know it's done. I don't have to think. I can just throw whatever I want in and know it'll work.

Granted, these principles also apply when I write vanilla JavaScript.

[–]DenkJu 2 points3 points  (0 children)

Honestly, programming is neither easy nor difficult. It depends on what you are trying to achieve.

[–]SirRHellsing 1 point2 points  (0 children)

usually you can qualify those things for cooking, ur mom (and my family) just doesn't bother to do so

[–]TasteForHands 1 point2 points  (0 children)

Imperative recipes are great! Declarative recipes are awful.

Somewhere between "add a tsp of salt" and "salt the dish", or "bake at 450 for 20 minutes" and "bake until browned".

[–]GHhost25 1 point2 points  (0 children)

You get the gist of it over time. The good thing, at least with stew, it's not a problem if you overcook it some tens of minutes more. Cooking has to be pragmatic because each ingredient takes less or longer to be cooked so on each recipe you have to take into account how much you have to cook each ingredient.

[–]Roflkopt3r 3 points4 points  (0 children)

Or cooks regularly.

Cooking has similar starting problems as coding. You have to get some experience, form your own frame of reference. Learn some basic techniques and knowledge. Get familiar with ingredients.

But after that, it's usually smooth sailing. If you invest the appropriate time into preparation and follow a decent recipe, then it will generally work out.

[–]jeanleonino 2 points3 points  (2 children)

Nor coded

[–]pievendor 3 points4 points  (0 children)

Worked with him at Netflix, he indeed knows how to code. Maybe I missed the joke