Re: Decouple SQL queries from class in OOP design
- From: "topmind" <topmind@xxxxxxxxxxxxxxxx>
- Date: 6 Dec 2005 18:42:53 -0800
Thomas Gagne wrote:
> Robert C. Martin wrote:
> <snip>
> > several days of discussions about the color of text
> </snip>
>
> Does anyone really wonder why 70% of software projects are late, over
> budget, or both?
Not mine. It is the brochure-tongued Java/UML/XML bloat blubs who have
that problem. Let me do things my way and I deliver fast and good.
>
> Software developers are too often asked to indulge the arrogance,
> incompetence, and laziness of managers and staff. In some cases
> programmers (or business analysts, or software engineers, or project
> managers or whomever's role it is to interrogate users) need to find out
> what the user really needs. To discover a total they'll ask for a
> report. To find a list of at-risk accounts they'll ask for color-coded
> account numbers. User's aren't in the habit of being precise about what
> they need, they're more accustomed to asking for what they're used to
> getting and perhaps some way of enhancing what they're accustomed to,
> rather than asking the software to do something more specific.
>
> Is this feature really qualify for an 80/20 rule of any sort? Is the
> software usable without it? Does it deliver value without it? Is this
> a feature they really want implemented before another feature that
> delivers greater value to the business? Does the customer really want
> programmers worrying about how to color-code text to each user's taste
> and proclivities?
>
> How often do we quite our longtime physician simply because they refuse
> to prescribe for us something we ask for? We trust our doctors to do
> what's best for us even though they aren't us. We feel the discomfort,
> but accept their treatment.
The new model of biz is to give the "customer" what they WANT. The US
is the marketing capital of the world for good or bad, and that means
you kiss up to the customer. If you don't, they will take their biz to
somebody who does or complain to your supervisor.
This is essentially a politcal battle between the libertarian view and
the European view. I won't select which one is "right" here, only say
that you better fit the culture you are in or you are doomed even if
you are smart.
>
> Programmers need to be a little more assertive in how they treat their
> clients business ailments, and do a better job of treating the patient
> than indulging their cosmetic vanities.
So one can be "right" all the way to the unemployment line? I have
learned that being liked is more important to one's career than being
right. I didn't want it that way, I am only the messenger.
> If the developers (individually
> or collectively) aren't in a place to offer expert business-relative
> advice, then perhaps they shouldn't be writing that specific application
> in the first place.
There are essentially 3 levels here:
1. Say nothing
2. Suggest what you feel is the "logical" approach
3. Insist on the "logical" approach
I propose 2, and you propose 3. I used to do more 3, but it does not go
over well. I thought the world was turning mad and illogical until I
read Dale Carnegie (sp?) and realized it was always mad.
Earth ain't for Volcans.
>
> How many of us hire a massage therapist when a urologist is needed? Why
> hire programmers with financial application backgrounds to write a
> workflow system?
-T-
.
- Follow-Ups:
- Re: Decouple SQL queries from class in OOP design
- From: Thomas Gagne
- Re: Decouple SQL queries from class in OOP design
- References:
- Re: Decouple SQL queries from class in OOP design
- From: Robert C . Martin
- Re: Decouple SQL queries from class in OOP design
- From: Thomas Gagne
- Re: Decouple SQL queries from class in OOP design
- Prev by Date: Re: Decouple SQL queries from class in OOP design
- Next by Date: Re: Decouple SQL queries from class in OOP design
- Previous by thread: Re: Decouple SQL queries from class in OOP design
- Next by thread: Re: Decouple SQL queries from class in OOP design
- Index(es):
Relevant Pages
|