Tim Case has started a series of entries on his blog called Reading on Rails. In this series, he examines how some of the major trends in software development, like test-driven development and refactoring, relates to Rails. And what literature you should be picking up if you want to know more. Great stuff.
Ralf Wirdemann and Thomas Baustert are relentlessly pushing Ruby on Rails in Germany. Besides working on the Web-Entwicklung mit Ruby on Rails book, they will be presenting at XP-Days Germany, and now they just got an article on Rails published in the German iX Magazine. Congratulations, guys! If you read German, do check it out.
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 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.
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”.
James Duncan Davidson and Mike Clark has delivered on their first large, commercial Rails project together: VitalSource Bookshelf. It’s a book store that aims to make it as easy to buy your ebooks as your music. What’s special is that it includes a native application, ala iTunes, that works together with the Rails-powered store.
On James’ announcement, there’s also a note from Willie Abrams of VitalSource. He writes about using Rails: “As for Ruby on Rails? Wow. A lot of things would have to change for us to consider doing a web application any other way. It is that good.”.
Thanks, Willie. And congratulations to both Mike, James, and VitalSource for shipping!
Scott Barron is toying with the idea of a rcss format that would allow you to specify your CSS file in Ruby. Why would you ever want to do that? Have a look at Scott’s example and note the use of variables. That’s a pretty good reason on its own.
In case you’re wondering with it’s
:controller => "weblog" and not just
"controller" => "weblog", you want to read Kevin Clark’s Understanding Ruby Symbols. It gives a number of angles on why symbols exist and why they make sense to use.
David Geary has moved into the Rails café and is now spending a considerable amount of time telling others about this place. Most recently, he did just that again at the No Fluff, Just Stuff symposium in Salt Lake City. His presentation left more than a few jaws hanging:
Near the end of that demo, I looked into the audience and saw something that I’d never seen at a NFJS symposium: a woman sitting at a table near the front of the room was looking at me with her mouth wide open and the most incredulous look on her face. It was almost like I could read her mind: “This can’t be real!”, she must’ve been thinking. I pointed at her and said “That’s pretty amazing, huh?” She nodded a reply, but the look of astonishment never left her face.
The language and environment you choose to work with those make a large difference on productivity. Smart people can succeed with nearly anything, but that doesn’t mean they shouldn’t look for that edge whenever they can find it.
The Rails job market continues to pick up pace. Here are a total of six new positions open for developers ready to leave the old world behind and join the hundreds of people working with Ruby on Rails professionally:
- Site5 is looking for two senior Rails developers and one Rails designer/developer to join their already sizable Rails development team. The latter is specified as the “…ideal developer/designer candidate has a complete understanding of both user interface design and object-oriented programming”. Contact Matt Lightner to apply.
- Money Management Group are looking for a Quantitative Systems Developer (whatever that means exactly) to help them use Ruby on Rails to develop, manage, and test trading systems for their dealings in the financial sector.
- Vespa is looking for preferably a Denver-native (but could be telecommuting) developer to help them finish a Ruby on Rails system and be “…comfortable with complex database design and relations”. Write Dale Hawkins to apply.
- Aasman Design Inc. in Whitehorse, Yukon, Canada is seeking a full-time web developer with strong knowledge of Ruby on Rails and who also places great value in an excellent user experience.