I will have a look at this new package, it looks promising
In every case, like the engineering team in this article demonstrates, the developer experience and end results have exceeded expectations. If you haven’t used Elixir, you should give it a try.
Edit: Fixed an editing error.
As an example, we just rolled out a feature in our cloud offering that allows a user to remotely call a robot to a specified waypoint inside a facility, and show real time updates of the robot's position on its map of the world as it navigates there. We did this with just MQTT, LiveView, Phoenix PubSub, and a very small amount of JS for map controls. The cloud portion of this feature was basically built in 2-3 weeks by one person (minus some pre-existing code for handle displaying raw map PNGs from S3, existing MQTT ingress handling, etc.).
Of course you _can_ do things like this with other languages. However, the core language features are just so good that, for our use cases, it blows the other choices out of the water.
At first, we used an erlang lib emqtt, but it was left unmaintained and then removed from github. We had to switch to something else. Not completely happy, but it works for us
https://www.youtube.com/watch?v=J1F_UJaaP1A
I don't know how common this is in aviation, but I had to think immediately of the Japanese railway workers.
PS: the same thing can be seen in this (admittedly silly and slightly outdated) aircraft carrier operation video:
If I'm acting as the non-flying pilot, my job is to talk to ATC, set radios, load flight plans and instrument approaches, etc. As an example (slight variation), if ATC gives us a flight level change, I would dial in the final altitude on the altitude pre-select. Typically, I'd repeat the clearance back to ATC, put my hand on the dial, change it and leave my hand on it until the flying pilot says "I see FL230".
I sometimes use the point technique before changing something, or after while repeating "I see ..." or "I did ...". It's really effective at making sure you don't do things mindlessly.
Changing MCAS another dozen times and updating the manuals does nothing to prevent this from happening in new future system design.
Deleted Comment