No offense but pilots are probably at peak automation since their job has mostly been reduced to being a glorified AutoPilot system babysitters mainly needed for regulatory hedging. The ground transportation is still fair game though.
For example, engine falls off. The automation doesn't know that happened, it just sees various problems like the hydraulic pressure falls, and for some reason the engine thrust went to zero.
When I was at Boeing, an incident was recounted to me where the autopilot glitched and rolled the plane over into a vertical dive. It was going so fast it entered "separation", where the airflow no longer flows over the flight controls. In other words, the pilots were just along for the ride.
But the pilot figures, since we're dead anyway, let's try lowering the landing gear and see if it slows the jet down. He did, and it ripped the doors off and bent the gear back, but it slowed enough that the flight controls could get a "bite" and the pilots were able to regain control and landed safely.
I'm not sure how the news being delivered by a carbon-based pilot would help with the dying part but I guess hospice care exists for a reason.
Wow. You clearly have zero idea of what a pilot's job is, and it shows.
You are also severely underestimating how much work and regulation would be required to replace pilots. And this work can be undone in a flash the first time automation messes up.
Also note that plane automation heavily relies on sensors. Many plane accidents were caused by faulty sensors even with humans in the loop.
How can software engineers maintain a healthy "manual programming" skill set? What employer would be willing to pay for so much wasted time for their software engineers to do deliberate training courses, or willing to accept the productivity loss from their engineers occasionally working manually for practice, when working manually is so much slower?