How Do You Store Your Previously-Written Code?
Asmor asks: "I'm a novice programmer who is largely self-taught. It's never been too much trouble for me to reinvent the wheel constantly before, but now as my ambitions get loftier I'm finding that I could really benefit from maintaining some oft-used code that can easily be reused. The problem is, I really don't have any experience with this and I'm not really sure how I should organize things, how the code should be stored, how it should be implemented, etc. I think this is what people mean when they talk about libraries and/or APIs, but not really sure. I'm specifically curious about PHP and JavaScript, but advice for other programming languages is also helpful! How do you store and maintain your most frequently used code?"
That's where I store mine: /home/user/code.
Just "gittin-r-done," day after day.
If you have code you want to maintain, you want it in CVS or SVN (preferably SVN since CVS sucks ass).
With Apache2 or alone, it'll sit on a nice server you can regularly backup, keeping precious meta-data and history information about your code!
To do anything less is foolish.
--
Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
They in turn reside on filesystems.
As an additional bonus, there are FOLDERS available to sort out your historic work.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
I have a recipe which has served me well for years. If you want to know more, read:
o re-my-previously-written-code/
http://rudd-o.com/archives/2006/02/16/how-do-i-st
Rudd-O - http://rudd-o.com/
I have a recipe which has served me well for years. If you want to know more, read:
o re-my-previously-written-code/
http://rudd-o.com/archives/2006/02/16/how-do-i-st
(this post contains the valid link, the others I couldn't edit and I don't know why)
Rudd-O - http://rudd-o.com/