I have several years of scripts I've written for various projects. I keep them mostly as examples of how to do something so I don't have to figure it out again. I also have scripts i use on a regular basis. Does anyone have a system that they are willing to share on how to store your scripts?
My method
That's all I can think of now
Here are some things that work well for us:
Code development generally occurs in standalone scripts or toolboxes. When we see an opportunity to capitalize on a function or a tool we've developed, we move it into one of the classes in the general functions folder.
Been working great for us!
If you're looking for a place where you can dump your code snippets, or classes, etc. where the code you are keeping is piecemeal? And not part of a larger package? Then I recommend Evernote. If you use it with PortoCode formatter then you get a nice note that you can add to at anytime.
Example Snippet
http://www.evernote.com/l/AAXZTkmP6pFGzJlQgIJ7gABn_9NcFdz9YQs/
PortoCode Formatter
PortoCode - Portable Codes With Syntax Highlighting On EVERNOTE
Once it's in Evernote then you can search keywords or if you take the time to tag it you get even greater control over accessing the pertinent information at a later date.
TortoiseSVN
We just keep it project-based, much like any other application and components might exist in SVN.
I'll second TortoiseSVN. It's nice because it's free, even for corporate use (open source).
They even have like a tutorial or how-to-use part of their site that helps you get started:
https://tortoisesvn.net/docs/nightly/TortoiseSVN_en/
There are also videos and such on YouTube, like: Tortoise SVN Tutorial - YouTube
Thank you everyone for your valuable input!
I've been using Eclipse\PyDev for the last five years and have decided to up my game. I'm currently setting up Python Virtualenv and GitHub to manage my Python Code. I've attached a print screen of my Eclipse\PyDev structure. This allows me to run any of my Python or ArcPy scripts outside of ArcGIS as well as schedule my scripts to run at any given time.
We simply use Windows task scheduler pointing to individual .cmd/.bat files that execute .py scripts. Aside from managing dev/test/prod versions, it's pretty straight forward.