Live data from Hacker News

Trying to become a better developer by learning more about aviation

medium.com

31–40 of 92 posts

Re: Trying to become a better developer by learning more about aviation

#31
post #26

Earlier quoted context omitted.

I like the term "defect" it's more accurate than "bug."

Is it? I think the definition of Bug is literally defect. Maybe it carries a different 'weight' for some people?

A “bug” is specific to computer systems. It traces back to a literal bug (moth) trapped in a relay and is an external factor with no responsibility attributed.

A “defect” is a declaration that something is evidently faulty with a clear onus on the vendor to fix.

Re: Trying to become a better developer by learning more about aviation

#32

It seems like there are almost daily HN front page items about aviation, and a lot of pilots in the comments. I've wondered about the reasons for such an overlap in interests among people here. I fit this myself: I grew up playing flight simulators, studied computer science as an undergrad, was a military helicopter pilot for a while, and then went to grad school for computer science. Along the way, I've personally m…

I studied Air Traffic Management = basically managing and evolving ATC systems. I work now as a product designer, which for the most part involves conceptual design, dealing with complex flows and optimising them, dealing with imperfect humans using those systems, "solving problems" that go far beyond design. I often say it's the exact same job, just in slightly different domain.

Re: Trying to become a better developer by learning more about aviation

#33

Makes sense if your software is responsible for keeping people alive. Most of us don't need to work to such a standard (thankfully).

There’s a certain level of arrogance that comes from the people who don’t work on safety critical stuff, that we could all do without

Re: Trying to become a better developer by learning more about aviation

#34

If you want to become a better developer through aviation, I can't recommend anything more highly than reading through NTSB accident reports. Learn from others the many, many ways small problems and misjudgements become accidents. It'll change the way you build things.

I'm really glad I stumbled on your comment. I train people in conflict resolution and emotional leadership and I've been looking for places to learn more about conflicts and causes and I think these NTSB reports could provide me a lot of examples from which to learn. They remind me of how at college I had a class on business communication and we discussed the communication issues that led to the Space Shuttle Challen…

the umbrella term for this in the aviation world is "crew resource management" [0] or CRM.

a major focus has been on encouraging less-experienced members of the flight crew to speak up if they notice something wrong, and ensuring that the more-experienced pilots are open to receiving that feedback instead of adopting an "I'm more senior, I know what I'm doing, don't question it" attitude.

0: https://en.wikipedia.org/wiki/Crew_resource_management

Re: Trying to become a better developer by learning more about aviation

#35
post #16

If you want to become a better developer through aviation, I can't recommend anything more highly than reading through NTSB accident reports. Learn from others the many, many ways small problems and misjudgements become accidents. It'll change the way you build things.

It takes two major failures or errors today to cause the crash of a commercial transport aircraft. All the single points of failure have been fixed. You'll see this repeatedly in NTSB reports. Failure or event A happened, and then failure or event B happened. Single-event crashes of airliners are very, very rare.

> All the single points of failure have been fixed.

Now you've jinxed it!

Re: Trying to become a better developer by learning more about aviation

#37
I have taken so much inspiration aviation industry when designing and operating software system. In addition to the inspirations mentioned in this blog, I find the idea of "antifragility" in aviation quite fascinating, where every near miss is studied, documented and checklisted across the entire aviation industry. This means that every near miss improves the resilience of the entire industry. We need to build similar means of learning from others' mistakes in complex software systems as well.

Re: Trying to become a better developer by learning more about aviation

#38

It seems like there are almost daily HN front page items about aviation, and a lot of pilots in the comments. I've wondered about the reasons for such an overlap in interests among people here. I fit this myself: I grew up playing flight simulators, studied computer science as an undergrad, was a military helicopter pilot for a while, and then went to grad school for computer science. Along the way, I've personally m…

I became a pilot at age 20, got all my ratings up to a frozen ATPL, worked as a flight instructor, gave up my airline ambitions due to deteriorating eyesight, became a software developer, worked on other stuff for 20 years, rekindled my interest using Xplane, got a job working on a new flight planning system for a major airline...

Re: Trying to become a better developer by learning more about aviation

#39

Earlier quoted context omitted.

The cliff note version: More people die because they're in a hurry/feel pressured and push a marginal situation when they should have known better than you could possibly believe.

This is one of the sadder reasons why scheduled aviation is so safe. When flying planes is your job, why would you ever push your luck? I feel so tired, that storm looks pretty nasty, or the maintenance guy seemed like he had no idea why it's doing that - fuck it, we're not going, get the airline to put you on another plane if there is one, otherwise get them to pay for your hotel, I'm not flying anywhere today. One…

My CFI said "graveyards are full of people the world couldn't do without, it can wait a day" - important to remember for many things, if you start pushing your luck it'll eventually push back.

Re: Trying to become a better developer by learning more about aviation

#40
post #26

Earlier quoted context omitted.

Is it? I think the definition of Bug is literally defect. Maybe it carries a different 'weight' for some people?

I think for many people “Bug” can imply something that crawled in from outside and messed up the system, “defect” implies that there was an avoidable deficiency in the specification or the implementation. The engineering mindset might prefer “defect” since it implies that we can fix the process and improve the quality of future products, whereas “bug” implies these things are just a fact of life and you can’t expect…

I’ve started using “defect” instead of bug for these reasons. The “bug” euphemism implies the software was once correct, but then problems crawled in from somewhere external to infest the otherwise good software.

That’s really not how 99% of software problems happen. They are defects because the software was defective from the moment it was conceptualized or typed in.

“Bug” tries to soften/downplay the developer’s role in producing a defective program.

Post reply on HN