cerberus

joined 2 years ago
[–] [email protected] 1 points 1 year ago

Yes I understand and agree that this is not the right path to take.

Automation however is inevitable. There is proven tech that’s existed for decades, the only new things being added here are taxiing, takeoff and landing (and honestly takeoff and landing are already automated, they’re just not used as much)

[–] [email protected] 12 points 1 year ago (8 children)

Considering most all commercial flights are fly by wire except for taxi, takeoff, and landing… not sure

[–] [email protected] 4 points 1 year ago

Had a stroke you mean?

[–] [email protected] 4 points 1 year ago (2 children)

Yeah looks great, what lights are they

[–] [email protected] 15 points 2 years ago (3 children)

5 tons you say?

[–] [email protected] 7 points 2 years ago

Versioning is one way; if you have an API you can have different versions which will can change depending on version.

E.G. let’s say you have contact information coming through an API… the database can largely remain the same, but if you want to add a field or change a fields name, you could upgrade the version. When the app is ready to use the new version, switch the app over.

Rereading your question once more, I believe you can just resolve all your issues with a common API.

[–] [email protected] 8 points 2 years ago (6 children)

This was a great read, and if your mind is open to evidence, lays out a lot of facts as to why those who follow Trump are susceptible to hate speech rhetoric.

[–] [email protected] 46 points 2 years ago

Great! Thanks for keeping things up to date and running!

 
 
 
 

if you're having trouble using shreddit lmk; ended up getting it running pretty easily

view more: next ›