There is always a nugget of truth, but that is used to justify disproportionate and a poor response. Clinton cut 400,000 employees, but hacking at headcount was not how it was done. It was a slow process, following the normal government processes and in collaboration, not the wild adversarial and demoralizing method under Trump. Lawsuits didn't happen because the rules were followed. The biggest method used by the Clinton administration was eliminating government processes which didn't need to be performed anymore, which takes time and diligence to uncover and wind down in a way which doesn't invite lawsuits. It is slow work but produced results.

They are following the Buc-ees business model. A very limited number of locations which are mega-fuelling stations. It is far more efficient and easier to implement than running dozens of locations. A typical Buc-ees has between 80â"120 gas pumps, with all the recent major builds having 120. They do have a small number of smaller stores in rural communities but they are the exception. They have been very successful with this "build-big" approach. You don't have to worry about underperforming locations or mis-estimating the demand if you become *the* highway stop.

Because that's what class actions are for. A company harms a lot of people, but it only hurts each a little bit. Individually it would be frivolous to sue, but as a group of harmed people you can exact a legal win to punish the company. And lawyers who can package up a group of people and present the harm to a judge need to be compensated because otherwise the class action lawsuit wouldn't happen. Class action lawsuits don't always end in justice, but they are a reasonably efficient method to try to find it.

Many people, including myself, don't write code everyday, and it's not something we have to be good at. Any assistance is appreciated since the alternative is to bang away for hours, copy stuff from the Internet and try to make it fit the problem I'm trying to solve, resolve bugs etc until somehow the code works. The new tools are not a perfect time saver, but they still save much more time than they "waste".

Perplexity.ai uses several different models (automatic or manual selection) and gives sources.

Similar experience. One of my children had been doing Duolingo for 2 years in a single language. Had no idea how to say the number 7,8, or 9, by themselves or in any other context.

A subsea power cable that long is a bit unusual, as in it just isn't done unless there is no better alternative. It would be very expensive. The other options might also be expensive but you can buy an awful lot of power plant for 32 billion dollars and you wouldn't have the risk of an anchor incident. The insurance alone on a cable that long and expensive would be eyebrow-raising.

And fiber in my area. An upstart fiber company did the hard work of putting lines in my whole neighborhood about 2 years ago. This prompted AT&T to finally wake up and they upgraded their copper lines to fiber last year. The new fiber company offered no caps and a flat monthly fee and so Comcast quickly lost at least half the neighborhood.

I'm sure it uses some very cherry-picked numbers.

Let's say a query uses 3000 watts for 10 seconds. That's probably within an order of magnitude because a 300w consumer GPU can do quite a lot in 10s, but the bigger models will be using a bit more hardware.

If every bit of that 0.00833 kWh of that went into boiling some water, you could vaporize about 13 grams or about 1/40th of a bottle of water.

We then need to consider that the data center cooling system will add about 1/3 more, and that to produce that electricity in a 40% efficient (coal) power station entirely cooled by evaporative cooling would a little more than double it again.

But we should also consider that not all thermal power stations are that inefficient, that even in evaporative cooling setups significant heat is removed by conductive b means, most thermal power stations in the US West are air cooled, and a lot of power will be coming from renewables. On a cowboy calculus basis you're back to 1/40th of a bottle or less.

One could argue that this doesn't include the energy to train the model, but amortizing that over all the queries made during the economic lifetime of the model probably doesn't add much more than 1x the power used by a single query. I would say that shouldn't be included in what a single query costs anyway.

In any case it isn't anywhere near using a bottle of water.

It is a big deal though. Pressure vessel and piping integrity are not typically major issues for a rocket this far along in development. Their QC program must be in a sad state for something like this to happen. It points to a culture that emphasizes speed and not quality, which completely aligns with how the CEO works and how the company is run. And that won't get better quickly.

It's very common for pipes to freeze in the winter. Most policies will cover the consequential damages of this even if the damaged pipe itself isn't for some reason. Frozen pipes are the justification for recent steep insurance increases in Houston of all places.

Didn't namedrop any viable alternatives either. Not a lot of passion in thse comments for anything else as well. Guess I'll stick with Firefox?

My guess is that being a contractor is a bad look, and may make receiving certain types of classified information more difficult. There's a lot of reasons why this might be the easier and less controversial choice.

It's not a completely unreasonable contract provision, in theory at least. Allowing a customer to service their own stuff while still being responsible for the maintenance contract is a potential nightmare. Suppose a Navy monkey makes a mistake and causes more damage in trying to fix it. Then you have to get contract managers involved and try to calculate and negotiate on how broke it was before (vendor responsibility) vs how broke it became due to the Navy's mistake. Given the bureaucracy involved and the foreseeable paperwork nightmare, everyone wants to avoid that. I don't know of many service contracts where the vendor doesn't have first right of refusal.

If you're within hand grenade distance, that distinction doesn't really come into play. At those distances, you want the enemy killed or surrendering. The limiting factor is the amount of explosives you can put into the device while still being able to throw it a reasonable diatance, and being small/light enough to carry several since it usually takes more than one to do the job.