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”.

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.

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.

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.

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.

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.

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 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.

It was Bullshit, textbook bullshit : https://press.princeton.edu/books/hardcover/9780691122946/on....

https://en.wikipedia.org/wiki/State_of_Origin_series

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

He spent time himself researching the law and going through the process, but he can't claim for that

Even if you had the complete plans to a top of the range EPYC processor, you would struggle to Fab it, and by the time you were able to do so, it would likely not be valuable.

The problem is DC CPUs are driven by power efficiency. Building the most efficient processors requires the latest manufacturing nodes and incredible optimisation. Generally your chips must be within the last 1-3 generations, the inefficiencies are very noticeable. Power efficiency impacts cooling and density, additionally driving the economics of DCs.

The existing manufacturers have the teams to churn these out, for someone else to join the club it would be a massive investment (just look at home many failed Server Arm companies there have been). You can also see that even companies that have ARM server chips are mostly just tweaking cores provided from ARM, not developing their own from scratch.

Given this I think your unlikely to see this unless the economics change. If one of the cloud giants decided that they aren't getting value with ARM, they might end up developing their own, potentially even using RISC-V as the architecture, but I can't imagine them wanting to share it. Unless you end up with a multi-cloud consortium deciding that its in all their interests to build a common processor in order to turn it into a commodity. In that case you might get an open source core out of it, but the fab problems still remain.