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
Full Post
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment