<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;CkQNR3g_fCp7ImA9WhBREkk.&quot;"><id>tag:blogger.com,1999:blog-24599054</id><updated>2013-03-02T09:06:36.644-07:00</updated><category term="Ruby|Web" /><category term="utahvalley.rb" /><category term="learning Ruby" /><category term="ruby books" /><category term="Fellowship" /><category term="Questions Five Ways" /><category term="SICP" /><category term="Tinyrb" /><category term="Luke Kanies" /><category term="erlang" /><category term="Amazon" /><category term="Jan Henry Nystrom" /><category term="cardinal" /><category term="Philippe Hanrigou" /><category term="community" /><category term="RubyNation" /><category term="Concurrency" /><category term="Tech Publishing" /><category term="grumpy old man" /><category term="rwb" /><category term="Ordeal" /><category term="scouts" /><category term="loty" /><category term="JRuby" /><category term="Data Visualization" /><category term="Patrick Farley" /><category term="DSL" /><category term="spam" /><category term="software engineering" /><category term="haskell" /><category term="performance" /><category term="lsrc" /><category term="Ruby.Net" /><category term="Pivotal Labs" /><category term="training" /><category term="Brotherhood" /><category term="Tab Sweep" /><category term="scala" /><category term="blogging contest" /><category term="refactoring" /><category term="RubyQuiz" /><category term="Hal Fulton" /><category term="On Ruby" /><category term="Rails" /><category term="Sequel" /><category term="ruby-prof" /><category term="one-click installer" /><category term="legion" /><category term="Sahpeech Chapter" /><category term="urug" /><category term="NetBeans" /><category term="tumble blog" /><category term="Summer of Code" /><category term="CouchDB" /><category term="Ruby Hoedown" /><category term="regional ruby conferences" /><category term="my best" /><category term="Gedankenexperiment" /><category term="rspec" /><category term="io" /><category term="rubyinline" /><category term="mwrc" /><category term="Brian Palmer" /><category term="Kathy Sierra" /><category term="Practical Ruby Projects" /><category term="Gregory Brown" /><category term="interviews" /><category term="Pat Maddox" /><category term="benchmarking" /><category term="Andrew Shafer" /><category term="No Starch Press" /><category term="testing" /><category term="Puppet" /><category term="Revactor" /><category term="V8" /><category term="James Turnbull" /><category term="RubyCamp" /><category term="RubyConf" /><category term="WebServices" /><category term="Evan" /><category term="design patterns" /><category term="Static Code Analysis" /><category term="debugging" /><category term="Dave Thomas" /><category term="Intellectual Property" /><category term="scala books" /><category term="zenspider" /><category term="Jeremy McAnally" /><category term="Survey" /><category term="Reia" /><category term="Infrastructure Operations" /><category term="gogaruco" /><category term="merb" /><category term="Lisp" /><category term="Factor" /><category term="Interview" /><category term="1.9" /><category term="Assaf Arkin" /><category term="coverity" /><category term="MountainWest RubyConf" /><category term="AutoTest" /><category term="protocol buffer" /><category term="Topher Cyll" /><category term="Wicked Cool Ruby Scripts" /><category term="FamilySearch" /><category term="Brixen" /><category term="Engine Yard" /><category term="Well-Grounded Rubyist" /><category term="Ruby Best Practices" /><category term="manning" /><category term="rubinius" /><category term="beautiful architecture" /><category term="VeloSLC" /><category term="Pat Eyler" /><category term="ruport" /><category term="diamondback ruby" /><category term="Ruby Mendicant" /><category term="ruby brigades" /><category term="Pragmatic Thinking and Learning" /><category term="agile retrospectives" /><category term="Ola Bini" /><category term="theory" /><category term="pinewood derby" /><category term="team building" /><category term="RubyRefactoring Workbook" /><category term="Ruby In Practice" /><category term="jim weirich" /><category term="Ben Mabey" /><category term="Lone Star Ruby Conf" /><category term="REST" /><category term="XRuby" /><category term="politics" /><category term="Actors" /><category term="seattle.rb" /><category term="bailout" /><category term="RubyZone" /><category term="Jobs" /><category term="Francesco Cesarini" /><category term="Ruby Tools" /><category term="flog" /><category term="Mike" /><category term="jvm" /><category term="Sander Land" /><category term="Gems" /><category term="Lego" /><category term="parsetree" /><category term="Conferences" /><category term="Data Processing and Visualization" /><category term="Tony Arcieri" /><category term="eric hodel" /><category term="YARV" /><category term="Ruby" /><category term="fund raising" /><category term="advance directive" /><category term="twitter" /><category term="parrot" /><category term="functional programming" /><category term="Russ Olsen" /><category term="charlie" /><category term="IronRuby" /><category term="ocaml" /><category term="Code Reading" /><category term="Rcov" /><category term="MINSWAN" /><category term="DataMapper" /><category term="Jolt" /><category term="profiling" /><category term="real world haskell" /><category term="reek" /><category term="R" /><category term="Systems Administration" /><category term="Books" /><title>On Ruby</title><subtitle type="html">The (mostly) tech related musings of Pat Eyler.  Ruby, Erlang, Haskell, Scala, Ocaml, Publishing, and more ...</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://on-ruby.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>458</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/on-ruby" /><feedburner:info uri="on-ruby" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;CkEHQnw8cCp7ImA9WhNSGE0.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-6530946735761086939</id><published>2012-11-01T13:10:00.002-07:00</published><updated>2012-11-01T13:10:33.278-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-11-01T13:10:33.278-07:00</app:edited><title>Reviewing Annual Reviews</title><summary type="html">Almost everyone seems to hate end of year performance reviews.  Done correctly though, they could be celebrations of your accomplishments.  What would it take to make them more exciting, more interesting, or at least less painful?

How about this for an annual review?




Maybe we're not going to see videos with voice-over announcers, screaming fans, or a pulsating soundtrack.  Surely we can do &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/CQwek_8v1JY" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/6530946735761086939/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=6530946735761086939" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6530946735761086939?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6530946735761086939?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/CQwek_8v1JY/reviewing-annual-reviews.html" title="Reviewing Annual Reviews" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://img.youtube.com/vi/JZiolTWcjdc/default.jpg" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2012/11/reviewing-annual-reviews.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0UER3g7fSp7ImA9WhVaFEk.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-2776747990718120337</id><published>2012-06-11T12:00:00.000-07:00</published><updated>2012-06-11T12:00:06.605-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-06-11T12:00:06.605-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Books" /><title /><summary type="html"> This is a book that I wish was on my son's required reading list.  Not that his code is hard to read (for someone in their first programming class), but that there are all kinds of bad habits that wouldn't need to be broken if he and his classmates spent some time learning what good code looks like before they started to write their own.



The Art of Readable Code from O'Reilly is a quick, easy&lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/oHzaWsoDf7g" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/2776747990718120337/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=2776747990718120337" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2776747990718120337?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2776747990718120337?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/oHzaWsoDf7g/this-is-book-that-i-wish-was-on-my-sons.html" title="" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2012/06/this-is-book-that-i-wish-was-on-my-sons.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkIMQH87eSp7ImA9WhVaEEU.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-1950528815729441444</id><published>2012-06-07T07:49:00.000-07:00</published><updated>2012-06-07T07:49:41.101-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-06-07T07:49:41.101-07:00</app:edited><title>The Linux Command Line</title><summary type="html">As a long-time, professional Unix/Linux sysadmin, I spend a lot of time on the commandline.  I've grown pretty familiar with it, but I often find that junior teammates don't have the same familiarity.  They often grew up in a world of windows and GUIs. That means I spend a lot of time helping them learn the ropes.  

When I saw that No Starch Press had published The Linux Command Line, I wanted &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/fw-9yL700pY" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/1950528815729441444/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=1950528815729441444" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/1950528815729441444?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/1950528815729441444?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/fw-9yL700pY/linux-command-line.html" title="The Linux Command Line" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-zD0Ku8X4EHs/T9C-tZ7UpnI/AAAAAAAABSY/6Que5Lbyp_k/s72-c/Screenshot.png" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2012/06/linux-command-line.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkMNRHcyeyp7ImA9WhRaFEw.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-6449589574591150820</id><published>2012-02-16T11:54:00.002-07:00</published><updated>2012-02-16T11:54:55.993-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T11:54:55.993-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Interview" /><category scheme="http://www.blogger.com/atom/ns#" term="Books" /><category scheme="http://www.blogger.com/atom/ns#" term="R" /><title>The Art of R: interview and mini-review</title><summary type="html">

The Art of R Programming is an approachable guide to the R programming language.  While tutorial in nature, it should also serve as a reference.
Author Norman Matloff comes from an academic background, and this shows through in the text.  His writing is formal, well organized, and tends toward a pedagogical style.  This is not a breezy, conversational book.
Matloff approaches R from a &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/97MbMkfz02s" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/6449589574591150820/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=6449589574591150820" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6449589574591150820?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6449589574591150820?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/97MbMkfz02s/art-of-r-interview-and-mini-review.html" title="The Art of R: interview and mini-review" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2012/02/art-of-r-interview-and-mini-review.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0ABQHc4eSp7ImA9WhZSFkg.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-895410373444518271</id><published>2011-04-01T05:09:00.000-07:00</published><updated>2011-04-01T05:09:11.931-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-04-01T05:09:11.931-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="interviews" /><category scheme="http://www.blogger.com/atom/ns#" term="Brian Palmer" /><title>Protocol Buffers - Brian Palmer's Take</title><summary type="html">Here's another in my continuing series of Ruby Protocol Buffers posts.  This time, I've got an interview with Brian Palmer.(I interviewed Brian about his participation in a 'Programming Death Match' back in 2006.)
While working at Mozy, Brian worked with Protocol Buffers, and now maintains the ruby-protocol-buffer.  He left Mozy last September, and is now working at a startup called Instructure &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/hF6ME7PMrmI" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/895410373444518271/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=895410373444518271" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/895410373444518271?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/895410373444518271?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/hF6ME7PMrmI/protocol-buffers-brian-palmers-take.html" title="Protocol Buffers - Brian Palmer's Take" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2011/04/protocol-buffers-brian-palmers-take.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkABR3o7eip7ImA9WhZSFUU.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-1496094169179618522</id><published>2011-03-31T08:35:00.005-07:00</published><updated>2011-03-31T09:25:56.402-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-31T09:25:56.402-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Interview" /><category scheme="http://www.blogger.com/atom/ns#" term="protocol buffer" /><title>Protocol Buffers - BJ Neilsen's Take</title><summary type="html">BJ Neilsen (@localshred or at github) is a member of my local Ruby Brigade, and he's hacking with/on Protocol Buffers with Ruby — oh, and he's a fan of Real Salt Lake too.
He works for a Provo, Utah based startup MoneyDesktop. Where he helped them transition away from a less-than-desirable PHP solution to Rails. They now enjoy an entirely new service-architecture driven by Ruby (and Protobuf).  &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/kX-de29dSoo" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/1496094169179618522/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=1496094169179618522" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/1496094169179618522?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/1496094169179618522?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/kX-de29dSoo/protocol-buffers-bj-nielsens-take.html" title="Protocol Buffers - BJ Neilsen's Take" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>3</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2011/03/protocol-buffers-bj-nielsens-take.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkIASHY-fSp7ImA9WhZSEUU.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-2737730984209930253</id><published>2011-03-26T12:06:00.001-07:00</published><updated>2011-03-26T16:02:29.855-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-26T16:02:29.855-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="protocol buffer" /><title>Ruby and Protocol Buffers, Take One and a Half</title><summary type="html">In a comment on my previous post on Protocol Buffers, Clayton O'Neill recommended trying out the java protobuf library with jruby.  I'll get to that eventually, but his comment made me wonder how jruby and rubinius would do with this little test.
I fired up rvm and looped through my installed versions.  Here are the results:
ruby 1.8.7 (2010-08-16 patchlevel 302) [i686-linux]
real 3m11.857s
user &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/K2mulL548XI" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/2737730984209930253/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=2737730984209930253" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2737730984209930253?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2737730984209930253?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/K2mulL548XI/ruby-and-protocol-buffers-take-one-and.html" title="Ruby and Protocol Buffers, Take One and a Half" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>5</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2011/03/ruby-and-protocol-buffers-take-one-and.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkECRH87eSp7ImA9WhZSEEs.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-2233393479774997149</id><published>2011-03-24T14:20:00.001-07:00</published><updated>2011-03-25T08:57:45.101-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-25T08:57:45.101-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="benchmarking" /><category scheme="http://www.blogger.com/atom/ns#" term="protocol buffer" /><title>Ruby and Protocol Buffers, Take One</title><summary type="html">At work, we're moving from XML to protocol buffers.  While we're mostly a Java shop, the operations/sysadmin team I'm on does a lot of Ruby. I was interested in how we might use the same technology for some of our stuff. After a bit of looking, I found two libraries that looked mature enough to investigate:

ruby-protobuf
ruby-protocol-buffers


ruby-protobuf, by MATSUYAMA Kengo (@macks_jp), was &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/gNNUn8VE08k" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/2233393479774997149/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=2233393479774997149" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2233393479774997149?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2233393479774997149?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/gNNUn8VE08k/ruby-and-protocol-buffers-take-one.html" title="Ruby and Protocol Buffers, Take One" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>4</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2011/03/ruby-and-protocol-buffers-take-one.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0UAR34_eSp7ImA9WhZTGEQ.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-2152823711294662081</id><published>2011-03-23T07:40:00.001-07:00</published><updated>2011-03-23T07:40:46.041-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-23T07:40:46.041-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Books" /><category scheme="http://www.blogger.com/atom/ns#" term="Russ Olsen" /><title>Review - Eloquent Ruby</title><summary type="html">The system management/administration team that I work on is starting to do more scripting and tool building.  That means bringing a bunch of people up to speed on Ruby.  We're using a combination of the Pickaxe Book and pair programming/mentoring to help bootstrap people.  So far it's been working pretty well.
Watching everyone else reading and learning made me want to get in on the action.  &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/mGOpLX2P2uU" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/2152823711294662081/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=2152823711294662081" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2152823711294662081?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2152823711294662081?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/mGOpLX2P2uU/review-eloquent-ruby.html" title="Review - Eloquent Ruby" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2011/03/review-eloquent-ruby.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUUNRngyeCp7ImA9Wx5QGUs.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-7811048195547426250</id><published>2010-09-08T09:28:00.000-07:00</published><updated>2010-09-08T09:28:17.690-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-09-08T09:28:17.690-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Books" /><title>Reading List Update 9/8/2010</title><summary type="html">
The recent news that GDB now supports D makes The D Programming Language jump up a notch or two on my reading list.
I've finished 52 Loaves: One Man's Relentless Pursuit of Truth, Meaning, and a Perfect Crust, it was a fun read.  I really identified with his trip to the French monastery. It seemed like a great climax to his year, with the perfect denouement as he came home to bake his final &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/HVekPFw5wlc" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/7811048195547426250/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=7811048195547426250" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/7811048195547426250?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/7811048195547426250?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/HVekPFw5wlc/reading-list-update-982010.html" title="Reading List Update 9/8/2010" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2010/09/reading-list-update-982010.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C08BR34zfip7ImA9Wx5QEko.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-307686712340732262</id><published>2010-08-31T09:24:00.000-07:00</published><updated>2010-08-31T09:24:16.086-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-31T09:24:16.086-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Books" /><title>My Reading List on 8/31/2010</title><summary type="html">
Thanks to Prentice Hall and Addison-Weseley giving me three new books, my reading list has bulked back up.  Here's what I'm working through at the moment:

The Freebies
UNIX and Linux System Administration Handbook (4th Edition) — I'm really excited about this one, I've loved the first three editions, and this looks like a really solid revamping of a classic in the Sys Admin field.
The D &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/RVU6Nva9WJs" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/307686712340732262/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=307686712340732262" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/307686712340732262?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/307686712340732262?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/RVU6Nva9WJs/my-reading-list-on-8312010.html" title="My Reading List on 8/31/2010" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>2</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2010/08/my-reading-list-on-8312010.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUIDQX07cSp7ImA9Wx5RF0s.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-6741446476539187608</id><published>2010-08-25T12:12:00.000-07:00</published><updated>2010-08-25T12:12:50.309-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-25T12:12:50.309-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ruby|Web" /><category scheme="http://www.blogger.com/atom/ns#" term="Interview" /><category scheme="http://www.blogger.com/atom/ns#" term="Pat Maddox" /><title>Ruby|Web Interview with Pat Maddox</title><summary type="html">
Ok, if I'm going to post about GoGaRuCo today, I should also spend some time on Ruby|Web, the latest regional conference from Mike Moore (@blowmage) and friends — truth in advertising, I'm a volunteer on the board for Ruby|Web, so I might be a bit biased.
Just so my biases don't show too much, I asked Pat Maddox(@patmaddox) to answer a few questions for me.  Of course, he's a speaker at Ruby|Web&lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/RLxJi0C8Hw4" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/6741446476539187608/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=6741446476539187608" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6741446476539187608?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6741446476539187608?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/RLxJi0C8Hw4/rubyweb-interview-with-pat-maddox.html" title="Ruby|Web Interview with Pat Maddox" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2010/08/rubyweb-interview-with-pat-maddox.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkUCSX4_fCp7ImA9Wx5RF0g.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-8411993391951473681</id><published>2010-08-25T08:31:00.000-07:00</published><updated>2010-08-25T08:31:08.044-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-25T08:31:08.044-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Interview" /><category scheme="http://www.blogger.com/atom/ns#" term="gogaruco" /><title>GoGaRuCo 2010: mini-interview with Ilya Grigorik</title><summary type="html">Ilya Grigorik (@igrigorik) is another GoGaRuCo speaker who's kindly agreed to sit down and work through a short interview with me.  Hopefully this gives you taste of what you'll be missing if you're not going to the Bay Area's regional Ruby conference.

Machine Learning and Ruby don't leap to mind as a common pairing.  Why is machine learning important to Rubyists?
Ilya I don't think the topic of&lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/lHWPd9a_Xpc" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/8411993391951473681/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=8411993391951473681" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/8411993391951473681?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/8411993391951473681?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/lHWPd9a_Xpc/gogaruco-2010-mini-interview-with-ilya.html" title="GoGaRuCo 2010: mini-interview with Ilya Grigorik" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2010/08/gogaruco-2010-mini-interview-with-ilya.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkMHRn46eyp7ImA9Wx5REk8.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-2424197592092097575</id><published>2010-08-19T07:33:00.002-07:00</published><updated>2010-08-19T07:33:57.013-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-19T07:33:57.013-07:00</app:edited><title>GoGaRuCo 2010: mini-interview with Josh Susser</title><summary type="html">
GoGaRuCo is just around the corner (Sep 17-18), and it looks like it's going to be a great conference again this year.  I wanted to touch base with Josh Susser (@joshsusser) again to see what was going to set this year apart.  He was kind enough to answer a few questions.  If you live in the Bay Area and haven't already decided to hit GoGaRuCo, what are you waiting for?

This is your second time&lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/UbobXij4-YA" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/2424197592092097575/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=2424197592092097575" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2424197592092097575?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2424197592092097575?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/UbobXij4-YA/gogaruco-2010-mini-interview-with-josh.html" title="GoGaRuCo 2010: mini-interview with Josh Susser" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2010/08/gogaruco-2010-mini-interview-with-josh.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEABRHs_eCp7ImA9WxFaE0w.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-8887048253837212640</id><published>2010-07-16T13:39:00.000-07:00</published><updated>2010-07-16T13:39:15.540-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-16T13:39:15.540-07:00</app:edited><title>Lone Star Ruby Conf Speaker Interview:  Jesse Wolgamott</title><summary type="html">
Today's a twofer for the Lone Star Ruby Conference.  My third interview (second today) is with Jesse Wolgamott (@jwo) who's presenting "Battle of NoSQL stars: Amazon's SDB vs Mongoid vs CouchDB vs RavenDB ".  Jesse shares some thoughts about NoSQL and the conference.



NoSQL looks like it's gaining momentum.  Why should Rubyists be interested in the topic?

Jesse Once you reach the point in &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/cXBilKmP1Uo" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/8887048253837212640/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=8887048253837212640" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/8887048253837212640?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/8887048253837212640?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/cXBilKmP1Uo/lone-star-ruby-conf-speaker-interview_16.html" title="Lone Star Ruby Conf Speaker Interview:  Jesse Wolgamott" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2010/07/lone-star-ruby-conf-speaker-interview_16.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUMDQXYyeSp7ImA9WxFaE00.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-138337444420905248</id><published>2010-07-16T11:03:00.001-07:00</published><updated>2010-07-16T11:04:30.891-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-16T11:04:30.891-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Interview" /><category scheme="http://www.blogger.com/atom/ns#" term="Lone Star Ruby Conf" /><category scheme="http://www.blogger.com/atom/ns#" term="regional ruby conferences" /><title>Lone Star Ruby Conf Speaker Interview:  Nephi Johnson</title><summary type="html">
Okay, time for a second interview with a Lone Star Ruby Conference speaker.  This time, Nephi Johnson (@d0c_s4vage) talks a bit about his presentation — "Less-Dumb Fuzzing and Ruby Metaprogramming".



Fuzzing isn't always well understood.  Can you describe fuzzing, and tell us what situations it's a good fit for?

Nephi Fuzzing is a term used to describe the process of feeding an application &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/QTbR4MZDXz8" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/138337444420905248/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=138337444420905248" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/138337444420905248?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/138337444420905248?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/QTbR4MZDXz8/lone-star-ruby-conf-speaker-interview.html" title="Lone Star Ruby Conf Speaker Interview:  Nephi Johnson" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2010/07/lone-star-ruby-conf-speaker-interview.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkAARno_eCp7ImA9WxFaEk8.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-6904854871436584323</id><published>2010-07-15T14:19:00.000-07:00</published><updated>2010-07-15T14:19:07.440-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-15T14:19:07.440-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Interview" /><category scheme="http://www.blogger.com/atom/ns#" term="Lone Star Ruby Conf" /><category scheme="http://www.blogger.com/atom/ns#" term="regional ruby conferences" /><title>LSRC Speaker Interview with David Copeland</title><summary type="html">
With the Lone Star Ruby Conference just over a month away, I thought it would be a good idea to talk to some of the presenters.  David Copeland (@davetron5000) is giving a talk about a topic that resonated with me, so I sent off an email to find out more about what he thought would make his presentation and the conference worthwhile.

I've never been a big 'web app' kind of guy, so I was excited&lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/io_tsKjMzIQ" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/6904854871436584323/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=6904854871436584323" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6904854871436584323?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6904854871436584323?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/io_tsKjMzIQ/lsrc-speaker-interview-with-david.html" title="LSRC Speaker Interview with David Copeland" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2010/07/lsrc-speaker-interview-with-david.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcMSXg6eSp7ImA9WxFaEkw.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-6047353137490137391</id><published>2010-07-15T09:08:00.000-07:00</published><updated>2010-07-15T09:08:08.611-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-15T09:08:08.611-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ruby|Web" /><category scheme="http://www.blogger.com/atom/ns#" term="regional ruby conferences" /><title>Ruby|Web Interview</title><summary type="html">Mike Moore, one of the big movers behind MountainWest RubyConf and the UtahValley.rb is getting the ball moving for another Ruby-centric conference —Ruby|Web. He was kind enough to sit down with me and share his thoughts about Regional Ruby Conferences and how Ruby|Web fits into that space.

SLC already has MWRC, why another Ruby (ok, Ruby+) conference?

Mike Moore  There are so many great &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/yO6RTLVhKAs" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/6047353137490137391/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=6047353137490137391" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6047353137490137391?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6047353137490137391?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/yO6RTLVhKAs/rubyweb-interview.html" title="Ruby|Web Interview" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2010/07/rubyweb-interview.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUUERnw8eyp7ImA9WxNVGE8.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-6233799583187667936</id><published>2009-10-29T07:37:00.001-07:00</published><updated>2009-10-29T07:40:07.273-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-29T07:40:07.273-07:00</app:edited><title>wave and interviews ... Too new or the wrong medium?</title><summary type="html">I'm trying to do an interview for my blog using wave, and so far it's not going very well.When I first thought about it, using wave to interview a small group seemed pretty natural.  The idea of a free flowing discussion with the ability to go back and massage the stream a bit felt more like sitting around a table and talking than sending emails back and forth.I asked the team from The Compleat &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/G3x_eEr2sAQ" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/6233799583187667936/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=6233799583187667936" title="6 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6233799583187667936?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/6233799583187667936?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/G3x_eEr2sAQ/wave-and-interviews-too-new-or-wrong.html" title="wave and interviews ... Too new or the wrong medium?" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>6</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2009/10/wave-and-interviews-too-new-or-wrong.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUUGQX09eSp7ImA9WxNWFEg.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-2980790902458885197</id><published>2009-10-13T11:05:00.003-07:00</published><updated>2009-10-13T11:07:00.361-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-13T11:07:00.361-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="community" /><title>Leveraging the Net</title><summary type="html">Second up in my series of posts about leveraging communities is the topic of the Internet.  I don't want to talk about mailing lists or sites like github yet, I'll cover those when I talk about User Groups and Free Software.  I do want to touch on google, blogs, and aggregators.There's a lot of information out there, but how you use it and how deeply you interact with it determine how much it &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/GZIbWCEelmA" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/2980790902458885197/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=2980790902458885197" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2980790902458885197?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2980790902458885197?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/GZIbWCEelmA/leveraging-net.html" title="Leveraging the Net" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>2</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2009/10/leveraging-net.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUQBQXk_eyp7ImA9WxNWFEk.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-2291736691948076958</id><published>2009-10-13T07:13:00.001-07:00</published><updated>2009-10-13T07:15:50.743-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-13T07:15:50.743-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="community" /><category scheme="http://www.blogger.com/atom/ns#" term="Books" /><title>Leveraging Books</title><summary type="html">As I talk about leveraging community to be more effective at what you do, let's start out with books.  I think this is a good theme to develop because it really shows how the three levels of passive, engaged, and committed involvement provide successively more benefit.  Books are also an easy gateway into improving yourself because people are used to reading as a learning method — we did it in &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/pQcrV4o5QuE" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/2291736691948076958/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=2291736691948076958" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2291736691948076958?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/2291736691948076958?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/pQcrV4o5QuE/leveraging-books.html" title="Leveraging Books" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>4</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2009/10/leveraging-books.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUQGRHk4cCp7ImA9WxNWFEg.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-3550156980925458622</id><published>2009-10-06T06:46:00.003-07:00</published><updated>2009-10-13T11:08:45.738-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-13T11:08:45.738-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="community" /><title>Leveraging the Community to be a Better ...</title><summary type="html">I'm giving a presentation at work about leveraging communitites to become a better developer/tester/sys admin and I thought that I should really drink the kool-aid and make it a better presentation by involving the community.  Over the next week, I'll be making a series of blog posts covering the material from my presentation.  I'd really like to see two outcomes:hopefully people outside my &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/Nf1oiricSk4" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/3550156980925458622/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=3550156980925458622" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/3550156980925458622?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/3550156980925458622?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/Nf1oiricSk4/leveraging-community-to-be-better.html" title="Leveraging the Community to be a Better ..." /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>3</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2009/10/leveraging-community-to-be-better.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0QASH06fCp7ImA9WxJVGUQ.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-4531593037796185263</id><published>2009-07-07T07:30:00.001-07:00</published><updated>2009-07-07T11:29:09.314-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-07T11:29:09.314-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Interview" /><category scheme="http://www.blogger.com/atom/ns#" term="Books" /><title>Finding or Keeping a Tech Job -- An interview with Andy Lester and Chad Fowler</title><summary type="html">Andy Lester (@theworkinggeek) and Chad Fowler (@chadfowler) the authors of Land the Tech Job You Love and The Passionate Programmer, respectively, agreed to do a joint interview with me.  It was a lot of fun to talk with these guys, I hope you enjoy reading this interview as much as I did doing it.Your books look like great companions to each other.  Did you interact at all when writing them?Chad&lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/G02wfc3sv8M" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/4531593037796185263/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=4531593037796185263" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/4531593037796185263?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/4531593037796185263?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/G02wfc3sv8M/finding-or-keeping-tech-job-interview.html" title="Finding or Keeping a Tech Job -- An interview with Andy Lester and Chad Fowler" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>3</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2009/07/finding-or-keeping-tech-job-interview.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEYAR3kzfip7ImA9WxJVE0U.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-3348268220449502312</id><published>2009-06-30T11:21:00.002-07:00</published><updated>2009-06-30T11:22:26.786-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-30T11:22:26.786-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Jeremy McAnally" /><category scheme="http://www.blogger.com/atom/ns#" term="Ruby Hoedown" /><category scheme="http://www.blogger.com/atom/ns#" term="Interview" /><category scheme="http://www.blogger.com/atom/ns#" term="regional ruby conferences" /><title>Ruby Hoedown 2009 mini-Interview with Jeremy McAnally</title><summary type="html">Jeremy McAnally (@jm) is a good friend, and we've worked together on regional Ruby conferences and other projects.  With the Ruby Hoedown looming, I thought it was about time to sit down with him for a mini-interview about his free conference.  How have the community and your sponsors responded to making the Ruby Hoedown free? Jeremy Everyone has largely been in two camps: "Wow that's awesome!" &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/GP6EKDyyffA" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/3348268220449502312/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=3348268220449502312" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/3348268220449502312?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/3348268220449502312?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/GP6EKDyyffA/ruby-hoedown-2009-mini-interview-with.html" title="Ruby Hoedown 2009 mini-Interview with Jeremy McAnally" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2009/06/ruby-hoedown-2009-mini-interview-with.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0UAR3o8fCp7ImA9WxJWGEs.&quot;"><id>tag:blogger.com,1999:blog-24599054.post-4153762788165966179</id><published>2009-06-24T09:34:00.000-07:00</published><updated>2009-06-24T09:34:06.474-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-24T09:34:06.474-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Interview" /><title>A Ruby Couple:  Interview with James and Dana Gray</title><summary type="html">It's another week without a Questions Five Ways discussion, but I've got another great interview that more than makes up for it.  James Gray (@JEG2) is very well known in the Ruby community.  His wife, Dana, is less well known, but won't stay that way for long.  Fresh from her Ruby presenting debut, a lightning talk on Ruby regular expressions at MWRC, the two of them are embarking on a joint &lt;img src="http://feeds.feedburner.com/~r/on-ruby/~4/ZLQNnnpzrdI" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://on-ruby.blogspot.com/feeds/4153762788165966179/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=24599054&amp;postID=4153762788165966179" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/4153762788165966179?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24599054/posts/default/4153762788165966179?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/on-ruby/~3/ZLQNnnpzrdI/ruby-couple-interview-with-james-and.html" title="A Ruby Couple:  Interview with James and Dana Gray" /><author><name>pat eyler</name><uri>https://plus.google.com/112846625814605102746</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-LqwxKEVmxIk/AAAAAAAAAAI/AAAAAAAACdo/_Dy3_-4RgCA/s512-c/photo.jpg" /></author><thr:total>3</thr:total><feedburner:origLink>http://on-ruby.blogspot.com/2009/06/ruby-couple-interview-with-james-and.html</feedburner:origLink></entry></feed>
