rco8786

It's worth noting that there are several other (nearly objectively better) EVs on the market with larger battery capacity than the CT and have V2H/Powershare tech.

Of course, it's just one example.

History is not in the side of this argument

AWS goes down too

Yes. If you think you don't have any SPoFs then I've got a handsome bridge for sale that may interest you.

Lots of companies run on railway

I don't really understand what this is. It seems like it's the same as all the other agents

I was in that boat also

It sounds like you could be on my team, tbh.

Everyone in SWE (who got into it for the love of writing code) is experiencing this. I've been direct with my team about it being a legitimate feeling of grief and the grieving process that comes along with it. It's been helpful for folks to hear that they aren't alone in that feeling.

And also that on the other side of that grief is something new and potentially exciting, but very different than what we're all used to.

There are 12,000+ data centers around the globe including ~1300 "hyper scale" DCs. It seems like at a glance that we are actually fairly distributed physically. Not to say that DCs wouldn't be valuable military targets but I would not call it centralized.

No it's all still React

Just a semi-educated guess....they plowed a bunch of cash into an "AI native" IDE product after getting spooked by Cursor.

Sounds eerily familiar to how we talked about ChatGPT doing [various things that it now does easily] when it was released.

Nothing you’re saying excludes AI from writing code. In fact I’ll bet my salary that boto3 has AI written code in it and you happily trust it.

You can’t say a new project is battle tested. Those are mutually exclusive, regardless of who or what wrote the code.

Low trust is not a reason that code can’t be battle tested. All non battle tested code starts as low trust by default. AI written or otherwise. I’m not even sure what you mean by fragmentation tbh. This feels like a very vague argument in general.

But you’re right that it’s the hill climb of human trust that AI is going through right now. Some of us are just farther along than others. Some of us refuse to consider trusting AI out of fear, and not rational evaluation of its capability.

That's because it's new. libflac and libcurl didn't come out as battle tested code. That takes time and...battles. And what are those battles if not people seeing issues with what those libraries are doing and fixing the code? There absolutely no reason that AI written code can't or won't become battle tested.

Of course. And then we fix the problem. It's no different here. The point is that reading the code first is absolutely not a requirement when adopting a new library.

I believe I can understand how a library behaves from the README and docs. I do this all the time. We all do.

Are they? I've never been able to blame library authors or hold them accountable for code running in my production environment.

> believing you can understand the behaviour of a program without at least reading the high level code is truly silly.

have you ever used a library after only reading the README and documentation, or do you always pull the source and read through it before you think you understand it?

Yes I’ve noticed AI speak popping up more in verifiably human communications also.

That's extremely silly. drunk, inexperienced, and elderly drivers are all human drivers. You can't just exclude them from your baseline because they are not in perfect driving form.

Let's also exclude young drivers, stupid drivers, distracted drivers, drivers who never took driver's education classes, short drivers, barefoot drivers, glasses-wearing drivers who forgot their glasses, and one handed drivers.

The insane variation of human drivers is exactly why AVs should ultimately bring vehicular deaths down..which is the goal.

> I don't need to consult a datasheet or design an AI test suite with a zillion simulations and a bunch of closed-course tests.

Traffic engineers have been doing this for decades though?

I don't know anything about this specific case but this exact thing will be a major barrier for autonomous vehicles to overcome. Instead of benchmarking AVs against the current, human-caused number of vehicular deaths - people will naturally benchmark AVs to 0 and treat every instance of death as a failure of AVs, even if the reality is that AVs end up 99% safer than human controlled vehicles.

Please, tell me more about my educational background.

Seems to me that the argument is really "are my premiums a passthrough to medical providers" and I have a really hard time answering Yes to that.

If they are, then what do we call it when my medical expenses surpass my premiums? Negative passthrough? Contra passthrough?

What do we call it when I pay premiums for a year, never use a dime of it, and then cancel my insurance? I don't get that money back, nor does it get passed through to medical providers.

Do life insurance companies consider my premiums to be a passthrough to my eventual benefit payment or do they count them as revenue?

No, they're collecting money specifically on behalf of a 3rd party and then giving it directly to that 3rd party. They are custodians of that money only, it never even hits their bank account (goes into a dedicated trust account before distribution), and they cannot legally keep it. THAT is an actual passthrough.

We have this in our harness markdown:

```

## Comments

Use comments extremely sparingly. Most comments should be at the request of the user. When something warrants a comment, keep it to one or two lines: what the code does and why it's necessary. No background narrative, no replaying the investigation or failure mode, nothing a test name or the commit message already says. Applies to specs too. If a comment needs a paragraph, make the code clearer instead.

```

The comments Claude was leaving got absolutely out of control. Just lines and lines of LLM drivel that was barely intelligible and not remotely relevant to what a code comment should be used for.