Archive for the ‘SEMINARS’ Category

Disaster Seminar 5 — Pick the best machine for disaster survival

October 29, 2018

It must function on its own without internet access.

It must have:

1. A Hard drive to contain your data and applications.

2. A Printer Port.

3. A DVD reader / writer.

4. A USB Port.

Desktop or Notebook Computers are good choices.

MORE IN THE NEXT MESSAGE

Advertisements

Disaster Seminar 4 — When Your Machine Breaks

October 22, 2018

When Your Machine Breaks, you will lose access to:

1. Your Data.

2. Your Applications and Programs,

3. Access to the Internet.

All Machines break, even the cloud based machines that
provide you with your computing capabilities.

How does one prepare for a machine failure?`

MORE IN THE NEXT MESSAGE

Disaster Seminar 3 — Computer Resource Failure Modes

October 16, 2018

Loss of Your Computer Resources results from:

1. Personal computer failure.

2. Remote computer service,

3. Power failure.

4. Internet failure.

5. Software failure.

6. Security failure.

MORE IN THE NEXT MESSAGE

Disaster Seminar 2 — The Most Ignored Serious Disaster

September 24, 2018

The Loss of Your Computer Resources

Why is this a major disaster?

Minimally. You will lose the ability to:

1. Manage your finances

2. Pay your bills.

MORE IN THE NEXT MESSAGE

Disaster Seminar 1 — Typical Natural Disasters

September 17, 2018

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

Life of A Programmer — Session 8.1 — Tools Help Make The Software Engineer

September 10, 2018

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

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

September 3, 2018

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

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

August 27, 2018

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

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

August 20, 2018

RULE 2 — TEST ALL WORK PRODUCTS.

I was able to “look over NSA’s shoulder” when they were developing
SELINUX (Secure Linux Operating System”.

Their activity can be best described as “programming as usual”.

I asked them about their test plans. They said that they were not
going to test the system. It would be Common Criteria tested when
delivered.

This is not an adequate test plan. Testing all of the work-products
is the only way to thoroughly test the product.

Back in my hardware engineering days, we made test plans which
thoroughly tested each circuit board. Divide and conquer!

SELINUX will fall short of its intended goal. The bad-guys will
find the weak points.

MORE IN THE NEXT MESSAGE

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

August 13, 2018

RULE 1 — RIGOROUSLY USE STANDARD METHODS.

Prepare a minimum set of standard methods that you will use on all your programming effort. Keep them “simple, stupid”.

In the hardware world, the Quality Assurance Manager working with management purchase the set of Integrated Circuits needed to get the job done.

These standard methods are your “Integrated Circuits”.

MORE IN THE NEXT MESSAGE