A List Apart

Menu
Issue № 257

The why and how of Ruby on Rails.

Getting Started with Ruby on Rails

by Dan Benjamin · 28 Comments

The "how" of Ruby on Rails: Hivelogic's Dan Benjamin prepares non-Rails developers, designers, and other creative professionals for their first foray into Rails. Learn what Ruby on Rails is (and isn't), and where it fits into the spectrum of web development and design. See through the myths surrounding this powerful young platform, and learn how to approach working with it.

Creating More Using Less Effort with Ruby on Rails

by Michael Slater · 25 Comments

The "why" of Ruby on Rails comes down to productivity, says Michael Slater. Web applications that share three characteristics, they're database-driven, they're new, and they have needs not well met by a typical CMS, can be built much more quickly with Ruby on Rails than with PHP, .NET, or Java, once the investment required to learn Rails has been made. Does your web app fall within the RoR "sweet spot?"

More from A List Apart

Columnists

Nishant Kothary on the Human Web

The Politics of Feedback

We’re obsessive about collecting input from a wide range of potential users and stakeholders. But with such an onslaught of feedback, there’s always a risk of having your motivation and faith in humanity sucked right out of you. Sometimes, you just need calm critique from the few people who really get you. So which kind of feedback is best? The answer is both.

From the Blog

Personalizing Git with Aliases

Part of getting comfortable with the command line is making it your own. Small customizations, shortcuts, and time saving techniques become second nature once you spend enough time fiddling around in your terminal. Since Git is my Version Control System of choice (due partially to its incredible popularity via GitHub), I like to spend lots of time optimizing my experience there.

Routines Aren’t the Enemy

I recently read Greg Smith’s piece on Bocoup's blog about how they think about time tracking, including all the fascinating data about how your brain works to solve problems. It interested me a lot, since I've been thinking about not just how I track projects, but also how I structure my day as a freelancer.