Carrots often have dirt caked on the outside that’s hard to get off with just water, so peeling is a good way to help with that.
The peel has the healthy bits
Sort of, but not really. The nutrients of a carrot may be slightly more concentrated in the skin, but all layers of a carrot contain those nutrients. You’re not depriving yourself of an appreciable amount of nutrients by peeling a carrot.
What is it with people trying to turn the entirety of October, November, and December into Christmas?
It’s one single night, it’s not a season. Is this the Americans trying to push it on us to increase our capitalist consumption or something? I see it a LOT these past few years.
What’s next, celebrating other holidays in the actual month that they fall in?
That’s pretty much exactly how you first learn to do arithmetic. Break the (whole) numbers down into their smallest (whole) part and count em up. That’s what number lines do, or using colored blocks to visually do the addition, or any number of other techniques you use when you’re first learning arithmetic. I mean, even just knowing 3 + 3 = 6 is memorization, a shortcut form of 1 + 1 + 1 + 1 + 1 + 1 = 6.
Fuckin goteem
That thread is from like 4 years ago, types in Python have come a long way since then. Maybe they’d reconsider if the community brought it back up
I cook rice without a rice cooker all the time, and some of the tips you’re getting seem dubious to me. Rice is pretty forgiving though, so maybe those recipes work, but I do it a bit different.
I treat all species of rice exactly the same, and they all come out perfect. Short/medium grain rice comes out just sticky enough so you can grab chunks of it with chopsticks, long grain rice comes out beautifully fluffy, no stickage, with all the grains nicely separated.
I use a 1:1 rice to water ratio, plus an extra quarter cup of water. That bit is important - the extra quarter cup is what evaporates off and escapes as it boils/simmers, the rest is absorbed into the rice. Doesn’t matter if I’m cooking one cup of rice or ten, I use an equal amount of water plus a quarter cup.
I bring the water to a boil first, then dump the rice in. Wash it or don’t - I usually don’t, and the difference is slight. Once the rice is in, I turn it down to a simmer, put a kitchen towel over the pot, then squish the lid down over the towel, onto the pot. The towel helps make a better seal to trap more of the steam, but without the danger of making a pressure bomb. The towel also prevents condensation from collecting on the lid and dripping into the rice, which can make it soggy towards the end of the cook. I simmer it for 20 minutes, turn off the heat, then let it rest for another 20, with the lid still on. Leave the lid on until after it’s rested, or else some steam will escape and your rice might end up “al dente”. Once it’s rested, take the lid off and stir it to fluff it up a bit, and you’re golden.
I’ve been making it that way for years with several different kinds of rice, and it’s worked like a charm for all of em.
The django-stubs package is decent though
Those of pure enough heart to weild a Keyblade will know how to login - all you need to do is trust your heart, and follow the light!
You think it’s unreasonable for a software developer to take one to two days to learn a tool that’s basically ubiquitous in their field?
What I do locally on my branch is my own business.
Lol ok, but don’t expect git to read your mind. Like I said earlier, if people take a day or two to understand the tool, they can adjust their personal workflows to work better within the confines of git.
I don’t think rerere applies here. Once you do a rebase, the rewritten commits should contain the conflict resolutions. The only way conflicts could reoccur on subsequent rebases is if changes reoccur in those same files/lines.
Only if there are changes in the same files and on the same lines in both branches. And if you’re a commit freak, you should probably be squashing/amending, especially if you’re making multiple commits of changes on the same lines in the same files. The --amend flag exists for a reason. No one needs to see your “fixed things”, “changed things again”, “fixed it for real” type commits.
That could happen if the base branch has changed a lot since the last time you rebased against it. Git may make you resolve new conflicts that look similar to the last time you resolved them, but they are in fact new conflicts, as far as git can tell.
Neither rebasing nor merging should cause trauma if everyone on the team takes a day or two to understand git
Three rats in a trenchcoat
What if we assume the ship is actually a spherical cow
They look like they were made for a tree frog. Them thangs are BULBOUS
Crocs makes slides. They’re insanely comfortable.
Why? They’re a comfortable, decently built, well-priced shoe. Why shouldn’t someone wear Crocs?
https://www.allrecipes.com/article/should-you-peel-carrots/
Carrots are not like other vegetables