Oh Untied! Oops!

[form810]

IDK?

"I'm not a 'strong' programmer. That's why I work in IT... for an airline." ???

'Tards 'tarding?

United Airlines resumes flights following nationwide ground stop

United Airlines flights are resuming following a brief nationwide ground stop due to a computer issue, the airline said.

abcnews.go.com

FAA lifts brief nationwide ground stop for United Airlines

"Earlier today a software update caused a widespread slowdown in United's technology systems," United Airlines said in a statement.

www.cnbc.com

 

[EAD]

Computer issues happen regardless of scale (especially at scale). Also, water is wet, news at 11

 

[knot4u]

IDK?

"I'm not a 'strong' programmer. That's why I work in IT... for an airline." ???

'Tards 'tarding?

United Airlines resumes flights following nationwide ground stop

United Airlines flights are resuming following a brief nationwide ground stop due to a computer issue, the airline said.

abcnews.go.com

FAA lifts brief nationwide ground stop for United Airlines

"Earlier today a software update caused a widespread slowdown in United's technology systems," United Airlines said in a statement.

www.cnbc.com

Untied?

 

[form810]

Untied?

That's the ONE World! Thanks for noticing!

 

[form810]

Computer issues happen regardless of scale (especially at scale). Also, water is wet, news at 11

Ok, good to know. Great culture of competence!!!! I'm psyched!!!

Is that culture also why airplanes crash? Also, if an airliner crashes, news at 11 will be the crash! I guarantee it!

 

[EAD]

Ok, good to know. Great culture of competence!!!! I'm psyched!!!

Is that culture also why airplanes crash? Also, if an airliner crashes, news at 11 will be the crash! I guarantee it!

Trolls are going to troll but I'll feed you this time.

My company had an IT meltdown a couple years ago that grounded ALL of our flights for hours and the resulting mess wasn't cleaned up for days. It occurred during a server swap (1 out of 3 servers) that IT had apparently designed and tested successfully before but this time something went wrong and it took down everything. It couldn't wait for a low volume time either.

As a result, new processes were put in place to mitigate the impact of another IT meltdown. These manual processes are slower, but would allow the company to continue operating instead of grinding the operation to a halt.

The point is, as dependent as we are on technology and as large as complex as these "structures" are, an IT failure is an eventuality. What matters is how the company responds to it, learns from it, and implements processes to dampen the effect of future failures because there WILL be another failure (only the size and scope can't be known).

Also, a proper culture of competence accepts that mistakes will happen and learns from them. The ASAP/ASRS system is a poster-child of this philosophy. Demanding IT be perfect is as asinine as demanding pilots be perfect. Accepting that "mistakes happen" doesn't mean hand-waving away major issues, it means accepting the limitations of being human and building processes to hopefully trap the next one

 

[Ian_J]

Trolls are going to troll but I'll feed you this time.

My company had an IT meltdown a couple years ago that grounded ALL of our flights for hours and the resulting mess wasn't cleaned up for days. It occurred during a server swap (1 out of 3 servers) that IT had apparently designed and tested successfully before but this time something went wrong and it took down everything. It couldn't wait for a low volume time either.

As a result, new processes were put in place to mitigate the impact of another IT meltdown. These manual processes are slower, but would allow the company to continue operating instead of grinding the operation to a halt.

The point is, as dependent as we are on technology and as large as complex as these "structures" are, an IT failure is an eventuality. What matters is how the company responds to it, learns from it, and implements processes to dampen the effect of future failures because there WILL be another failure (only the size and scope can't be known).

Also, a proper culture of competence accepts that mistakes will happen and learns from them. The ASAP/ASRS system is a poster-child of this philosophy. Demanding IT be perfect is as asinine as demanding pilots be perfect. Accepting that "mistakes happen" doesn't mean hand-waving away major issues, it means accepting the limitations of being human and building processes to hopefully trap the next one

This is a really well thought-out and logical post. Thanks for this!