I only added a photo of a cat because people like cat photos on the internet, and this is about the internet.

Learning how to make the internet, a guide

(Editor’s Note: This was initially posted on July 11th, 2011, on my old blog, andymboyle.com, which I’ll probably sunset eventually because ugh, old content, amirite? I’ve updated it a bit because, well, I’m less dumb than I was in 2011. And because people regularly ask me how to learn how to make the internet, and they’re generally not journalists, so I’ve tried to make this more for anyone.)

I’m regularly asked how I got started doing web development, and how folks can learn what I learned. So I thought I’d not only tell my story of how I got into the l33t internet game, but also give a basic roadmap of online resources and what you generally need to know to do the internet-making job, whatever the hell that means.

The big problem with learning how to make the internets is you need to know a little about a lot just to get a basic project off the ground. And not every tutorial tells you that you need to know X, Y and Z. Therefore, I’ll try to mention all the things you should get some basic reading up on.

But before I start babbling, you need to know that I come at this with a bias toward the programming framework called Django. Just because I like Django does not mean you have to like it. When possible, I will point out other frameworks/languages you can and should check out. The important thing to remember is that you can get the job done using many different tools. It’s your job to find the one that’s best suited for you.

(Editor’s Note: See, I already mentioned a framework. If you know nothing about the internet, you may already be lost! Which sucks, but stay with me, as I try to walk you through some stuff.)

Here’s a list of the shit you need to know, more or less, to be a well-rounded internet maker:

  • A scripting language (Python, Ruby, PHP)
  • SQL
  • HTML
  • CSS
  • JavaScript (and libraries, such as jQuery, etc.)
  • Server ops (aka making servers work)
  • How MVC frameworks work

And here’s a cool graphic, called Engineering The Internet, that’s also a good primer.

Now that that’s out of the way, let’s begin!

HOW DID I GET STARTED

I used to be a reporter. My thing, at the time, was telling stories using data, stuff I would fight public officials for, big databases I would smash into other databases, find new, fancy story ideas.

After doing one big project during an internship where I found a bunch of felons had used guns illegally to hunt in Arkansas, a long Sunday story ran. And I had all this data that could’ve told an even cooler story online. So I decided, I should learn how to put data online and tell stories that way.

Six years later, I’ve been slowly moving up the ladder of figuring out how the internet works, how to make data do shit online, and more. Every time I got a new job, I’d have to learn new skills, new ways of telling stories not just on the internet, but of the internet.

That’s how it’s going to be for you: Once you start doing this shit, you realize how little you know. And then you know more, and realize still, how less you know than you thought you did. But hey, what’s important is you’re learning. So let’s dive into how the goddamn internet works.

SO THE INTERNET SORT OF REALLY IS A SERIES OF TUBES

Did I just blow your mind? Okay, well, in order to build anything on the internet, you need to know how the damn thing works.

The basics are this: You’ve got servers. On them are databases. Think of a database as a fancier Excel spreadsheet, with rows of data. A website is basically a database that your computer is asking to talk to. Your browser renders the code that makes the website look pretty.

So the basic areas you need to understand in order to get a project live are this: Servers, databases and website code.

Let’s start with the code on the website. When you go to a website — like this one — something makes it look pretty. You may have heard of this. The basic building blocks are HTML and CSS. If you right click on the page and hit “view source,” the stuff that pops up is the HTML, or hypertext markup language.

After viewing the source, you’ll see somewhere a file (or files) ending in “.css.” That’s the CSS. It basically makes it quick and easier to style stuff. So instead of writing “make the background of this box red, make the font of any text in it size 14 and make this box 300 pixels wide,” you just call something you previously defined.

This follows one of the basic rules of programming: Don’t Repeat Yourself. You could program something without CSS, which is called using inline styles, such as on this amazing website, but you’d be repeating things over and over. Hence the use of CSS, which stands for cascading style sheets.

So these are some basic building blocks you should learn. You don’t have to be a master at it — I’m certainly not. But you need to know the rudimentary basics so you can chat with more experienced folks and learn from them.

DATABASES AND STUFF

So knowing HTML/CSS will show you how to make flat websites where basically every individual page has to be hand-coded. Think the internet from 1997. (This should refresh your memory.) Another way websites work is by hitting databases, asking for information and spitting it out on a page. This blog — most blogs, really — work this way.

Think of it like this: Each part of a blog post, or a story on a newspaper website, is made up of different parts. A headline, byline, text field, related links, etc. All of that is stored in a big spreadsheet, basically. And the website is programmed in such a way that when it sees www.thiswebsitewhatever.com/2011/04/22/best-cat-photos it knows to pull information for that post or story.

So you need to learn the basics of something called SQL, which is the language most databases talk. It stands for “structured query language,” just so you know. A basic line looks like:

SELECT * FROM awesome_pet_names WHERE pet="cat"

That may be rusty. But basically, you talk to a table named awesome_pet_names, asking for every thing in it where the field “pet” has the word “cat” in it. That’s a basic SQL query, and that’s more or less how the entire internet runs. Especially the part about cats.

SQL is one of the main internet building blocks, so it doesn’t hurt to know. Here’s a good place to start learning some of the basics.

OKAY SO WEBSITES ARE MORE THAN HTML, RIGHT?

OMG you’re learning so fast! Yes, they are more than that. Instead of writing our websites in SQL queries, most of us write them in what’s called a server-side scripting language. These are languages that talk to the server, hit the database and spit out data onto websites. Some examples include Python (some don’t agree), Perl, Ruby and PHP. Python is what powers Django, Ruby powers Ruby on Rails and PHP can be used on its own (and it also powers Wordpress). Other folks may use Java, which a lot of the internet is built on.

Also, don’t learn Perl. Just trust me. (This is where I point out that many web developers have silly biases against programming languages that are usually pointless and silly. But really, Perl isn’t used that much in making websites, unless you’re planning on working in Moveable Type, aka the Huffington Post’s website.)

Before diving into a framework, I would highly suggest learning the basics of PHP and how it interacts with MySQL, which is database software, among the most common on the internet. A good book is Head First PHP and MySQL. It teaches you the basics and it doesn’t get too boring. You can also find some good tutorials online.

Once you get the basics of PHP down, I suggest learning how to install WordPress and setting up your own blog on your own server. Which we shall now sort of discuss.

(Editor’s Note: In the four or so years since I wrote this, I really wouldn’t suggest learning Wordpress or PHP as your first programming language. I know, I know, a lot of Wordpress devs are going to be like “HOW DARE YOU,” but I think you should start with anything else.

Python, Ruby and JavaScript [which is a frontend language, but has been co-opted into a server-side language for things, such as node.js] are great starters instead. You can’t pay me enough money to program ever again in PHP.)

HOW DO YOU MAKE A WEBSITE DO SHIT?

I’ve always maintained that the hardest part about making a website is setting it to run on a server. So if you make cats_rule.php that lists your favorite cats, you want it to live somewhere that people can see. Just so you’re aware, if you’re lucky enough to work at a place that has server operations people — server ops, ops, whatever they get called — you may not have to deal with this stuff as much. But it certainly doesn’t hurt to learn it.

So, a server runs on an operating system, just like your computer. One that I prefer is Ubuntu 10.04 LTS, which is one of many variations of Linux, an open source operating system that people work on out of the goodness of their hearts. Or you could use Windows Server, which was made by people who want you to have to pay lots of money to use it. Not that making money is bad or anything, but I tend to go with free stuff made by people who want to help the world.

(Editor’s Note: Holy shit, I talk about using Windows Server. Don’t use Windows Server. Man, my life in 2011 was a different place. Also, Ubuntu is on a way higher level than 10.04. Again, this is four years old. But use something Linux-based for your server operating system. If you’re having to ever worry about this side of internet making, odds are you’ll have done some reading and know more about it than this blog post.)

The server, which has that operating system I mentioned, has to actually live somewhere. For many, many years, the only way you could really run a server was to either build your own box or rent space somewhere. Or have awesome ops people who set up stuff in a server room.

You may have heard of this “cloud” thing. (Editor’s Note: the cloud, lol) Basically, big companies like Amazon have so much server space that they had a bunch left over that they can turn into virtual machines. Instead of making an individual physical server, they just partition their hardware to make multiple versions.

This means you can set up stuff really easy. This also means you can store media really cheap, too. I would suggest using either Amazon Web Services or Heroku. They are both relatively cheap, with their cheapest server space costing about $10ish a month. Rackspace may be a bit easier because you don’t have to deal with ssh keys, so perhaps start out with that.

You can also use webfaction, which is about $10 a month. What’s awesome is they do a lot of the server setup for you. And you won’t really have to do much server setup, which I explain in a few grafs. So, webfaction is an option, so are many others.

(Editor’s Note: lol I use my affiliate link to webfaction up there so if you sign up I would get some money. Many people signed up via this old blogpost.)

My Django tutorials walk through some of the software you need to install if you’re making a Django-y project, but you basically need server software for your server, despite what you’re coding is. Apache is the standard one many people use. It’s open source and nice. I’m a bit fancier, so I use nginx. Whatever you prefer, it’s just another tool to get the job done. Apache works alright with PHP/MySQL.

(Editor’s Note: Those Django tutorials are so out of date, do not use them, they sadden me.)

BUT HOW DO I CONNECT TO MY SERVER?

This is where you learn about FTP, SFTP and SSHing into your server. FTP and SFTP are two ways of uploading/deleting/changing files on your live server. SFTP is much more secure than FTP, and other news developers will make fun of you if you use FTP. It’s not necessarily wrong, it’s just not as safe. And if you’re learning, no reasons to not use FTP for now.

But before that, you need to know how to ssh into your server. This involves using the terminal, which is scary for some folks. It’s all text, with no shiny buttons to click. Yet this is the most powerful part of your computer. If you’re using Windows, download PuTTY and scroll down in this link. If you’re using Apple products, then search for Terminal and open it then follow the instructions sort of here. If you’re using Ubuntu, why are you reading this?

Before you can FTP, you need to set up software on the server to let you FTP in. Here’s a quick walk-through of installing vsftpd, which is FTP software. Boom. Now you can FTP into shit. You’re welcome.

SO WHAT ABOUT THESE FRAMEWORKS?

Frameworks are sweet. They make it easier to quickly develop the web. I use Django, like I previously said. If you want to get the intense walk-through of setting up Django — INCLUDING LEARNING ABOUT SERVERS! — you can go through my almost-finished tutorial starting here. You can also go through the creator of Djangos’ own tutorials here.

(Editor’s Note: also I wrote some new Django tutorials that had some more updated methodologies, but they’re still 2.5 goddamn years old and sorta out of date.)

If you want to learn more about Ruby (but not making websites), the wonderful Dan Nguyen has some great walk-throughs here. This could be a good Rails walk-through. Who knows.

So that’s some basic info on frameworks. If you want more, use The Googles.

BUYING DOMAINS AND STUFF

If you’re going to set up a website, you need to learn how to buy a domain. My pal Emily Ingram walks you through how to use GoDaddy.com to buy them at this page. That’s what I use, but I would definitely suggest you do NOT use them for hosting. Do not do not do not. You can use other service providers to buy .coms, but hey, it’s quick and easy. (Edit: You should use Namecheap.com instead of the previously mentioned godaddy. Just do it.)

(Editor’s Note: lol at me editing this year ago, telling you to not use GoDaddy. I rule.)

Just remember to set your .com’s DNS settings to point toward your server, which is stuff you get to learn on your own, because I am getting tired from explaining the entire internet to you, my dearest friend.

MORE FRONT-END STUFF OTHER THAN CSS/HTML

Now, you may have learned that HTML/CSS stuff. But guess what? There’s more! Javascript is next.

Just so you’re aware, lots of places are looking for people to be kick-ass at Javascript and CSS/HTML. They call this front-end development, because it mostly deals with stuff that happens on the client side, aka in your browser. My main focus, and all that stuff about PHP and Django and servers and whatnot, is backend development.

Javascript, and its widely used library jQuery, are what lots of the cool internets are built out of. When you click on something on a webpage, and it moves, or changes color, or slides around, usually that’s Javascript/jQuery. These are things totally worth learning. Basic Javascript tutorials can be found here. Here’s the page for jQuery, which also includes tutorials. Here’s even more in-depth stuff for jQuery. A good Javascript book I’ve been going through is Head First Javascript.

JavaScript allows you to reload stuff on the page by hitting the server without having to actually load a new page. Think about how when you’re on Facebook and it pops up, saying your Aunt Glady Crapplebottom just liked that photo of those new shoes you bought. Learn about some of it here.

These are skills I need to get better at, as they allow you to make awesome web graphics. People who are good at this stuff make me envious, because it’s like they can somehow do magic. Wouldn’t you like to know magic? Yes you would. So figure it out, folks.

(Editor’s Note: I have since learned more about this magic. I build most projects these days as just backend RESTful APIs using Django, and then hit them on the frontend using some sort of JavaScript framework. And so should you, probably.)

SO NOW YOU OBVIOUSLY KNOW EVERYTHING

Okay. This was nowhere near an exhaustive list. I apologize. I didn’t realize what a monumental task this would be. I know I’ve forgotten stuff, so hopefully nice/mean people will write in the comments about other sites, and I’ll update this post with their wonderful suggestions.

If you’re going into this, it’s also good to keep up to speed on the goings-on in the tech world. You can do that by checking Hacker News every once in awhile. It’s a pretty good site. Another good place to look for answers to questions is Stack Overflow.

Get an account at github and start looking at other people’s code. That’ll be the best way to learn, honestly. And odds are if you’re going to make a project, someone else has already made something similar and they’ve put up free code for you to use. So search for it, figure out how someone else made the similar project and incorporate it into your own.

(Editor’s Note: This next paragraph is mostly for journalists.)

Join the NICAR listserv. This is the National Institute for Computer-Assisted Reporting. Lots of news developers lurk on the NICAR-L, as we call it. And you get to join the Investigative Reporters and Editors, or IRE, which is also a great organization that you should already be a member of. Why aren’t you? JOIN TODAY.

Also, the most important thing you need to learn is that someone has probably had the same error or problem you’re having while building something. So either you can read the official docs, or just Google the error. Sometimes people post similar questions/answers on various message boards or Stack Overflow. If all else fails, tweet about it. Or email the people who’ve written the open source software.

Most of us learned what we learned through the helpfulness of others, so we’re glad to help others learn more.

HOLY CRAP YOU MADE IT THIS FAR? NOW WHAT?

First off, crack open a beer, because you’re probably thinking OMGWTFLOL THAT IS SO MUCH CRAP. Well, yeah. Making the internet is kind of hard. Hell, it is hard. But it’s a little less emotionally draining than most traditional journalism jobs. And the first time you get something to work, I guarantee you will throw your arms up and shout, “YES!”

Every time I make something work, I feel as though I have reinvented fire. It’s a great feeling, and it’s especially great when you can show someone else the tools of the trade. So if you decide to go down this path, please be vocal about what you’re working on. Write about it. Explain how you did stuff. Be social.

So here’s what you do. Come up with a project. It can be as simple as making a website that tracks the movies or books you own. (FYI, I already made that. See here.) You can even go more advanced, perhaps making something that scrapes all the legislative votes in your state. Hell, go even super easy: Just learn how to use Google Fusion Tables to make something like this.

(Editor’s Note: Does Google Fusion Tables even still exist? Is that a thing?)

The point is, go out and make something. Then let us know how you do it. If you get stuck, ask us for help. We’d be glad to see you kick some ass.


Update, Dec. 27th, 2015

So I wrote all of that a long time ago, back when I barely knew anything. Or, more accurately, when I thought I knew everything (I did not). But what helped me, I think, is writing about my experiences in learning how to become a web developer.

I set up a blog to write about my failures, commiserate with others, show my work, explain to others how I learned shit, and hopefully helped folks so they wouldn’t have to tread down the same failed paths as me.

If you want to become a web developer, you should start adopting this practice, too. Make your own little world on the internet, such as yourname.rules, or perhaps yourname.awesome. Whatever exists.

All that matters, overall, is you try and execute an idea. Everyone has cool ideas. Everyone always is spouting out the “next new great app.” I have been contacted probably 50 times by friends who told me about their great app idea, which would revolutionize the world, or at least be super awesome.

The number of people who have executed those ideas still remains at zero. Because ideas are endless. But creating an idea and making it real? That’s the hardest shit ever.

Yet when you become a web developer, that’s what you need to do. You come up with an idea and make it real. Or you have a hypothesis why something doesn’t work so you can fix it. And then the whole internet updates or changes and you’ve got to fix a bunch of shit.

Never be scared that this shit is impossible. Because it isn’t. Others have done it before you, which means you can do it, too. When in doubt, Google a question. People have usually asked the same question as you before, and you’ll find an answer.

Long story short, here’s the main advice I give anyone who wants to learn how to make the internet: Write down an idea you want to make real. And then try and make it. That’s how you learn, by doing, by fucking up, by executing and making shit real.

Yell at me on Twitter if you have any questions. Good luck.