When I'm
> working on a commercial
> product though, I'll never go out of my way to
> expose myself to additional
> somebody else's bugs in order to fix them. I just
> can't afford that big a
> potential hit in my personal productivity, whatever
> the advantages to
> society at large. 
> 
>       

You cannot be serious. C’mon, are you saying that
dealing with “blackboxed” product bug helps your
personal productivity?! 

 “Common good” is a worthy purpose, but even on very
pragmatic, personal and immediate level it is highly
rewarding to be able to dive into somebody else’s code
and fix bugs here and there.
-       if you fixed the bug – you just gained productivity;
-       went through that project code and did not throw up
– you just gained confidence in the project and gained
productivity again by becoming familiar with internals
of the tool/library whatever;

Of course there is certain threshold where original
developers of the project must do changes, but
dismissing even idea of diving into project source
seems gross. 


Konstantin Ignatyev




PS: If this is a typical day on planet earth, humans will add fifteen million 
tons of carbon to the atmosphere, destroy 115 square miles of tropical 
rainforest, create seventy-two miles of desert, eliminate between forty to one 
hundred species, erode seventy-one million tons of topsoil, add 2,700 tons of 
CFCs to the stratosphere, and increase their population by 263,000

Bowers, C.A.  The Culture of Denial:  Why the Environmental Movement Needs a 
Strategy for Reforming Universities and Public Schools.  New York:  State 
University of New York Press, 1997: (4) (5) (p.206)

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

Reply via email to