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

June 30, 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

Software Engineers are Quality Assurance Managers

June 30, 2015

Have you ever noticed that Quality Assurance, ISO-9001,
and the Deming Cycle is taught only in Business Administration?

I have found that when Quality Assurance was taught in Engineering
Schools, it was in Engineering Management Classes.

Is Quality Assurance just an Engineering Management Problem? Is
a Software Engineer a Quality Assurance Manager?

Computer Programs are special Deming Plans to be Done at the
client’s site by a computer not by a human being.

Software Engineers are, in reality, Quality Assurance Managers.
For the most part, they do not realize this fact.

WHATIFWE taught Quality Assurance, ISO-9001, and the Deming
Cycle to all Engineers in our Engineering Schools?

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

June 30, 2015

PRINCIPLE 3: MAKE SMALL SELF-DOCUMENTING SOURCE FILES.

Each of your source code files should not be longer than
three or four pages.

Each source code file should have lots of descriptive
comments.

Each source code file should reference a section of
your plan.

Each variable name should be instantly identifiable.

Keep in mind that your source-code goal is to be able
to instantly relate to its design and use when you open
its file.

You might have to answer a question over the phone a year
after you complete the project.

MORE IN THE NEXT MESSAGE

The Purpose of My Blog

June 30, 2015

The original purpose of my blog was to provide me an easy
means of reporting my activity on my personally funded
research and development activities on error-free software
development methods.

I subsequently expanded the purpose of my blog to encourage
others to improve their skills by conducting their own
regular experimental process.

I became a software engineer in 1966 due to an experiment
that I had performed. I have never taken a course in
Software Engineering. You are encouraged to take a similar
path. If my tools can be of any benefit, they can be
downloaded free-of-charge from my web-site, http://www.whatifwe.com

Life of A Programmer — Session 4.3– How Can You Become More Skilled Than Your Fellow employees.

June 26, 2015

PRINCIPLE 2: KEEP A WRITTEN DAILY LOG

Keep an accurate written log of your activities.

This log should contain the beginning and end time
for each activity.

This log should briefly define the activity and its
results.

Where appropriate, the log should reference particular
sections of your plan.

The “Weight of The Evidence” is always valuable in any
progress report.

You will always be able to show management your current
status at any time.

MORE IN THE NEXT MESSAGE

I, A Programmer, Am Also A Quality Assurance Manager

June 26, 2015

To be strictly compliant with ISO9001, Programmers must
use enforceable standard methods and processes.

Assembly Language Programmers used macros for common
multi-instruction processes. These macros, once developed,
were never changed.

Software “breaks fatally” when it illegally writes. The
error cannot be fixed and it might take the machine down.

There are many error detection code segments that programmers
use during checkout and then remove before delivery.

I developed a C++ Macro Preprocessor to provide a highly
competent macro capability to facilitate using error detection code.

Unlike the Macro Assembler, my C++ Macro Preprocessor prepared
source code exclusively from the Macros.

IBM developed the first piece of error-free software in 1968.
It was the PL/1 Compiler and it was a joy to use.

The PL/I Compiler was error free due the strict application of
the requirements of simple precedence.

In the late 1960’s, Bob Prince of Lockheed developed a simple
precedence based compiler writer which I used.

In the early 1970’s, I used the Lockheed Compiler Writer to
prepare non-compiler applications with moderate success.

I had difficulty with the Compiler Writer on non-compiler
applications because data flows differently than processes.

I realized many years later that a multidimensional precedence
process could manage both processes and the data flow.

I learned how to make a set of coupled precedence processors
that “policed” the use of classes and the flow of data.

I updated my C++ Macro Processor to render it capable of
deploying simple precedence principles to my programming efforts.

My Macro Processor satisfied the Standard Methods and
processes requirements of ISO9001.

I inadvertently became a Quality Assurance Manager.

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

June 26, 2015

PRINCIPLE 1: WRITE AND EXECUTE A PLAN

In many companies, when a new major task is assigned, the
responsible software engineer will be asked to make a plan.

This plan will be presented to management and the senior
programmers for their comments and criticism.

In most cases, this plan will become obsolete and forgotten
with the first software development keystroke.

To become more valuable in the eyes of management, you must
strictly execute the plan that you have prepared.

It can be done and you will learn how to plan your tasks much
better than anyone else

MORE IN THE NEXT MESSAGE

The Computer Wisdom of Bugs Bunny

June 26, 2015

Do you remember the Bug’s Bunny cartoon where he pops out of the ground
in the middle of the desert and says “I think that I should have turned
left at Albuquerque”?

Mistakes always happen; some because of stupidity, some because of greed;
some because the required knowledge was not available, and some because
we are just human beings.

We are currently experiencing a great many security problems due to
hackers.

The basic computer design that makes this possible has a common program
and data buss. Hackers can cause their program to be loaded on the target
machine via this common buss.

In the late 1970’s, there was a different computer design, the Harvard
Architecture with separate data and program busses. This architecture
cannot be hacked.

About 1985, the microprocessor became practical and the Harvard
Architecture became obsolete.

“Did we turn right at Albuquerque in error”? I believe so. Could
have avoided it? I think not. We could not have predict the future.

Should we re-vitalize the Harvard Architecture? I think the benefits
would greatly out-weigh the costs.

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

June 23, 2015

You were recently employed as a software developer in a major software engineering company.

You have a family that needs the financial resources that your job provides.

You need to reduce the risk of lay off and increase the probability of a raise.

Your needs are more likely to be met if you adopt the following four principles.

PRINCIPLE 1: WRITE AND EXECUTE A PLAN

PRINCIPLE 2: KEEP A WRITTEN DAILY LOG

PRINCIPLE 3: MAKE SMALL SELF-DOCUMENTING SOURCE FILES.

PRINCIPLE 4: ACCEPT NO VERBAL ORDERS

MORE IN THE NEXT MESSAGE

Limitation to My Response to Your Comments

June 23, 2015

Every day I receive between 50 and 100 comments. Many of these comments request information or advise from me.

I appreciate the honour of your request for information.

Unfortunately, there is only one of me managing and writing the blog. Consequently, I simply do not have enough time to reply to each of your questions.

There are many comments that ask the same question. In these situations where I have the information, I will provide my knowledge in a post, time permitting.

I will respond to any comment made by a person who is experimenting with my software development tools.

Thank You

Robert Adams


Follow

Get every new post delivered to your Inbox.

Join 408 other followers