How often do you like to compile?
-
Someone here, I believe it was honey the codewitch, mentioned they "develop very iteratively". It made me think about styles of coding vs. debugging. Where I work, some people tend to code much more than others before compiling. I like to err on the side of caution- compiling much more often to see that what I think I did, actually worked the way I think it did. Maybe some of it is confidence in your code skills? You can certainly code more if you don't check your work every two seconds, but if you embedded a bunch of bugs, they may be hard to find if you wait too long. ...Just curious what you guys think? Is it a matter of style, or is there a right or wrong way? How often do you like to compile? :confused:
-
Someone here, I believe it was honey the codewitch, mentioned they "develop very iteratively". It made me think about styles of coding vs. debugging. Where I work, some people tend to code much more than others before compiling. I like to err on the side of caution- compiling much more often to see that what I think I did, actually worked the way I think it did. Maybe some of it is confidence in your code skills? You can certainly code more if you don't check your work every two seconds, but if you embedded a bunch of bugs, they may be hard to find if you wait too long. ...Just curious what you guys think? Is it a matter of style, or is there a right or wrong way? How often do you like to compile? :confused:
Do you mean compile or actually test? A function that adds a and a instead of a and b compiles fine, but it's still a bug. I compile more often than test. How often I compile depends on what I'm doing. If I'm writing new functionality I usually don't compile until I think it's (partly) done. Whenever I'm fixing bugs or typo's I sometimes compile after every few keystrokes. And I save VERY often, like every minute or so (and sometimes more often).
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly