Archive for the ‘Uncategorized’ Category

Blog Alerts May Become Annoying

August 23, 2019

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.



The Twitter Seminar On The Development of Error Free Software Continues — Session 3

August 12, 2019


In most cases, the management of data is quite different than that of
the associated process.

In the 1960’s, the acronym HIPO defined a basic software documentation

HIPO stands for the following four sections; hierarchy, input, process,
and output.

Obviously, the flow of data was considered different than the associated

Would you believe it if I told you that simple-precedence can also be
used to manage data?

Data Management is also a process. Therefore, Simple-precedence methods
can be used to manage data.

WHATIFWE rigorously used the principals of simple precedence in all
software development? Is that all we have to do?


The Twitter Seminar On The Development of Error Free Software Continues — Session 2

August 5, 2019


The principles of simple-precedence produced one of the
best compilers that I have ever used.

Can the principles of simple-precedence be used in the
development of other applications?

Would you believe it if I told you that simple-precedence
has been used in a lot of different applications.

In 1973, IBM introduced the principles of structured

Strict Structured Programming satisfies the requirements
of simple-precedence.

Strict Structured Programming is a excellent means of
defining an error-free process.

Unfortunately, the management of data is different than
the management of a process.

WHATIFWE developed a simple-precedence means of managing
data? Can we do it?



My Comment Approval Criteria

August 2, 2019

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


The Twitter Seminar On The Development of Error Free Software Has Begun — Session 1

July 29, 2019


When was the last time that a computer error created a real
problem for you?

An ATM failure occurred when I was transferring $1000. It took
the bank 5 hours to find it.

Have you heard that the development of error-free software was
economically unachievable?

Would you believe it if I told you that a major error-free
application was developed in 1968.

IBM developed the PL/1 compiler in 1968. It was error-free.
Unlike Fortran, it had no bug list.

How did IBM do it? They developed it in strict compliance
with the principles of simple-precedence.

WHATIFWE developed other applications in strict compliance
with principles of simple-precedence? Can we do it?

My Response to Large Quantity of Comments

July 26, 2019

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.

Disaster Seminar 22 — Concluding Remarks

July 22, 2019

The preparation for a Disaster sounds like
a lot of work!

It isn’t as much as you think.

Keep in mind that a disaster will occur.

All computers eventually break.

When this happens, you will appreciate
your preparation efforts.



My Invitation To You

July 19, 2019

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, and they are
well documented.


July 18, 2019


The functional development  and testing of the commonclassarithmetic
library has been completed in the windows environment.  Minor
modifications to the commonclassfloat library were required.

Portability challenges are necessay.  To make it totally portable
with the apple environment will require changing the tab setting
of the Windows and Linux environments from two to eight.

There are also problems in the Linux text editor.  A means of making
it a strict ANSI text editor or replacing it must be found.

Disaster Seminar 21 — Accounting Disaster Preparation

July 15, 2019

The accounting requirements are as follows:

1. Don’t use paper-less billing,
a. Loss of internet equals not receiving
your bill.
b. Multiple copies of bills means you
are more likely to get your bill even
in a disaster.

2. Make printed copies of all of your
Accounting activity.
a. In a dire emergency, you can do
accounting by hand.
b. (Paper) Weight of the evidence is
useful in a disagreement.

3. Make strong passwords.
a. If you can easily remember the
password, it isn’t strong enough.