Disaster Seminar 1 — Typical Natural Disasters

July 29, 2015

Every Location Has A Potential Disaster:

1. Tornado
2. Hurricane
3. Earthquake
4. Mud Slide
5. Flood
6. Tsunami
7. Brush Fires.

MORE IN THE NEXT MESSAGE

My Problems With LinkedIn.

July 29, 2015

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

July 29, 2015

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

Blog Alerts May Become Annoying

July 29, 2015

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

July 28, 2015

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

Resume Preparation: A Gigantic “Plumbing” Project

July 28, 2015

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!

Can Programming Be Strictly Portable Relative To Language?

July 27, 2015

The activity associated with development of strictly portable methods
of software development will be presented here. Included in this
Portability effort will be Windows based C, C++, C#, and Visual Basic;
and Linux based C and C++.

MONDAY: 2015/07/27

STATUS: This project has been restarted by preparing a common program
output library.

DETAIL: This common output library will be capable of 1) making a
comment line, indenting a program line, and making lines of any length.

RESULTS: The Certification process has been prepared and the Setup has
been started,

NEXT TASK: The Indentation Variable has been defined. Incrementing and
Decrementing a specific Indentation is next

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

July 26, 2015

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

How Do I Make My Blog

July 26, 2015

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.

Robert Adams

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

July 24, 2015

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


Follow

Get every new post delivered to your Inbox.

Join 409 other followers