logoalt Hacker News

_DeadFred_today at 12:26 AM3 repliesview on HN

Imagine you work as an aerospace engineer. Imagine having to couch/overthink everything your say in communication so that it can't be taken out of context later. You literally have yearly training on how you have to communicate and in hugely impacts how people work because one dumb one off comment in email can financially end the company when an accident occurs.

and that's before you get to the fact that you have to defer how your IT systems work to the lawyers from the big overseas insurance company that covers your company/products. It's a major pain to get them to sign off on collaboration systems because they are such a discovery risk not because you are hidings, but because of how people communicate especially around issues. As far as discovery goes with aerospace, if your engineers anywhere acknowledged any problems, you are hit. How can you have a good product/continuous improvement when you can't acknowledge issues in writing?


Replies

whatshisfacetoday at 12:33 AM

I'd be surprised if you could find a single aerospace engineer with more than five years of experience who hadn't learned to couch everything they say in a way that made it difficult to misinterpret or change by taking out of context.

benhurmarceltoday at 10:35 AM

I am exactly in that line of work and that's not my experience. All our written communication is kept basically forever in case of investigation, and yet people don't second guess everything they write.

At the same time I've never seen anyone knowingly defend anything unsafe or illegal anyway.

And my experience is that the "blameless" culture is very present.

lxgrtoday at 12:51 AM

> You literally have yearly training on how you have to communicate and in hugely impacts how people work because one dumb one off comment in email can financially end the company when an accident occurs.

Wow, that's a very sad contrast to the blameless failure analysis culture of aviation accidents/incidents I've heard so much about (and actually see as a model for what we should strive for in software).

I can't even begin to imagine what kind of organizational chilling effect this must have on the way problems are discussed.