Project fragments and prototypes - how to organize?

While learning langugage, I regularly find myself prototyping new concepts outside of the current project, and often find myself in dozens of small single-use projects that I link to, as well as a lot of useful code snippets that don't necessarily belong in a function library but need to be stored unnecessarily.

How can you name, sort, and generally keep track of these projects and code snippets so that you can return to them when needed, quickly and easily? How do you deal with this?

Hello

Mu

+2


source to share


2 answers


What I did (in .NET):

I use the Snippet Compiler or (lately) LINQPad to do most of the spikes and then discard the results. In the unusual case that I have executed a Visual Studio project, I store it in a junk folder that is not under source control.

"True" snippets or macros (in Visual Studio or ReSharper) are under source control.



What I think about the future:

I heard Bobby Norton talk about Test-Driven Learning and he recommended writing tests in your favorite xUnit when learning a language / technique. Then you can save them, refer to them, try to recreate them from memory, etc. He used the term "knowledge store". If you are using Ruby or Java, he got a tool (on GitHub as Yaraer mentioned) called shubox to help with this.

EDIT: Presumably you will host the training tests under source control.

+1


source


Why don't you use Github Gists? You can set up an account to save them. You can even develop them if you learn something new.

This account can also store a "snippets" repository where you can store more complex demos or pet projects.



Should bring you a pleasant, centralized space and all the benefits of working with SCM.

0


source







All Articles