Archive for June, 2013

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

June 30, 2013

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

Open Source Software Development Tool: Upgrade Progress

June 30, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

SUNDAY: 2013/06/30

STATUS: The development/modifications of the software parts associated
with basic output library continues.  I briefly reexamined the need to
add a read segment command to find the next CRLF.

DETAIL: To properly perform the desired certification function, we must
read and compare all of the lines in the subject file.  We cannot
error-out when we find the first discrepancy.  In as much as many
segments will be read before the CRLF, we must be able to find the CRLF
command in a line with a reported discrepancy.

RESULTS: I was able to prepare a general-purpose read-segment utility
capable of finding the next CRLF. There is no current need to develop
an additional command.

NEXT TASK: I will continue to develop/modify the software parts
associated with basic output library. When completed, I will use the
testing of this library as a means of testing the new Programmable
Software Development Environment version.

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

June 28, 2013

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

Open Source Software Development Tool: Upgrade Progress

June 28, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

FRIDAY: 2013/06/28

STATUS: The modifications to the precmac and precoper source files have
been completed and are ready for test.

DETAIL: The current development and testing is being done by OpenWatcom
on a Windows 7 machine.

NEXT TASK: The basic output library will be used to test these new
features.  Its current software parts will require considerable
modification.  Making the required modifications will be the next task.

PROGRAMMERS ARE SPECIAL QUALITY ASSURANCE MANAGERS!

June 24, 2013

Requiring our programmers to be special Quality Managers? This would be a terrible inconvenience?

On one of my contracts, I had the opportunity to witness an attempt to become ISO-9001 certified.

There were two ISO-9001 certification meetings; the first with the software manager and the second with QA.

The software manager had no idea as to what his group could do to be compliant with ISO-9001.

The QA manager described the increased formality required to be compliant with ISO-9001.

The body language of my client’s employees told me that no one except management wanted ISO-9001 certification.

One of the requirements of ISO-9001 is the use of “Standard Processes and Methods”.

The use of “Standard Processes and Methods” means that management would control our programming efforts.

Would you believe it I told you that programmers are already using “Standard Processes and Methods”?

No I don’t! As long as I do my job, management leaves me alone. They create more problems than they solve.

Then would you believe it I told you that programmers create their own “Standard Processes and Methods”.

No? How many times have you prepared a new source file by modifying an old previously developed source file?

Your collection of sources files defines your “Standard Methods and Processes” that you use.

Will this help you to develop error-free software?  Reflect on your experience. It already has.

WHATIFWE were to make a conscious Quality Assurance Effort?  Will it help?  Try it, sees what happens.

Open Source Software Development Tool: Upgrade Progress

June 24, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

MONDAY: 2013/06/24

STATUS: The srcproj source code for the Windows version has been
modified to report a user error if the last line of an output file is
incomplete; i.e., has no CRLF.

RESULTS: The modifications has been successfully tested on an
application that will not produce an incomplete output file.

NEXT TASK: The next task will be to add the _WRITE_SEGMENT and
_READ_SEGMENT commands to the precmac source file. When this is done,
these new commands can be tested.

The Twitter Seminar On The Development Of Error Free Software Concludes

June 21, 2013

ARE PROGRAMMERS SPECIAL QUALITY ASSURANCE MANAGERS?

Can a software engineer be a Quality Assurance Manager?  Quality Assurance is a management task.

To find out, let us look at the beginning of all Quality Assurance programs; i.e., the Deming Cycle.

The Deming Cycle, first used in Japan in 1947, consists of the following four steps.

The first Deming Cycle Step is “make a plan”. The second Deming Cycle Step is “do the plan”.

The third Deming Cycle Step is “check the results”. The four Deming Cycle Step is “change the plan if needed”.

The Deming Cycle appears to be a concise definition of common sense!

Would you believe it if I told you that all programmers are Quality Assurance Managers?

No! Then would you believe it if I told you that a computer program is a Deming Plan?

A computer program is a Deming Plan to be done at the client’s site by a computer, not by a person.

Most Programmers do not understand that they are very special Quality Assurance Managers.

WHATIFWE required our programmers to be special Quality Managers? Would this be a terrible inconvenience?

Open Source Software Development Tool: Upgrade Progress

June 21, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

FRIDAY: 2013/06/21

STATUS: The status flag has been implemented into the text output
commands of the precoper source code and has been tested on the
_WRITE_OUT command.

DETAIL: The current development and testing is being done by OpenWatcom
on a Windows 7 machine.

NEXT TASK: The next task will be to modify the srcproj source code so
as to make it a user error if the last line of an output file is
incomplete; i.e., has no CRLF. Again, I will continue to develop the
Windows version first

The Twitter Seminar On The Development Of Error Free Software Continues

June 20, 2013

CAN WE PREVENT ERRORS DURING SOFTWARE DEVELOPMENT?

Suppose we had a software tool that produced source code exclusively from a set of macros? Would it be restrictive?

A computing language is often considered the pallet where the programmer expressive his creative juices.

Restricting the programming effort to a minimal set of macros would take all of the fun out of the project.

In addition, a highly skilled programmer can be trusted to do the job correctly without these constraints.

Would you believe it I told you that all programmers, even the great ones, make errors.

The errors made by the junior programmers show up quickly during checkout and are easy to fix.

The errors made by the senior programmer take a long time to show up and are difficult to fix.

Restricting the “field of play” can greatly simplify the development process.

Restricting the “field of play” can greatly reduce the occurrence of errors.

In the hardware world circa 1980’s, management select the Integrated Circuits to be used in the project.

Unfortunately, management cannot provided the an appropriate set of software parts.

Programmers are needed to develop an appropriate set of software parts.  Is a programmer a QA manager?

WHATIFWE had a senior programmer who was also a Quality Manager?  Would this help?

MORE IN THE NEXT MESSAGE

Open Source Software Development Tool: Upgrade Progress

June 20, 2013

It is planned to upgrade the Programmable Software Development Environment to include the capability of reading the paste-in text files where the each paragraph is one very long line.  You may need to download the latest version of the Programmable Software Development Environment to fully understand my reports.

The ability to read the paste-in text file is needed to certify that the file has not been changed, was developed using the agree-upon standard libraries, or has not been illegally copied.

THURSDAY: 2013/06/20

STATUS: The options associated with completing a task before the writing of an output line has been completed (No CRLF) have been examined.

DETAIL: If the completion of a task occurs before an output line has been completed (No CRLF) should be considered a user error resulting in the deletion of the output files.

RESULTS: The best way appears to be a status flag variable for the text output file system. There will be three states: empty file (No lines),  complete last line, and incomplete last line (no CRLF).  Then the proper action could be taken at the end of the task.

NEXT TASK: I will proceed to implement the status flag into the text output commands of the precoper source code.