Government: So I see that your H-1B jobs are all for "Computer Programmer (I)" and your U.S. hires are all for "Software Engineer (III)" or "(IV)".
Company: Yes. We haven't had much luck in hiring level one programmers here in the U.S. We put the jobs out there, but nobody is applying.

Prevailing wage for the job doesn't mean what you think it does. A bunch of sleazy outsourcing firms made sure of that.

I'm genuinely curious, while you make a good underlying point for which there is plenty of data to back it, why on why would you pick an example profession that has such an insanely low sample size, and a profession known for its mortality too. Seriously dude, we have huge aggregated datasets showing how average across the population there are improvements. WTF would you use an example subset of 45 people to make your case.

Cars aren't using machine learning. Learning is done elsewhere and a model is applied to the car. That model is equal across all cars where it's applied, no different from any other algorithm. Fix a problem in that model and you fix it equally in all cars.

It's still a correctable behaviour. Human behaviour is not correctable. The biggest improvements we have made in road safety is through systems that take away the requirement for human skill.

Skilled working visa schemes like H1-B are not about attracting world-class experts in anything. They are about attracting skills in specific areas where there may be shortages. The idea of raising the wage limit is a good one, but the reality is H1-B can be any speciality requiring a minimum of a masters degree. Heck there's even a cave out for fashion models to get H1-B visas.

This one will serve only to drive talent off shore. Imaging training people and then exporting that knowledge to another country by disincentivising working locally.

Large houses in hot climates don't have enough roof space to accommodate the number of panels you would need to displace grid power. Using obsolete panels that generated less power when they were new is only going to make the problem worse.

Leaning into unreliable power sources when demand is increasing is just going to make any supply issues worse.

Someone posted what they pay for electricity in California and what their buy back rate is and their rates are insane.

Surprisingly little money. As soon as the extra cost exceeds the cost of hiring one person to maintain workarounds, it is cheaper to do the workarounds. Tricks like that might ostensibly work for individuals, but they fail badly every time when you're talking about big corporations.

Yes, but to be fair that's how things work in cutting edge world. AI LLMs in generic form are a bag of dicks, but on the flip side when we have alpha tested other products they've brought a world of benefits. The idea of testing cutting edge on employees isn't inherently bad, it just failed miserably with copilot.

I don't think so. I think it systemic of two things:
a) AI agents are actually not that good. They constantly make mistakes and hallucinate things. I've had Gemini provide citations that say the opposite of what Gemini summarised, I've had CoPilot screw up meeting summaries, I've had ChatGPT spit out absolute rubbish that didn't make sense.
b) Microsoft is desperate to rush this shit into the market unfinished. It's not just CoPilot. I've updates to Office 365 with active regressions that get fixed in future updates. Teams constantly changes, sometimes for the better, sometimes for the far worse (seriously why can't I stop streaming incoming video when I'm on a shitty connection anymore). I've uncovered serious bugs in Azure DevOps, it's just endemic to how Microsoft rolls out software these days.

It's a dual whammy of AI + crap supporting infrastructure. I don't think CoPilot is gimped on the onset, I just think it's not very good.

Precisely what did people get here? A security vulnerability automatically patched in the back end quickly with no evidence of exploit? It sounds like this was addressed faster than any windows server patch ever was, including past Active Directory.

I'm not sure what you're saying here, that we should all switch to the cloud because of how quickly the issue was addressed and how seriously Microsoft took the situation? I think you're trying to say something negative about a story that is actually a rather big success story for customers and Microsoft. Not the right platform for your rant.

Microsoft *SUCKS* at naming products. Not only new products, but confusing existing products. What the heck is Microsoft 365 by the way?

Precisely no 32bit games are being dropped as part of this announcement. I have no problem running my entire steam library on 64bit hardware. The Steam client itself won't support 32bit going forward, that's no the same thing as 32bit games losing support.

I think the opposite. I think this is an example of why human drivers will be easily surpassed by automated systems. When a problem is fixed by a vendor they can roll out a fix that fixes everyone. We've been trying to fix human behaviour for a century and have failed at doing so.

Ten tiny companies, ten meters.