Writing code for others demands these higher standards, but writing a quick fix needs no documentation - until it becomes a popular "work-around". So I think we need coding habits that are economical, not only for the author, but also for those who "pick up the pieces" - when methods are used outside their effective domain, and fail. Not only is brevity the resulting gain from deprecating unneccessary SAS statements, those who follow will appreciate the clarity of purpose when the see "the code and nothing but the code". Abhor redundancy in programming A statement is not redundant if it clarifies. Production code should not be expected to serve as a model, or example for learning. But should the code generated by wizards serve in that way? Should there be a warning in the code generated by a wizard (for example, the tasks of EG and DI and proc import) - redundant code might be generated here?