dgriffith

It's because the two most important metrics of EVs , range + performance, aren't visible.

And - let's be honest here - those metrics are mostly the same across manufacturers due to battery limitations.

So they have to overcompensate with style to stand out from that other EV that uses the same base platform and the same battery chemistry and the same charging system and etc etc.

rustfmt

is stopping me from writing code like this, and I have never been more happier using it after viewing this.

harmonic response several times stronger in flight than had been seen during testing,

Pogo oscillations at higher g loads towards the end of the burn? 🤔

People don't just leave leaking apps out there for consumption.

Ha! Welcome to corporate, where vendors sell you software and say that the hardware has to have 128GB of ram and when you poke around a bit you discover a single JVM with constantly growing memory usage with a script that restarts it every time it runs out of resources.

AND a log file that describes - in typical Java excruciating detail - the precise lines in each module where the devs allocated resources but didn't free them. About 40 times a second.

I loaded the video, paused, jump jump jump jump jumped through the timeline looking at the thumbnail images, about 5 seconds of actual playback while I watched them mess it up, more minor adjustments in the timeline, paused for 15 seconds at the thing I actually wanted, closed the video.

Good luck getting any kind of decent metrics out of that.

I can skim documents at 800 words a minute, they are mostly nicely arranged and indexed/sectioned. Compare that to videos where half the words are "um, so", and it's no wonder I prefer text.

Lol between the top paragraph and the bottom one the number of partners increased by 23. I wonder how many partners they have now?

Today I had the pleasure of trying to search for how to shift a chartjs array and finally had to try and watch a "tutorial video" where they allegedly discussed it.

Cut to me clicking around just trying to find the screenshot where they are actually doing the thing that I want to do, and then they proceed to fuck up its usage three times with much scrolling back and forth through their example code that they didn't show in full anywhere and rapidly clicking between windows while they got their shit together.

I just wanted to see like, three lines of code.

Maybe I should have just asked chatgpt.

Motor oil tastes funny.

It's pretty simple:

• USA and Russia have public talks and say they have a "good solution".
• Ukraine says ,"We are not interested in a solution negotiated by a third party and the aggressor in this conflict"
• USA says "oh look Ukraine isn't coming to the party here these negotiations were in good faith we can't believe how they're acting we are withdrawing support."
• Ukraine gets stomped on, USA and Russia divvy up the spoils of war.

Lots of expensive industrial equipment runs these kinds of processors still. You can still buy motherboards with 8 bit ISA slots even, although you'll pay quite a premium.

But all of that kind of gear typically runs its own distro with an in-house build system. For example, my work uses a flavour of Buildroot for their embedded Linux systems and you can just set whatever processor type you like all the way back to plain old i386 when you build it.

Map usage times for a week.

In the middle of a non usage time type the string of characters that are first typed at the start of usage time.

Then open a browser using keyboard shortcuts (does Win+R open a browser in Windows if you type a URL in?) , type a URL, type in all learned username password combos, close browser using keyboard shortcuts.

It's only one wire in the cable, and it's not the wire, but it looks like the pin, or possibly the crimp point on the female pin.

So a few possibilities:

• Bad pins. Female pins (sockets) have internal wipers that grip the male pin and there is also the crimp connection. Bad QA on those leads to hotspots in the pin under high current draw. I'd probably go for this explanation, looking at the photos.

• Bad electrical layout on the card that means that the bulk of the current goes through this pin. Milliohms on the track traces are enough to cause imbalances. This might be balanced out by having a small-but-still-larger resistance in the (standard) cable, which leads to:

• It looks like thicker cabling is soldered and heatshrinked to smaller cabling that actually goes into the pins in the connector. There's a reason why industrial cable connections aren't soldered. Possibly a solder connection on another cable has broken and hidden in the hearshrink leaving more current to pass through this one.

• Following from this it's also quite possible that the thicker cable with less resistance , now has less voltage drop across it, and simply allows more current then designed through a connection already at its limit.

• It's quite possible that there are different pins/connector sets for different current draws. This cable might be using the wrong connector with the same physical size but lower current rating. The fact that the cable has been soldered to skinnier wires in the actual connector suggests this, but it's quite possible that the connector is the right one.