Using a Notepad in Industry to keep track of modified code

Started by
21 comments, last by swiftcoder 10 years, 5 months ago

Is that common to have a programmer have a notepad in front of him/her keep track of code that was modified (ie: list before and after code comparison, line location from the IDE)?

I figure if someone modifies something, there might be a chance something else might break in a different area of the program. So this would be a good way to revert the issue.

I never worked in the industry. I am still a CS undergraduate but I was curious about whether or not this is actually how it works in industry.

Advertisement
There's a whole set of software tools known as version control (or "revision control") which solve this problem far more powerfully than doing it by hand.

Wielder of the Sacred Wands
[Work - ArenaNet] [Epoch Language] [Scribblings]

Yeah use software to track changes (also called source control). I'm surprised they don't teach you about that in uni. SVN and SourceSafe are 2 I have used in the past (Git has been mentioned too, not used it).

I'm a firm believer in notepads though, notepads don't crash and lose your data. Best notepads are hardbound and you can't rip pages out. Always keep your old notepads. It's also best to date each entry. (Not "sexy time" date, calendar date).

EDIT: Biggest problem with notepads is illegible writing ;)

"Most people think, great God will come from the sky, take away everything, and make everybody feel high" - Bob Marley

I usually have a notepad for task lists, scribbling down ideas / solving problems, and explaining things to people visually (but no, not for line numbers / change logs).

As mentioned above, if you want to see which lines of code you changed, your VCS program can tell you ;) Usually it's as simple as right clicking on the file and selecting "show diff". If you want to see what you changed in the past, you right click on a file/folder and bring up the log, which then lets you see who's changed it on which date with what description (and then open up a diff of each file they modified and see the line-by-line changes).

There's also a tool called "blame", where you can highlight a particular line of code that you're interested in, and the VCS program will tell you when this line was written and by whom.

Personally, I use git for my code these days... but I'd probably recommend Subversion (and TortoiseSVN for integration with Windows Explorer) as it's easier to learn.


Personally, I use git for my code these days... but I'd probably recommend Subversion (and TortoiseSVN for integration with Windows Explorer) as it's easier to learn.

I don't want to take us too far off topic, but I'd go exactly the other direction on this.

SVN is full of odd little pitfalls that only occur in weird edge-cases, whereas git has a very simple set of base operations which tend to be self-consistent. Yes, advanced operations are unintuitive in both, but SVN is hair raising...

Tristam MacDonald. Ex-BigTech Software Engineer. Future farmer. [https://trist.am]

There's a whole set of software tools known as version control (or "revision control") which solve this problem far more powerfully than doing it by hand.

Interesting.

Yeah use software to track changes (also called source control). I'm surprised they don't teach you about that in uni. SVN and SourceSafe are 2 I have used in the past (Git has been mentioned too, not used it).

I'm a firm believer in notepads though, notepads don't crash and lose your data. Best notepads are hardbound and you can't rip pages out. Always keep your old notepads. It's also best to date each entry. (Not "sexy time" date, calendar date).

EDIT: Biggest problem with notepads is illegible writing ;)

What course do they teach about source control? I'm a CS undergraduate and I am taking 2 CS Classes this semester: Computer Architecture and Discrete Structures.

As this thread is relevant, and recent: http://www.gamedev.net/topic/650027-version-control-and-programming-with-a-team/

Yeah use software to track changes (also called source control). I'm surprised they don't teach you about that in uni. SVN and SourceSafe are 2 I have used in the past (Git has been mentioned too, not used it).

I'm a firm believer in notepads though, notepads don't crash and lose your data. Best notepads are hardbound and you can't rip pages out. Always keep your old notepads. It's also best to date each entry. (Not "sexy time" date, calendar date).

EDIT: Biggest problem with notepads is illegible writing ;)

What course do they teach about source control? I'm a CS undergraduate and I am taking 2 CS Classes this semester: Computer Architecture and Discrete Structures.

there are usually no courses directly related to source control, however it will often be used in larger practical excercises.

In any case, beside git and svn you could also check out (vcs pun, yay!) perforce, which is quite commonly used in industry and free for up to 20(?) users.

I'm a firm believer in notepads though, notepads don't crash and lose your data.

Then there's something seriously wrong with the version control software you're using.

"I would try to find halo source code by bungie best fps engine ever created, u see why call of duty loses speed due to its detail." -- GettingNifty

This topic is closed to new replies.

Advertisement