Ways to Organise Oneself in Linux

[Crimsonfire]

I am starting to read online books and tutorials about programming and a lot of them have code blocks for you to try out yourself and require you to write small programs to get the hang of things.

I'm sure other people have done the self-taught thing themselves and was wondering how you organised your learning materials and example code properly instead of just having a million bits littered about your home directory and desktop. Not looking for cutting edge, sage advice here just a light-hearted discussion on how people organise their crap in linux.

[meton_magis]

I have under my home directory a directory for programming, then under that a directory for each language, then a directory for each learning project I have. I do this just for my learning and expirementing projects, not for anything that i'm programming for actualy use. that stuf I create a dedicated directory under my home.

[Crimsonfire]

It can be a pain to navigate from this file to that folder sometimes as the command line is nowhere near second nature to me yet but I try to use it whenever possible purely to get used to the keyboard. I never realised that the flow of my typing would be radically different when writing code than, say, writing an email.

[bigtomrodney]

When navigating, a handy tip is that by hitting the tab key you can autocomplete paths. This can make things very fast and will become second nature in no time.

Also using pushd and popd. Instead of cd'ing to a directory that is "far away", use pushd and then when finished you can jump back to the previous directory using popd.

[Crimsonfire]

Cool thanks for the tips. This is why I like this place. Little nuggets of wisdom everywhere!

[nopycckn]

I use Tab constantly, but never have stuck with pushd and popd long enough to like it, I guess. I always keep books/pages/etc. under my Documents directory in their own directories (source code in the directory of the book). I usually keep it as simple as possible, so if there's no need to do so, I won't have more than the one programming file. I'll use a name like test.c or test.plx, and reuse it if possible. If using more than one file, obviously I'll do that, but for single file programs (which beginner-intermediate type books are very often), I'll just use the same one, regardless of what they suggest naming it. I always use VIM, but I'm not really an advanced user.
I'm saying I like to keep things compact and together, I don't do much more ...