A lot of people have asked me for advice on learning to code. What should I learn first? How long will it take? How can I get a job as a programmer? The answer to most of these questions is “it depends.” But there is one question that I can answer definitively. Should I learn to code? The answer is yes.

No matter what your day job is, how old (or young) you are, or what your level of commitment might be, any exposure to programming will have a notable impact on your life. Learning to code is like learning to speak a new language. With a relatively small amount of effort — just learning a few phrases really — you’ll find that a whole new world has opened up to you.

In the next few paragraphs I’ll try to say some stuff that’s relevant to as many people as possible.

My first recommendation for learning to program is to learn HTML. HTML is the language of the web. It’s relatively simple, and very forgiving of mistakes. It’s a great way to ease yourself into a very fundamental aspect of programming: syntax. Before you can make any headway, you have to learn to read and write syntactically correct code. htmldog.com has some great introductory tutorials on the subject that walk you through creating a simple web page. After a few hours you will have an understanding of a core piece of technology that billions of people use every day and which has completely transformed the world in the last two decades.

Once you have a bit of HTML under your belt, you can move on to a simple procedural programming language like python. Python is a great programming language to start with because it lets you focus on the more conceptual side of programming without having to worry about the nitty gritty details of how computers really work on the inside. What makes python especially great is that it’s not just for beginners. Some of the biggest sites on the internet were programmed in python. The most popular example is YouTube. The Beginner’s Guide on the python website has a very thorough list of resources for learning python. Ten years after reading it, I still recommend the book I used to learn python, which is available online for free: How to Think Like a Computer Scientist, co-authored by my first computer science teacher: Jeff Elkner.

If you’ve managed to navigate your way through HTML and python, then you are well on your way to accomplishing any goal you are willing to pursue.

Now a word about motivation. Programming can be hard. Programming can be frustrating. At some point you will find yourself staring at your computer screen for an hour, not being able to figure out why your code isn’t working the way you expect. This is par for the course and a normal part of the learning process. I’ll leave you with a few tricks to getting through these rough spots.

1. Try not to program alone. Two heads are better than one and 99.999% of software is written collaboratively. Working together makes problem solving a lot easier and you’ll learn more in the process. There is an entire programming methodology that is premised on two people working together. It’s called Pair Programming and you should do it.
2. Have a project. It’s incredibly boring to spend all your time doing tutorials and reading books. It doesn’t matter how big or small the project is, it’s just there to act as a test bed for all the new things you are learning. A great first project is making a personal web page about something you are interested in, or even just coding up your resumé in HTML.
3. Get involved in an open source project. There are tons of projects out on the internet that other people have started and which desperately need your help to fix bugs, build new features, or even just write documentation. Working on an open source project is a great way to improve your coding skills because you can learn from the code that’s already been written. If you are reading this and already have an open source project that you are working on, add a link to it in the comments.

At the request of many people, I’ve moved the code from my Easy Facebook Scripting in Python gist into a proper Github repository and made a python package for it that has been published to pypi. The api has changed a bit so be sure to check out the documentation in the README file.

In the next release of fbconsole, I plan on adding these additional features:

• Handling of expired access tokens
• Logout function
• Video upload support

If there are any specific features you’d like to see added to fbconsole, file an issue on Github.

I’ve just been playing around with Sphinx, the new cool documentation generation tool for python. It takes a bunch of restructured text documents (like doctests!) and converts them into a slick looking website that will literally blow your mind. I was able to create a fairly complete documentation site for z3c.form in about an hour. Check it out, and let me know what you think. The URL is http://docs.carduner.net/z3c.form/.

Some nice features of Sphinx are:

• Full documentation search
• Module index
• Documentation cross referencing
• A lot more that I haven’t had the chance to play with

I’ve spent the last several weeks being extremely busy. I’m afraid anyone waiting for the updates to the z3c/zope tutorial may have to wait a little longer.

These are roughly the steps that I took to get through the last several weeks:

1. Drop out of school halfway through my junior year – yes, I’m officially a college drop out, but far from being a “deadbeat.”
2. Fly all around the country/world looking for a job. I don’t even want to think of my carbon footprint right now.
3. Meet Adam Bosworth (who is “just a simple country boy from Vermont”) and get an awesome job at an awesome startup with awesome coworkers.
4. Rent a truck and drive 18 hours from Eastern Washington to Sunny San Francisco (although it was pouring rain/snow/sleet the whole way).
5. Find a great apartment in a great neighborhood (Downtown Berkeley), and generally “live it up.”

Overall, I’d say I’m pretty happy about life at this particular moment.

One of the SchoolTool developers, Ignas, created a buildout script that generates ctags for any python egg and all of its dependencies, to be used with emacs or vim. Seeing just how useful such a buildout script is, I decided to package it up and release it as an egg under a new package name: z3c.recipe.tag. Here is the rundown on using it (direct from the README.txt):

Dependencies

Before running a tags enabled buildout, you must install the
appropriate command line tag generation tools: exuberant-ctags and
id-utils. In Ubuntu, you can install these with apt-get::

$ sudo apt-get install exuberant-ctags id-utils

How to use this recipe

Suppose you have an egg called “MyApplication“. To use this recipe with
buildout, you would add the following to the “buildout.cfg“ file::

[tags]
recipe = z3c.recipe.tag:tags
eggs = MyApplication

This produces a script file in the bin/ directory which you can
then run like this::

$ ./bin/tags

This script produces files called TAGS (for emacs) and tags (for vi) in the directory from
which you ran the script. You can then use this file in your editor
of choice.

I’ve just been playing around with Google Trends to see how the various open source web frameworks are stacking up against each other.

The chart below shows the trends for zope (blue), turbogears (red), django (orange), and ruby on rails (green). Clearly zope has been in a steady decline since these other web frameworks started showing up. Could it be that their websites are so much better than zope.org and that they have so many more tutorials and documentation (doctests do not count!) than zope? I think the answer is yes. I hope this changes.

If you are looking at this blog post another couple years down the road, try doing the same google trends query and see what it looks like now.