Talking head
Ruby Conference 2011

This presentation, by Tyler Hunt, is licensed under a Creative Commons Attribution ShareAlike 3.0

Now that there are now over 25,000 gems on, it's time we took a step back to look at the quality of what we're producing and the best practices we can all follow that will benefit the community. Other languages expend a lot of effort maintaining a standard coding style and consistent APIs among their shared libraries, but the Ruby community doesn't. This has done a lot to lower the barrier to entry and allow the Ruby ecosystem to flourish, but it has also produced a lot of code of questionable quality that doesn't always mesh well in our applications. There are simple conventions we can follow, though, that will make a big difference in establishing a consistent baseline for our gems. These include things like writing gemspecs instead of Rake tasks that generate them, properly namespacing your libraries, and not polluting the load path. But there are also other practices that will benefit others, like producing good documentation, including binaries when needed, and establishing a sane versioning strategy. We'll cover the full lifecycle of a gem from beginning to end, from your first push to to making and accepting community contributions, and consider the conventions that we can establish each step of the way to increase the value of the gems we're producing.

Rated: Everyone
Viewed 1,138 times
Tags: There are no tags for this video.