Archive for April, 2017

WhatifWe127 Blog — Web Browser Inquiries

April 30, 2017

There have been many comments and inquiries relative to Web
Browser and Display format problems relative to my blog and
website. I appreciate your comments but I do not have sufficient
time to individually respond to them. I have prepared this
post that will hopefully provide some answers.

Relative to the blog, I use the free Word Press blog site.
The only thing that I prepare is the text. I don’t have any
videos. I do attach pdf files containing my articles. I must
assume that WordPress is up-to-date relative to the various
Web Browsers and Displays. I have absolutely no control over
the format.

Relative to my website, I designed it a number of years ago
using Microsoft Front Page which is now obsolete. I would
assume that it would not behave properly on some of the newer
Web Browsers and Displays. I am currently redesigning it
using the CSS technology. I am using this need as a means of
building standard Web Site development kits and I cannot
at this time predict when this will be completed.

CODEPLEX SHUTDOWN

April 29, 2017

For many years, I have used the Microsoft Codeplex site for my Programable
Software Development Environment project from which my current tools could be
downloaded.

Microsoft will shut down CodePlex in month of December and will no longer
be able to contain updated versions of my tools in October. There may
be another site which will replace CodePlex.

You can always my current Software Development tools from my website,
http://www.whatifwe.com.

PROGRESS REPORT

April 28, 2017

This purpose of this post is to publish single line status
reports on the projects performed during the week.

**************************************************************
**************************************************************

2017/04/21

APPLE PROJECT

The necessary files (source, make files) have been transferred
to the IMACS machine. The testing of the make file in the
Apple machine will begin.

**************************************************************

2017/04/22

APPLE PROJECT

Ran the make file on the IMACS for the first time. Base directory
was incorrect. Modifications to the source code will be made and
a new make file will be generated.

**************************************************************

2017/04/23

RELATIVITY BOOK

The page describing my efforts to test the accuracy of my computer
simulation effort reported in Oslo, Norway has been completed.
The revised page has been added to the Open Source version of the
book. The format of this page will be reviewed.

**************************************************************

2017/04/24

APPLE PROJECT

Base directory
was corrected. Make and object file were found.
There are still problems in processing the header file. An attempt
to find documents that will define the gcc / apple application.

**************************************************************

2017/04/26

RELATIVITY BOOK

The page presenting my Prague Conference experience has been
tentatively prepared. Minor revisions are expected. The
story-telling strength needs to be improved.

Resume Preparation: A Gigantic “Plumbing” Project

April 26, 2017

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!

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

April 25, 2017

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

The Purpose of My Blog

April 23, 2017

The original purpose of my blog was to provide me an easy
means of reporting my activity on my personally funded
research and development activities on error-free software
development methods.

I subsequently expanded the purpose of my blog to encourage
others to improve their skills by conducting their own
regular experimental process.

I became a software engineer in 1966 due to an experiment
that I had performed. I have never taken a course in
Software Engineering. You are encouraged to take a similar
path. If my tools can be of any benefit, they can be
downloaded free-of-charge from my web-site, http://www.whatifwe.com

Limitation to My Response to Your Comments

April 22, 2017

Every day I receive between 50 and 100 comments. Many of these comments request information or advise from me.

I appreciate the honour of your request for information.

Unfortunately, there is only one of me managing and writing the blog. Consequently, I simply do not have enough time to reply to each of your questions.

There are many comments that ask the same question. In these situations where I have the information, I will provide my knowledge in a post, time permitting.

I will respond to any comment made by a person who is experimenting with my software development tools.

Thank You

PROGRESS REPORT

April 20, 2017

This purpose of this post is to publish single line status
reports on the projects performed during the week.

**************************************************************
**************************************************************

2017/04/14

APPLE PROJECT

The maccert make file error was corrected. Additional similar make file
errors were found. A detailed source file examination is needed.

**************************************************************

2017/04/15

APPLE PROJECT

A detailed source file examination has been performed; there are no
detected errors in the source section of the test make-generation
files.

RELATIVITY BOOK

The Addition of Mathematical section into the Open Source version
of the book continues. The Computer simulation page has been
replaced with a Numerical Approximation Section. Spelling Errors
have been detected but not as yet corrected.

**************************************************************

2017/04/16

APPLE PROJECT

The functional testing of the Apple-based Mac development tool
has been completed. The explrpde folder will be copied to the Apple
machine and an attempt to compile the explrpde tool will be made.

**************************************************************

2017/04/17

RELATIVITY BOOK

The modifications of the page describing my efforts to test the
accuracy of my computer simulation effort reported in Oslo,
Norway has been made. This page has been added to the Open
Source version of the book. The detected spelling error has
been corrected.

**************************************************************

2017/04/19

CLASS DEVELOPMENT PROJECT

The ASCII and UNICODE software parts have been successfully added
and functionally tested in the common typedef software parts
library.

I, A Programmer, Am Also A Quality Assurance Manager

April 19, 2017

To be strictly compliant with ISO-9001, Programmers must
use enforceable standard methods and processes.

Assembly Language Programmers used macros for common
multi-instruction processes. These macros, once developed,
were never changed.

Software “breaks fatally” when it illegally writes. The
error cannot be fixed and it might take the machine down.

There are many error detection code segments that programmers
use during checkout and then remove before delivery.

I developed a C++ Macro Preprocessor to provide a highly
competent macro capability to facilitate using error detection code.

Unlike the Macro Assembler, my C++ Macro Preprocessor prepared
source code exclusively from the Macros.

IBM developed the first piece of error-free software in 1968.
It was the PL/1 Compiler and it was a joy to use.

The PL/I Compiler was error free due the strict application of
the requirements of simple precedence.

In the late 1960’s, Bob Prince of Lockheed developed a simple
precedence based compiler writer which I used.

In the early 1970’s, I used the Lockheed Compiler Writer to
prepare non-compiler applications with moderate success.

I had difficulty with the Compiler Writer on non-compiler
applications because data flows differently than processes.

I realized many years later that a multidimensional precedence
process could manage both processes and the data flow.

I learned how to make a set of coupled precedence processors
that “policed” the use of classes and the flow of data.

I updated my C++ Macro Processor to render it capable of
deploying simple precedence principles to my programming efforts.

My Macro Processor satisfied the Standard Methods and
processes requirements of ISO-9001.

I inadvertently became a Quality Assurance Manager.

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

April 18, 2017

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