Oh Jesus God

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.

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!

I mean you’re the one coming into a thread in a different community getting snarky with multiple different people who are all being pretty level headed so

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

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?

Look, it’s fine if you prefer other languages to python, I won’t besmirch anyone’s preferences. But literally everything in your post exists in nearly every programming language (minus some of the typing stuff, I’ll give you that, but it’s getting a lot better). Like, every language has some learning curve to setting up tooling, or configuring your IDE the way you like it, or learning how to navigate documentation so that it’s useful, or trying to decide on one of the multiple ways of doing things. I guarantee, as someone with limited experience with Java, I’d have a difficult time setting up and using IntelliJ, and figuring out which build/packaging system I need to use, and figuring out how to use whatever libraries I need, simply because I’m unfamiliar with the ecosystem. That’s all you’re describing - the initial learning curve in getting familiar with a new language. Which is why I pointed out all the things I pointed out. It’s where I start when I’m introducing developers to python.

That feels like a packaging issue, which would be a problem specific to the developer of that app, not Python. For the most part, pip packages install basically instantaneously.

especially when u are indenting stuff inside stuff with a bunch of conditions everywhere

That’s an anti pattern in basically every language though. The fix is to simplify those conditionals, not use a curly-bracketed language.

If you need any kind of libraries

PyPI has a huge selection of libraries

assistance from an IDE

PyCharm a super powerful IDE, VSCode has tons of Python extensions that L rival PyCharm’s functionality, lots of other IDEs have decent python support

or a distribution build

Not sure exactly what you mean by this

or you’re more familiar with another language

Yeah this can be said about any language. “You’re quickest in the language you’re most familiar with”. That’s basically a tautology.

IDK if this is helpful for you, but for myself, as long as I get one thing on my to-do list done, I consider that day a win, and I try not to be too hard on myself for letting things slip. It’s really easy for me to get overwhelmed by the sheer amount of things on my list, but by just taking things one at a time, I know I’ll slowly get through it.

On a tangential note, care to share your pickled pepper recipe?

Not really. You might think that from looking at thumbnails, because thumbnails all have to basically look like clickbait for people to actually engage with your videos. But there’s tons of good YouTube content out there.