But you shouldn't though, you shouldn't allow meat to enter the danger zone (40 °F - 140 °F / 4 °C - 60 °C) while defrosting. The cold meat and warm water yields lukewarm water, and if you let it sit for an hour, that's prime bacteria breeding grounds.
Run the meat over with some cold water and let it sit in a bowl filled with cold water for 30 minutes, and replace the water with new cold water every 30 minutes until defrosted.
The safest way to defrost meat though is in the refrigerator, throw it in there 24-48 hours before you plan on using it and you're golden.
That's seriously my top contender for my next phone right now, and it's a model more than a year old. But it's the only 1 of 2 available phones on the market with 5g, a removable battery, and an SD card slot. Fucking baffles me.
okbuddyphd, shittymobilegameads, pizzacrimes, garfieldwithoutgarfield, just all the really stupid obscure ones that give me a chuckle browsing through.
...small concern though: I currently use the rail planner a lot, usually to map out how I want my outposts to look at long distances. If the rail planner, particularly shift + click, is actively looking for rails to snap to, I hope it won't greedily try to snap to rails I don't want it to. I'm sure the devs already have this considered, but I just want to make sure that if I have multi-layer train crossings, and I'm trying to plan them out before I actually build them, that I'm able to path out rails behind an elevated rail without the rail planner assuming I want the rail to connect to the elevated rail. I hope that won't be an annoying issue.
Man, no kidding. We've got SoCs, we've got processors running on the FPGA fabric, we've got communications to Ethernet, PCIe, any AXI you like really. They can talk to RAM, storage, other processors, output graphics, kiss me on the forehead, and tuck me in at night. (I think.)
A coworker was telling me about the big shots in New York trading companies that are starting to implement FPGA architectures into their high-frequency trading algorithms, as the blazing high speed and great parallelization helps them squeeze out a couple extra microseconds in their algorithms. I think that's a good sign of people wising up to this potential here.
I don't know of any ML training on FPGAs, but I have no doubt that it can be / it is being done.
Edit: I just remembered the other day, I was shown a module that could take in a grey scale image, do edge dection, and output the edges as a new image file. Which isn't that hard, it's convolution on a sliding window, but what baffled me is that it was done in fewer cycles than could be compiled through C code, and the pipeline wasn't even that deep. It's crazy!
The "print hello world" equivalent of FPGAs is to make an LED blink. That teaches you how to use an FPGA's clock, divide it down to a frequency the human eye can actually see, and route it out to a pin (the LED on your board). Then you can experiment with your catalog of digital circuit building blocks using buttons, switches, LEDs, and 7-segment displays. You can make your own custom logic of ANDs and ORs to display different logic.
Some super beginner projects I found fun back in college:
Create a counter, and increment the counter every time you press a button. That's the easy part. Then display the value on a 4-digit 7-segment display. It's harder than it sounds, because you have to learn about time multiplexing! (At any one instance in time, only one digit is on, and the other three are off. Human persistence of vision makes us believe all 4 digits are being shown at once, but in reality, the system cycles through each digit, flashing one on for a few milliseconds, then turning it off and moving to the next one. Implementing this takes effort!)
Learning Finite State Machines and then implementing your own is fun. I made a "vending machine" state machine once, where different buttons corresponded to inserting different coins, and then once a certain amount of money was put in, you could select which beverage you wanted, the machine would "vend" (an LED would flash), and then change is administered. Another fun and classic FSM is the pattern detector, where you input a series of 1s and 0s, and the machine will blink an LED if it detects a certain pattern in the sequence, say, 11010. This one is a lot harder than it sounds, because it requires a lot of thinking of the different edge cases! If I input 111, for example, the system shouldn't be like, "well he inputted 111 but I was expecting 110..., so I'm gonna start over", because I could input "111111010" and the pattern is there, just at the end. This one teaches you how to draw state diagrams and Mealy/Moore machines!
Then you can get into using peripherals, like RGB LEDs, gyroscopes, graphics on a screen, ethernet connections, etc. You just need to learn the protocols and follow the correct logic in your own logic. It's a lot of copy and pasting at first, but if you put in the effort to understand what you're copying, you'll pick up on it fast.
Really, the world's your oyster, all you need is a development kit and a program that will synthesize/place&route your Verilog or VHDL.
FPGAs, love the damn things. They're circuits that you can re-program at will after they've been manufactured! If you build, like, a 2-input AND gate, that's all it will ever be. It can only take in 2 inputs and AND them together. But with an FPGA, they're manufactured to be versatile; you "program" the circuit you want to achieve onto the chip, and it will achieve that functionality! You can make a 2-input AND gate, slap it onto a bread board, and have yourself that nifty little AND gate, but if you later decide you wanted it to be a NAND gate, just reprogram the chip and like magic, what was once an AND gate is now a NAND gate. They're great!
What a coincidence, I just started getting back into geocaches myself!
Anyway, all the advice here is great, but I'd also like to point out that we are on the fediverse. There aren't that many people here, compared to other platforms, and the demographic is certainly skewed one way. You can definitely use these in your favor, but don't get discouraged when you're "only" pulling a few hundred, when that pretty solidly puts the community into one of the big ones (again, comparatively speaking). Things are just a bit more quiet here.
Calling Devolver Digital the "Cult of the Lamb publisher" is like calling Pixar the "Toy Story 4 creators". It's not untrue, but they're also known for publishing a lot of other things. But I get why they picked this game for the headline, it's in vogue right now.
On places like 4chan, it's used as a kind of dogwhistle. For example: