Board index » delphi » Re: Developers in Pain

Re: Developers in Pain


2008-01-03 03:25:30 AM
delphi144
Paul Nichols [TeamB] writes:
Quote
Farshad writes:
>:)
>www.youtube.com/watch
>

Who among us, cannot relate to "developer pain!"
I can't! No customers, no boss. <g>
--
Rudy Velthuis [TeamB] www.teamb.com
"Manuscript: something submitted in haste and returned at
leisure." -- Oliver Herford (1863-1935)
 
 

Re: Developers in Pain

Paul Nichols [TeamB] writes:
Quote
fortune 50 company, gave us two months to write an application with 4
developers that took another branch of the company 2 years and 40
developers to accomplish
I guess they don't want to remain in the top 50 for long.
--
Dave Nottage [TeamB]
 

Re: Developers in Pain

"Rudy Velthuis [TeamB]" <XXXX@XXXXX.COM>writes
Quote

I can't! No customers, no boss. <g>
Hey Rudy,
I sling code for a living, but I have been thinking of getting into dentistry
as a hobby. Whatdya think? :^)
Cheers,
Van
 

Re: Developers in Pain

Rudy Velthuis [TeamB] writes:
Quote
Paul Nichols [TeamB] writes:

>Farshad writes:
>>:)
>>www.youtube.com/watch
>>
>Who among us, cannot relate to "developer pain!"

I can't! No customers, no boss. <g>

Lucky dog... :)
 

Re: Developers in Pain

TJC Support writes:
Quote
"Rudy Velthuis [TeamB]" <XXXX@XXXXX.COM>writes
news:XXXX@XXXXX.COM...
>
>I can't! No customers, no boss. <g>

Hey Rudy,

I sling code for a living, but I have been thinking of getting into
dentistry as a hobby. Whatdya think? :^)
If you can find patients, why not? <eg>
--
Rudy Velthuis [TeamB] www.teamb.com
"Testing proves the presence, not the absence, of bugs."
-- Edsger Dijkstra
 

Re: Developers in Pain

"Rudy Velthuis [TeamB]" <XXXX@XXXXX.COM>writes
Quote

If you can find patients, why not? <eg>
Hmm, I am afraid that even if I can find patients, I will still have no
patience. :^)
Van
 

Re: Developers in Pain

Dave Nottage [TeamB] writes:
Quote
Paul Nichols [TeamB] writes:

>fortune 50 company, gave us two months to write an application with 4
>developers that took another branch of the company 2 years and 40
>developers to accomplish

I guess they don't want to remain in the top 50 for long.

I don't know. Most of the application development is like that. Old team
members still call me about finding them a position with my new company. :)
However, I think it may change somewhat, since the merger.
Last project I was on there was much better. The manager however, came
from IT and understood application development. Makes a huge difference.
 

Re: Developers in Pain

"Jouni Aro" <XXXX@XXXXX.COM>writes
Quote

Do not ask what happened next, but at least we learned that the prototype
should never be too good...
I produced a "working" prototype, complete with *scripted* live data in time
for a client to present it at a trade show many years ago. It was good
enough that his potential customers were ready to buy it on the spot,
needless to say, that merely led to completely unrealistic schedules for
the real application that had not even been properly scoped out or designed
yet.
I will never produce such a prototype again. Since then I mockup screens
(easy to do in Delphi of course) and then just insert screen shots in a Word
doc.
--
Wayne Niddery - TeamB (www.teamb.com)
Winwright, Inc. (www.winwright.ca)
 

Re: Developers in Pain

On 2008-01-02, Mike Orriss <XXXX@XXXXX.COM>writes:
Quote
Rudy Velthuis [TeamB] writes:

>I don't knmow your dentist, but why do people always associate
>dentistry with pain?

Perhaps its because visits are painful?

I don't ever remember any visit to any dentist that didn't cause me
pain :(
Actually my two worst visits to the dentist are actually not related to
actually dentistry, but to medication that accompanied it.
A sedation (for a simple filling) that made me pretty much incoherent for
three days, and an antibiotic (for a problematic root c{*word*7}no less that
actually paled compared to the medication).
 

Re: Developers in Pain

Wayne Niddery (TeamB) writes:
Quote
"Jouni Aro" <XXXX@XXXXX.COM>writes
news:477cfbca$XXXX@XXXXX.COM...
>
>Do not ask what happened next, but at least we learned that the
>prototype should never be too good...

I produced a "working" prototype, complete with *scripted* live data in
time for a client to present it at a trade show many years ago. It was
good enough that his potential customers were ready to buy it on the
spot, needless to say, that merely led to completely unrealistic
schedules for the real application that had not even been properly
scoped out or designed yet.
Sounds too familiar...
Quote
I will never produce such a prototype again. Since then I mockup screens
(easy to do in Delphi of course) and then just insert screen shots in a
Word doc.
Yes, it is after all much better to just try to put everything in a list
and calculate the estimates without showing anything concrete before the
schedules and costs have been agreed to.
After all, the e{*word*277}ment of creating new apps can be very tempting and
you want to show that you can do it. But if you do it too quickly or
the tool (such as Delphi) helps to create something too quickly, people
tend to draw conclusions that the rest cannot be much more difficult.
On the other hand it is very hard to admit to yourself that it will take
that much time for you to get such a simple application done :)
Also, for some reason (well, it is the only visible part :) ) when the
GUI is there it seems like almost finished, even if it would not do
anything. But the GUI is usually only a small fraction of the complete
system - especially the initial GUI which will require several changes
before it finally satisfies.
Lessons learned :)
 

Re: Developers in Pain

"Jouni Aro" <XXXX@XXXXX.COM>writes
Quote

Also, for some reason (well, it is the only visible part :) ) when the GUI
is there it seems like almost finished, even if it would not do anything.
But the GUI is usually only a small fraction of the complete system -
especially the initial GUI which will require several changes before it
finally satisfies.
For customers that do not know anything about software development, this is
the biggest point - they can only go by what they see (and they cannot be
blamed for that) - and when they see what appears to be a working program,
for them the GUI *is* the program and it already works, so why can not they
have it *now*?
--
Wayne Niddery - TeamB (www.teamb.com)
Winwright, Inc. (www.winwright.ca)