tag:blogger.com,1999:blog-18677687.post6732009680834042199..comments2024-03-27T15:13:24.764-04:00Comments on Computer Science Teacher: Code, Compile, Test, RepeatAlfred Thompsonhttp://www.blogger.com/profile/05575057876858763822noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-18677687.post-66555315979454665692015-05-13T14:51:14.342-04:002015-05-13T14:51:14.342-04:00I try to beat this through my students sometimes t...I try to beat this through my students sometimes thick skulls. Test every change in code. It is so easy to run with new IDEs that anything else is just foolish. One of my Programming I assignments involves drawing a tessellation with Small Basic. The kids will enter 20 lines of code at once and get junk when they run it. They then ask me to troubleshoot it for them. I delete 19 lines of code and tell them to test it. I too was in the punch card and limited compiling time era. There was something special about writing the whole program in one sitting and just hoping it worked.Garthnoreply@blogger.comtag:blogger.com,1999:blog-18677687.post-34196145463847422762015-05-13T12:04:10.715-04:002015-05-13T12:04:10.715-04:00I don't use an IDE, rather a highly customized...I don't use an IDE, rather a highly customized Emacs install. Whether live coding or coding on my own stuff it's always save/compile/test on every concept - that is a loop, a conditional, a formula. One concept at a time.<br /><br />I model it and also talk about it.<br /><br />Maybe my compulsiveness w/r to this hearkens back to the days when idle hands would instinctively type "sync" in the Unix shell.Mike Zamanskyhttps://www.blogger.com/profile/15069276938781711576noreply@blogger.com