We know best - Woes of a Web Warrior
This blog post is more than 4 years old, so the content may be out of date.
So, you want a new website? What do you think the odds are of getting a site that you're happy with…a near certainty? 1 in 2? 1 in 6? I can't say that I have all the answers, but I do have some stories to tell - and I hope these tales will help you beat the odds.
So, why did I write this series? I'll admit it is partly a rant, and partly a sales gimmick…On the one hand these tales illustrate some of the risks of building websites. On the other hand, I am a busy guy, I can't help everyone, and I do like to see websites built right, even when I'm not involved. After all, I never know if I might end up using them! Whether you're working with me or not, I hope these tales will help you avoid some of the pitfalls that await even the wary.
- "We know best"
- If it's worth doing once, it's worth doing again and again and again
- Agility is the answer
- "The Grid"
- I can haz environments?
"We know best"
(This is the first article of six…they do get longer!)
In my early days of Drupal, I worked with a company who had recently adopted Drupal. They had a history of working with Java and Perl - no significant PHP experience - but they were consciously learning.
But they knew best - after all, they had built a CMS before, right? They developed their own series of custom modules. They created their own practices. They created their own deployment system. And they hacked their patches into core and contrib.
Four years later, the sites they had launched, maintained, and still hosted, were still running on the same (minor!) version of Drupal - in four years, they hadn't updated core or contrib once. Despite half a dozen (and then some) security patches. All because a team of a couple of software engineers - who had never developed in PHP before - knew better than the entire Drupal community.