Add some of the more recent posts
This commit is contained in:
R. Tyler Croy
parent
4a606afa42
commit
3aa7b34149
|
|
@ -0,0 +1,40 @@
|
|||
---
|
||||
layout: post
|
||||
title: JUC Tokyo 2012 Slides and Recap
|
||||
tags:
|
||||
- presentation
|
||||
- jenkins
|
||||
- juctokyo
|
||||
---
|
||||
|
||||
|
||||
Just over a week ago I returned from a trip to Tokyo for the [Jenkins User
|
||||
Conference 2012 - Tokyo](http://build-shokunin.org/juc2012/). I attended the
|
||||
summer [Developers Summit](http://codezine.jp/devsumi/) and a Jenkins hackathon
|
||||
while I was in Tokyo, but JUC 2012 was the main event.
|
||||
|
||||
|
||||
I can't say enough good things about the Japanese Jenkins community, they are
|
||||
as friendly (if not more so) as all of the other hackers, users and testers
|
||||
that I've met throughout the years working with the project. My only regret is
|
||||
that I had to take so much of [Kohsuke's](https://github.com/kohsuke) time for
|
||||
translation or assistance due to the language barrier.
|
||||
|
||||
|
||||
The talk that I gave at JUC Tokyo was titled "Rebuilding the airplane at
|
||||
10,000m. Continuous Deployment with Jenkins and Gerrit"
|
||||
|
||||
I've uploaded my materials:
|
||||
|
||||
* [Slides without notes (pdf)](https://github.com/rtyler/juc-tokyo-presentation/raw/master/juc-tokyo.pdf)
|
||||
* [Slides with notes (pdf)](http://strongspace.com/rtyler/public/juc-tokyo-notes.pdf)
|
||||
* [Source "code" for the presentation](https://github.com/rtyler/juc-tokyo-presentation)
|
||||
|
||||
|
||||
Unfortunately I don't yet have the video to post, so for now you'll have to
|
||||
take my word when I say the talk went well.
|
||||
|
||||
|
||||
I look forward to traveling to Tokyo again next year to enjoy the heat, Soba
|
||||
and to try more of whatever delicious food [Sotoru](https://twitter.com/cynipe)
|
||||
and Takashi try to feed me.
|
||||
|
|
@ -0,0 +1,59 @@
|
|||
---
|
||||
layout: post
|
||||
title: I'll be speaking at PuppetConf 2012
|
||||
tags:
|
||||
- presentation
|
||||
- puppet
|
||||
- puppetconf
|
||||
- puppetconf2012
|
||||
---
|
||||
|
||||
Today the organizers of [PuppetConf](http://puppetconf.com) released an
|
||||
["almost complete"
|
||||
list](http://puppetconf.com/uncategorized/an-almost-complete-list-of-puppetconf-speakers-and-topics/)
|
||||
of speakers and talks for this year's PuppetConf in San Francisco, guess who's
|
||||
on it?
|
||||
|
||||
|
||||
Through some twist of fate, both of my proposed talks were accepted. Originally
|
||||
I had submitted two sessions to improve the chances that I would be able to
|
||||
speak on at least one of the many ideas I had swirling around in my head. I
|
||||
didn't quite expect to have both talks accepted, but here we are.
|
||||
|
||||
|
||||
I've included the titles and abstracts for both my talks below, be sure to
|
||||
[register soon](http://puppetconf.com/register/) so you can also take one of
|
||||
Puppet Labs' beta certification exams while you're in town.
|
||||
|
||||
---
|
||||
|
||||
**Red, green, re-provision: Test-driving Operations**
|
||||
|
||||
> The developers you work with have a new service they're building, and it is
|
||||
> your job to add the appropriate Puppet modules to provision it. Where do you
|
||||
> start? A base image, Vagrant and some tinkering? Editing files in "/etc/puppet"
|
||||
> on a staging Puppet host? What is the most maintainable work-flow which won't
|
||||
> saddle you with technical debt in the future?
|
||||
>
|
||||
> In this talk, I will take you from the "outside" inward, writing tests along
|
||||
> the way with Cucumber and RSpec. This approach encourages you to think more
|
||||
> about where the lines are drawn between the various services and resources
|
||||
> you're configuring. While the work-flow is a departure from the "traditional
|
||||
> sysadmin" role, the resulting modules can be more easily re-used and
|
||||
> re-factored.
|
||||
|
||||
**We'll do it live: Operations Anti-Patterns**
|
||||
|
||||
> I have done unspeakable things.
|
||||
>
|
||||
> The best indicator of industry experience in Ops is an engineer with regrets.
|
||||
> An engineer who has designed near-perfect systems but due to outside
|
||||
> constraints has had to cut corners. Let's be honest with ourselves and air some
|
||||
> dirty laundry.
|
||||
>
|
||||
> In this talk, I'll take a jovial romp through some of the most heinous
|
||||
> offenders of what could be considered "Ops Anti-Patterns." I'll share maddening
|
||||
> stories from companies that I have worked at as well as stories from
|
||||
> colleagues, who wish to remain nameless.
|
||||
>
|
||||
> Names may be changed to protect the innocent, or guilty, or whatever.
|
||||
|
|
@ -0,0 +1,54 @@
|
|||
---
|
||||
layout: post
|
||||
title: Pairing with the fourth wall
|
||||
tags:
|
||||
- programming
|
||||
- voyeurism
|
||||
- justintv
|
||||
---
|
||||
|
||||
Some time ago I found myself captivated by watching another developer work. Not
|
||||
anybody that I work with or know in person, but the infamous
|
||||
[Notch](https://twitter.com/notch). Throught some twist of fate I stumbled
|
||||
across a live stream of [his](http://www.twitch.tv/notch/) and spent a
|
||||
non-trivial amount of time watching boxes and code fly by in Eclipse.
|
||||
|
||||
Inspired, I figured I would try out the same set up on my own. The first major
|
||||
hurdle to overcome was actually *streaming* my desktop to
|
||||
[Justin.tv](http://justin.tv/agentdero). After a full evening of searching, and tinkering
|
||||
with `ffmpeg`, I managed to get [this
|
||||
script](https://gist.github.com/3495063#file_screenstream.sh) working well
|
||||
enough to send audio and video across the internets.
|
||||
|
||||
|
||||
With the "infrastructure" figured out, I started hosting a couple of sessions
|
||||
while I worked on projects that I'm passionate about. I found the live coding
|
||||
concept immediately useful when I managed to get live help from an engineer at
|
||||
[Puppet Labs](http://puppetlabs.com) while I dug through the `Puppet::AST`
|
||||
parsing code.
|
||||
|
||||
Taking the experiment further, I even tried helping some folks on IRC with
|
||||
"live support sessions" which were so fruitful that I posted a couple videos
|
||||
([1](https://www.youtube.com/watch?v=ZaF6tMGI0Ps&feature=plcp),
|
||||
[2](https://www.youtube.com/watch?v=S¸OHZ74KI&feature=plcp)) from them. In the
|
||||
office, I can say "hey, come over here and look at this" when others need help,
|
||||
and the live coding stream allowed me to extend that concept to practically
|
||||
anybody I wished to help.
|
||||
|
||||
|
||||
I haven't helped anybody in a few months now, I use my typically viewer-less
|
||||
sessions to help me focus on a single project. Whenever I turn the stream on,
|
||||
I'm pair-programming with a companion who may or may not be there (considering
|
||||
the `#codingwithrtyler` channel on Freenode is generally empty, I'm guessing
|
||||
there's nobody watching), but I focus just as if I had another engineer sitting
|
||||
next to me.
|
||||
|
||||
It's almost like a weird hybrid of pair programming and [rubber duck
|
||||
debugging](https://en.wikipedia.org/wiki/Rubber_duck_debugging) now that I
|
||||
think about it.
|
||||
|
||||
|
||||
The projects I work are not nearly as visually pleasing as Minecraft, and I
|
||||
don't have the geek fame that Notch has but I'm perfectly content to stream [my
|
||||
desktop](http://justin.tv/agentdero) to zero viewers as long as it proves
|
||||
useful for evening and weekend hack-sessions.
|
||||
Loading…
Reference in New Issue