Just pull the trigger, we both know how this ends.

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.”

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.

Last week, used a package over a cake. Poke Cake.

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.

“Where does this green wire go?”

I appreciate HW engineers and techs. I’m not afraid of datasheets, circuit diagrams, or a mso and they’re always patient enough to explain things to me so I can make the rocks behave. Or at least tell me how to go from diagram to board lol.

“the serial output from my test unit turns into garbage and it happens at completely random times!”

“Did you make sure they were plugged in all the way?”

“WHAT?!?! ARE YOU SUGGESTING I DON’T KNOW WHAT I’M DOING?!?!”

Some time later

“Yeah, it turned out to be the serial connection was loose.”

They’re they’re, it’ll be all right.

Haha! Jokes on you! It was mostly gnu makefile calls to ruby scripts!!! You’ve just broken the build a million different ways!

Last time somebody did this to me there were a lot of sit downs about how to properly chop up large scale code changes and why we don’t sit on our own branch for two months.

“How long will this take to get in?”

“Well, two weeks for me to initially review it, a week for you to address all the changes, then another week or so for me to re-review it… Then of course we have to merge in all the changes that have been happening in primary…”

Good ones don’t.

Hey, we’re working on making this way more fair. Places like Kentucky are trying to repeal child labor laws so that they can at least pay these poor for profit lunch serving companies.

Just a short jog north (from Iowa) and all the kids get lunch. Even though mine still insist on a home lunch… Ugh.

I’m working on moving to local control as much as possible for my smart home stuff. Switched to zwave for my thermostat from nest, excellent move, I don’t lose connection (and automations) randomly anymore.

Also ripping all my optical media for jellyfin to avoid relying on these assholes deleting stuff from their streaming catalogs for tax breaks.

It’s not just google, it’s all of these companies.