Or a piling or filing or filling or recording.

In order to be using any of these DNS providers you would have already needed to switch away from your ISP’s default DNS. This must be targeting the people who knew how to change their DNS servers but somehow forgot.

I mean, it’s pretty accurate if you ignore the elephant in the room.

Hot sauce! I didn’t know about that. Gonna follow that thread for sure. A laptop with good Linux support, choice of CPU, trackpoint that’s upgradeable and and supports hot pluggable hackable modules! This is the future I want to be in!

I went with a Thinkpad for my most recent upgrade but I really, really wanted a Framework. If there was a straightforward trackpoint keyboard kit available for the Framework I’d be all in next round. There’s no love lost between Lenovo and I at this point.

So much this. Health insurance is the primary reason I have a salaried position.

Yup, total recall.

For a real trip check out this Japanese laptop:

It was the style at the time! Lots of CD players had flip up tops, as did the Sega Saturn. I assume it was because the slide out tray mechanism was more expensive and also more fragile.

Just writing deployments by hand? That’s probably not going to be super fun to manage across a couple clusters and a bunch of namespaces. Might be worth looking at kustomize a bit before you get to having a real prod environment. I use helm at work but it seems like people consider kustomize to be the new hotness.

A “swap” file is for holding pages of memory that have been swapped from RAM to disk.

Hi fellow traveler. I think you and I took a similar path to get here except I started with a 33.6k modem in high school and the catch phrase I remember is “Information wants to be free.” What’s your thought on copyright reform? Somewhere along the lines of 25 years and non-renewable? How you feeling about the concept of software/algorithm patents? Talking about stuff like this is reminding me of /. :)

Windows 95 OSR2.1 (with USB support!) -> RedHat 5.1 (from a CD included in a book at the local Barnes and Noble) -> Debian 2.1 (or so? apt was a fucking revelation. RH5.1 was pre-Yum) -> experimented with Gentoo in college for a couple months (doesn’t everyone?) -> Debian -> Ubuntu (maybe around 8.04?) -> (a bunch of cycles between Debian, Elementary and Ubuntu) -> back on Debian now and it feels like home :) (but I have Elementary, Haiku and Ubuntu on some old laptops I play with sometimes)

• As long as you have something besides prod you’re probably fine for now. If you need dev to be more “real” later you can add it. It’s a two way door: https://shit.management/one-way-and-two-way-door-decisions/
• Interactions between k8s pods during a deploy, and PVs moving between nodes mainly. K8s just has a metric butt ton of moving parts and as you deploy more stuff to it over time you increase that number of moving parts
• yeah, one namespace per dev could be fine. Are you using helm? Kustomize?

Anyone remember the dotcom boom (and bust)? The AI hype bubble reminds me a lot of that. It ticks all the same boxes: wild new tech showing up all the time, stratospheric hype, corporate FOMO, a money spigot that seems to be spraying investments at any company with AI in the name, business plans that lose money per unit sold but plan to “make it up at scale.” And unlike the last 16 years this is all happening when interest rates are non-zero so money actually costs something.

When I think about the dotcom boom and bust I tend to group the companies into 3 or so broad categories:

• Companies that were doing the right thing at the right time. These are the companies that weren’t necessarily pushing the envelope from a technology perspective; they were building a business model on where the technology was at the time but that could improve as the technology did. In the dotcom days the business model that most exemplifies that was e-commerce. Amazon and eBay grew up in the dotcom era and survived the bust no problem because they were already profitable by the time the investment money stopped flowing.
• Companies that were way too early. These are the ones that had a great vision but that were too far ahead of the technology curve. Did you know we had online grocery delivery in 1999? Webvan tried to move fast and corner the market but due to mismanagement and the tech and market not being ready they crashed hard in 2001. Grocery delivery is of course totally commonplace today, but even if Webvan wasn’t mismanaged I find it highly unlikely that they could have succeeded when less than half the country even had dialup and the common wisdom of the day was to not type your credit card number online.
• And last but not least, you’ve got the startups that never really had a business plan and the existing companies just jumping on the hype train because of FOMO. Startups were getting investment dollars just to … build a website. Big companies were putting up totally contentless “web experiences.” Suddenly every breakfast cereal had a website. Did it have nutrition information? No. Online ordering? No. Mostly it was just marketing drivel and maybe a recipe for snack mix if you’re lucky. These are the ones I think of when I hear that Taco Bell is going “AI-First.”

Anyways, there’s more I could say about why I think this will play out faster than crypto did but this is already a wall of text. For all the people who missed the dotcom boom: Enjoy the hype cycle. It’ll be a smoking crater before you know it. :)

On mobile so I’m not going to get into the weeds too much but I do have a couple questions that might help you make a decision:

• Do you have a “staging” or “testing” environment where things are deployed first before they go to prod? If so it might not be a huge deal to have the dev’s individual environments not be exactly what prod looks like
• Are you actually in an HA type scenario where you expect updates to not actually cause downtime? If you can tolerate the odd 2-5 minutes of downtime now and then during releases then you don’t need to go that crazy making sure all your pod deployment strategies are exactly perfect. That means you can probably tolerate more divergence between dev and prod
• Are the devs expected to get all their containerization stuff exactly right before going to prod? Or is that mostly your job? If the expectation is on then they need the tools to test their stuff. If it’s on you then you just need to figure out what you need to accomplish that.

Anyways, welcome to the k8s admin club and may whatever god you believe in have mercy on your soul.