Introducing Dougal Campbell

I’m very excited to announce that Crowd Favorite has grown once again, this time bringing on a developer who needs no introduction to most people in the WordPress world: Dougal Campbell.

Dougal Campbell

Dougal has made numerous contributions to the WordPress community, from core code contributions and plugins to Ping-O-Matic. Like me, he’s got years of experience working with WordPress. Since much of what we do at Crowd Favorite is custom WordPress build and functionality work, this experience is a perfect fit for us.

However Dougal also has a broad depth of experience in general web technologies and web application development. He’ll be helping out on Crowd Favorite products as well as the custom WordPress work we do.

I’m very excited that Dougal has agreed to come on board, and look forward to working with him again.

Here is a brief bio on Dougal (also on the Crowd Favorite About page now):

Over the past 25 years, Dougal has molded his fascination with computers from a hobby into a career. Dougal joined the WordPress effort early on and developed much of the initial XML-RPC code and the Ping-O-Matic service, and now enjoys “Developer Emeritus” status. From the early ’80s to present day, he has worked on customized inventory database systems, and developed web applications for trucking companies, the hospitality industry, and a startup with a web-based video platform, among other things.

Along the way, he has contributed his efforts to several open source projects, the most well-known of which are WordPress and POV-Ray. Dougal comes to Crowd Favorite with a strong background in developing web applications in Perl and PHP, and with with an eye towards web standards and the emerging semantic web.

Dougal’s offline time is spent with his wife, three children, a dog, and a cat. He hasn’t taught the dog and cat how to set up their own blogs yet, but he’s working on it.

UPDATE: read Dougal’s post as well.

This post is part of the thread: Crowd Favorite – an ongoing story on this site. View the thread timeline for more context on this post.