Ship It! LIVEShip It! LIVE
home about services writing contact

We develop, test, and create fine software products, and design creative solutions to your problems.
The development of software is an intrinsically creative process. We are dedicated to improving our mastery of the art.
Links · RSS Feed
Popular Pages

...It would be really nice if, as an industry, we could stop being such a bunch of screwed-up clowns and start living up to our potential. Ship It! is one of the things that could help, if only tho...
-Mike Gunderloy
Jared Richardson’s talk titled “Build Teams, not Products,” in particular, was one of the best presentations I’ve ever witnessed. It was just one of those talks where all the points seem tautologic...
-Yev Bronshteyn
I haven't had the chance to read and review any books from the Pragmatic Programmers series. I decided to change that with the book Ship It! - A Practical Guide to Successful Software Projects by ...
-Thomas "Duffbert" Duff

Ruby Hoedown 2007: Sign Up Now! (Aug 1)
If you were considering signing up for the regional Ruby conference in North Carolina, the Ruby Hoedown, you'd better move quick. This is the mail I received this evening.

The Ruby Hoedown is less than two weeks away, and we couldn't be more excited about it! A top-notch charity workshop, a line up of seven great talks, lots of hallway time for meeting fellow Rubyists, and some really sweet t-shirts add up to a great, Southern-style conference. What, you're not registered yet? Well, it so happens we have a few seats left, so proceed to post-haste and grab yours before we sell out! And, if you have any questions, please don't hesitate to send them to organizers AT - we're glad to help out however we can.

See ya'll real soon now,

The Ruby Hoedown Organizers

This conference will have some great speakers (including me!) and a great crowd. Our local Ruby crowd has a lot of very talented software folk. Although the Hoedown is the first of it's type we've had here in Raleigh, I know several of the speakers and the organizers. I expect it to be top notch, so come out and join us!

Category: Ruby

One Language to Rule Them All? (Jul 28)
I just read another classic post by Martin Fowler. Among other things, he's pointing out the distinction between when it's appropriate to go learn a new language and when you should re-use the one you already know... and there's a bit of why people like Ruby as well.

Should we strive to only have one language in our development efforts?

A few gems from the posting:

...many frameworks resort to configuration files, which are effectively external DomainSpecificLanguages written in XML - which adds a jigger of 80 proof ugliness to them...

For many developers, the one-language notion is a sign of lack of professionalism....

Time and time again I hear experienced Java and C# developers report they are more effective in Ruby - which is why I've been encouraging Ruby. It wouldn't surprise me if similar reports appear in the next few years about other languages too...


Category: Ruby

Matz Linked to Me (Jul 28)
My blog entry on my OSCON talk had a spike in visitors, so I looked at my logs and found this:


Category: Ruby

Summing Up Ruby and Rails (Jun 15)
This picture on Dave Thomas' flickr stream just sums it all up. I wish I could read Matz' addition!


If you can't say this about your programming language (or your career for that matter!), you're doing it wrong.

Category: Ruby

Got Rdoc? (May 25)
I'm always hearing people say that they want to have local docs like the ones at the Ruby Rdoc page. I've also wanted this and looked all over for a way to download these docs and haven't found them. Everyone says "Use Rdoc" but nothing more. I've only used rdoc on my own project and just didn't get what they were suggesting.

With Rdoc, it takes a few minutes to generate them, but you can make your own local copy of any Ruby docs. I think 90% of the Ruby/Rails world knows this already, but those of weren't in the secret, try this.

cd into your local directory that holds your Ruby/Rails code. This could be your own project code, /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3 (to generate your Active Record docs), or /usr/local/lib/ruby/1.8 (to build your own core Ruby docs). Since Ruby is interpreted, you've got all the system code right there on your own box.

Create a directory in your home folder called rdoc (or whatever you'll remember).

type rdoc -o ~/rdoc/activerecord or rdoc -o ~/rdoc/ruby or so on. Rdoc wants to create that last directory itself, so don't help it out by having it in place already.

When you're done, you'll have a nice, very fast, local copy of the docs. More importantly, you've created docs that match exactly what's installed on your machine.

It does take a few minutes to generate your own copy of the Ruby core docs, but the rest run fairly quickly.

Category: Ruby

Previous page
DevNexus GROWS Workshop (2016-02-15)
I'll be giving a full day GROWS workshop!
Agile Leadership Network (2016-02-23)
I'll be at ALN to discuss GROWS
TISQA (2016-03-03)
I'm speaking on the continuous paradigm

© 2007 Agile Artisans.