Jobs, jobs, jobs: Hiring Ruby on Rails is hot

You take off for just a little vacation and come back to an inbox stuffed with job offers for Ruby on Rails:

  • LookSmart, based in San Francisco, is putting their enterprise app on Rails — a dynamic advertising marketplace managing millions of listings and bids, syndication partners, integration with CRM, credit card processing, web services APIs, etc. They’re working with Mike Clark and James Duncan Davidson to help bootstrap this project, and they’re looking for a top-notch, high-energy lead for the team, plus an additional engineer. A great opportunity to get paid to work in Rails on an app that’s central to a public company’s mission. If you’ve got the chops for either role, they’d like to talk to you. Contact Bert Knorr (bknorr_at_looksmart.net) for more info.
  • Naviance is looking for a designer with Rails experience. Especially Ajax and Ajax on Rails experience. The person will be working with Chad Fowler, who just joined the company as their lead developer.
  • Digital Age Media is looking for an experienced Ruby on Rails programmer to work on an online game. The work can be done remotely. Experience with video game theory and programming is a plus, but is not required. If interested please send an email with a resume, links to your work, rates, and availability to jobs at digitalagemedia dot net.
  • Free The Slaves is looking for a volunteer (unpaid) Rails developer to create an e-commerce system for the organization.

A List Apart 4.0 uses Ruby on Rails

A List Apart is an institution in web design. I’ve learned more than a few tricks over the years from this venerable magazine and its therefore with great honor that I see the newly relaunched version 4.0 is a Ruby on Rails application. Congratulation to Dan Benjamin, Zeldman, Erin Kissane, and the rest of the team behind ALA.

Comparing WebObjects to Ruby on Rails

Deirdre recently gave a presentation at BarCamp that compares the implementation of the same application in Apple’s WebObjects to Ruby on Rails. It includes this graph that contrasts the code-base size of the WO application to the Rails version:

Convince your manager to let you use Ruby on Rails

Zed Shaw has compiled a long list of suggestions on how you can get your manager to let you use Ruby on Rails for your next project. It’s full of goodies including this strategy of dealing with the ill-informed ‘does it scale’:

For example, they say, “It needs to handle 500 connections/second.” Don’t let them say “users”, “users” means nothing. Then you go test their current WizBangOMatic and find it only handles 10 conn/second. You can then come to them and say that Rails can’t do 500 conn/second, but it can do better than the WizBangOMatic which only has 10 conn/second performance. It’s evil, but it puts the performance harpies at rest.

Calling SAP models from Rails

SAP is one of the ERP behemoths that dominates in the enterprise world. Pretty far removed from Rails? Not really, it turns out. Piers Harding has written a great article for the SAP Developer Network that shows how to create a Rails application that uses a SAP backend as the model instead of Active Record.

The article shows how to use SAP4Rails with two BAPI objects – Currency (BUS1090), and ExchangeRate (BUS1093) – and make those available through a standard Action Controller setup. Very cool stuff.

Jason Hunter explains Java's Dilemma

Jason Hunter explains in an article called The Innovator’s Dilemma: It’s Happening to Java why there’s such a big interest in Ruby on Rails from the big Java thinkers like himself:

Ruby on Rails today looks poised to eat Java’s mindshare on the web tier. If not Rails, then something else. Empirically 10 years seems like the right point. Java’s viewed as solid and stable, mature enough for the most stodgy business folks. That leaves a large soft underbelly for a technology intended to help small teams (10 or fewer) who just want to make a site that’s good enough without paying a high price in mental effort.

I’ve written earlier on Rails as a disruptive technology according to Christensen’s framework of thinking.

SwitchTower: Automating Application Deployment

As the 37signals applications have scaled up to run on multiple servers, we needed a better way to manage the deployment phase. We wanted to automate that all six servers got the newest version, that the database server ran the migrations, that the FastCGI processes were restarted on the application servers, and possibly that the web servers showed a “down for maintenance screen”.

SwitchTower is the extraction of that need and its going to be a new part of Rails in the next release. It’s the work of Jamis Buck and you can preview it right now by playing with the beta gems/subversion trunk.

You won’t even be going in blind-folded. Jamis has already created an incredibly extensive manual that teaches you all about how to use SwitchTower. Get on the band-wagon and reduce your deployment pains to “rake deploy”.