Many cloud providers (the cheap ones in particular) will put patches on top of the base distro, so sometimes root always gets a password. Even for Ubuntu.

There are ways around this, like proper cloud-init support, but not exactly beginner friendly.

How many tokens fit in your context window?

Clearly your gender field is a boolean. Which means it can be either true, false, null, or undefined. Except in javascript where for some reason it can sometimes be NaN, but only when you try to compare two people.

I think you’re over exaggerating the effort needed for tagging resources. Between terraform/pulumi/cdk and the tag tool, it’s relatively easy to make sure everything is tagged. Doubly so if you have a finance department who’s literal job is to go through and do that (or ask you for help with it)

You can get a full itemized bill. The only thing that isn’t fully broken out are elastic ips. We found that out because we were tagging everything for billing and those weren’t showing up correctly.

Mind you, it’s likely a bit more itemized than you want. Like you’ll see a separate line item for each price tier you paid for something, and things like ebs disks are all split out. It can be a bit…much.

When I was a young dev
My senior took me into the city
To push my code to prod
He said "Son, when you promo
Would you be the savior of the broken
The buggy and the OOM'd?"

Bottom rack retail workers distributing replica weaponry is hardly a good basis for a system of government

Half grandfathered in from a period when UK was a commonwealth, and ANZAC were not technically independent.

ISO-3166-1 has a lot of “countries” that aren’t actually independent - but useful to have codes for because they are geographically distinct.

ccTLDs are based on the ISO two letter country codes - it’s deferring the responsibility for cleaning up the British mess to ISO

Nope. They already have .mu

Once the treaty is signed, the .io cctld will phase out over 5 years.

Unless ICANN get greedy and grant an exemption.

You can still adopt or go through surrogacy, so don’t think you’re completely out of the woods yet

Once upon a time, I accidentally created a folder named “~” in my home folder (the company provided scripting framework would inconsistently expand variables, so the folder had a ton of stuff inside it).

I ran “rm -rf ~” and only panicked when I started to wonder why it wasn’t taking too long.

Good news is that it only managed to get halfway through my local checkout of aosp before I stopped it. Bad news was that it nuked most of my dotfiles.

That guy? He was horrible at AA. Did something to the water cooler and now everyone is falling off the wagon

I mean, it is shit posting

I think we finally figure out how to not poop for three days

None built in from what I recall. That was from back in 2011, so it’s possible things changed since.

Reading through, it looks like retries do exist, but remember that duplicate packets are treated as a window reset, so it’s possible that transmission succeeded but the ack was lost.

I remember the project demos from the course though - one team implemented some form of fast retry on two laptops and had one guy walk out and away. With regular wifi he didn’t even make it to the end of the hall before the video dropped out. With their custom stack he made it out of the building before it went.

I’ll need to dig through to find the name of what they did.

To be fair, because of window size management it only takes 1% packet loss to cause a catastrophic drop in speed.

Packet loss in TCP is only ever handled as a signal of extreme network congestion. It was never intended to go over a lossy link like wifi.

Seriously though - JIRA isn’t always a massive pain in the ass. It’s just the way it’s used that sucks. Workflow restrictions so devs can’t move tickets from testing back to in progress, dozens of mandatory fields, etc.

When your tools start dictating your workflow rather than the other way around then it’s time to switch tools.

Friends don’t let friends use JIRA