Posts Tagged ‘system capabilities’

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

January 28, 2015

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

Advertisements

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

September 16, 2014

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.4 — How Do I Become a Quality Assurance Software Engineer

May 4, 2014

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.4 — How Do I Become a Quality Assurance Software Engineer

March 3, 2014

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 — How Do I Become a Quality Assurance Software Engineer

November 24, 2013

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 multi-tasking capabilities unless
absolutely necessary.  This capability can expose you to many
challenging problems.

MORE IN THE NEXT MESSAGE

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

September 20, 2013

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

Relative 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 multi-tasking capabilities unless
absolutely necessary.  This capability can expose you to many
challenging problems.

MORE IN THE NEXT MESSAGE

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

September 13, 2013

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 7 — How Do I Become a Quality Assurance Software Engineer

July 24, 2013

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

Relative 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 multi-tasking capabilities unless absolutely necessary.  This capability can expose you to many challenging problems.

MORE IN THE NEXT MESSAGE

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

July 20, 2013

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 7 — How Do I Become a Quality Assurance Software Engineer

April 27, 2013

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