jlawer

Purely observed correlation between catastrophic error reports. So now I carry a “tiger rock” with me. I figure there wasn’t much of a downside to avoiding swearing in my agent instructions.

I have a theory that swearing actually results is less comprehension of instructions by the model due to lack of training data over more conventional MUST.

We were reviewing reports of situations where the models failed to follow directions and there was a common thread of some where when the operator got the model to acknowledge the rule breach, it quoted back something that included swearing.

I don’t have the data to truely look into it, but I did give the instruction to my engineers to avoid it as a “might be a problem”.

> the average person in a post-work future needs to have a genuine ownership stake in the AI compute that's making things happen, not just welfare funded from the profits of the billionaires who own it

So nationalise the AI companies? Isn’t that exactly what that would be. I am not opposed to the idea of public ownership, but I think some of the existing investors aren’t going to be happy with that option.

I wonder if we end up with z series running on arm long term.

The value in z series is in the system design and ecosystem, IBM could engineer an architecture migration to custom CPUs based on ARM cores. They would still be mainframe processors, but likely able to be able to reduce investment in silicon and supporting software.

For Grok’s sake you hope this is data that was public, something that was buried deep that it has surfaced.

It’s a shame transparency is so poor here. A simple grep of the training data would likely give a clear explanation of where this has come from.

I would think the comparison would be the BYD ATTO 3 premium vs Tesla Y premium.

Australian sticker price for the atto 3 is under $45,000 AUD, a smidgen over $30K usd.

With a wife with a mobility scooter and working 30-90 mins away from the office depending on traffic, I picked on up (salary sacrificing) as the lease costs less than what I was paying for fuel on the Kia carnival (Sedona in the us) each week.

Tesla model 3 entry level was another $10K AUD for a car with less features.

Job / Position description means something more... It means that your expected to do the task and perform well at it or you will be let go.

Generally you don't put those skills in a Junior PD, but you would expect a Junior to take on these tasks if they hope to progress. The Mid level PD would have it listed and as the junior shows they can meet each and every additional skill, the option of a promotion becomes available.

Guess we need to do a follow on study, what a way to use the R&D budget. I don't think I will be short of volunteers.

I look forward to publishing the differing effects of XXXX Gold vs Stone & Wood in order for us to optimise the department budget. However I will be waiting for further research before starting trials of Bundy Rum. I am concerned the development efficiency will be offset by repairing punched screens.

My understanding is that they were tracking significantly fewer parts in Excel as many of what they are now tracking as separate parts were previously tracked as a single part (kind of an assembly). I think they were previously tracking somewhere in the 100-200 parts in Excel.

My understanding for why this is coming out now is that there was a talk Vowles has done recently where he mentioned the massive hit getting ready for this season because they changed both Excel into the new ERP systems AND started tracking each individual part, which complicated the transition and why it was such a rush for Williams to be ready for this year.

Confirmed, the successor to Starship will be SkyRanger, later to be replaced by the Avenger once they master Elerium-115

I know Nested Virtualisation is a thing on both KVM and hyper-v, what is different about what you could do on "big iron"

The obvious question is how effective at carrying small improvised explosives is it?

Yes, we have a single tickets repo seperate from the code, and use GitHub projects collect tickets from multiple repos into one board.

Team of 8 devs + other supporting roles. Devs are happy with it, PM and portfolio management not so much, as you loose a lot and GitHub projects is still fairly new.

Why did we do this? We were acquired and the new corporate has different ideas and we lost Jira. Project managers end up manually syncing status of epic tickets between GitHub and their project management tools. We make it work, but much more labour intensive the Jira+Jira Portfolio