“Nice try… FBI”

Don’t forget Louisiana… My wife’s favorite.

The Pope?

Believe it or not, also Hamas.

Above everything, lack of curiosity. If someone is uncurious, it’s a big red flag to me.

Capital idea!

“it would be far more efficient to create company scrip to pay them with, it’s not like they need anything we don’t provide right here.”

Is it not safe to expose externally with ssl yet?

Hilux >>>>>> Cybertruck

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…

Nate Silver is a prime example of this thing that happens a lot with technical people. They get good at describing what is and then they start to think they understand “why”. Sometimes a good understanding can lead you to the why of a situation, but often you need actual experts to analyze the data you’ve collected.

The whole thing about the way his methods work is based on not actually understanding the interactions of the inputs he’s selected.

His book was interesting, but I wouldn’t trust his analysis too much.

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.

I work in an esop. It’s pretty cool in that we own the company in shares based on tenure, it’s not like a union though.

We don’t vote on the CEO or the board, we have third party trustees that manage the esop account.

We aren’t beholden to external shareholders, which is the absolute best part. Line doesn’t go up, it really just affects our retirement accounts, but even then our valuation takes into account stuff like cash on hand and contract stability. So… We have pretty fiscally conservative management, which is a great thing for us.

Generally speaking I do things myself because it’s cheaper, in that it lets me allocate cash in higher quality versions of things than I would otherwise be able to afford. I grew up pretty poor and that was how my family did things. Car breaks, that’s why you buy a Chilton’s. Appliance isn’t working? You can always order the part for a tenth of what it costs to have the appliance guy tell you what’s wrong. AC quit working? Those capacitors are super easy to replace and only cost $7.

Now I could pay people to do more things for me, but it’s only under certain circumstances.

Sometimes it just boils down to something my Dad told me underneath a car (or a house maybe) like 30 years ago: “Nobody is gonna care about your shit more than you do.”

Why bother hacking when they can just buy it all from the same folks the cops do?

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.