The population of professional Ruby on Rails developers is calling for growth:
In just a few days, the list of people working professionally with Rails to earn “…a substantial or full paycheck” has blazed past 200! It includes programmers from 33 countries. From China to Finland to Jamaica to South Africa. But the United States is still the dominant force. Almost half of programmers on the list are living there.
Growing the ecosystem around Rails is very important and I’m thrilled to see the list so large already. Who dares venture a guess at the numbers in 3, 6, and 12 months?
Cincom Smalltalk has long touted the Kapital system at JP Morgan (PDF) as an example of what an edge in productivity can mean for profits in financial services. So, it’s not entirely surprising to see MSCI Barra from Berkley, California look for a senior software developer and desire that the candidate has Ruby on Rails skills for use with their investment systems. I believe we may just have an E for Enterprise here.
The Struts/Hibernate vs Rails comparison from a while back is the latest fresh stuff at Slashdot. This marks the 8th Slashdotting of Rails. Coming up on the big 10 soon ;)
Make it as easy as not to.
When we originally launched rubyonrails.org, none of the Rails-based blogging engines were really up to the task of running the show. But with the appearance of Typo and it’s massive uptake and rapid improvement, we have a very viable solution now. So goodbye, WordPress! You served us in a crunch, but I’m also very pleased to see you go.
The switch means that we’ll actually be able to keep comments open without the blogging engine mysteriously shutting them off. And that we’ll hopefully be even better equipped to combat spam.
Thanks once more to Tobias Luekte for blessing the world of Rails blogging with Typo.
David Geary did a cool demonstration of Rails yesterday at the Denver Java User Group by getting a member of the audience, unfamiliar with Rails, to do the demo for them:
In the end, Kirk pulled off the demo without a hitch. That says something about Kirk, but it speaks volumes about Rails. After he left the podium, I added some users to the db and refreshed the app and there, magically, were the new rows in the database. Then I tweaked the pagination parameter for the controller that controls page size from 10 to 5, saved the file and refreshed the browser. I asked the audience if they noticed how long that deployment took. Then I changed the prameter to 3 and then to 2 and reran the demo each time. Each time, the number of contacts displayed updated according to the pagination parameter and each time the redeploy time was, well zero. That got people’s attention.
Change’n’refresh is an intensely addictive form of working, no doubt.
We’re trying to get a sense of who and where people are doing commercial work with Rails. So is the framework paying at least a substantial part of your bills? Put your name on the list.
Duane Johnson has a great how-to on productizing your application. Which basically means that you have a core application that you need to tailor ever so slightly for each customer. How do you do that and still ensure high reuse? Well, that’s just what Duane’s approach explains.