“Rolling back” estimated bills is reprocessing the historic metering data by an older or newer pricing plan version. As i mentioned in another comment someone will have messed up a metering type vale (eg GB/B). Thats why theyll need a few hours to redrive the metering data.

$7,000 of credits is no problem. At that time a friendly neighborhood PM or director could issue the credit without much oversight.

Your problem is the time period. Amending a bill in the same cycle is EZ. Fixing the previous cycle is a PITA but pretty common. Issuing amendments for the previous financial _years_ would be a huuuuge PITA going through finance etc.

Services emit metering values that arent directly tied to prices. Every SKU/line item is defined in a “pricing plan”, with a unit type, regions, and price per unit. The metering records are joined to a pricing plan based on account id, region, sku, etc. mess up the unit type in the pricing plan and the metering data conversion doesnt work, and you get crazy bills.

My recollection is that PA Semi was very much for the architectural and design talent, even though it was an “asset purchase” and all the existing Power & military chips were hived off.

For Intrinsity I recall a lot of interest was actually in their existing graphics work and EDA. ISTR that those early mobile GPUs were what they focused on.

I was in the mansfield org circa ‘07-11. I spent a lot of time flying between cupertino and austin/bee caves that first year.

- “iaas” (OCI) is growing 50% yoy and the bulk of the revenue. - “cloud license and on prem license” (new software licensing) is $5B or ~10% of the segment - ERP, peoplesoft etc arent broken out but are also very large in their market categories.

Edit: I know recall JCS is reported to have said something like “its bullshit” about the Israeli operational plan/end state. But subsequent discussion focused instead on “can we”, not “how” or “should.”

And the current civilian administration is doing a pretty thorough job of eliminating anyone who _would_ point out previous lessons learned around strategic outcomes, going in to conflict necessitating clear & achievable exit criteria, creeping escalation, conflating use of force with success, etc.

Theres a reason everyone talked about “adults in the room” last time and anyone inclined to those kind of thoughts, or voicing the associated opinions, is absent now. And personally Id say that amplifies culpability, nit diminishes it.

This was already reported a month or so back. It also matched some of the early, unprepared, statements along the lines of “acting before they (israel) do.” And matches previous reporting along the lines of JCS/NSC giving “nuanced” advice which is easily interpreted as agreement or compliance.

Note: if you want to conflate “containers“ with an entire job management and scheduling system (“k8s”) then you’re not actually talking about the current target customer for VMware.

Larger providers can also get bulk zone access for TLD’s and whois/registrar data. For this use case it’s relatively easy to create a time based filter on that. Anything that’s “new” will be de facto absent from your “allow” check and create an implicit deny.

Then your large IT provider or recursive DNS system will probably layer in RPZ where they can insert explicit denies at resolution time. Either based on QNAME, RDATA, zone, etc.

Second, its critical that treasury bonds are denominated in USD. The us gov controls the monetary policy and can choose to inflate away the debt over time. This is in contrast to EM debt where they get trapped with foreign denominated bonds. See also the tensions around EU debt, greece, etc.

Transcription is both too good, and not good enough. The magic generative content only makes it worse.

Too good: a lot of commercial settings forbid persistent transcription because it makes an easily discoverable record of specific details. Thats a business risk that can be mitigated simply by having participant notes or summaries where the secretary can omit sensitive discussion or present consensus without specifics. And notes/summaries also introduce a interpretive defense with some “strategic ambiguity.”

Not good enough: if you look at STT its still probabilistic. The actual evaluation output will have just much data about alternate words/phrases as the selected choice. That leaves lots of room for creating alternate impressions or representing words that werent actually spoken. The fact that people _think_ a STT transcript is authoritative only makes this worse.

When you add generative inference in top (eg summarization) you exacerbate both problems. I suspect that counsel is more accepting of summaries as its less likely to contain specific discoverable terms, likely to diffuse responsibility and specificity, and your judge/jury will be more amenable to “the ai summary is wrong” than “the transcription selected the wrong vowels.”

And yes, Im sure theres a very lonely radar bug for this. But even MM of revenue wont fix “edge cases” like this.

Operationally, and tactically AFAIK, the US has been dominant. Strategically it appears to be a massive failure, mainly because there was no actual achievable strategic goals going in to this war. Read some of the reporting on JCS advice and cabinet level decision making leading up to the war. It's illuminating (again and again) of the risks on overly loyal advisors and getting the advice you want, not the advice you need.

In short, the allbirds financiers are taking a slightly reduced interest payment in exchange for the option to capture stock price appreciation if the gamble finds a greater fool.

Surely they wouldnt mind bragging about their fantastic GAAP P&L in their filing docs. Maybe its the pesky quiet period theyre trying to avoid, so they can be even more transparent about finances and equity holders.