[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Amazing, Incredible OddBall version performance ?



PureBytes Links

Trading Reference Links

"I can tell you what the problem is, developers only want
> to deliver what they are capable of, they are hard headed and will refuse
to
> collaborate to create the perfect solution. So basically all you will ever
> get is compromise."."

I agree with everything Lawarance said.  And yes many developers are hard
headed when there isn't enough incentive.  If you're working on a shoestring
budget to deliver say some trading software to market that may or may not
sell, it's can be hard to convince developers that the risk is worth taking.
However, cutting loses early can help.  If one person doesn't work out go
find another. If that one doesn't work out go find another.  It's time
consuming and a pain but developers are individuals too with different
perspectives and others may have more compatible views with yours.  Finding
the right people is key; who not only have the knowledge to implement your
ideas but also are risk takers can help create cooprertiave synergy it takes
to deliver software.  In the absence of that the only thing that talks is
cash.  You got the cash you can ask for anything and a lot of people will
interview.  But then it may not be profitable for you.  So you have to
decide.

Brian.

-----Original Message-----
From: Lawrence Chan [mailto:stnahc@xxxxxxxx]
Sent: Thursday, February 14, 2002 6:44 AM
To: Tom Nielsen; omega-list@xxxxxxxxxx
Subject: Re: Amazing, Incredible OddBall version performance ?



I do tend to agree what you quoted Mark saying that
"developers only want to deliver what they are capable of"
but must quantify that with a few extra points.

1. many, but not all, independent developers have this
   problem due to lack of software enginnering background.
   Everybody can learn to write programs, but when one is
   writing a large program that requires multiple programmers,
   testers, etc. then you need good software engineering
   to enable efficient collaboration.

2. many programmers like to pull from their bag of tricks to
   write code - sort of like a habit to solve certain type of
   problem they will tend to use a specific solution.
   If this developer has a bad habit in certain type of code,
   and no quality assurance by testers, then the bad or
   inefficient code will go to the hand of the user.

3. many programmers also like to use their first impression of
   a problem to code a solution. When they are down at middle
   of the coding and find that it is not a good solution at all,
   they will patch the solution to make it fit.
   With good planning, and willingness to dump code, good
   solutions can be created.

4. But remember, the cost to produce software is so high that
   many programmers are pressed by time constrain, limited by
   available resources (you can only type so much an hour!) and
   worst of all, unclear objective from the boss (I want to create
   the best trading software around! - but what define best?!) :)


Lawrence Chan
http://www.tickquest.com


--- Tom Nielsen <tnielsen@xxxxxxxxxxxxx> wrote:
> List,
>
> whereas I fully agree with the comments regarding posting private emails
> publicly without all parties of the correspondence giving prior consent to
> it (...VERY bad form!), the illustrious Mr. Brown did sort of leave
himself
> open to such comments:
>
> Mark Brown, 30th January 2002, on this list: "Otherwise I always wonder
what
> keeps a developer from listening to what the public wants and simply
> delivering it. Well on second thought having lived "barely" thru the
> TradeWare debacle. I can tell you what the problem is, developers only
want
> to deliver what they are capable of, they are hard headed and will refuse
to
> collaborate to create the perfect solution. So basically all you will ever
> get is compromise.".
>
> Even though this comment was made in relation to system development
> platforms, I think it's fair to say that it fits quite well. What goes
> around...
>
> Tom (a "developer")
>
> P.S.: I also agree with the comments saying (basically, anyway) that the
guy
> who started this thread should pull himself together and figure the thing
> out himself. If you expect to have the perfect solution handed to you on a
> silver platter for free, you're going to die poor...
>