views:

86

answers:

2

When you are learning a new subject or technology what ways do you use to remember your achievements ?

In the past I have used a variety of methods including some of the following :-

  • Paper-based Journal (A4 paper cut in half with a guillotine, and bound with a plastic spine.) I keep this chronologically, and frequently reorder the pages to group continuations or similar pages together.
  • Emails - I frequently email snippets of code to myself
  • Test programs - Short self-contained snippets of project code.
  • ProtoPage.com - web based repository of notes.
  • Memory - frequently the least reliable method, but occasionally it's better.

Finally :-

  • Stack overflow - I previously asked a question on here as I was working on the solution. Then came back to provide my own answer. Is this an acceptable use of Stack overflow ? Banging in questions as I think of them, and then coming back to provide an answer an hour, few hours, or maybe days later whn I've worked through it. Maybe coming back in the meantime to see what answers I'm getting, maybe providing me with new directions to try.

I was tempted to create a blog where I can store all these kinds of voyages of discovery I have but I think there may be greater value putting it on here.

Thoughts, opinions, and your methodologies girls and guys please.

+1  A: 

If you build a core library for all your applications, you can use that for reference/commenting etc. You dont need to remember the full implementation of code, you just need to rememeber a reference to where it is (which is naturally/structurally categories by your code)

Mark Redman
Interesting. I shall bear this in mind. I was thinking that small snippets of code in a '101 useful code snippets' kind of way was what i had in mind, however maintaining a code library, properly documenting it, and using source control, and a semi-formal release process, with automated testing might provide a LOT of value. It doesn't help newbies coming along on SO later on, who might want to invent the same wheel I invented a month ago.
cometbill
+1  A: 

The thing is a Blog is exactly the means to achieve what you are wanting to. Its an online reference, allows for collaboration and you won't get shot to pieces when you post "random" questions on SO all day long, and answer them in a week when you find the answers.

SO is basically Q&A whereas a blog is a running counter of your problems and solutions to your coding problems.

It doesn't hurt either, can get some nice recognition from your blog, and gain yourself some reputation/followers in a community.

Kyle Rozendo
I think the idea of sharing my knowledge using SO is becoming more appealing. I don't have to maintain a blog, I still get recognition from my peers through the voting and comments system, and gain reputation points as a side-effect. I'm not looking to gain an army of followers after all every man and his cat seems to have a blog these days, or twitters about how many times they've been to the bathroom, or whatever.
cometbill
Kyle Rozendo
on the other hand, if the quality of the answers were sufficient then other programmer's trying to achieve something I've done before will benefit, whereas they may not even find the content if it were on my blog. Information on blogs becomes static and out of date quickly, whereas many people editing questions on here, or providing their own answers adds a lot of value, I feel.
cometbill
Sure, but you're still missing the point. This specific site, is not intended for that type of use. Perhaps the answer may be to create your own implementation of this, which from what it seems you will get is a Wiki with voting.
Kyle Rozendo