Twirrim

Much, much less from what I understand.

I've spent most of my career non-FAANG. Health insurance has been fine previously, and mostly I know folks outside of the tech industry having similar coverage. FAANG health insurance isn't that great a thing these days. It has been nickled and dimed about as much as anything else.

I've a neighbour who declined, and then got hit by layoffs. It was quite a gamble, and they lost out big time.

Honestly, if work was to come at me with a buy-out offer, and I was in a position to be able to afford to not work for a few years, I'd probably accept. Maybe go find some non-tech work for a little bit to stretch the dollars and ensure I have health insurance.

We're in such a bubble at the moment, things are going to get really rough.

I've seen so many "truthy" results coming back that suggest it's not even remotely as smart as you might hope.

I'm mostly starting to have some success telling TPMs and engineers to ask chatgpt to give them appropriate code that generates more accurate answers.

The frustrating part about an LLM is at a fundamental level it's designed to do the wrong thing, it's designed to provide an answer for things it can't do, e.g. one argument I've been in recently at work is someone using it to summarise numerical data. They've a raw data spreadsheet they're putting into ChatGPT and asking it to produce a report in a particular style. So the LLM is doing its job, predicting the tokens to emit, and not actually doing mathematical analysis of the underlying data.

I had a team proudly show me how they were feeding their dashboard data into an LLM to predict growth needs, instead of doing basic linear regression or any number of pre-existing basic statistical analysis. The part that depressed me the most on that was it was a bunch of engineers that did it, the people you'd most hope would understand what an LLM is/does.

lima uses vz, so it's built on top of hvf, seems perfectly fine and lightweight to me.

Where, exactly, does Amazon classify the PHP RCE as Important?

I'm not sure anything says what your editorialised title, and comment link says.

They were calling out that an NGINX CVE that was Important took 20 days. They're saying nothing about what classification Amazon has set on PHP,.

> So, from the CVE publication to an available fixed package it took 20 days, not a month.

They specifically call out that it's not the same as the Nginx case:

> In contrast to the PHP's case, that CVE wasn't Critical, but only Important, that doesn't have the same urgency.

Given the RIFs and what they've done to engineering culture, I can't help but wonder what else they've done. Like maybe cripple their architectural review processes that might have caught such things?

Assuming that it could have been spotted in their inbox, amongst a probable flooded of LLM slop like a number of security mailing lists for open source projects that I know of. We've all seen the impact on open source github issues, hackerone etc. The same is happening to standard email disclosure paths.

I've bought something the other week that I'm still waiting to be delivered. The shop was fine, sent it out within hours.

The carrier has been letting them down every single step of the way (and to add insult to injury, I have to use that damn "Shop" app to track the delivery.) From a pick up on the 1st of October, they've supposedly had the package go back and forth between Los Angeles and here a couple of times.

Not sure what the price difference is for them to have used this carrier, but it can't be worth it compared to the fuss both of us are having trying to get the carrier to actually deliver the shipped product. The vendor is going to send a second one if the delivery doesn't happen to day like the carrier pinky promises it will (they've promised for 3 days straight it was going to be delivered that day, so I'm not holding my breath)

To emphasise your point, this is already happening. It's not theoretical. Data Centres across the world can already get signals from their grid, and will do things like proactively switch to local generators.

Nearly 20 years ago I had such a wonderful debugging experience when the power grid where I lived sent a "switch to backup" message and then milliseconds later a cancellation. The colo's power system got jammed between generator and mains electricity and everything rapidly ran out of UPS backup power and died. I found so many dependency loops between servers that day, took me hours to get things back up and running.

For whatever reason, the daemon has been refusing to start and Codex has been grumbling to me. I was wondering where the daemon had come from, and thought maybe I missed something previously and that it had just broken.

They just use npm as a binary delivery mechanism, for whatever reason (I guess they expect all their users to have npm?)