

Half my visits to Wikipedia are because I need to copy and paste a Unicode character and that’s always the highest search result with a page I can easily copy and paste the exact character from.
Half my visits to Wikipedia are because I need to copy and paste a Unicode character and that’s always the highest search result with a page I can easily copy and paste the exact character from.
They have (had?) a fairly generous free tier that works well for people starting out.
I ended up buying a license after evaluation because the UI provides everything I reasonably want to do, it’s fundamentally a Linux server so I can change things I need, and it requires virtually zero fucking around to get started and keep running.
I guess the short answer is: it ticks a lot of boxes.
They could have just not had the monkeys. They added nothing to the story and were the most egregiously bad CGI.
You can’t do much preparation since you don’t know what they’re going to ask. You can assume there will be some “basic” programming questions, but that’s really as far as you can take it in advance.
My advice here is for during the interview: keep talking. You should always be talking. That’s how the interviewer assesses you. They want to know how you are deconstructing a problem and how you want to solve it. Sitting there silent for 5 minutes and then banging out some code isn’t giving them anything.
“Ok, I need to modify this array and I should try to do that in place. I need to look up the syntax for that because i rarely need to do this…”
“I don’t remember what a splurgenarf is. Can you give me a quick definition before I get started?”
“I’m going to just slop this incomplete code in and run it once to see the output. It won’t work but I want to see if the first part is on the right track.”
“I think you’re asking me to write a wrapper around a basic network call so that it will _______. Is that right?”
Oh, and you’ll always home your first interview if it’s been a few years. Don’t sweat it, and don’t make your first interview at a place you really really want to work because of that. You need to go through a couple of interviews before your brain remembers how to function in a coding interview because it’s so far divorced from how a developer usually works.
I tried them for a few months and cancelled.
For me, the quality of the recipes was poor. It was the kind of stuff I’d make when i’d just moved out from home and was learning to cook for the first time. Boring. Simplistic.
There’s also way too much trash. There’s a big cardboard box, a few ice packs, and a mound of pre-portioned ingredients each in little plastic bags. They cheerfully say you can keep the ice packs and reuse them! How many fucking ice packs can one person use?? Anybody can use a couple of ice packs. No one alive needs 2 new ice packs a week.
If you aren’t a confident cook and/or you need some inspiration for new things to make, it’s totally worth it for a few weeks or months. After that, though, I think most people will outgrow it.
Oh my god it’s real. https://www.telegraph.co.uk/news/2024/03/05/spanish-soldiers-change-gender-benefits-for-women/
Similar stories run from all the usual deplorable papers. New York Post, Daily Mail, you name it.
Why don’t they teach this shit in school?!?!
You can appeal a total loss settlement. They’re supposed to take into account the cost to replace the car at local rates, so unless that 16k model you’re looking at is in dramatically better condition or has way way less mileage on it, they need to justify that.
White cables also transmit slower in the dark. As soon as the cabinet is closed the data is going to slow way down with only the dim glow of the LEDs of the equipment acting to accelerate packets.
That game is too memorable. I tried replaying it a while back after not touching it in 15 years.
Five minutes in and nope, this whole story is seared into my long term memory and there’s nothing fresh yet.
I’ll try again when I’m 80.