TL;DR version: Skip to In a nutshell.

This article assumes you understand the notiation for file system permissions, and have a basic grasp on the topic. If not, there is a nice starter article on the Ubuntu community wiki:

By default, when you create a file in Ubuntu as a standard user (either in Nautilus or with touch), it gets the permission of 644. If you mark that file as executable, as expected, it gets the permission 755.

What may be surprising is that directories also have a default permission of 755. Even though it seems like directories aren’t the type of thing that would be “executed”, this flag is actually very important to Linux!

Say you already added a tag, but later realized that it was in the wrong place, or perhaps you needed to add a few more last-minute commits. How would you go about moving it?

TL;DR version: Skip to Storing your HTTPS credentials using a Keyring.

If you use GIT in Ubuntu, you may be used to this seeing this several times a day:

Tired of constantly typing typing in your credentials? (especially since GitHub requires an alpha-numerical password, so your standard, “easy-to-type” one won’t do)

My one line if statements have been described as “um… unique” and “making me cringe”, but trust me, there is method to this madness; mainly, it’s practical for debugging.

The man pages for GIT aren’t usually the clearest or most helpful, and is seldom the first place I turn to for help. Still, I ran across some valuable “best practices” information which I myself have not been following due to ignorance.

As we all know, if you don’t call super() in your constructor’s code, the Flash compiler will automatically append it to your constructor’s code.

Turns out, this isn’t entirely true. The compiler only adds super() if it doesn’t see it written out in the constructor. It makes no distinction whether you actually call it or not. Here is a simple little trick if you want to completely hop over calling super() when creating a sub-class.

Learning to program all on your own can be hard, really hard in fact. Sometimes it helps having a place where you can ask questions when Google just isn’t giving you what you are looking for. There are also benefits in using a community to answer programming questions (a topic I will cover in an upcoming blog post).

To assist in choosing a community, I have compiled a list containing details about various communities and my experience in using them.

No, it’s not a trap. There is no fine-print.

If you need any help with code but are working on a low budget, I’m your man. I also do tutoring, helping to explain anything you may have missed or still don’t understand fully when learning a new programming language.

I typically prefer the information in my posts to be more “practical”, but the last few posts have been mainly monologues. Bear with me though, I’m working up to one central point, and after that I’m back to writing useful information.

Note: I can only speak from personal experience on this issue, so I could use more input.

To say that I have been “programming” since I was 13 would be a stretch. I knew how to write code, but I was crippled by how much Visual Studio.net generated automatically for me. I never learned many of those automated tasks manually.

Aside from a programming class in high school with a fantastic teacher, I’m entirely self taught. Being self taught is usually viewed as a great thing, though I cannot figure out why.