Resources (was: Saving the System i: Fight Rather Than Switch)

Trevor Perry wrote:

Here is my concern. You say "I expect the compiler to catch that and
provide me quick access to fix it". This means you are using system
resources to cater for your undisciplined programming approach.

That to me is a lack of commitment to the bottom line of the BUSINESS.
If you are compiling on a production server to resolve your spelling
mistakes, I think that is a misuse of CPW. If you have a development
server, go for it. If you have a development PC, go for it.

Misuse of CPW?  Huh?

This isn't the 80's when mainframe compiles took hours and ate up huge
system resources.  This is the 21st century.  CPU power is CHEAP.
Programmer time is EXPENSIVE.

If you're working on a system that can't handle a few extra compiles,
then it's the organizations leadership that has a lack of commitment to
the bottom line of the BUSINESS.

Heck, even when I did work on a low powered system, I ran my compiles in
my own jobq & subsystem so as not to impact the business operations.

david