Re: SproutClass.pdf

A paper by Mike Feathers:

http://groups.yahoo.com/group/welc/files/SproutMethod.pdf

> Still, as an explanation and a pattern I think it's outstanding.

Why are we gushing about a paper specifying how to write a 4 line function
(plus the Java cruft)?

Here's why:

In the olden days, the programming industry wrote tutorials on what object
models a program should use. That trend peaked in /Design Patterns/, which
set off the Great Pattern Easter Egg Hunt.

The result was heuristics for static qualifications of the shape of a
program as fixed in one point in time.

Today, we talk of pairing, refactoring, integrating, releasing, accepting,
and TDD-ing. These all represent "testing the act of changing". They all
have "ing" on the end.

This new wave, Patterns of Change, has us writing papers saying what simple
but effective changes will grow healthy static design instances, as an
emergent behavior.

Even papers with topics as screamingly obvious as how to sprout a method!!

<mutter> well done, Mike </mutter>

--
  Phlip


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/NhFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/