On Drupal certification programs

Every once in a while, the discussion of Drupal cerification comes up. Is a Drupal certification program a good thing or a bad thing? Are certification programs overrated? Isn't one's track record as a contributor on drupal.org the best measure of someone's past (and possibly future) performance? Should the Drupal Association manage the program, and if not, then who? What do other Open Source projects do?

Lots of unknowns and lots of subjective questions always make for a good discussion.

While I'm often skeptical about certification programs myself, I do see the value in them. Certification isn't for everyone but for some people it is valuable. A masters degree from MIT, an MBA from Harvard or a Ph.D. from Stanford is a form of certification too. But, just as there are good examples, there is no lack of examples where bad certification programs deliver certified engineers that don't know what they are actually doing. That fact, though, doesn't invalidate the valuable certification programs that do exist; for example, the CISCO certification program is very thorough and valued by the market. Similarly, I think that employers do value certificates achieved in higher education. All things considered, I believe there is value in having a well-executed high-quality Drupal certification program, especially as Drupal continues to grow.

My personal view is that the Drupal Association is not the best body to create "the" Drupal certification program. It is my belief that we are best served by allowing many organizations to create their own Drupal certification programs, and have the marketplace set their value -- similar to how universities build reputations. Competition around Drupal certification programs could be a great thing, because it would likely improve quality and allow for specialization. A certification, of course, is ultimately only as valuable as the organization standing behind it. In such a scenario, it is very important that the certification programs are labeled properly; that is, "ACME Drupal certified" rather than just "Drupal certified", where ACME is the name of the company or organization providing the service. It has to be ACME's reputation that is on the line for the quality of their participants. The Drupal trademark policy is designed to help achieve that.

I also don't believe that a certification program is a zero-sum game: that is, holding a certification doesn't imply that your track record on drupal.org (through your user profile) is of either less or more value. Again, the market and the buyer will determine the value of a drupal.org user profile versus a certification program versus a resume versus a portfolio versus degrees obtained through higher education. In any event, it is unlikely that one would hire someone solely on the basis of having a Drupal certification. I certainly wouldn't.

When we launched Acquia two years ago, we announced a Drupal certification program code named 'Yellow Jersey'. That program hasn't materialized yet, and we're not putting resources in it at this point in time. Building a high-quality certification program is a significant undertaking and we're not ready to take on such a program. And last but not least, the marketplace hasn't demanded these types of programs to a sufficient degree. Yet.

Other Open Source projects like MySQL, Zend, Linux, Ubuntu, RedHat, BSD all have certification programs so I think it is a matter of time before we see one or more Drupal certification programs emerge. Personally, I would support a well-executed high-quality Drupal certification program.

peach - all drupal themes:

In Drupal it would be rather interesting, would you need to take a test that involves both theme and module development, and would you need a new certificate for every main increment of Drupal ...

August 11, 2009 - 08:37
Tim Millwood:

I agree.

If three applicants went for a Drupal developer job. One 'Acquia Drupal certified', one 'Lullabot Drupal certified' and one 'Joe Bloggs Drupal certified'. I think the ones taught by Acquia and Lullabot would have a much better knowledge than the ones taught by Joe Bloggs because of the reputation.

If all three were just 'Drupal certified' there would be no way to differentiate between the quality of teaching.

August 11, 2009 - 09:26
Jamie Giberti:

Hi Dries,

You make a lot of good points, I have investigated a couple of times whether there is any Drupal certification active in the UK at the moment, one that seems to crop up quite often is a certification being offered by NobleProg, they seem to run various Drupal training courses, and also a certification. I do not know how advanced or well thought of it is, but this seems to be the main activity of this type in the UK.

August 11, 2009 - 09:54
Ravi Sagar:

Having a certificate is one thing but respecting it is another. In India most of the companies would give just little preference to the certificates. It might be true for other countries as well. Once a company associated with some product start their certificates all the small computer institutes start offering their courses and earn money. They even help students pass the exams. So all this just decrease the quality of the certificate.

Practical knowledge and experience is what matters the most. Even if Drupal ever has to offer a certificate I would like it to be like RHCE exams, which is more focused on "doing things" rather than "knowing things".

August 11, 2009 - 09:55
Dries:

I agree that 'doing things' is really important. One thing a certification program could do, is lock up the participant in a room for one or two days, and have him solve different Drupal problems.

For example, a participant could be given some infrastructure, a Drupal site with real content, and simulated site traffic that corresponds to 30 million page views a month. Then as part of the certification program the participant could be asked to use the provided infrastructure to make the site scale under different simulated traffic patterns. The solution could require a combination of things: installing memcached, installing APC, configuring page caching, configuring Varnish, configuring MySQL in master-slave, profiling Drupal, rewriting some module code, adding some missing indices, enabling the MySQL query cache, installing the Boost module, tweaking the Apache configuration, etc.

It would make the certification program valuable because most Drupal developers don't have practical experience with scaling a Drupal site to 30 million page views a month.

It is the kind of certification program I'd like to build, but as said in my blog post, that is no small task -- and maybe somewhat naive.

August 11, 2009 - 12:24
Andy Walpole:

So does the Drupal Association oversee the course / exams?

I think there needs to be some sort of official seal of approval then the courses can carry the label "Approved by the Drupal Association".

August 11, 2009 - 13:46
Jake Strawn:

I like the way this is headed as a topic. At first my thought would be that it would be very valid to have a certification program, but as it was pointed out several times, "value is in the eye of the beholder" seems to make sense.

I do still think there "could" be a good market/desire for this.

What if even, there was let's say 4 levels of certification:

  • Drupal Certified Engineer - Module/Core engineer focus
  • Drupal Certified Themer - Theme Focus only
  • Drupal Certified Designer - Designers with the chops to design well for Drupal
  • Drupal Certified Rockstar - a combination of 2 or all of the above options

To me something on these lines helps break things apart, as some of those groups would be difficult or impossible for some users that don't design for example. But also, having "levels" or "branches" of certification, including a "super certified" type level to me can also help drum up interest from some parties.

I think that even though being a "Drupal certified company" MIGHT not weigh in a decision to choose that company, there's always the chance that it DOES land the "big" client that wont accept any less.

Potential does lie here I believe.

August 11, 2009 - 21:40
Dominik Lukes:

Hi all,

Robert Castelo from Code Positive and I have been playing around with this idea for the last couple of months.

I think there is a way to have a certification that can take into account both practical experience and Drupal.org juice.

I suggest a successful programme would need to have two components:

  • Open Source style curriculum
  • Portfolio assessment

Here's a document suggesting an outline of such a curriculum
http://docs.google.com/View?id=dmjbnhb_4pnh27kc9.

This curriculum could be community-driven, have a maintainer, periodic version releases and some sort of a compatibility measure (API). Different providers could then provide differently structured training courses to help people compile a portfolio that would be a proof of a certain level. This could also help new users with self-instruction and large companies to manage their in house training and staff development.

I was hoping for a session on this in Paris (http://paris2009.drupalcon.org/session/training-drupal-professionals-tow...) but it looks like I might not be able to make it afterall.

There's also this project that's trying to achieve something similar: http://groups.drupal.org/node/22703.

There's a lot of experience with curriculum authorities and portfolios in the world of education but I'd like to experiment with bringing some open source ideas into educational design (and vice versa).

August 12, 2009 - 17:44
s.Daniel:

Certification programs are grounded on the idea of "If someone I trust thinks she/he does xyz good I'll believe that". Now how as someone new to Drupal know if he can trust the “Lullabot Drupal Certification”? Of cause we know Lullabot and know what they have done with and for Drupal but we don't need Drupal certificates any way, do we?

The way this is handled usually is to have some form approval of the certificate by an authority. The only authority I could think of is the Drupal Association.

I don't know how it works in other countries but in Germany universities are approved by the state. Still they can built reputation among others and focus on particular skills in the training of their students.

I think the best would be if the DA could maintain propositions of certification programs similar to the ones proposed by Dominik Lukes. Companies willing to do certification programs could use these as a starting point for their own programs and then hire the DA to approve their program.

This way we could maintain a comparable level while having a low entry barrier for new certification programs.

August 14, 2009 - 10:40
Baris Wanschers:

Sounds like a great idea. I agree with Tim Millwood that there has to be a differentiation between the certificates by adding the company name. So it's a matter of time before I can I get my Dries Buytaert Certified Drupal Designer Certificate?

August 14, 2009 - 12:45
Shaun:

@Ravi Sagar: "They even help students pass the exams. So all this just decrease the quality of the certificate."

What you mean to say is that companies in Asia help students cheat on exams for the right price. So, don't hire Chinese and Indian programmers.

October 7, 2009 - 09:26
Sudipta:

@Shaun: As Ravi Sagar told (and I am aware of these happenings myself), training institutes "train" the students "only" towards certification, that is, they provide dumps and make student "just perfect" for the certification, may not be "just perfect" for undertaking a real life challenge.

These certifications are just a means of "increasing" one's the value in the market by putting a logo on the CV.

Certification in X = Reading the "X for Dummies" + Taking a quick specialized training for certification in X + Getting latest question dump for ceritication in X

January 28, 2010 - 22:00
Jim:

If nothing else, some consistency in how to design and architecture a Drupal site would be a benefit. By that I mean if there were some basic standard practices. As a consultant and contractor, I've seen designs all over the road. I've noticed that module builders tend to write custom modules to solve a problem when there is already a module built that accomplishes the desired result. And we're not talking specialized contributed modules. I've seen simple menu structure so over-customized that any changes require hours of reverse engineering rather than going in and making a configuration change.
I'm not being critical of the module developer. When I started out in Drupal, I focused on building modules. But over time my focus changed and I decided to look for a Drupal solution first. That involved seeing what I could do with CCK or Views or Webforms or some other modules. I started spending more time understanding configuration and templates in what was already built rather than the API.
There was a mention earlier in the post about 3 distinct tracks. I think something of that nature would fit the bill.

March 15, 2010 - 13:10

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.
© 1999-2010 Dries Buytaert Creative Commons Attribution-NonCommercial-ShareAlike 3.0 License.
Drupal is a Registered Trademark of Dries Buytaert.