Archive for April, 2014

Developing a Website using a software parts library

April 29, 2014

The activity associated with development of a software parts library
for the development of a web-site will be presented here. This will be
an extension of the library used to prepare Programmable Software
Development Environment manual.

This effort was started a long time ago following the development of
the manual software parts library. Its purpose was to eliminate the
need for Front Page. It was subsequently put on hold so that other
more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently
offered to reconstruct my Web-Site. I told him my plan to use my tool
to rebuild my site. He has had difficulties relating to my technology
(It is quite different than normal programming methods) and I am not
really skilled in Web-site design. We both felt that this might a great
opportunity to make the technical connection.

TUESDAY: 2014/04/29

STATUS: The CSS name management/communicate software parts have been
prepared.

DETAIL: The CSS name management/communicate software parts are as
follows: 1) _WEBSITE_NAME_INITIAL_LOAD loads the base group name, 2)
_WEBSITE_NAME_CHILD_LOAD loads the child name called by a parent, 3)
_WEBSITE_NAME_FINAL_RETURN processes the final return, 4)
_WEBSITE_NAME_CHILD_RETURN processes a return from a child to its
parent, 5) _WEBSITE_NAME_GET_MAME_NO gets the number associated with
the name, 6) _WEBSITE_NAME_GET_PARENT_NO gets the number associated
with the parent, and 7) _WEBSITE_NAME_BASIC_LOAD is the basic name
loader.

MY NEXT TASK: My next task is to integrate the names management system
into the the Whole Page CSS software parts.

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

April 29, 2014

To become a Software Engineer with a Quality Assurance
capability, you must implement a basic philosophical change.

Software is not an art form; the computer is not the easel
where you can express your creative juices.

You will become an engineer responsible for providing tools
and services that will affect public safety.

You think not. I beg to disagree.

I was transferring $1000 between my savings and checking
accounts when the ATM went down. It took the bank half a
day to find my money.

You ask, what do I need to do in order to improve my quality
and be more indispensable to my employer.

RULE 1 — RIGOROUSLY USE STANDARD METHODS.

RULE 2 — TEST ALL WORK PRODUCTS.

RULE 3 — USE OLD, WELL-TESTED, OPERATING SYSTEM CAPABILITIES.

RULE 4 — NEVER USE A PATCH TO SOLVE A PROBLEM.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 6.3 — What should a Quality Assurance Software Engineer Know.

April 26, 2014

SOFTWARE ERROR SOURCE 2: THE OPERATING SYSTEM.

The operating system is the silent partner in all software
development activities.

The operating system, also having been developed by human
beings, will also have errors.

Most of the errors will have already been discovered.

The ones that have not been discovered will, in general,
be difficult to fix.

You, as the user, will have no control over that repair
process.

Consequently, you may end up with a difficult task of
working around a system error that was discovered on your
watch.

MORE IN THE NEXT MESSAGE

My Invitation To You

April 26, 2014

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.

Life of A Programmer — Session 6.2 — What should a Quality Assurance Software Engineer Know.

April 25, 2014

SOFTWARE ERROR SOURCE 1: THE SOFTWARE DEVELOPMENT ENGINEER.

All Software Development Engineers are human beings, not little
green-guys from Mars

All human beings, including Software Development Engineers make
errors.

Software errors created by Junior Programmers are discovered early
and easily fixed.

Errors created by Senior Programmers take a long time to surface
and are usually hard to fix.

You have probably already had to solve a very difficult problem
on a project that you completed a year ago

MORE IN THE NEXT MESSAGE

Developing a Website using a software parts library

April 25, 2014

The activity associated with development of a software parts library
for the development of a web-site will be presented here. This will be
an extension of the library used to prepare Programmable Software
Development Environment manual.

This effort was started a long time ago following the development of
the manual software parts library. Its purpose was to eliminate the
need for Front Page. It was subsequently put on hold so that other
more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently
offered to reconstruct my Web-Site. I told him my plan to use my tool
to rebuild my site. He has had difficulties relating to my technology
(It is quite different than normal programming methods) and I am not
really skilled in Web-site design. We both felt that this might a great
opportunity to make the technical connection.

FRIDAY: 2014/04/25

STATUS: While preparing the software group section parts, I observed
that all of ID and class names in Mr. Mike’s example were lower case.
It occurred to me that I should examine the literature to determine the
the syntax rules associated with these names.

DETAIL: I found the syntax rules in the Microsoft MSDN Library

RESULTS: The syntax rules (and I experimented with the whole_page class
in Mr. Mike’s examples) associated with the class names and the ID
names were essentially the same as the Programmable Software
Development Environment name.

NEXT TASK: I believe that a set of name management/communication parts
is in order and will be prepared. It will be first be integrated into
the whole page CSS software parts.

Life of A Programmer — Session 6.1 — What should a Quality Assurance Software Engineer Know.

April 24, 2014

Being a Software Development Engineer also makes
you a Quality Assurance Manager.

You have had no training in Quality Assurance.

You do not like it when management brings up the subject.

None the less, you are a Quality Assurance Manager.

Maybe I can help you to benefit from this unwanted
job description.

The first thing that you need to know is that there
are two sources of software errors.

SOFTWARE ERROR SOURCE 1: THE SOFTWARE DEVELOPMENT ENGINEER.

SOFTWARE ERROR SOURCE 2: THE OPERATING SYSTEM.

NOTICE THAT I DID NOT MENTION THE USER.

IT IS YOUR RESPONSIBILITY TO PROTECT THE USER FROM HIS
OWN STUPIDITY.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 5.3 — You are a Quality Assurance Manager

April 22, 2014

The Deming Cycle consists of the following four steps:
Plan, Do, Check the Results, and Analyze the Results.

A computer program is a very special Deming Plan to be
performed at the Client’s site on a computer.

There is a big different between Deming Plans done by
people and Deming Plans done by computers.

If people find a problem in the plan, they will stop the
activity and report the problem to management.

On the other hand, a computer will continue to execute
the plan, no matter how defective it is.

A software developer is a very special Q.A manager and
he does not even know it.

MORE IN THE NEXT MESSAGE

Developing a Website using a software parts library

April 20, 2014

The activity associated with development of a software parts library
for the development of a web-site will be presented here. This will be
an extension of the library used to prepare Programmable Software
Development Environment manual.

This effort was started a long time ago following the development of
the manual software parts library. Its purpose was to eliminate the
need for Front Page. It was subsequently put on hold so that other
more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently
offered to reconstruct my Web-Site. I told him my plan to use my tool
to rebuild my site. He has had difficulties relating to my technology
(It is quite different than normal programming methods) and I am not
really skilled in Web-site design. We both felt that this might a great
opportunity to make the technical connection.

2014/04/20

STATUS: I have performed the experiments needed to define the software
parts defining the group sections These sections contain header,
contents, and text sections and are identified by unique id names.

MR_MIKE_CONTRIBUTION: These experiments were performed on Mr. Mike’s
web-site contributions.

DETAIL: Two types of group sections are required: A top-to-bottom
collection and a left-to-right collection. The top-to-bottom collection
could be header, text and footer. The left-to-right collection could
be links and text. These group sections can contain other group
sections.

MY NEXT TASK: My next task will be to prepare, integrate and test the
software parts associated the top-to-bottom and left-to-right group
sections.

Life of A Programmer — Session 5.2 — You are a Quality Assurance Manager

April 19, 2014

Q.A. is a management activity. It is taught in Business
Administration.

You have a college degree in Software Engineering, not
Business Administration.

In spite of all of this, you are still a Quality Assurance
Manager.

The Deming Cycle is the historical basis for all Quality
Assurance Programs.

It basically consists of the following four steps: Plan,
Do, Check the Results, and Analyze the Results.

A computer program is a very special Deming Plan to be
performed at the Client’s site on a computer.

MORE IN THE NEXT MESSAGE