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

If your company uses some sort of code checking tool on PRs, there may be a requirement that all functions have a docstring, even if it’s obvious what it’s doing. Leads to silly comments like this quite often

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

I’m a test automation developer, I’m not necessarily bound by the platform that the application is written in unless I’m writing white-box tests.

subprocess.Popen(["bash one-liner"], stdout=PIPE, stderr-PIPE, text=True)

Web testing is also done in python. Selenium has support in all major Python test frameworks. I’ve done SE-only tests in Robot, hybrid SE/Python using BDD with Behave, etc.

Unless I’m testing a language-specific API, I’m probably going to use Python…

Python is the language of choice for most test automation

eh, just squash and merge. Feature branch can be messy as long as main is clean