Archive for October, 2016

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

October 31, 2016


Suppose we had a software tool that produced source code
exclusively from a set of macros? Would it be restrictive?

A computing language is often considered the pallet where
the programmer expressive his creative juices.

Restricting the programming effort to a minimal set of macros
would take all of the fun out of the project.

In addition, a highly skilled programmer can be trusted to do
the job correctly without these constraints.

Would you believe it I told you that all programmers, even the
great ones, make errors.

The errors made by the junior programmers show up quickly
during checkout and are easy to fix.

The errors made by the senior programmer take a long time to
show up and are difficult to fix.

Restricting the “field of play” can greatly simplify the
development process.

Restricting the “field of play” can greatly reduce the
occurrence of errors.

In the hardware world circa 1980’s, management select the
Integrated Circuits to be used in the project.

Unfortunately, management cannot provided the an appropriate
set of software parts.

Programmers are needed to develop an appropriate set of software
parts. Is a programmer a QA manager?

WHATIFWE had a senior programmer who was also a Quality Manager?
Would this help?


How Do I Make My Blog

October 29, 2016

There have been quite a few requests for advice on
“how to build a blog”. As you can see from my blog, I have
prepared a lot of posts. Therefore, I have learned how
to do it efficiently.

There are some simple rules for making your blog easy
to prepare.

1. Have a well-defined purpose for your blog. For myself,
my blog was a means of publicly documenting my research and
development efforts.

2. Use a standard format. Then you can build a template
which will greatly facilitate its preparation. I use
my development software to write the blog.

3. Don’t get carried away with an artistic design. I use
the free WordPress. I do not use any pictures; all I
have to do is paste in the text. Above all, I did not
have to develop the blog web-site.

Above all, recognize that every post you publish will be
in the public domain forever. I have been very careful
to put just enough information to identify and date my
efforts but not to give away any proprietary data.

Hope that this helps.

Limitation to My Response to Your Comments

October 28, 2016

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


October 27, 2016

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

Relativity Book
The final proofing process continues. Every
chapter except the Epilogue has been reviewed
and updated as necessary. The Epilogue needs
revisions to strengthen its conclusions.

Portable Software Development
Parts independent of Language/Operating system
Data types
Three levels needed:
Basic: Supported by the language/Operating system
Derived: Supported by the Basic data types with restrictions.
Alias: Alias names for the collection of data
types to standardize its use
Relativity Book
The Epilogue has been revised.
The Final Review continues

Software “Breaks”!

October 25, 2016

A 17 year old sailor on a submarine must be able to
fix a critical piece of electronic equipment within
15 minutes.

Critical submarine hardware has the required subsystems
to facilitate the location of a failed replaceable components.

Most hardware these days has at least one computer within it.
This includes critical submarine systems.

Can the same 17 year old sailor on a submarine find and
correct a critical software failure within 15 minutes?

Does software “break”? Not really. but software fails when
it illegally or incorrectly writes some data.

Programmers have many ways of preventing illegal writes which
they use in checkout and then remove before delivery.

WHATIFWE used formal illegal write prevention code in delivered

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

October 25, 2016


It is important to detect and properly respond to an error
condition during the execution of the product.

It is also very important to prevent errors in the software
development process.

Perhaps we should look again at the development of military
hardware, circa, 1980’s.

In the hardware world, Quality Assurance begins with the
selection of a set of parts.

Management selected a set of Integrated Circuits and the
Engineers were required to use them in the design.

Would you believe it if I told you that there is an software
equivalent to the integrated circuit?

There is a “software part” equivalent and it is not an object
(which is more like a circuit board).

We can find our “software part” in the history of software

Specifically, it is the macro instruction set in the
macro-assembler circa 1990.

These macros were used to define common multi-instruction
processes such as 4-byte addition in a Z80 machine.

Once defined, these macros were never changed. They became
standard “Software Parts”.

Unfortunately, the use macro instruction set was optional
in the development of an assembly language program.

WHATIFWE had development software tool that produced source
code exclusively from a set of macros?

WhatifWe127 — My Internet Interface

October 22, 2016

Hopefully, this post will answer many of the questions that I have received about the Internet services that I am receiving.

First, please understand that I do not have a team. There is one of me and I am home based.

My Internet service is provided by Earthlink.

Recently I changed from DSL to a cable Internet communication process due to a major regional outage.

My blog is provided by the free WordPress site which may or may not add some advertising.

I also have a whatifwe Codeplex site and and a @whatifwe2048 Twitter site.

I designed my Website using Microsoft Front Page.

I have successfully accessed my web-site and blog on a LINUX, WINDOWS, and MAC machine.

My Problems With LinkedIn.

October 22, 2016

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.


October 20, 2016

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

Relativity Book
I am having considerable difficulties using
LibreOffice and OpenOffice to prepare
my book in the appropriate format. I
believe that now it may be time to prepare a special
tool for preparing a book in a *.html format where
it can be easily converted to the appropriate

Resume Preparation: A Gigantic “Plumbing” Project

October 18, 2016

We all understand a Plumbing Project. This where a supposedly
simple task become a massive, complex effort.

One of the common “Plumbing Projects” in today’s environment
is the preparation of a resume.

Each resume must be customized to the target audience. This
effort usually takes several hours to complete.

Resumes are always needed: Job searches, contracts, professional
network, and volunteering activities.

The resume effort is made more complex due to the need to paste
it into a web-site window, discovered usually at the last moment.

I have been using my Programmable Software Development Environment
to maintain its manual. Its use has greatly simplified this task.

WHATIFWE used the Programmable Software Development Environment
to develop resumes? Would it help? Yes it does!