typo

_posts/2012-08-02-pushcode-story.markdown

@@ -5,7 +5,7 @@ title: "A Pushcode Story"
 
 *Fact: Pushcode is the result of a failed job interview.*
 
-I started planning Pushcode after I failed an interview process for a *dream* position with [Mozilla's Web Team](http://blog.mozilla.org/webdev/). I was thrilled to get the interview, and I talked to a couple manager and several members of the team. After many years building web solutions in multiple CMSes (dating back to Dave Winer's [Frontier](http://frontier.userland.com/), but including [Wordpress](http://wordpress.org), [Movable Type](http://www.movabletype.org/), and a few less-well-known systems) my lack of experience in "full-stack" development made for an ill fit. While disappointed, I couldn't really disagree with them. I also decided that Mozilla or no, I needed to branch out, and I was going to get the experience I lacked.
+I started planning Pushcode after I failed an interview process for a *dream* position with [Mozilla's Web Team](http://blog.mozilla.org/webdev/). I was thrilled to get the interview, and I talked to a couple managers and several members of the team. After many years building web solutions in multiple CMSes (dating back to Dave Winer's [Frontier](http://frontier.userland.com/), but including [Wordpress](http://wordpress.org), [Movable Type](http://www.movabletype.org/), and a few less-well-known systems) my lack of experience in "full-stack" development made for an ill fit. While disappointed, I couldn't really disagree with them. I also decided that Mozilla or no, I needed to branch out, and I was going to get the experience I lacked.
 
 This was at the end of 2010, and the continuous deployment / #[devops](https://twitter.com/#!/search/realtime/%23devops) movement was growing out of work that [Flickr](http://flickr.com)'s ops team (and their transplanted engineers at [Etsy](http://etsy.com)) had done, and I was fascinated. I needed a project, and I decided that I was going to try my hand at building a simple deployment tool. I'd build it from the the ground up (sort of, I wanted to use [Django](http://djangoproject.org) rather than a more bare-bones framework) and teach myself about all the bits and bobs I hadn't explored before.