Posts Tagged ‘lockheed’

Life of A Programmer — Session 4.5 — How can you become more skilled than your fellow employees.

April 8, 2015

PRINCIPLE 4: ACCEPT NO VERBAL ORDERS

In 1961, Lockheed had a standard document called an ANVO. This meant
“ACCEPT NO VERBAL ORDERS”.

This is a very important and valuable concept. Spoken commands are
more likely to be misinterpreted.

Your boss might only make verbal commands. In this case, give him
your interpretation in writing.

When an ANVO has been issued, make sure that its required effort
is properly documented in your log.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 4.5 — How can you become more skilled than your fellow employees.

November 5, 2014

PRINCIPLE 4: ACCEPT NO VERBAL ORDERS

In 1961, Lockheed had a standard document called an ANVO. This meant
“ACCEPT NO VERBAL ORDERS”.

This is a very important and valuable concept. Spoken commands are
more likely to be misinterpreted.

Your boss might only make verbal commands. In this case, give him
your interpretation in writing.

When an ANVO has been issued, make sure that its required effort
is properly documented in your log.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 4.5 — How can you become more skilled than your fellow employees.

August 30, 2014

PRINCIPLE 4: ACCEPT NO VERBAL ORDERS

In 1961, Lockheed had a standard document called an ANVO. This meant
“ACCEPT NO VERBAL ORDERS”.

This is a very important and valuable concept. Spoken commands are
more likely to be misinterpreted.

Your boss might only make verbal commands. In this case, give him
your interpretation in writing.

When an ANVO has been issued, make sure that its required effort
is properly documented in your log.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 8 — Tools Help Make The Software Engineer

September 22, 2013

With the right development program, you can develop Error
Free Software.

There are some historical examples of this truth.

In the early 1960’s, Fortran was a major computing languages.

The Fortran compiler had a never ending bug list.

PL/1, the next major language, was far more reliable.

I used it at Lockheed for over five years and never encountered
any errors.

PL/I was designed in strict compliance with the principles of
simple precedence.

MORE IN THE NEXT MESSAGE