You can only do things quickly after you have invested a great amount of
time in learning how to do them?
At that point you can raise the issue of cost.
My two ha'pence worth
-Maurice O'Prey
Kelly,
The arguments (while I agree with the speed,quality, expense in general)
are not quite accurate because of the mythical man month.
Speed - Get it done quick, more likely to have errors or the better
developers cost more.
Quality - Take more care in getting it done more time = more money and
less speed.
Expense - More speed coupled with more quality equals higher cost.
Its that simple.
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
Kelly Cookson <KCookson@xxxxxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
12/17/2010 05:34 PM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
To
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
cc
Subject
Re: [WEB400] business rules?
Why can't I have all 3? What are the
technical obstacles that prohibit "business
rules" from having all 3? (maintenance,
performance and flexibility)
I think we're talking past each other. I don't think the choice between
maintenance, performance, and flexibility is the same as the choice
between speed, quality, and expense.
Here is the choice between speed, quality, and expense:
1. Time is required to do a job well. The higher the quality the
deliverable of a job, the more time it will take to complete that job.
2. Labor costs money. The more people work on a job, the greater the
expense of labor to complete that job.
3. If you want a high quality deliverable, and you want to save labor
costs, you can have a minimum number of people work on the task. But then
the task will take more time because fewer people are working to complete
it and live up to quality standards.
4. If you want a high quality deliverable, and you want it done quickly,
you can have several people work on it to complete it quickly. But then
you have to pay labor costs for several people.
5. If you don't really care about the quality of the deliverable, you can
assign a minimum number of people to work on the job and force them to
complete on a short deadline. But the quality of the deliverable usually
suffers (design limitations and bugs).
Armchair philosophy is so much easier than software development! :-)
Kelly Cookson
Senior Programmer/Analyst
Dot Foods, Inc.
217-773-4486 x12676
www.dotfoods.com
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Mark Murphy/STAR BASE Consulting Inc.
Sent: Friday, December 17, 2010 3:39 PM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] business rules?
You've left out price. You can have maintenance performance and
flexibility, that would fall under good an fast, but it is going to cost
you.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
-----web400-bounces@xxxxxxxxxxxx wrote: -----
To: web400@xxxxxxxxxxxx
From: Paul Holm
Sent by: web400-bounces@xxxxxxxxxxxx
Date: 12/15/2010 03:55PM
Subject: Re: [WEB400] business rules?
Why can't I have all 3? What are the technical obstacles that prohibit
"business rules" from having all 3? (maintenance, performance and
flexibility)
-Paul
Kelly Cookson wrote:
...good, quick and cheap at the same time.
2 out of 3 is about the best you can do.
Price. Service. Quality.
Pick any 2 . . .
The choice would be Low Price, Fast Service, and High Quality: pick any
2.
Kelly Cookson
Senior Programmer/Analyst
Dot Foods, Inc.
217-773-4486 x12676
www.dotfoods.com
midrange.com
