teamwork

In my last posting, I talked about the benefits of code reuse and how any good programmer should swear by that coding principle. Today, I move on to another key programming methodology, that of version control.

Version control (revision control, source control, or any of a number of other similar names) is a method for archiving and documenting changes to programming code, web pages, XML files, and, frankly, any other type of file of which you might want to store multiple versions in one centralized location. A benefit of this is that multiple programmers can work on the same code base without interfering with each other, and that you can easily track or back out changes to a file and go back to an earlier version, should a new change cause problems. (more…)

For my first instructional posting, I thought that I’d reach back to one of my finest failures in my history of being a programmer. This little tale harkens back to when I was first starting out in programming, back to my freshmen year in college. I never did a lick of programming prior to entering college, unless you count hacking away at the BASIC source code for that hidden artillery game in DOS 5.0 when I was supposed to be paying attention in high school typing class. Actually, doing that was quite fun, making the explosion radius half the size of the screen — I even showed the trouble maker in the class how to do it, which promptly got him in trouble with the teacher. He never did have that innate instinct for ALT-tabbing when said instructor was walking past you.

Note quite the same game (this is from Blarworld.net), but close in appearance.

(more…)

Controlling your code through versioning

How NOT to design programming code

Recent Posts

Archives

Categories

Good tech reads

Links