Archive for the ‘Uncategorized’ Category

Disaster Seminar 1 — Typical Natural Disasters

September 17, 2018

Every Location Has A Potential Disaster:

1. Tornado
2. Hurricane
3. Earthquake
4. Mud Slide
5. Flood
6. Tsunami
7. Brush Fires.

MORE IN THE NEXT MESSAGE

Advertisements

My Comment Approval Criteria

September 14, 2018

Every day I receive between 50 and 100 comments requesting approval. There is only one of me managing the blog and hence must perform this function quickly and efficiently. To this end, each comment must:

1. Have a text message. For the most part, a comment with no text message will be deleted.

2. Be written in English using real words. I am not familiar with text message abbreviations.

3. Adhere to the basic principles of civilized behavior (I have had not problems with this so far).

4. Be consistent to the associated post and the purpose of the blog.

5. Be short. If it is over ten lines, I will delete it.

6. Not advertise any product, service or cause. I have been receiving a lot of promotions of solar panels for generating electric power which I have permanently deleted.

Thank You

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

September 10, 2018

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

My Response to Large Quantity of Comments

September 7, 2018

I am the only one managing the blog and hence
have a limited amount of time to do so.

If there are less than 100 comments, I will examine
each comment to determine whether I will approve it
or delete it.

If there are more than 100 comments, I will examine
and approve comments according the following rules:

For each group of twenty comments, I will:
1. Find the first one that I can approve.
2. Approve the selected comment.
3. Delete the remaining 19 comments.

Thank You for your understanding.

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

September 3, 2018

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

My Invitation To You

August 31, 2018

I became a software engineer in 1966 due to an experiment
that I had performed. I have never taken a course in
Software Engineering. Over the years, I have continued
to experiment on my own time and have greatly benefited
from this activity

In 1992, I became a home based software development business.
I developed a set of tools to aid me in my business activities.
These tools evolved over time and are now capable of helping
a software engineer to become a better, more competitive programmer.

I invite you to take a similar path. My tools can be downloaded
free-of-charge from my web-site, http://www.whatifwe.com and they are
well documented.

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

August 27, 2018

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

Limitation to My Response to Your Comments

August 24, 2018

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

I appreciate the honor 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

PROGRESS REPORT

August 23, 2018

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

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

2018-08-16

MACHINE PORTABILITY

The biggest problem with portability between the Linux, Microsoft and Apple
machine is the size of the tab character. Specifically, the size of the tab character
in the text editor in the Apple machine is 8-characters and is not resettable.
In the Windows and Linux machine where I am using the Notepad++ editor,
the tab character can be reset and is currently set at two. Today, I have found
isome equivalent text editors for the Apple machine which I can download
free of charge. This, obviously, is the next step in the machine portability efforts.

2018-08-21

MACHINE PORTABILITY

I downloaded an Apple “equivalent” to the Notepad+++ editor. It did not have
ability to change the size of the tab character. The best current solution to the
tab character size problem is to set the tab size of the Windows and Linux editors
at eight characters. I have also developed a softwarepartslibrary for replacing tab
characters with the equivalent number of blank characters.

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

August 20, 2018

RULE 2 — TEST ALL WORK PRODUCTS.

I was able to “look over NSA’s shoulder” when they were developing
SELINUX (Secure Linux Operating System”.

Their activity can be best described as “programming as usual”.

I asked them about their test plans. They said that they were not
going to test the system. It would be Common Criteria tested when
delivered.

This is not an adequate test plan. Testing all of the work-products
is the only way to thoroughly test the product.

Back in my hardware engineering days, we made test plans which
thoroughly tested each circuit board. Divide and conquer!

SELINUX will fall short of its intended goal. The bad-guys will
find the weak points.

MORE IN THE NEXT MESSAGE