Core Dump

Although all the “cool kids” these days seem to be writing web apps, and the word “cloud” has taken on a new meaning that is sure to confuse meteorologists and normal people alike, I still think that desktop apps are very important. Maybe even important enough to deserve a little more attention than they’ve been getting lately (living, as they do, in the shadow of the buzzword friendly “web app”).

Now, I’m not deriding web apps here – I use them, too! But let’s face it – the web was not designed to be an application. Look up the history of what hypertext means and you’ll see how far we’ve had to stretch it to get to where we are today.

Even the very best web apps tend to spend a lot of effort to look just like a desktop app. When the lazy programmer in me sees this sort thing, it causes me to develop an unhealthy twitch (in minor cases) or curl up into a ball in the corner (in extreme cases), muttering something about “code reuse.”

Of course, this is just a generalization – there are web apps that have absolutely nothing in common with desktop apps – take Google and Twitter, for example.

But even truly unique web apps still end up tied to the desktop in one way or another. I use Google all the time; but most of my searches happen through the “search” box in Firefox. I use Google Notebook, but I get to it through a Firefox add-in. I use Twitter, but I do so through a client (I’m currently using Witty Twitter, but there are literally dozens and dozens of clients out there).

Sometimes I worry that we focus too much on web app design, to the detriment of desktop app design (UI design in particular). Web apps are cool, sure, but the desktop app is still “king,” and it’s not wise to ignore the king!

So, I started using Skype recently (for videoconferencing). It’s a good program, and I like it – though I do just use it for Skype-to-Skype calls with a few people.

However, while browsing through the settings, I came across this little gem:

The sample chat that Skype uses is an exchange from two characters in George Orwell’s 1984.

That is just awesome on so many levels. Well done, Skype – I like your style!

GNU (that’s “GNU is Not Unix,” in case you were wondering) turns 25 years old this year. Apparently, Stephen Fry has made a little video to help celebrate – and I think it’s wonderful and you should definitely go watch it right now.

In fact, you may want to watch it and send it to a friend – after all, it’s free!

Happy 25th, GNU!

It occurred to me the other day that I’ve been doing this stuff (programming) for more than a few years now – most of them in a very much “professional” manner. So I guess that makes me qualified to come up with lists like this!

1. Learn the machine. Build yourself a computer. Understand how the CPU, memory, and IO work. Even if you forget it all tomorrow, you’ll have at least a rough understanding – trust me, it’s important.
2. Everything you know is wrong. Well, not really, but you need to act like it is. Always go back and look at your code with a critical eye – as if it was written by someone else, if that helps – and imagine that you just know there’s something wrong with it, something terribly, terribly wrong, and it’s your mission to find it. Your code will be better because of this sort of attitude.
3. Communication is key. Coding is basically communicating with a very dumb machine (the computer). You have to give it very, very precise instructions, being very careful to tell it exactly, precisely what you want it to do. The mark of a good programmer is someone who can commune with the computer on an almost instinctual level. But it’s equally important to be able to talk to real, live people in just as effective a manner. So don’t neglect that “speech” class that they make you take in college!
4. Everything you’ve done is junk (a corollary to “everything you know is wrong”). Be humble. Learn from your mistakes. Because you will make them.
5. Doublethink can be your friend. Being a really god programmer means walking a fine mental line between being totally confident in what you’re doing – you think that Bill Gates will show up at any given moment to kiss the ground you’re walking on, that’s how good you are – and simultaneously thinking of your work as the worst possible junk that looks like it was hammed out by a bunch of monkeys banging randomly on keyboards.
6. 99% of the time, it’s been done before. Otherwise known as “be a lazy programmer.” Take advantage of work that’s been done before – unless you really want to learn how it’s done, in which case you should re-write it on your own, get it to work, and then throw it out and use the pre-made code instead. Humility AND experience, all in one deft stroke!
7. Be multi-lingual. You don’t need to be able to write an OS from scratch in x86 assembly or anything, but being able to at least read other languages is a great asset – especially since so much of the 99% of code that’s already been written (see #6 above) has probably been written in a different language from the one you’re using right now.
8. Always think of yourself as a student. Programming languages grow and there is always something more to learn, so always think of yourself as a student, and never let go of that feeling.
9. Know your tools – but don’t be held hostage by them. Experiment with different IDEs. Try a different code editor. Yes, we all love auto-complete and Intellisense, but you should at least not be completely helpless without it.
10. Learn and use source control. Hey, you knew I had to squeeze this in here. There’s just no excuse for not using some form of source control, no matter how small your project is – even if it’s just a little side project you’re doing for nobody but yourself. Subversion is free, and so is the great client TortoiseSVN. They’re both available for Windows and Linux, so you have no excuse for not using them.

Well, there you have it. If you’re a new programmer, hopefully these tips will be helpful to you – goodness knows I wish I had known them all when I started out.

Enjoy!

A very amusing “Vista Sucks” parody video.

Make sure you’re not drinking anything while you watch it; you may end up spewing your drink all over your screen when you laugh out loud.