[PD] Good PD programming practice?
pd at earcatching.com
Thu Mar 4 22:50:17 CET 2004
Has anyone seen rules-of-thumb for "good PD programming practice" (in
the same way "Extreme Programming" has advice for good C++ writing?) Or
does anyone have strong opinions on the topic?
e.g. are abstractions preferable to subpatches, or is there a time and
place for each? Is there a recommended limit to objects in any canvas,
for clarity's sake? Any recommendation on the extent and style of
My aim is to have some "house rules" so a number of us can work on the
same large-scale patch with maximum clarity and minimum confusion.
(Also, it's part of an assignment, so we need to do things as "by the
book" as possible.)
Thanks very much for your ideas,
More information about the Pd-list