Agile programming (was Re: [P|C] Banksel)
Gerhard Fiedler email (remove spam text)
> Gerhard Fiedler wrote:
>>> I don't like to think of programming as a black art, I think we can
>>> and must learn how to do it well.
>> That's (part of) the point. Agile is "art" -- whether black or white is
>> in the eye of the beholder.
> You may be OK with programming being an art, ...
Nope. I'm not (and you're not either) talking about programming. We are
talking about management of programming. Agile is /not/ about
programming; it's about management of programming.
OTOH, it may make some uncomfortable, but the difference between
("just") solid programming and good programming /is/ art. The difference
between ("just") solid engineering and good engineering is art. The
difference between doing anything solidly and doing it well is art; it's
something that can't (predictably) be taught (even though some are more
inspiring than others) and a feature of the individual.
> ... but I find comfort in knowing that I have tools that give me a
> degree of predictability that make programming more of a craft.
What do you consider the difference between "art" and "craft"
(predictability)? If predictability, predictability of what? What tools
are you talking about (Agile techniques)? And why do you think you can
know that they (Agile techniques, if that's what you mean) increase
FWIW and IMO, the relatively frequent refactoring required by Agile
techniques makes most (solid, "crafty") programmers uncomfortable. This
works better with a team of good (imaginative, "artsy") programmers.
In reply to: <BE2EE627353F4312AA81A876020F530D@ws11>
See also: www.piclist.com/techref/microchip/devprogs.htm?key=programming
You must be a member of the
piclist mailing list
(not only a www.piclist.com member) to post to the