Gotta hype that AI :| .. 280,000 hours is 134 years for 1 person working 40 hour weeks, non stop. If that were a team of 20, that'd be about 6 years ... Just to UNDERSTAND the code! Where the hell did they get that metric from? And why is that code so horrible that it would take 134 years for 1 person just to comprehend!?

Totally agree! And I also wish there were a case sensitive version as well ... but unfortunately that's a job of the filesystem itself :/ NTFS is 31 years old. It's old enough to have died in a war. It lived through the dotcom crash. It knows the origin of Pokemon. It saw Melissa and Stuxnet have its grandchild. It's older than formalized versions of C++ and C. It saw the birth of Java, C#, JavaScript and so many other languages. It's so old it actually knows what a book is. If it ain't broke, don't fix it ... spoken like a true [insert old person joke here] ye olde NTFS.

I remember splicing RGB cables into my coax so that my old CRT could play content off my PC that had a TV tuner wtih S-Vid out.

What's old is new again.

I'm not asking for "free" ... but when I go to WalMart or Target, I don't have to buy Tampons along with my potato chips (no matter the brand or flavor).

Ala-cart is lost on the for-profit entertainment system.

Having worked on hardware/electronics before as a the "coder", I can completely agree that it's hard to WFH when you have industrial tech or proprietary hardware that you can't take home.

To that, what I would do would be to build out simulators or emulators that would "react and respond" just like the hardware did, either by just displaying a simple prompt or even making some simple UI that showed what the hardware could/would be doing.

I did this for a few reasons; 1. it made testing my code before deploying to a million dollar machine much easier, 2. it allowed other dev's to get in the code and make fixes/updates as well especially if there was only one prototype, 3. it allowed the company to train people in a sim before going direct to the hardware, and one of the biggest reasons was that I could then WFH a bigger chunk of time because I didn't need access to the hardware to do the majority of my job.

I know that's not always an option for many due to various reasons, and totally not disagreeing with you, just saying that sometimes WFH is even possible when you have to deal with hardware.