Different methodology; same goals. The reduction of the Art of Programming to a paint-by-numbers process with interchangeable machine parts. (Programmers)
That's been the attraction for management with every new process or programming method or language that ever gained a lot of buzz: the promise of being able to replace temperamental, expensive craftsmen with fungible, cheaper assemblers.
So if something gets a lot of buzz in industry magazines, I assume it's probably not particularly good for programmers or for the craft of good programming. It hasn't failed me yet.
Aaron B.
Available for small or large Perl jobs and *nix system administration; see my home node.
In reply to Re^4: Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship
by aaron_baugher
in thread Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship
by eyepopslikeamosquito
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |