Energy

Last weekend I had the good fortune of being able to attend TEDxRainer. The event could best be summed up in one word:

Passion.

Everybody there seemed passionate about being there, sharing ideas, looking for ways to make the world a better place. And after spending a solid 10 hours among such passionate, engaged people, it's hard to come away without being inspired.

Short answer: it depends.

We still do most of our projects in Drupal 6, mainly because it's been around a few years, and modules we use on many sites are not yet stable for Drupal 7 (and some are still a ways off).

However, for sites that don't need particular modules, Drupal 7 at its core is a nice improvement.

My first Drupal 7 site is a personal one, http://www.hikeswithhazel.com. So far as a user, it doesn't seem that different from Drupal 6, especially if you turn off the "Overlay" module which pops open editing screens in what I find to be a highly annoying way.

All the planning and preparation in the world won't prevent an incident, but it can greatly reduce the consequences.

Nothing better prepares you for responding to disaster than experience. In the world of web applications, sometimes we act as firefighters, coming in to rescue the smoldering remains of a hacked site, a crashed server, or an unexpected traffic burst.

No matter how diligent you are at preventing vulnerabilities and securing your environment, it's impossible to be completely secure on the Internet. What you can do is plan for how to limit the damage that people can do when they manage to compromise some part of your system. This line of thinking is called "Defense in depth" -- you can't just apply security updates and call it good.

I get this question all the time: What's the difference between Drupal and Ruby on Rails, or another framework?

Quite simply, Rails is something you build an application in. Drupal is an application. So chances are you're one major step closer to building a web site that does what you want it to do, if you start with Drupal.