ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Over the years I have been collecting snippets of code and have written my own but have never come up with a good system to store the code. I am not an everyday programmer but code adhoc to get things done.
I have been been just storing in text files but have been considering either a personal wiki (Dokuwiki) or a CVS (overkill?). So how do you store your personal code?
For my job, i do write my own code, but i'm not a programmer by trade. mostly, i don't know how to write code for multiple systems, and i am usually the only user of my code.
i have a scheme to document and save my codes. i do use cvs, for code, for TeX documents, for many things.
i think what is most important is that, if you do feel code is worth saving, save documentation for it as well. maybe most people here would say, "of course!" document, but for a long time, i didn't document my work.
a personal wiki is interesting, find something you are comfortable with. i screwed up CVS a few times, it took a little time to get used to it. i find cvs makes me stay organized. a wiki would be another way to stay organized.
i hope that helps. it would be interesting to hear what others have to say.
CVS is useful if you are making changes to code but if all you want to do is store it then i's not really much different than creating a folder and sticking everything in there in some kind of hierarchy. I'd say only use CVS if you plan on actually version controlling.
When I'm working on code for personal purposes, I like to store it in a CVS repository once it is at a satisfactory level of polish and usefulness. This makes it easy to keep track of, and back up. Otherwise, it just gets lost amongst the myriad of other bits and fragments of maybe-working stuff. It's really just an organizational tool, more than a rigorous versioning system.