Archive for the ‘Uncategorized’ Category

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

April 6, 2020

The Tool, if it is to be compliant of the principles of ISO-9001 must be capable of:

1.0 Developing a system of Standard Methods.

2.0 Exclusively using these Standard Methods in the development of product.

3.0 Testing all work-products from the Standard Methods all the way to the Product.

An experimental beta development system that satisfies these requirements is available on my web-site, http://www.whatifwe.com

I have developed both a Linux and Windows Open Source version.

They can be downloaded free-of-charge.

The download has a fairly decent manual.

THE END

My Invitation To You

April 3, 2020

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 8.1 — Tools Help Make The Software Engineer

March 30, 2020

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

Limitation to My Response to Your Comments

March 27, 2020

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

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

March 23, 2020

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 Problems With LinkedIn.

March 20, 2020

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.

 

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

March 16, 2020

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

Blog Alerts May Become Annoying

March 13, 2020

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.

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

March 9, 2020

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

My Comment Approval Criteria

March 6, 2020

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