Programming Throwdown, Episode 168, Godot.

Take it away, Patrick.

Welcome, everyone.

Starting with a bit of a...

A rant? Is that? I don't know. Man, it's so negative.

I have something to rant about. We have a cup, a pair of rants.

Oh, okay. Is there a word for that? You know how there's like a flock of geese?

Is there a word for a gaggle of rants?

Okay. All right. Going to buy right. So one of the things that has been like a recurring theme and it feels like it's getting worse.

Now, I guess like to set the context if this is your first, first episode with us,

maybe you don't know. But I don't know how you would call the like role of software I do.

So maybe it's particular to the kinds of software I do. But it's always been persistent.

So it's some combination of embedded application engineering. Maybe web is a bit better.

I don't know. But maybe back end is pretty

similar. And that is the number of things you're expected to know how to do on a computer that

really don't have anything to do with programming, but you're just like, you're supposed to know

how to take care of it. Like just random things, not just the kind of slightly strange things. Like, you need to know how to set up your computer, like plug in the keyboard and mouse and, you know, monitor. Not, not admittedly, these things aren't hard and most of us know how to do them. But like, this isn't really related to programming. Like, you could not know how to swap hard drives on your computer and install new RAM, but occasionally, like, someone the other day

had a hard drive, you know, crap out. And so the IT person just, like, sent them a new hard drive

in the internal mail and, like, here, installed a new hard drive or whatever. Now, people

I mean, that is not common. I mean, weird, right? But, like, you wouldn't be also surprised

that a programmer was expected to know,

like, how to install their own hard drive. Like, because it's, I guess it's part of my rant. It's just

...