by RobLaughter » Apr 11th, '07, 21:30
I'm having trouble relating magic to software development, as magic is a manual art while software development (though I only have experience in web development) seems to be a linear process.
In development, you have to create a working product, while in magic instruction (assuming you're indeed talking about learning an existing trick rather than creating a "new" effect) is a learning process--that is, one is constructive and one is perscriptive.
I think paragraphs and bullet points are both equally efficient at teaching how an effect should be done and that saying "both approaches are difficult to understand" is almost pretentious. Concrete terms like "are" and "must be" should not be used without sufficient evidence that something "is" or "must be"--relying on anecdotal evidence such as "I have" is simply not enough.
Magic has been taught for thousands of years and of thousands--perhaps millions--of magicians have learned in this way since magic became an art form and not "witchcraft" or "sorcery." Certainly, it's not a valid argument to appeal to antiquity, but I'm left doing so for lack of a better example.
Perhaps I'm just not seeing things your way, as you've not included any example with your ideas. If you're saying that things should be broken down, I'd contend that they already are; we learn sleights, then put them together to form routines. Perhaps you can give us a more concise example of what you're talking about, we could better understand how this is supposed to work.
Regards,
Rob
P.S. I'm not sure how this pertains to "file sharing," either...