ChatGPT is famously bad at the things you’d use a calculator for though
ChatGPT is famously bad at the things you’d use a calculator for though
Holy shit I forgot about Drakengard. That’s the one with the giant sky babies right?
Thank you for reminding me about Enshrouded. I started playing that a few months ago, but a week into it my gamer friends wanted to start a new Valheim playthrough, and that was that. I should revisit it though
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
Maybe, and I’m not a biologist or an expert on evolution, so take my uninformed opinion with a big ol’ chunk of salt, but I feel like what you’re describing is more cultural than biological. Like, generally women just play video games (at least online competitive ones where there’s interaction between players, like the ones you’re describing) less than men, because those kinds of video games are sort of a hellhole for women. So in general, their eyes probably aren’t attuned to things like aliasing and digital sniper glints because that’s not something they experience often, not necessarily because their brains aren’t as well equipped to recognize those things.
I will continue to argue that GenX is the only true technology literate generation because we grew up with the technology as it evolved.
This is a terrible argument. Technology is always evolving. There have been like 10 different versions of Windows that I’ve used growing up as a millennial, across 3 different architectures, with huge advances in storage, memory, CPU speeds, and graphics processing - it’s pretty ignorant to dismiss all that and claim Gen X “grew up with the technology”. Like duh, every generation “grows up with the technology” of their generation.
I think the point I’ve seen elsewhere on this post is more accurate - every generation has some technologically literate people and some technologically illiterate people. Congrats, you happen to be literate, but I guarantee for every one of you, there’s also a Gen X’er that can barely function a computer enough to check their email. Just like the boomer generation, and the millennials, and even Gen Z and Alpha. This whole “XYZ generation is the most ABC” bullshit is just another way to create divides, and make people forget we’re all way more alike than we are different.
Either that or they show up right as you sit down to take a shit, or while you’re in the middle of your shower
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.
Yup, runs super smooth out of the box with Proton, and changing to Vulkan in the video settings
Neither rebasing nor merging should cause trauma if everyone on the team takes a day or two to understand git
Right? Dude Vulkan has impressed me a bunch lately. I use it for Deadlock and it feels much smoother than the streamers I see using DirectX, which is crazy since Deadlock is super early alpha. More stuff needs to support Vulkan
Can confirm, as someone who spent multiple study halls trying to program a top down shooter on his calculator