Reading List Update 9/8/2010

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 loaves.
With a chance to get involved with a local restaurant group (not behind the counter though), the food books are still winning out in my what to read next decisions.

My Reading List on 8/31/2010

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 Programming Language — I'd like to see how well D stacks up to C and C++ (though I've got pretty minimal chops with either).
  • Distributed Programming with Ruby — another Ruby Book?  I've always got room for one of those.
• Three More I'm Working On.
  • The Little MLer — I'm tired of waiting for a good OCaml book, and this looks like the best option for getting up to speed in the ML world.
  • Charcuterie: The Craft of Salting, Smoking, and Curing — yeah, besides languages and communities, I like to hack food.  I've had a couple of goes (each) at jerky, bacon, and sausage.  Now, it's time to take a step up to the big leagues.
  • 52 Loaves: One Man's Relentless Pursuit of Truth, Meaning, and a Perfect Crust — Another fun food book.

What are you reading? Why?

Ruby|Web Interview with Pat Maddox

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, so the spin is probably still there.
Regardless of our mind-set, this looks like it's going to be an awesome conference.  The only problem is that you need to register before Sep 3rd.  You don't have much time ... maybe you should go register first, then come back and read what Pat has to say.

---

Ruby|Web is a new name in the regional Ruby conference space.  What drew you to it?
Pat I love coding in Ruby, and I think the web is a great platform to develop for.  I'm eager to spend a few days rubbing elbows with like-minded people.  And between the over all theme, the fantastic organizers running the show, and Snowbird (!!), Ruby|Web jumped to the top of my list.  Plus I don't know anything about HTML 5 or CSS 3 and I need to get on that :)
Seaside is interesting technology, how did you discover it?
Pat Seaside is a fascinating and fun technology!!  I came across it a few years ago, not long after I got into Rails.  Over the years I had a couple of false starts with it...it's a bit opaque at first because the development environment is so different from anything I'm used to.  And it's only fairly recently with Pharo that it's become easier to get started, because it's such a clean environment geared towards development.  Also the documentation for both Pharo and Seaside are getting really good.  There are free books on each at pharobyexample.org and book.seaside.st/book.
Okay as for what's so interesting to me about Seaside... it's 50% the framework and 50% the Pharo environment. Seaside itself represents a step forward in web development similar to how Rails did.  Rails takes care of a lot of the plumbing for you - you don't have to parse query params, set up response headers, manage the session (unless you want to of course).  Seaside does all that of course but also manages application state for you.  So you don't have to worry about putting stuff into a database, then pulling it back out and operating on it.  I can't do it justice in a few sentences, but that's why I'll be showing lots of examples at the conference! :)  At any rate, that same feeling you get when you code Rails for the first time and see how much easier things are, you get that same feeling with Seaside.  It's not a replacement for Rails by any means - Rails definitely has a sweet spot, particularly when it comes to RESTful websites and interoperability with the unix ecosystem - but for the things that Seaside is strong at (which for me so far has been complex and/or configurable workflows), it runs circles around everything else.
The other thing I'm loving about Seaside development is Pharo, an open-source smalltalk environment.  Smalltalk is a great language, and Pharo has great tools that allow you to discover everything in the system.  Honestly it makes RubyMine or etags look plain silly.  The best bit is that nearly everything in Pharo is implemented in smalltalk, including all of the tools.  So if you want to see the mechanics of a refactoring tool, and even build your own, it's trivial to do so, because it's just smalltalk code.
Wow this answer got long.  I could go on all day about this stuff.  Gonna stop now.
What other smalltalk tools/ideas do you think Rubyists should be looking at?
Pat Let's see...I'd love to see Rubyists take the ideas from the Pharo IDE and build some really snazzy development environment for Ruby.  The next killer Ruby app, I think, is going to be a development environment that uses the runtime structure of objects to do all of its magic, rather than just statically analyzing source code.  Even just having portable refactoring tools would be awesome.
I'm also really excited about Maglev, whenever that becomes available for daily use.  It is incredibly liberating to write actual OO code, and so I think my style of coding Rails will change completely once Maglev enters the field.  fingers crossed
Which Ruby|Web presentations are you most looking forward to?

Pat In order of them being listed on the sessions page...

• BJ Clark's (@robotdeathsquad) talk on HTML / CSS / Javascript.  He told me a few months back when he planned this talk that he thought, "if I were to school Pat on HTML / CSS / Javascript, what would I say?"  He and I have worked together for years and he gets frustrated with my lack of understanding of those things.  So basically this talk is geared specifically to people like me, hardcore backend developers with "div-itis" and who typically use inline javascript and CSS.  I'm looking forward to getting schooled.
• Alistair Cockburn's (@TotherAlistair) samurai talk.  His talk summary means absolutely nothing to me (on purpose, I'm sure) but he's always a trip to watch speak, and I'm glad to see him get more exposure in the Ruby community.
• Evan Light's (@elight) iOS talk - Evan is a diverse developer and entrepreneur.  Really excited to learn from his experiences.
• Joe O'Brien's (@objo) communication talk.  For starters, Joe is one of my favorite people in the Ruby community.  Again, he's one of those folks that combines technical expertise with good business sense and a warm heart.  I think folks attending this conference are going to have more of the entrepreneurial spirit than most, so his talk will be particularly important and insightful for us.
• Dirt Simple Datamining by Matthew Thorley (@padwasabimasala) - because really, who doesn't love datamining??

It's clearly shaping up to be a rocking conference!!!

GoGaRuCo 2010: mini-interview with Ilya Grigorik

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 Machine Learning (ML) can or should be linked any specific language or runtime - it is much more general then that. Wikipedia provides a good starting point: "Machine learning is a scientific discipline that is concerned with the design and development of algorithms that allow computers to evolve behaviors based on empirical data". Artificial Intelligence is a close cousin to this definition, and you will find a lot of people using these two terms interchangeably, but I prefer the ML definition because, to me, defining and modelling the learning process is where the work happens, whereas "intelligence" is the ultimate outcome (plus, defining intelligence is a much harder concept to agree on).
With that in mind, I think you could make the argument that Rubyists apply ML to many everyday situations already: sorting algorithms, recommendations, and so on. It is also a truism that by the time any "AI" hits the mainstream, it is usually no longer interpreted as "AI". For example, computers answering telephone calls was the domain of pure science fiction only a few decades ago, whereas now we don't even stop to think about it. How about your ITunes "genius" playlist? Pandora, Last.fm? You see where I'm going. It's all around us.
Why is Ruby a good fit for machine learning applications?
Ilya Because Ruby commands such a presence in the web development world, I think it naturally finds itself in domains and applications that stand to gain a lot by leveraging the available data in some interesting and novel way. But once again, it's not really a question of language, as much as it is a question of modelling what you know, and applying that data to interesting questions. If Ruby, as a language, allows you to model your data in a faster or easier way, then so much the better.
On a purely practical, implementation side, Ruby has a number of great libraries and plugins that allow you to leverage many interesting algorithms: support vector machines, decision trees, bayes filters, neural nets, and so on. Will those tools scale to million row matrices? Perhaps not, but they will allow you to iterate through a number of solutions at a minimal cost, which in itself is a big win.
Where doesn't ruby fit well in the domain?
Ilya It is unlikely that you will be analyzing a multi-terabyte dataset with a Ruby ML algorithm. More likely, you'll work on a scale of a gigabyte (or a few), model and iterate your algorithm on a subset of data with Ruby, and then implement a lower level solution to scale up to larger datasets.
You're pretty well know for deep diving blogs about Ruby.  What's your day to day relationship with the language?
Ilya My day to day job is with PostRank, where being CTO/founder means I'm wearing many different hats throughout the day. Having said that, most of our systems are written in Ruby, and we have definitely pushed the limits of the language on many fronts.
My blog, is in many ways, a reflection of the technical challenges we're currently dealing with at PostRank, or technologies we're evaluating to improve our infrastructure. So, while I may not be working on implementing the next feature which is going into our analytics product, I am likely to be involved in the design and deployment of the infrastructure that has to deal with servicing all of the data requests required to make that feature possible (and when you're pushing as much data around as we do at PostRank, that's always a non-trivial challenge). The combination of having an awesome team, and a large and exciting problem to work on means there is never a shortlist of what to write about out on my blog!
Ilya
Other than your own talk, what are you most looking forward to at GoGaRuCo this year?
Ilya To be honest, every single talk on the agenda sounds fascinating to me - it's hard to pick any favorites. Having said that, I have been recently thinking and talking to a few people about the topic of "test driven learning", so I'm really looking forward to the "Test First Teaching" presentation by Sarah Allen and Alex Chaffee. I am really curious how this concept could be applied more broadly, outside of just learning a programming language. For example, could you structure a physics course in the same manner? Arguably some (great) teachers do this already, but I would love to extract and distill some general rules and patterns.

GoGaRuCo 2010: mini-interview with Josh Susser

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 around with GoGaRuCo.  What was your biggest lesson from 2009, and how did it impact this year's version?
JoshBiggest lesson?  Make sure you have comfortable chairs!  Well, chairs are important, but I think most about the technical program and how to put together the best one I can.  Last year we did a mix of invited talks and talks selected from submitted proposals.  And consistently, attendees rated the invited talks higher than ones selected from proposals.  Now, I can't say what that means overall and it's certainly not a reason for conferences to stop doing CFPs, but this year I wanted to try doing a curated program where all talks were invited.  That let us craft a program that has balance, diversity and high quality.  It can be more work than doing a CFP because you end up with some speakers who take a little more cat-herding than those that are self-motivated to submit a proposal, but it's worth it.  I know we might miss out on a great proposal from someone we wouldn't think to invite, but it also lets us have speakers who wouldn't think to submit a proposal, so I think it works out in the end.
Why the change from a Spring time slot to one in September?
JoshPlanning a conference takes a long time.  For GoGaRuCo we have to get started about six months in advance, and ramping up for an April conference meant we had to start around December, which is nearly impossible given that so many people are off on vacation or focused on wrapping up the old year or starting the new.  It made things terribly difficult to get off to a good start.  The hardest part of doing GoGaRuCo has been finding a venue that was large, affordable and good enough.  We just couldn't find a venue for April, so we moved later in the year to have more time.  It's also nice that September is the best weather of the year in San Francisco, so it will make the trip that much better for people visiting us.
The Wrap was a unique feature from GoGaRuCo last year.  How much impact has it had on the conference?  Will it be back this year?
JoshThe Wrap will definitely return this year.  The initial idea for The Golden Gate Ruby Wrap was to avoid having to print color program schedules.  We've seen them at a lot of confs, and they don't seem that useful and probably only exist as a place to print sponsor ads.  The Wrap saves on paper and cost, and gives us a more long-lived place for sponsor ads.  It also serves as a rich record of the conference, something like the proceedings published by traditional, academic conferences.  I don't know how much impact it's had, but the 2009 Wrap was downloaded by thousands of people, more even than looked at the videos of the talks.  I think that makes the historical impact of the conf greater, since there is an actual record of it.
If there's one reason people should come to GoGaRuCo this year, what is it?
JoshThis is San Francisco!  It's the highest concentration of hardcore Rubyists I know of.  Last year 96% of the conference attendees used Ruby as the primary language in their regular job.  That means being at the conf you are surrounded by people who love Ruby and know how to get things done with it.  And we have comfortable chairs.

Lone Star Ruby Conf Speaker Interview: Jesse Wolgamott

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 transaction system where the database is the scalability cause of your scalability problems, there's no going back. You've taken the red pill. Table-based transaction databases are constrained by memory and there's a hard maximum until your app crawls to a halt. The dream of true replication and easy sharding is built in.

Also: migrations just suck, even in Rails.

There are a lot of NoSQL players, what made you zero in on these four?

Jesse CouchDB was my first experience with NoSQL -- the built-in map-reduce is so unique. MongoDB is a newer kid on the block, and is easier to get running in Rails, so that's a plus. I like to mention Amazon's SDB because it's frequently overlooked; You use Amazon's servers so in that respect it's the easiest to setup. RavenDB is new and shiny. Cassandra is also really cool, but not as ruby/rails friendly.

What's your current involvement in the NoSQL world?

Jesse I've used CouchDB, MongoDB, and SDB in the real world, but I'm just a lowly programmer.

What made you want to present at LSRC this year?

Jesse I got jealous looking at all the ruby conferences across the country, and heard about LSRC through the local Houston ruby group. Austin rules, Ruby rules, so win win win.

Other than your own talk, what are you most looking forward to at LSRC 2010?

Jesse The "Vim for the modern Rubyist" talk -- Vim is so hot right now! (but really, it should be cool and I love the AntiIDE thinking).

Lone Star Ruby Conf Speaker Interview: Nephi Johnson

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 unexpected inputs in order to find flaws in the code.  During development, it's pretty much impossible to write code that will handle all possible inputs correctly.  Fuzzing helps to uncover some of the more subtle and unforeseeable flaws that haven't been found through code reviews and normal testing.  Fuzzing is typically very automated and usually involves feeding a program thousands or millions of sets of malformed input.  The program being fuzzed is then monitored for crashes, exceptions, and/or performance.

The last person to really talk about fuzzing in the Ruby Space was Zed Shaw.  That's kind of a tough act to follow.  Why is this an important topic for Rubyists, and why are you the right person to talk about it?

Nephi I think fuzzing is an important topic for every developer (or anyone who wants to find bugs in an application).  If you have the time to fuzz a product, you will almost certainly uncover flaws in it.  One bug fixed during development is one less bug that customers have to experience with a release product.  Not finding flaws in the code after extensive fuzzing is also a big confidence booster.  I think this is especially applicable to Rubyists because of the flexibility (and fun) that comes with using Ruby.  I think anyone could make their own fuzzer/data-generator with Ruby in a short amount of time.  Also, if someone wanted to use the library I've written, it just so happens that I've written it in Ruby [*sarcasm*].

Why am I the right person to talk about fuzzing?  Fuzzing is something that I spend most of my free time doing or working on.  I put a lot of thought into coming up with ways to more efficiently fuzz programs.  As a security researcher, I have different goals in fuzzing than developers.  I want to find the really interesting bugs, bugs that might allow one to run their own code or do something entirely unexpected with the program.  I think my perspective on fuzzing might provide different insights for those who use fuzzing outside of the security field.

What prompted you to speak at LSRC this year?

Nephi Someone had mentioned to me that it might be interesting to hear from somebody in the security field and suggested I submit a talk.  I liked the idea, chose to talk about a project I've been working on using Ruby, and here I am.

Other than your own talk, what are you most looking forward to?

Nephi I'm looking most forward to the talks "Vim for the modern Rubyist", "What every Ruby programmer should know about threads", and "Getting Started With C++ Extensions."  Why these talks?  I love using vim - it was the first text editor I used when I started using Linux and now it's all I use, threads give me trouble sometimes (ruby threads, that is), and I've been wanting to write my own ruby extensions for a while now.

LSRC Speaker Interview with David Copeland

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 to see "Why And How You Should Make Awesome Command Line Apps with Ruby" as a presentation.  Why do you think Ruby works well in this space?

Dave Having used PERL and bash in the past, Ruby is just a FAR more pleasant environment; it's just really easy to make a well-designed system, the code is clearer and easier to write, and there's a lot of great libraries that are easy to install and set up.   My talk doesn't go TOO heavily into this, but I think everything that makes Ruby great for web apps makes it great for command line apps.

As a Sys Admin, CLI stuff is my bread and butter.  Do you see Ruby as a good language for Sys Admins?  Why or why not?

Dave Nothing's going to be "as close to the system" as shell scripts, but Ruby has some great libraries that let you write cross-platform scripts, and that's a good thing.  Ruby also has a culture of terse-but-readable syntax, code-as-configuration and overall UNIXness that I think a sysadmin would find familiar and comforting.  Ruby really embodies the "motivated laziness" that is the hallmark of a good sysadmin (by which I mean automating painful tasks away into something simpler).  Further, there's some great management tools built with Ruby, like chef and capistrano.

What prompted you to present at the Lone Star Ruby Conference this year?

Dave I've spoken at a few conferences and user groups and really liked it, and I liked the idea of a Ruby-focused conference; Java-based conferences always feel a bit behind the bleeding edge to me, and the Ruby world is always pushing the boundaries.  I also thought my talk would be interesting to share, specifically for the reasons you note above; Ruby and Rails go hand in hand, but Ruby is an awesome language all on its own.  Plus, the last time I was in Austin, I was there for one night on a cross-country drive, so I didn't get to see much :)

Besides your own talk, what are you most looking forward to while you're there?

Dave There's a ton of really interesting looking talks scheduled; The ActiveModel/Active Relation talk looks good, as well as the NoSQL stuff and deployment talks.  And, I'm sure Tom Preston-Warner from github will give a good talk!

Ruby|Web Interview

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 regional Ruby conferences that are happening in the west this fall. GoGaRuCo, SunnyConf, mountain.rb are all very close both in distance and time. And then there is Lone Star, Ruby Hoedown, WindyCityRails, Ruby DCamp, and eRubyCon/JRubyConf all this fall as well. All of these are great events and deserve to be attended. So if you are near one of them you owe it to yourself to attend! I guess a broader question might be with so many regional conferences, why another? This is something I've struggling with, because I didn't want to take away from any of the other awesome conferences. But the thing I've realized after doing MountainWest RubyConf/MWRC for the last four years is that the Ruby community is much larger than we think, and there are many, many local folks who just won't ever make it to another conference. And many in the local community has been asking for both a second local conference and more Rails/web content for years now. So I guess a short answer is that there is demand for it. That said, I've really been humbled by some of the interest we've gotten from Rubyists outside of our local area. I really think this is going to be an awesome event and will inspire everyone who attends to become better at what they do.

MWRC has a reputation for being tech heavy, geek friendly, and a great value; but you're changing the location, the timeframe, and the general 'theme' for Ruby|Web. Why play with a good thing? What makes you think you're going to make people happy with a different conference? 

Mike  Every year we've experimented with small tweaks to the format of MWRC, but it has largely remained the same. I love MWRC and I think it does many things really well. I love that it is downtown SLC and you get to walk around and explore the city. We hold it in the SLC Library's auditorium and its a beautiful venue with comfy seats and a nice big screen. And Engine Yard's annual Hackfest has been a great time to learn and hack with some of the brightest Rubyists around. The only real complaints we get each year is the short breaks and lack of space to lounge around and talk to each other. There are lots of couches and tables, but you have to go upstairs to get to them, so its proven to be inconvenient. And I have a hard time saying no to the many wonderful proposals we get each year, so we tend to pack the schedule pretty tight with little break time. I personally prefer to have so much great content that my brain feels tired after the conference, but some want more time and space for interacting with the other attendees. So for Ruby|Web I figured we had an opportunity to try something new and see if we can improve the experience with some more radical changes. The first thing is the venue; Snowbird provides a location where we don't have to walk four blocks to find some food or a comfy couch to hack on. The entire resort is awesome and we get to keep the exploring aspect while acquiring some conveniences like having a lot of room for lounging. Secondly we're planning a relaxed schedule that will allow attendees more time to talk with each other or pair on some code or even ride the tram up the mountain. Basically we want to make it easier to be with each other and learn and hack, since that is kinda the point, right?

What is the biggest impetus behind Ruby|Web? Why should people plan on coming? 

Mike I, like a lot of Rubyists, do web programming for a living. I was a web guy long before I found Ruby or Rails. I think the Ruby community has done a really good job of showing that Ruby is so much more than Rails, and I am fully on board with that. But with this event I wanted to give us permission to focus on the web stack as much as we wanted. So I guess you could think of this as a regional RailsConf, without the risk of getting a cease and desist letter from O'Reilly's lawyers for naming it that. :) But this will be more than just Rails; there is Rack and Sinatra and Sammy and Scripty2 and HTML5 and CSS3 and OAuth2 and so much more. I want to be a better web developer, and I want this Ruby|Web to help me do that.