Archive for March, 2014

Life of A Programmer — Session 1.3 — Are You A Software Engineer?

March 31, 2014

I used to know a software engineer who did not just “do it” at work.

He had significant personal accounting difficulties.

He occasionally would use hexadecimal numbers on the checks that he wrote.

Most assuredly, software engineering defined him as a person.

So I will again repeat my question. Are you a software engineer?

MORE IN THE NEXT MESSAGE

 

Software “Breaks”!

March 31, 2014

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
software?

Life of A Programmer — Session 1.2 — Are You A Software Engineer?

March 30, 2014

Are you a software engineer? This sounds like a really stupid question!

How can a person with a college degree in I.T not be a software engineer?

A software engineer is a person who is defined by software engineering.

A software engineer does not just “do it” at work.

So I will repeat my question. Are you a software engineer?

MORE IN THE NEXT MESSAGE

The Role of the Media

March 30, 2014

Both the incompetent and the competent benefit from
media attention.

The competent leader requires community participation.
The media helps him to obtain the participants.

The incompetent needs 15 minutes of fame. The media
helps him to satisfy his greedy goals.

Unfortunately the entertainment associated with the
incompetent attracts a lot of media attention.

The competent pioneer finds new solutions to current
problems.

WHATIFWE were to provide the media attention needed
to develop hope from the new ideas of the competent
pioneers?

Life of A Programmer — Session 1.1 — Are You A Software Engineer?

March 29, 2014

Your interest in this seminar tells me that you have programming experience

You probably have a college degree in information technology or related subject.

You may have a software engineering job or are looking for one.

But are you a software engineer?

MORE IN THE NEXT MESSAGE

Monte-Carlo Test Method

March 29, 2014

A Number of years ago, I had a contract to build a hardware
control sub-system software product.

This hardware control sub-system was designed to control
legacy hardware shipped back from the Middle East.

This legacy hardware appeared to have not been well-maintained;
it needed a lot of service.

I was afraid that I might break this hardware when I tested my
hardware control sub-system software product.

I developed a Monte-Carlo Simulator/Stimulator Test System to
validate my hardware control sub-system product.

The Monte-Carlo technology is based on a pseudo-random generator.
It was originally used in the development of nuclear weapons.

The random nature of my Monte-Carlo Test System enabled me to
rapidly and thoroughly test the hardware control sub-system, both
from a user and hardware point-of-view.

The use of a Monte-Carlo Simulator/Stimulator Test System
enabled me to deliver an error-free software product.

WHATIFWE used Monte-Carlo software test methods for all software.
Would we get better products?

1991 IMACS Symposium MCTS Casablanca relocated Lille, France

March 29, 2014

In 1991, I presented my fourth article on my personally
funded research at the IMACS Symposium MCTS Casablanca
relocated Lille, France. I performed my computer
simulations on my personal computer.

I have attached a scanned copy of this five page article to
this post.

Please may I remind you that companies and organizations do
not make discoveries and inventions; Individuals do. May I
encourage you to turn off the TV set and work on your own
personal research project.

Lille_Article_1991-1_no_address

Lille_Article_1991-2

Lille_Article_1991-3

Lille_Article_1991-4

Lille_Article_1991-5

 

The Experimental Process — Any One Can do It!

March 29, 2014

Many years ago, there was the HeathKit company.

It had for sale various electronics kits.

They sold amateur radio, television, instrumentation kits.

I bought my first personal computer from them. It was a Heathkit H89.

That computer was the beginning of my personal research effort.

This computer resulted in three overseas conference publications.

I have never taken any course in software engineering or electronics.

I have learned everything through an extensive experimental effort.

Would you believe it if I told you that every person knows how
to experiment.

No! Let me show you that it is true.

As soon as a baby gains enough strength to roll over and get his
tummy off of the floor, he crawls around and gets into things.

What does he do with them? He puts them in his mouth.

Did you ever think that a baby’s mouth is his best instrument at birth?

It has to be! Otherwise he won’t be able to eat.

You are not a little green guy from outer space.

You were once a baby. When you started to crawl, you put things
into your mouth.

Therefore, you basically know how to experiment.

I rest my case.

Open Source Software Development Tool: Upgrade Progress

March 28, 2014

he overall purpose of the current Programmable Software Development
Environment upgrade process is to certify that a product generated is
certifiably releasable.

To certify a software parts library, every command except the _ERROR
command defining a library must respond to a ‘<—‘ debug flag comment
at the end of a the command line. Specifically, when the debug flag is
present, the subject command will be executed first and then the
command data (command, arguments, and results) will be displayed and
then the operator will be given a option of terminated execution or
continuing.

The _ERROR command must be corrected to equivalently respond to the
debug flag.

The major difference between the _ERROR command and all other commands
is that the debug flag will be processed before the command is executed.

The Programmable Software Development Environment will be modified so
that the _ERROR command will respond to the debug flag before
terminating execution.

FRIDAY 2014/03/28

STATUS: The WIN32 precsrce source files was restored to the archival
files. Both the WIN32 and the LINUX precoper source files were then
modified to implement the above revised _ERROR definition.

DETAIL: The _ERROR command basically terminates the execution of the
development process. The zero argument _ERROR statement rendered
obsolete by the _CONTINUE_IF and _CONTINUE_IF_NOT commands is still
available.

RESULTS: Both the updated WIN32 and LINUX Programmable Software
Development Environment prepared, built and tested and found to be
functional.

NEXT TASK: The next task will be to examine the manual to see what
changes need to be made.

 

Open Source Software Development Tool: Upgrade Progress

March 27, 2014

The overall purpose of the current Programmable Software Development
Environment upgrade process is to certify that a product generated is
certifiably releasable.

To certify a software parts library, every command except the _ERROR
command defining a library must respond to a ‘<—‘ debug flag comment
at the end of a the command line. Specifically, when the debug flag is
present, the subject command will be executed first and then the
command data (command, arguments, and results) will be displayed and
then the operator will be given a option of terminated execution or
continuing.

The _ERROR command must be corrected to equivalently respond to the
debug flag.

The major difference between the _ERROR command and all other commands
is that the debug flag will be processed before the command is executed.

The Programmable Software Development Environment will be modified so
that the _ERROR command will respond to the debug flag before
terminating execution.

THURSDAY: 2013/03/27

STATUS: My preliminary experimental modifications of the precsrce
source file were unsuccessful and it occurred to me this morning that
my original approach was probably overkill.

DETAIL: The _ERROR command basically terminates the execution of the
development process. The one argument _ERROR statement provides the
capability of running a test project. I believe that the “<—-” is
indicative of the fact that this statement has not as yet been tested
and requires that the process should be unconditionally stopped.
Permission to continue in a test project can be granted by replacing
the “<—-” with the date.

NEXT TASK: The precsrce source files will be restored to the archival
files. The precoper source files will be then be modified to implement
the above revised _ERROR definition.