Is it not safe to expose externally with ssl yet?
Is it not safe to expose externally with ssl yet?
It would be a crying shame if someone were to figure out a way to force those e ink displays to refresh fast enough that it kills the batteries on those things…
I’ve still got my old Anova, Bluetooth one. I don’t even use the app ever, I can set it up with the wheel and buttons. Still works great after like 5+ years. That said, I won’t be recommending them to anyone going forward.
So how long till the Supremes rule that CBP is not only allowed to search your phone but also to perform colonoscopies at checkpoints 100 miles inland and sell the resulting videos to extremely wealthy perverts?
Beyond any issues with the owner of the company, these cars have multiple dangerous issues.
You cannot treat a company that makes physical stuff that can endanger lives the same way you treat a software company that makes a leisure activity platform.
Iterative design for a purely software environment is way more forgiving than iterative design for physical hardware or even software that interacts with physical hardware. You can profoundly fuck up the backend for a website and take the whole thing down until you could roll back to last known good production, you won’t kill anyone, but you’ll make the line go down temporarily.
If you profoundly fuck up an iteration on an embedded vehicle system and don’t catch it because you don’t respect safety regulation or existing engineering norms you can and will kill people.
Analogue doesn’t have firmware that can reject a device based on id.
So you can reverse engineer a replacement part if you absolutely have to.
It’s not the iPads themselves, it’s the addition of Bluetooth and/or wifi to support them. I agree that they can alleviate a lot in terms of paperwork reduction etc. My issue is the additional exposed surface.
It doesn’t, that’s just a very common reaction to these types of articles. I recall having some very intense discussions around stuff like iPads in cockpits. I’m on the “not a fan” side, but I’m also not making avionics software anymore either.
Certification is expensive. But updated dbs are pretty huge and seem to only get bigger over time. Stuff like radio firmware tends to be in the hundreds of KBs though, so for that it really wouldn’t be a big deal either way.
These should be USB sticks, but otherwise this is preferable to something like wifi.
You do not want to stop requiring physical access to avionics for updates and reprogramming.
The fewer surfaces for entry into the avionics systems the better and if that means an engineer schlepping a database update on a thumb drive to the cockpit that’s what you want.
I spent the better part of a decade on avionics, and while this as a headline sounds bad it’s one of the few things Boeing shouldn’t be mocked for right now.
That’s crazy. You can’t do six. It’s seven! SEVEN MINUTE ABS!
The real question is when they’re purchasing the child size targets.
This won’t have terrible consequences at all.
Welcome to late stage capitalism where the game’s made up and the points don’t matter.
Privatize the profits and socialize the losses.
I’ve tried to use “AI” to help me with minor programming tasks, or to start basic projects, it’s really bad. As in, it takes me more effort to fix the garbage it outputs than it would have to write it from scratch. In addition to that, it writes things badly in non-obvious ways. Junior engineers make similar mistakes to each other, because they’re working logically. “AI” makes weird mistakes because it’s not working in the same way a human mind does.
Gotta be able to boot Nazis. Otherwise it’ll be Nazi bar.
We no longer have humor, it’s been beaten out of us by code reviews and merge conflicts.
I’ve just rejected firmware updates and will continue to do so as long as possible. If it gets to where I can’t do that anymore for some reason I might leverage my professional expertise into remedying the situation more permanently.
They’re getting worse too. Retroactively blocking third party toner cartridges.
I caught a junior trying to reimplement an existing feature, poorly, in a way that would have affected every other consumer of the software I’m a code owner on a week or two ago. There’s good reason to keep them around.
PRs suck to do, but having a rotating team of owners helps, and linting + auto formatting helps with a lot of the ticky tacky stuff.
Honestly, the worst part is “newGuy has requested your review on a PR you requested changes on but he hasn’t addressed” that’ll get you in the ignored pile real quick.
Zwave. Keep your control local. There’s some decent smart locks out there with zwave.