{ "attachments": [ "363349096cfa.jpg", "4a282a6fa7c7.png" ], "title": "How webdev has been getting better", "author": "lmorchard", "layout": "post", "permalink": "/2012/07/10/webdev-more-better", "dsq_thread_id": [ 1107338707 ], "categories": [ "Uncategorized" ], "tags": [ "devops", "mozilla", "webdev" ], "year": "2012", "month": "07", "day": "10", "isDir": true, "slug": "webdev-more-better", "type": "entry", "date": "2012-07-10T19:00:00.000Z", "postName": "2012-07-10-webdev-more-better", "html": "

So, in the last thing I posted, I wrote about how fixing problems on live web sites feels like fixing space robots. At Mozilla, though, things have been getting steadily better and more interesting:

\n

\n

There’s still the sysadmin-as-remote-pair-of-hands-driven-by-trouble-tickets thing going on, but less so every day. More and more, we’re getting into continuous deployment. Our sysadmins are really smart cookies: They’re steadily replacing themselves with scripts of varying sizes. That way, they can get on to more interesting things. In fact, just recently, they gave us a great Big Red Button that deploys code from a git repository to the live site on demand. And, for some reason, I’m one of the people who got a key to it.

\n

Okay, maybe not that exact button, but ours is very keen. Of course, when it broke once, I felt like the Pakled on the right (and not Geordi):

\n

\n

But, the Big Red Button hasn’t broken very often. So, I’d rather be a Pakled some of the time than pretend to be a rocket scientist all of the time.

\n

Oh yeah, and we’re using GitHub a lot these days. It’s crazypants awesome for collaboration, and it fits right in with our style because we want to do everything in the open anyway. We’ve even somehow lured people who don’t normally code into submitting Pull Requests. And, it’s amazingly powerful to refer to specific lines of code and commits by URL in IRC or email.

\n

I’ve also been getting a lot better at building development environments, using Puppet and Vagrant and Amazon EC2. I haven’t quite gotten to the point where I can borrow IT’s Puppet manifests directly – ie. those scripts with which sysadmins are replacing themselves.

\n

But, we are maintaining the recipes for spinning up dev servers right alongside the code. Our READMEs are shrinking, rather than growing – and yet we’re still adding more services and dependencies. I no longer really fear totally jack-knifing my dev rig, because I can just toss it and conjure up another in the time it takes me to run to lunch.

\n

Let’s see, what else? I’m sure I’ll think of something. Until then, SHIP IT. (The post, I mean.)

\n", "body": "So, in the last thing I posted, I wrote about how fixing problems on live web sites [feels like fixing space robots][1]. At Mozilla, though, things have been getting steadily better and more interesting:\r\n\r\n[][2]\r\n\r\nThere’s still the *sysadmin-as-remote-pair-of-hands-driven-by-trouble-tickets* thing going on, but less so every day. More and more, we’re getting into [continuous deployment][3]. Our sysadmins are really smart cookies: They’re steadily replacing themselves with scripts of varying sizes. That way, they can get on to more interesting things. In fact, just recently, they gave us a great Big Red Button that deploys code from a git repository to the live site on demand. And, for some reason, I’m one of the people who got a key to it.\r\n\r\nOkay, maybe not [*that* exact button][2], but ours is very keen. Of course, when it broke once, I felt like the Pakled on the right (and not Geordi):\r\n\r\n\r\n\r\nBut, the Big Red Button hasn’t broken very often. So, I’d rather be a Pakled some of the time than pretend to be a rocket scientist all of the time.\r\n\r\n[][4] Oh yeah, and [we’re using GitHub a lot these days][5]. It’s crazypants awesome for collaboration, and it fits right in with our style because we want to do everything in the open anyway. We’ve even somehow lured people who don’t normally code into [submitting Pull Requests][6]. And, it’s amazingly powerful to refer to specific lines of code and commits by URL in IRC or email.\r\n\r\n[][7] I’ve also been getting a lot better at building development environments, [using Puppet and Vagrant][8] and Amazon EC2. I haven’t quite gotten to the point where I can borrow IT’s Puppet manifests directly – ie. those scripts with which sysadmins are replacing themselves.\r\n\r\nBut, we are maintaining the recipes for spinning up dev servers right alongside the code. Our READMEs are shrinking, rather than growing – and yet we’re still adding more services and dependencies. I no longer really fear totally jack-knifing my dev rig, because I can just toss it and conjure up another in the time it takes me to run to lunch.\r\n\r\nLet’s see, what else? I’m sure I’ll think of something. Until then, SHIP IT. (The post, I mean.)\r\n\r\n [1]: http://blog.lmorchard.com/2012/07/10/webdev-in-spac\r\n [2]: http://www.amazon.com/gp/product/B004D18MCK/ref=as_li_ss_il?ie=UTF8&camp=1789&creative=390957&creativeASIN=B004D18MCK&linkCode=as2&tag=0xdecafbad01-20\r\n [3]: http://www.slideshare.net/MattBrandt/mozilla-continuous-deploment-on-sumo\r\n [4]: http://octodex.github.com/\r\n [5]: https://github.com/mozilla/\r\n [6]: https://github.com/mozilla/kuma/commit/1a8038215a2c4bb7fba5ff098875d034704d79bd\r\n [7]: http://vagrantup.com/\r\n [8]: http://opensourcebridge.org/wiki/2011/Inviting_Contributors_to_Open_Source_Webdev_through_Virtualization", "parentPath": "./content/posts/archives/2012/2012-07-10-webdev-more-better", "path": "2012/07/10/webdev-more-better", "thumbnail": "/2012/07/10/webdev-more-better/363349096cfa.jpg", "needsBuild": true, "prevPostPath": "2012/07/03/biospheric-xenophobia", "prevPostTitle": "Biospheric Xenophobia", "nextPostPath": "2012/07/10/webdev-in-spac", "nextPostTitle": "How webdev is like space exploration" }