Life of A Programmer — Session 7.5 — How Do I Become a Quality Assurance Software Engineer

June 6, 2017

RULE 4 — NEVER USE A PATCH TO SOLVE A PROBLEM.

Never patch the program!!!.

A patch is usually a last minute change which is not clearly
thought out.

The product delivery is usually close at hand.

Management is saying “All you have to do is …” (The most
dangerous phrase in the English Language).

The patch will probably violate RULE 1 (The strict use
of standard methods).

None-the-less, avoid the short-cut and you will more likely
find the solution to the problem.

MORE IN THE NEXT MESSAGE

WhatifWe127 Blog — Web Browser Inquiries

June 4, 2017

There have been many comments and inquiries relative to Web
Browser and Display format problems relative to my blog and
website. I appreciate your comments but I do not have sufficient
time to individually respond to them. I have prepared this
post that will hopefully provide some answers.

Relative to the blog, I use the free Word Press blog site.
The only thing that I prepare is the text. I don’t have any
videos. I do attach pdf files containing my articles. I must
assume that WordPress is up-to-date relative to the various
Web Browsers and Displays. I have absolutely no control over
the format.

Relative to my website, I designed it a number of years ago
using Microsoft Front Page which is now obsolete. I would
assume that it would not behave properly on some of the newer
Web Browsers and Displays. I am currently redesigning it
using the CSS technology. I am using this need as a means of
building standard Web Site development kits and I cannot
at this time predict when this will be completed.

My Problems With LinkedIn.

June 3, 2017

I need to alert everyone that I do not have a working LinkedIn system.

I have made several attempts at correcting the problems without success.

People trying to connect with me on LinkedIn will be unsuccessful, no
matter how much I want to connect with them.

PROGRESS REPORT

June 2, 2017

This purpose of this post is to publish single line status
reports on the projects performed during the week.

**************************************************************
**************************************************************

2017/05/29

APPLE PROJECT

The Apple Version of the Microsoft Visual Studio was successfully
installed but unfortunately was found unusable for the current
needs. It supported C# but not C++ which I need for the near-
term installation.

RELATIVITY BOOK

I am still making important modifications to the book to
strengthen it. My Toastmaster Mentor has provided me with some
valuable suggestions.

The Deming Cycle — Everyone Should Know It.

May 31, 2017

The Deming Cycle, the historical basis for all Quality
Assurance Programs, helped Japan to recover after World
War II.

The Deming Cycle consists of four steps: Plan, Do, Check
the Results, and Alter the Plan if necessary.

The Deming Cycle is a good definition of common sense.
I have used it on many occasions without knowing it.

When applying the Deming Cycle, when do we learn new and
better ways of doing our task?

We learn during the fourth step of the Deming Cycle when
we Alter our Plan.

WHATIFWE were all taught the Deming Cycle as a part of
our public education?

Life of A Programmer — Session 7.4 — How Do I Become a Quality Assurance Software Engineer

May 29, 2017

RULE 3 — USE OLD, WELL-TESTED, OPERATING SYSTEM CAPABILITIES.

Relative to the operating system, use the old, well established
capabilities and minimize your interface.

Think of it in a similar manner as purchasing a new car.
If you purchase a radically new model, you will become an
unwilling member of the test team.

Similarly do not use a pipe if a file will do as well. Files
were developed long before the pipes.

An above all, do not use its multitasking capabilities unless
absolutely necessary. This capability can expose you to many
challenging problems.

MORE IN THE NEXT MESSAGE

The Purpose of My Blog

May 27, 2017

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

Blog Alerts May Become Annoying

May 27, 2017

Placing a request to be alerted when I make a post is not the best way to keep track of my activity.

I have made a lot of posts. Some of them are research reports which are individually written with the aid of my Programmable Software Development Tool. Others such as the seminars have been written some time ago and are periodically posted on my blog. Frequently, I will make as many as three posts on a single day.

As a consequence, you are going to get a lot of alerts which may become annoying to you.

Please may I suggest a better way of keeping track of my activities.

I recommend that you follow me on Twitter (@whatifwe2048). You will see that my tweets are the titles of my blog posts in the order of occurrence. You can then easily select the ones that you wish to read,

This approach will give you greater control over your internet traffic.

PROGRESS REPORT

May 26, 2017

This purpose of this post is to publish single line status
reports on the projects performed during the week.

**************************************************************
**************************************************************

2017/05/20

APPLE PROJECT

By removing the fcloseall statement in precfile subroutine and
correcting a number of errors in the make file, all of the
subroutines were successfully compiled. There is still problems
with the link statement of the make file and the need to replace
the fcloseall statement. The error detection capabilities of the
make file generator need to be upgraded.

RELATIVITY BOOK

The detailed presentation of the second Rule of Physics, “Your
Beliefs May Lead You Astray” has been started.

**************************************************************

2017/05/22

APPLE PROJECT

A request for suggestions relative to the link statement of
the make file has been made to the appropriate Apple Technical
Community.

RELATIVITY BOOK

The detailed presentation of the second Rule of Physics, “Your
Beliefs May Lead You Astray” has been been tentatively prepared.
A significant improvement in the strength of the conclusions
is required.

**************************************************************

2017/05/23

RELATIVITY BOOK

The detailed presentation of the second Rule of Physics, “Your
Beliefs May Lead You Astray” has been been modified as required
to improvement in the strength of the conclusions. A preliminary
detailed presentation of the third Rule of Physics, “The Value
Of Mathematics” has been prepared.

**************************************************************

2017/05/24

RELATIVITY BOOK

A preliminary detailed presentation of the third Rule of Physics,
“The Value Of Mathematics” has been reviewed. The final rules
are detailed in the “Einstein’s Postulates Re-Examined” which
has prepared. This completes the preliminary preparation
of the “The Discovery” which must be now aggressively reviewed.

The Computer Wisdom of Bugs Bunny

May 24, 2017

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.