This stuff goes back decades, and I suspect both parties look the other way because when they get in power they're doing the exact same thing.

That's aside from the build-out jobs.

Anyone who works anywhere close to data center build including construction, networking, sysadmin is cleaning up right now. Their wages have doubled and demand is huge.

Maybe it is 100 permanent jobs, but that's huge for a small community, and the thousands of temporary jobs make an impact, too.

In my local area, there's routinely local opposition to substations built due to growing residential demand and water infrastructure facility build.

They're old boomers who don't want anything built, especially not if it will economically benefit their children.

On the flip side, software I used that was majority built by 'real human engineers' coding by hand is utter garbage.

As a recent example, Facebook Ad Manager is extremely slow, plagued with UX issues, blatant state management problems (double scrollbars, iframes, random rerendering).

Other examples of 'real engineers' building software include SAP, Oracle ERPs, most banking software, most government websites. They're trash.

Human engineering is the reason your personal information gets leaked every other week. Human engineering is the reason there's a critical vulnerability in core software every day at this point.

The average software engineer cannot build good and secure software. Just like the average car driver is a safety disaster on the roads.

This is because these models act as a productivity enhancer for engineers. A 1x engineer becomes 5x. A 10x becomes 50x. And so on.

Slop is a risk that can be mitigated through team policy, skills and other mechanisms. Nothing we produce is slop, in fact incidents are down dramatically. It's more stable than ever.

Nobody is measuring LOCs. They're up, but that's barely relevant to me. I'd rather measure defect rate, rollback rate, sprint velocity, roadmap adherence etc. Those measure actual progress.

I don't use LOCs as a reason to manage people out. But if they're vehemently refusing to even try AI, other metrics will make it obvious that they're falling behind.

The window for the gunslinging no-AI coder sitting in the basement with Mountain Dew and cranking out thousands of lines a day is essentially closed now.

My previous superstar 10x engineers are now superstar 50x engineers thanks to AI-enhanced output. All metrics are up. There's also no negative effects either, in fact incidents and faults have declined.

This position is the equivalent of the delivery driver in the early 1900s who refused to get an automobile and instead insisted his horse and cart is better.

Know that if you oppose a productivity tool that transforms every other engineer, you will be managed out. I've seen it happen more than once already.

My point was that this news is of the hack, and not of bombshell revelations from the emails themselves, which kind of indicates there's nothing there.

If you found the smoking gun, you would say "look I found a smoking gun!".