re[2]: Differences between Structs and Turbine ???

2002-10-09 Thread Rich Persaud

Berin wrote:
|  Even when Quick and Dirty takes longer.  I tried to convince my boss 
that
|  a certain customization required so many fundamental changes that it 
would
|  be quicker and easier to develop/maintain if we did it right.  He told 
me
|  that he would never be able to convince the CEO that was the right 
choice,
|  so the Quick and Dirty route was the choice--taking me twice as long 
to
|  get it done.

Preferred pain is a known pain with an experience-based cap.

New and improved pain may promise an average POI (Pain-on-Investment) that 
is 50% of the familiar pain, but will be assigned a risk profile with 
unknown maximum pain.

If your previous experience confirms that max(NewPain) = max(OldPain), 
then go ahead and implement NewPain, but make it look like OldPain.  If 
max(NewPain) turns out to be  max(OldPain), you're on the hook.  But you 
would have first hand experience to make the call, whereas your boss (and 
definitely his boss) would not (or they wouldn't object in the first 
place).

One successful implementation of NewPain where max(NewPain) = 
max(OldPain), while delivering promised improvements, will set a precedent. 
 But someone has to take the risk.  And it won't be people twice-removed 
from the pain.

...  in my (painful) experience.

Rich

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: re[2]: Differences between Structs and Turbine ???

2002-10-09 Thread Bill Barker


- Original Message -
From: Rich Persaud [EMAIL PROTECTED]
To: Jakarta General List [EMAIL PROTECTED]
Sent: Tuesday, October 08, 2002 8:26 PM
Subject: re[2]: Differences between Structs and Turbine ???


 New and improved pain may promise an average POI (Pain-on-Investment) that
 is 50% of the familiar pain, but will be assigned a risk profile with
 unknown maximum pain.

Now we finally know what the POI developers were thinking. ;-)


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: re[2]: Differences between Structs and Turbine ???

2002-10-09 Thread Andrew C. Oliver

I knew that was coming.  

-dysfunctional Andy

On Wed, 2002-10-09 at 03:36, Bill Barker wrote:
 
 - Original Message -
 From: Rich Persaud [EMAIL PROTECTED]
 To: Jakarta General List [EMAIL PROTECTED]
 Sent: Tuesday, October 08, 2002 8:26 PM
 Subject: re[2]: Differences between Structs and Turbine ???
 
 
  New and improved pain may promise an average POI (Pain-on-Investment) that
  is 50% of the familiar pain, but will be assigned a risk profile with
  unknown maximum pain.
 
 Now we finally know what the POI developers were thinking. ;-)
 
 
 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]
 
-- 
http://www.superlinksoftware.com - software solutions for business
http://jakarta.apache.org/poi - Excel/Word/OLE 2 Compound Document in
Java
http://krysalis.sourceforge.net/centipede - the best build/project
structure
a guy/gal could have! - Make Ant simple on complex Projects!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: re[2]: Differences between Structs and Turbine ???

2002-10-09 Thread Nick Chalko



 -Original Message-
 From: Rich Persaud [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, October 08, 2002 8:26 PM
 To: Jakarta General List
 Subject: re[2]: Differences between Structs and Turbine ???
 
 Preferred pain is a known pain with an experience-based cap.
 
 New and improved pain may promise an average POI 
 (Pain-on-Investment) that 
 is 50% of the familiar pain, but will be assigned a risk profile with 
 unknown maximum pain.
 
 If your previous experience confirms that max(NewPain) = 
 max(OldPain), 
 then go ahead and implement NewPain, but make it look like 
 OldPain.  If 
 max(NewPain) turns out to be  max(OldPain), you're on the 
 hook.  But you 
 would have first hand experience to make the call, whereas 
 your boss (and 
 definitely his boss) would not (or they wouldn't object in the first 
 place).
 
 One successful implementation of NewPain where max(NewPain) = 
 max(OldPain), while delivering promised improvements, will 
 set a precedent. 
  But someone has to take the risk.  And it won't be people 
 twice-removed 
 from the pain.
 
 ...  in my (painful) experience.


Here is the short answer.
Always say Boss I think this will take a little refactoring of some code.
I should be able to reuse the most of the code.  
I will only change what has to changed, and I will make sure that the
changes are isolated.

Then do you whatever it takes, including throwing out ALL THE OLD CODE.

It's your reputation regardless.  You will not be able to say My manager
wouldn't let me do it right
They will always say If you knew it was the wrong approach, you should have
come to me so we can discuss it with your manager.

R,
Nick

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]