|
Cooking is pretty daunting for someone who hasn't yet invested time and energy into learning how to do it. Experienced cooks often sell the end results of said efforts without mentioning how long everything will take initially.
For a complete dunce or recovering ramen-fueled college student it goes like this.
- Receive recipe.
- Go to store to pick up incredients for recipe.
- Spend twice as long or more shopping than any cook would expect. Finding unfamiliar ingredients/cuts of meat is hard.
- Take five times longer to dice/skin/prepare ingredients than recipe expects.
- Trip up over assumptions in the recipe. "Oh, I was supposed to do X first/in parallel/later." happens, a lot.
- Find out your bowls/pans/whatever are too big/small/warped for what you're doing.
- An attempt at baking/frying/boiling/whatever happens.
- Results are not quite right, but edible.
- Total time spent is forever.
- Never again.
Once you've learned the basics and have a few familiar recipes things go far quicker, but that takes time. You're going to be several dozen extended grocery trips and multi-hour cooking misadventures in before the time investment per meal shrinks to a comfortable level.
It's ultimately worth it, you can save yourself a ton of money and be healthier by cooking for yourself, but it's like climbing a mountain that starts with a cliff face before tapering off into more reasonable climb.
|
tabernacle and stuff are perfectly normal words, I'm sure the french catholics also know them.
|
I don't think most people know what tabernacle is apart from a Quebecois curse word actually. Chalice, ostie, those are pretty common (I dunno if most people would know what a chalice is exactly, but they'll know the word), but the others I don't think even my fairly religious grandmother could tell me what they are in the context of Christianity.
When I tried to make ratatouille, it took me over an hour (an or a, do we dismiss the h?) of preparation and cooking, not counting the groceries (which didn't take long because I live not 5 minutes from a supermarket and ratatouille doesn't ask for anything fancy. And then because my frying pan was too small for the quantity part of it ended up not being cooked as well (and it took longer because I moved it around to cook parts, instead of being able to cook it all in one go).
And as Monte says, the result was "edible". I'd rather cook steak and roasted potatoes, takes 30 minutes including boiling the potatoes the first time, no effort, still healthy.
On November 25 2014 01:40 Alzadar wrote:
Are courriel, stationnement (vs parking), etc Quebecois creations? I know l'Academie francaise promotes their use, so I figured they were France words.
As a side note, l'Academie francaise has to have the most pompous titles in the world. Their inner council is literally called the Forty Immortals.
An old high school teacher of mine uses the very "loller" on Facebook, it has a pleasant feel to it. "Nous lollerons" feels really nice in your mouth.
Stationnement is how we should be calling it, it's just parking is shorter (same why we say se garer and not me stationner), otherwise I don't think it's Quebecois (Quebecois works too? WordReference told me "Quebec", sounded weird as a way to refer to the people too).
A bunch of "technological" words for which you encounter a Frenchified equivalent will generally come from Quebec and be backed by l'Académie though, since we borrow a lot more words in these more "modern" topics (pourriel for spam, mix of courriel and pourri (rotten/rubish, eg. which you'd send to the trash), I have no idea what they came up with for smartphones but I'm pretty sure they found something).
The Immortals apparently comes from l'Académie's motto, To immortality, which refered to the French language (as their role is partly to preserve it). I guess it was extended to the people because at the time entering l'Académie would grant them fame (in the intellectual world at least) and also because they are people whose work, in a way, will grant them a form of posterity by being used by the people for the centuries to come (yup, we totally held their standards even till now).
|
On November 25 2014 02:09 Seuss wrote:Cooking is pretty daunting for someone who hasn't yet invested time and energy into learning how to do it. Experienced cooks often sell the end results of said efforts without mentioning how long everything will take initially. For a complete dunce or recovering ramen-fueled college student it goes like this. - Receive recipe.
- Go to store to pick up incredients for recipe.
- Spend twice as long or more shopping than any cook would expect. Finding unfamiliar ingredients/cuts of meat is hard.
- Take five times longer to dice/skin/prepare ingredients than recipe expects.
- Trip up over assumptions in the recipe. "Oh, I was supposed to do X first/in parallel/later." happens, a lot.
- Find out your bowls/pans/whatever are too big/small/warped for what you're doing.
- An attempt at baking/frying/boiling/whatever happens.
- Results are not quite right, but edible.
- Total time spent is forever.
- Never again.
Once you've learned the basics and have a few familiar recipes things go far quicker, but that takes time. You're going to be several dozen extended grocery trips and multi-hour cooking misadventures in before the time investment per meal shrinks to a comfortable level. It's ultimately worth it, you can save yourself a ton of money and be healthier by cooking for yourself, but it's like climbing a mountain that starts with a cliff face before tapering off into more reasonable climb.
Can confirm, tried a new Fumi Salad recipe (basically asian coleslaw) this weekend, took forever to chop vegetables. It came out pretty well, but I may or may not have had to look up how to properly chop cabbage...
|
Czech Republic11293 Posts
You made me look up how to chop up cabbage properly
I should have done that ages ago, god damn
|
Cutting vegetables is hard. We should grow them into rectangular prisms. If we can do it with cheese plants surely we can do it with other plants.
|
On November 25 2014 01:44 red_ wrote:
But see now you're starting to make the point of why cooking high quality meals vs building a high quality PC is just not a good analogy. I can build a really good machine in very little time, or at least I don't save much time if I buy pre-built. High quality food just doesn't really work that way. I'm not saying go buy tons of 'pre-built' fast food or whatnot, I'm just saying the analogy falls apart for me. It's useless.
Most of the time in cooking is waiting. much like building a PC.
On November 25 2014 02:09 Seuss wrote:Cooking is pretty daunting for someone who hasn't yet invested time and energy into learning how to do it. Experienced cooks often sell the end results of said efforts without mentioning how long everything will take initially. For a complete dunce or recovering ramen-fueled college student it goes like this. - Receive recipe.
- Go to store to pick up incredients for recipe.
- Spend twice as long or more shopping than any cook would expect. Finding unfamiliar ingredients/cuts of meat is hard.
- Take five times longer to dice/skin/prepare ingredients than recipe expects.
- Trip up over assumptions in the recipe. "Oh, I was supposed to do X first/in parallel/later." happens, a lot.
- Find out your bowls/pans/whatever are too big/small/warped for what you're doing.
- An attempt at baking/frying/boiling/whatever happens.
- Results are not quite right, but edible.
- Total time spent is forever.
- Never again.
Once you've learned the basics and have a few familiar recipes things go far quicker, but that takes time. You're going to be several dozen extended grocery trips and multi-hour cooking misadventures in before the time investment per meal shrinks to a comfortable level. It's ultimately worth it, you can save yourself a ton of money and be healthier by cooking for yourself, but it's like climbing a mountain that starts with a cliff face before tapering off into more reasonable climb.
aye, but we were comparing people who know how to build a PC and saying its easy and takes little time to me, who knows how to cook and bake and it doesn't take much time for me.
i don't know how to build a PC and i can tell you it'd likely take me a week to research parts, order them, get replacements when i screw it up ect.
|
On November 25 2014 02:15 Scip wrote:
You made me look up how to chop up cabbage properly
I should have done that ages ago, god damn
right?!
I felt like an idiot, but I'm glad I took the 2 minutes to check haha.
I've got some couscous sitting in my cupboard that I want to use in something, but I have no idea what. Anyone have any suggestions?
On November 25 2014 02:18 PrinceXizor wrote:Show nested quote +On November 25 2014 01:44 red_ wrote:
But see now you're starting to make the point of why cooking high quality meals vs building a high quality PC is just not a good analogy. I can build a really good machine in very little time, or at least I don't save much time if I buy pre-built. High quality food just doesn't really work that way. I'm not saying go buy tons of 'pre-built' fast food or whatnot, I'm just saying the analogy falls apart for me. It's useless. Most of the time in cooking is waiting. much like building a PC.
If you're taking actual ratios of time for each, waiting is a far greater portion of PC building. It takes less than 2 hours to build a PC, it's really quite simple. Aside from that, your time is spent picking parts and comparing things (shopping - comparable to grocery shopping), and then just waiting days for your parts to come in. Once they're in, you plug/play, and boom, you've got a computer for 2+ years that you can continually update and maintain.
Compared to cooking, which is a far lesser % waiting, and contains much more prep time and actual work.
|
Sorry. I usually expect people to say "rite of passage" instead of "Hajj", lol.
|
|
|
inkedplaymats is pretty good, it's where I got my Viktor playmat
|
United States37500 Posts
On November 25 2014 02:20 Sufficiency wrote:
Sorry. I usually expect people to say "rite of passage" instead of "Hajj", lol.
I've never heard anyone use 'hajj' outside of the actual term. zz
|
Czech Republic11293 Posts
On November 25 2014 02:24 NeoIllusions wrote:Show nested quote +On November 25 2014 02:20 Sufficiency wrote:
Sorry. I usually expect people to say "rite of passage" instead of "Hajj", lol. I've never heard anyone use 'hajj' outside of the actual term. zz
hearing hajj used instead of "rite of passage" is the hajj of forum-goers
|
On November 24 2014 04:48 onlywonderboy wrote:Show nested quote +On November 24 2014 04:36 AsmodeusXI wrote:
Marathon relay in pouring rain complete.
At least we weren't dead last.
Ow my legs. I signed up for a Tough Mudder in May. I should probably start doing more cardio.
Oooo the one near Mansfield/Akron or w/e? I think I'm doing the PA one since it's in August.
|
On November 25 2014 02:19 jcarlsoniv wrote:
If you're taking actual ratios of time for each, waiting is a far greater portion of PC building. It takes less than 2 hours to build a PC, it's really quite simple. Aside from that, your time is spent picking parts and comparing things (shopping - comparable to grocery shopping), and then just waiting days for your parts to come in. Once they're in, you plug/play, and boom, you've got a computer for 2+ years that you can continually update and maintain.
Compared to cooking, which is a far lesser % waiting, and contains much more prep time and actual work.
I dunno i've found that "prep times" tend to be almost nil for cooking, when you know how to actually cut things properly ect, it takes me maybe 5 minutes of prep work for any non-dough related recipe. and then another 3-5 minutes if the ingredients need pre-cooking. and then its all waiting and plating. if you spend a lot of time doing prep work while cooking you are as inept at cooking as the people that have to spend 4-5 hours putting a PC together because they have to keep looking things up.
though i do understand the audience here is much more into tech than cooking and likely spent more time around PCs than ovens growing up. the nature of a gaming forum after all. i spent about 7 hours looking up parts before i just asked a friend to build my PC for me because it was going to take me much more time. but he often comes to me for cooking advice.
though soniv, compare a loaf of bread to building a pc:
i spend about 7 minutes making the dough, 2 hours letting it rise and 20 minutes baking it. with maybe an extra minute and a half of kneading throughout.
the complexity in building a PC is in selection of parts more than anything, where the complexity in cooking.baking is knowing how to prep the ingredients.
any idiot knows how to take a part out of a box, but learning to cut veggies quickly and accurately takes a bit of time, likewise, its a hell of a lot easier to pick out produce than it is to find PC parts.
|
Most of the cooking "timesaves" are just knowing the optimal order of things
instead of a recipe they should write down build-orders
It's a lot more comprehensive too!
"Fast expand into potato salad while microing your vegetable cutting
put meat into pan at 10 supply of tomatoes"*
*this is not a real dish. but it could be!
|
On November 25 2014 02:27 PrinceXizor wrote:Show nested quote +On November 25 2014 02:19 jcarlsoniv wrote:
If you're taking actual ratios of time for each, waiting is a far greater portion of PC building. It takes less than 2 hours to build a PC, it's really quite simple. Aside from that, your time is spent picking parts and comparing things (shopping - comparable to grocery shopping), and then just waiting days for your parts to come in. Once they're in, you plug/play, and boom, you've got a computer for 2+ years that you can continually update and maintain.
Compared to cooking, which is a far lesser % waiting, and contains much more prep time and actual work. I dunno i've found that "prep times" tend to be almost nil for cooking, when you know how to actually cut things properly ect, it takes me maybe 5 minutes of prep work for any non-dough related recipe. and then another 3-5 minutes if the ingredients need pre-cooking. and then its all waiting and plating. if you spend a lot of time doing prep work while cooking you are as inept at cooking as the people that have to spend 4-5 hours putting a PC together because they have to keep looking things up. though i do understand the audience here is much more into tech than cooking and likely spent more time around PCs than ovens growing up. the nature of a gaming forum after all. i spent about 7 hours looking up parts before i just asked a friend to build my PC for me because it was going to take me much more time. but he often comes to me for cooking advice. though soniv, compare a loaf of bread to building a pc: i spend about 7 minutes making the dough, 2 hours letting it rise and 20 minutes baking it. with maybe an extra minute and a half of kneading throughout. the complexity in building a PC is in selection of parts more than anything, where the complexity in cooking.baking is knowing how to prep the ingredients. any idiot knows how to take a part out of a box, but learning to cut veggies quickly and accurately takes a bit of time, likewise, its a hell of a lot easier to pick out produce than it is to find PC parts.
No shit prep time is nil when you know how to cook and actively work with cooking. What's next, water is wet?
|
On November 25 2014 02:18 PrinceXizor wrote:Show nested quote +On November 25 2014 01:44 red_ wrote:
But see now you're starting to make the point of why cooking high quality meals vs building a high quality PC is just not a good analogy. I can build a really good machine in very little time, or at least I don't save much time if I buy pre-built. High quality food just doesn't really work that way. I'm not saying go buy tons of 'pre-built' fast food or whatnot, I'm just saying the analogy falls apart for me. It's useless. Most of the time in cooking is waiting. much like building a PC. Show nested quote +On November 25 2014 02:09 Seuss wrote:Cooking is pretty daunting for someone who hasn't yet invested time and energy into learning how to do it. Experienced cooks often sell the end results of said efforts without mentioning how long everything will take initially. For a complete dunce or recovering ramen-fueled college student it goes like this. - Receive recipe.
- Go to store to pick up incredients for recipe.
- Spend twice as long or more shopping than any cook would expect. Finding unfamiliar ingredients/cuts of meat is hard.
- Take five times longer to dice/skin/prepare ingredients than recipe expects.
- Trip up over assumptions in the recipe. "Oh, I was supposed to do X first/in parallel/later." happens, a lot.
- Find out your bowls/pans/whatever are too big/small/warped for what you're doing.
- An attempt at baking/frying/boiling/whatever happens.
- Results are not quite right, but edible.
- Total time spent is forever.
- Never again.
Once you've learned the basics and have a few familiar recipes things go far quicker, but that takes time. You're going to be several dozen extended grocery trips and multi-hour cooking misadventures in before the time investment per meal shrinks to a comfortable level. It's ultimately worth it, you can save yourself a ton of money and be healthier by cooking for yourself, but it's like climbing a mountain that starts with a cliff face before tapering off into more reasonable climb. aye, but we were comparing people who know how to build a PC and saying its easy and takes little time to me, who knows how to cook and bake and it doesn't take much time for me. i don't know how to build a PC and i can tell you it'd likely take me a week to research parts, order them, get replacements when i screw it up ect.
It entirely depends on what you are preparing(unlike a PC, where it's pretty much always the same). I'm not a master chef or anything, but I'm not a novice to the kitchen either. I prepare a very large % of my meals, and I prepare them in bulk ahead of the time when I can. It's still time consuming.
A PC will last you 2-years if you're quick on the upgrade, 4-5 or more if you don't mind falling behind in tech and playing games on low settings as it ages. There's just no comparison to cooking here. Even if you learn to cook, to maintain quality will still take considerable time and effort, whereas learning to build a PC once makes it an extremely streamlined process pretty much every time you do it in the future.
I'm probably a kind of outlier here because of how/what I eat, but that's obviously built in to my personal disagreement with your post that started this discussion.
|
I don't think it takes expert knowledge to put a PC together.
It takes knowledge to pick good parts, but usually you can ask others for the choice of parts.
|
On November 25 2014 02:09 Seuss wrote:Cooking is pretty daunting for someone who hasn't yet invested time and energy into learning how to do it. Experienced cooks often sell the end results of said efforts without mentioning how long everything will take initially. For a complete dunce or recovering ramen-fueled college student it goes like this. - Receive recipe.
- Go to store to pick up incredients for recipe.
- Spend twice as long or more shopping than any cook would expect. Finding unfamiliar ingredients/cuts of meat is hard.
- Take five times longer to dice/skin/prepare ingredients than recipe expects.
- Trip up over assumptions in the recipe. "Oh, I was supposed to do X first/in parallel/later." happens, a lot.
- Find out your bowls/pans/whatever are too big/small/warped for what you're doing.
- An attempt at baking/frying/boiling/whatever happens.
- Results are not quite right, but edible.
- Total time spent is forever.
- Never again.
Once you've learned the basics and have a few familiar recipes things go far quicker, but that takes time. You're going to be several dozen extended grocery trips and multi-hour cooking misadventures in before the time investment per meal shrinks to a comfortable level. It's ultimately worth it, you can save yourself a ton of money and be healthier by cooking for yourself, but it's like climbing a mountain that starts with a cliff face before tapering off into more reasonable climb.
Or go the easy way.
Buy crockpot
Chop shit up.
Toss it in.
Set it and forget it.
|
|
|
|
|
|
EPT
