eschneider

In this sort of situation, always take the first offer. Subsequent offers are always worse.

Just spitballing here, but I bet Palantir could shut it off if the bill wasn't paid.

After doing this a few decades, one of the things I've discovered that, working 15 hours a day is insanely overrated. A shocking number of 'impossible' problems become quite easy if you just think about them lightly overnight.

It looks bad on the insurance paperwork.

Cool. How many did they add?

Yeah...AGI isn't going to successfully replace Chris. But you know what this shit will do? It'll teach people that any information that they share about what they're doing or how they do it will ultimately be weaponized against them.

That'll work out well in the long term.

Failures in production remain expensive.

This...has been a feature on security cameras for at least a decade.

There's a fine line here when dealing with customers. Sometimes it works well to answer the exact question, if you can, and follow up with "Can you tell me a bit why you're asking so I can understand a bit more about the problem?" Once you tease out a bit more about how they got there, it's often possible to offer better solutions and it never feels like you blew off their original ask.

It's ok to reject for any number of (or no) reasons. Nobody needs to feel like a jerk for taking a project in the direction they want.

This seems...fine?

I know when I run into bugs in a project I depend on, I'll usually run it down and fix it myself, because I need it fixed. Writing it up the bug along with the PR and sending it back to the maintainer feels like common courtesy. And if it gets merged in, I don't need to fork/apply patches when I update. Win-win, I'd say.

But if maintainers don't want to take PR's, that's cool, too. I can appreciate that it's sometimes easier to just do it yourself.

Well, this is disappointing. They were my goto site for keyboards. :/

That sorta surprised me. Once I could identify a connector type from a schematic, it was almost never a huge problem getting them in small (1 to 5 piece) quantities. It's mostly a question of finding the right distributor.

Because when the AI customers explode N months down the line, you don't want to be on the hook for a new factory.

Interesting...1999 is probably a bit early for that Bosch to be running one of the usual ECU update protocols like UDS. It sounds like it's in the bootloader and looking for a valid executable. So the FW updater is likely in the bootloader.

If you can open it up and find the JTAG pads, it should be simple-ish to use a JTAG reader to dump the image and then you can figure out the update protocol from that. It's unlikely to be complicated.