I’ll use an LLM to write bulk code, unit tests, other boring stuff… but, I specifically only have it write code I’m already very familiar with, and even then, I hand-code it every so often, like 1 in every 3 times I’ll do it by hand to make sure I’m still able to. If I have to look something up, then I’ll stop using an LLM for that task for a long while.

Amateurs not keeping at least one backup off-planet SMH

Seems like a great thing at first, y’know, wife AND Kate? Awesome!

Next thing you know, it’s “Kate does this, why don’t you?” and “You don’t satisfy me the way Kate does”, then “Kate and I are going to go on a cruise together.” Before you know it, it’s “I think it’s time we took a break, I need to focus on my relationship with Kate”; before you know it, you’re living by yourself in a van down by the river!

zip ties are single use though, better to get a pack of velcro cable ties

Well, when was the last time you looked at a hammer and thought “y’know, you’re pretty smart!”

and the one that keeps getting slept on for some reason, watch breakpoints - stop when foo is changed. Great for figuring out what is screwing with your data when foo mysteriously changes

Bad analogy.

This would be more like the property management having a record of what apartments are rented, and having a second list of who is renting apartments (but not which one), and the landlord wanting to know who is renting apartment 420 so they can draw up eviction papers.

From someone who does this for a living… vary your names and addresses. Less chance of collisions if your suite teardown fails to clean up properly. Depending on your needs, having a hard-coded unique name/address per test can be fine, or if you’re using Python, there’s a library called Faker that will generate ISO-valid test data. It’s also a bit easier to see where a teardown failed if maybe an exception got swallowed.

Doesn’t need to be any design flaws, a few minutes with a welder and/or a truck load of concrete at the door once they’re in there would render the whole billionaire problem “solved”, Hotel California style.

This can be generalized to say that programming has become such a diverse profession that you will find experts in one area that know very little about others. There’s simply too many things that are programmed in too many ways for anyone to know it all anymore. Hell, that was the case in the 70’s and 80’s too.

I’ve been using it to write unit tests, I still need to edit them to mock out some things and change a bit of logic here and there, but it saves me probably 50-75% of the time it used to take, just from not having to hand-write all that code.

Something like this is useful as well if you have a large item to convert since you can offload that processing to your server/NAS and not have it bog down your PC/phone/etc

Break it up into functions with names that describe what it does, then the script becomes basically a sequence of function calls and is easier to read and troubleshoot.

yeah, 98 was trash. 98SE was good

IIRC vote buying is against Reddit TOS, so might have been removed for encouraging it

No arguments there, if you’re gonna depend on a piece of code, you better own it or have a rock solid plan b.

left-pad was the first thing that came to mind for me

https://en.wikipedia.org/wiki/Npm_left-pad_incident

Are you slow? nobody is arguing that you can hot swap a GPU. That’s not what people are correcting you on.

YOU claimed that PCIE is not PLUG AND PLAY

NO. PCIE is not plug and play.

That was your comment. It was wrong. You were wrong.

Dude… you’re the one that said PCIE isn’t plug and play, which is incorrect. Plug and play simply means not having to manually assign IRQ/DMA/etc before using the peripheral, instead being handled automatically by the system/OS, as well as having peripherals identify themselves allowing the OS to automatically assign drivers. PCIE is fully plug-and-play compatible via ACPI, and hot swapping is supported by the protocol, if the peripheral also supports it.

There’s a reason it’s nickname is helldesk