In this three part series, we're exploring what it takes to break into the technical blogging space. In the first part, we looked at initial steps you can take when preparing to write. In the second part, we explored how to to get into a good writing flow during the actual writing itself. In this, the third and final part of this series, we'll talk about one more aspect of how to write a technical blog post: getting as many people to read it as possible.
Everyone knows that the Internet is a series of tubes, but until a few weeks ago, I had never really thought about how the whole journey from computer A to B unfolds, on a low level.
For google.com to travel from a remote server to my laptop, an ungodly amount of technical wizardry unfolds. The beauty of the system is that you as a programmer don’t have to think about any of it, because you sit atop layers of clever abstractions.
You asked, and we answered. We're bringing sexy back to Backbone.js. Sign up today for our Intro to Backbone.js workshop July 25 at Galvanize in Denver. Early bird pricing on registration ends tomorrow! Space is limited.
In a previous post, I explained the fundamentals of database design. This guide will cover the second half of that topic: how to make the database work with Rails. Before reading this you should have a good understanding of what a database is and how to organize one.
Rails is a framework that sits on top of the programming language Ruby. The framework speeds up web development by filling in code that you'd otherwise write from scratch on every new project. A component of this is ActiveRecord, a subset of Rails that acts as the bridge between your database and your Ruby code.
- ← Previous
- Next →