tag:blogger.com,1999:blog-4068183698747623113.post3153427326664309101..comments2023-10-29T10:40:34.638-04:00Comments on A CS Professor's blog: How to write programsClaire Mathieuhttp://www.blogger.com/profile/10957755706440077623noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4068183698747623113.post-82376620495134414172011-05-15T13:18:23.237-04:002011-05-15T13:18:23.237-04:00I am not really serious about "deleting every...I am not really serious about "deleting everything". As you said, for a programming assignment, it's not worth it (unless you've twisted yourself into such a knot that starting from scratch would be easier than completing the partially written code.)<br /><br />The goal is to make the program easier to grade. <br /><br />I advocate to "consider" removing helper procedures, not systematically to remove them. People err both ways in that respect: some use too few, some too many.Claire Mathieuhttps://www.blogger.com/profile/10957755706440077623noreply@blogger.comtag:blogger.com,1999:blog-4068183698747623113.post-6540707639408293092011-05-15T07:23:49.817-04:002011-05-15T07:23:49.817-04:00In either case, what is the goal with point 6? To ...In either case, what is the goal with point 6? To make the code easier to read? Easier to reuse? To double-check for bugs? That might help decide your answers.<br /><br />I personally would not encourage removal of helpers when they can make the code more transparent nor would I always suggest re-starting from scratch... <br /><br />... if you are writing a masterpiece (in code, paint, or a novel) I could see that first writing a sketch and then re-starting is natural. But for a programming assignment I am not sure what justifies the extra work. On the other hand double-checking for bugs and making the code more readable is good both for students and graders!<br /><br />What are these very verbose books?Anonymousnoreply@blogger.com