[hand with pencil]
Stuff For Sale
2004 Summer Tour
About
Blog
Class Stuff
Email Me
Events
Gallery
Home
In The Press
Newsletter
Services
Smalltalk
Veggie Van Gogh

Credits
© 2002,
Bytesmiths

[this is simply a banner and menu bar]

Please patronize sponsors of this page!

Bytesmiths no longer is involved in software consulting. Maintenance of this web site is currently subsidised by unrelated business activities. Please pass the word to other interested folks, so I can continue to host this page!
Your site could be listed here, for as little as $12 per month! Go to Bytesmiths Press for details.

This site has been selected by PC Webopaedia as one of the best on this topic!
This site has been awarded a Links2Go Key Resource Award in the Smalltalk category!

[ prev | top | next ]

Curious Minds, Better Solutions

(This is a slide show. You really won't get 
anything out of it unless you have a graphical web browser with graphics turned 
on.)
- All work and no play makes for unimaginative problem solutions. Serendipitous discoveries during idle diversion often drive tomorrow's business solution.
- Such "discretionary hacking" often turns up entire solution patterns that can be re-used for business purposes. Solving a particular business problem under schedule pressure usually results in lower re-use than does recreational programming, as developers feel they should be coding when they are under schedule pressure, rather than figuring out how to do things.
- There is a tricky balance between discretionary hacking and getting real work done. Given absolute freedom, half your team will end up spending all their time writing tools, the other half will end up reading network news. To strike a balance:
  • Define a certain percentage of developers' time as discretionary and require regular informal reports on what is discovered in such time. Let it be known that if it is abused, it will go away.
  • Keep a "job jar" of interesting, but low priority tasks that people can play with in their spare time, such as "menu improvements," "new GUI ideas," "audio interface," etc., and volunteer these out as time allows.
  • Similarly, define a few broad guidelines for those who would be toolsmiths, so they end up playing with things that have potential project use, instead of working on a personal software toy.

    [ prev | top | next ]