How I Protect My Proprietary Data

April 4, 2020

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.

My research and development activities produces a large
quantity of proprietary data. How do I protect this data?
Simple! I do not publish it on my blog or any other web-sites.

The purpose of “reporting my activity” involves establishing
the date at which a particular task was accomplished. The
task is sufficiently identified to enable me to identify
the associated proprietary data and daily log which is
stored on my machines, flash drives, and DVD’s.

Also, please let me remind you that when your machine is
not connected to the internet, hackers cannot access your
machine.

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.

I, A Programmer, Am Also A Quality Assurance Manager

March 31, 2020

To be strictly compliant with ISO-9001, Programmers must
use enforceable standard methods and processes.

Assembly Language Programmers used macros for common
multi-instruction processes. These macros, once developed,
were never changed.

Software “breaks fatally” when it illegally writes. The
error cannot be fixed and it might take the machine down.

There are many error detection code segments that programmers
use during checkout and then remove before delivery.

I developed a C++ Macro Preprocessor to provide a highly
competent macro capability to facilitate using error detection code.

Unlike the Macro Assembler, my C++ Macro Preprocessor prepared
source code exclusively from the Macros.

IBM developed the first piece of error-free software in 1968.
It was the PL/1 Compiler and it was a joy to use.

The PL/I Compiler was error free due the strict application of
the requirements of simple precedence.

In the late 1960’s, Bob Prince of Lockheed developed a simple
precedence based compiler writer which I used.

In the early 1970’s, I used the Lockheed Compiler Writer to
prepare non-compiler applications with moderate success.

I had difficulty with the Compiler Writer on non-compiler
applications because data flows differently than processes.

I realized many years later that a multidimensional precedence
process could manage both processes and the data flow.

I learned how to make a set of coupled precedence processors
that “policed” the use of classes and the flow of data.

I updated my C++ Macro Processor to render it capable of
deploying simple precedence principles to my programming efforts.

My Macro Processor satisfied the Standard Methods and
processes requirements of ISO-9001.

I inadvertently became a Quality Assurance Manager.

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

WhatifWe127 Blog — Web Browser Inquiries

March 28, 2020

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.

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

PROGRESS REPORT – 2020-03-19

March 26, 2020

2020-03-20

The Array Library has been significantly modified. Every array specification will be associated will be associated with a element or a structure. The array name will be a uniquely modified name of
the element or structure. In defining the array, the element or
structure name will be used. The revised version was functionally tested. Some additional minor modifications are still required.
2020-03-24

The Modified Array Library completely tested on the Windows, Linux, and Windows machine. Its modification has been completed. The next step will be to modify the Struct Library to include the array library modifications and the status variables.

 

Prague Conference in 1987

March 24, 2020

In 1987, I presented a scientific paper at a conference
in Prague, Czechoslovakia.

At that time, Prague was a city in the territory under
control of the Soviet Union.

I have always performed my research on my own time and money.

I attended the conference on my vacation.

Needless to say, the other attendees were quite curious
about my personal research efforts.

During this time, I had an interesting conversation with
a Polish attendee while walking along the river:

POLISH ATTENDEE: We are not special.

MY RESPONSE: Being special is defined by what you do
to be the very best in your field.

POLISH ATTENDEE: We have no resources.

MY RESPONSE: Do you have a personal computer at your home?

POLISH ATTENDEE: Yes.

MY RESPONSE: Probably a better one than I have. My is
a Heathkit H89.

POLISH ATTENDEE: The bosses will not like it.

MY RESPONSE: Usually, the bosses don’t kill the goose
that lays the golden egg right away.

At this point he understood and I was effectively
“walking on water”.

You ask: why am I sharing this little bit of history
with you.

History is a great teacher and today we need to learn
this lesson.

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

 

The Purpose of My Blog

March 21, 2020

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