As developers, saying "no" to clients sounds, on it's face, like a bad idea. You want to do what the clients need, you don't want to upset them, and, frankly, you want the hours. But the truth is, in order to build websites that are cost-effective and sustainable, you have to say "no" sometimes.
Whether you belong to an organization which has, or is planning a Drupal site implementation, or a Drupal developer, you should know, and care about Symfony.
About a year ago, I was deeply enmeshed in fixing a rather badly-developed Drupal site for a client. In my frustration and anger, I wrote these commandments. I thought these would go without saying, but obviously, they needed to be said.
Responsive is a great concept. An increasing number of people are surfing on phones and tablets, and they expect to be able to do almost anything on their devices that they can do on a desktop. So why are so many nonprofits still building non-responsive sites?