Quite some time ago, we did some work on certification for fronteers. Then it went dark, as all the volunteers, including myself, had too much other stuff to do. That is, until last autumn. During the last fronteers conference some members signed up as volunteers. As I have some time on my hands now we have decided to get things started again.

The idea is that we have is to do a two way exam. The first part will be a written exam on knowledge of HTML and CSS. In the second part the candidate will have to do some 'live coding', he/she will be given a graphic design and they have to draw a possible solution on a white board. Explaining the choices made to two members of the certification committee (or other judges) as he/she goes along.

If the candidate successfully passes both tests, he/she will receive two 'stars' on the certification for HTML and one for CSS. In the future we could expand the exams to include stars for JavaScript, performance, mobile, 'webrichtlijnen', accessibility and more. The first two stars are mandatory, as I think that any front end developer needs to have a basic knowledge of HTML and CSS.

The stars are something a developer could put on their cv, site. Companies that employ them could use it to show the skills they have on board. The exams should be repeated every one or two years, as the field continues to change. Stuff that is relevant now could be plain obsolete in two years...

Our big problem is now that we don't know if front end developers are interested in this certification.

Some big companies are as well as dutch government agencies have expressed definite interest in this. For them it is a good way (they think) to find the right people to hire. Developers on the other hand are not that interested and I must say that I see their point. Other fields that have certification, like Java, made it clear to me that the best developers are not necessarily the certificated ones. Many front end developers are self taught and are not keen to study for something they have been doing for years, just for the sake of some certificate that may or may not be important.

So here is my question to all of you developers out there, are you interested in certification. I even wanna know if you are not dutch or no members of fronteers, also clients may react. The easiest way to react is to tweet using the #hashtag #frontcert. All tweets containing this will be gathered below this article...

UPDATE
This article has created quite a buzz on the internet, something I had hoped for, but a lot bigger then I expected. A lot of people reacted strongly against certification, some with good points and all. The main consensus is that (experienced) developers are against, for a variety of reasons. This is what I expected and we (the whole committee) will take your opinions into account. I will write a follow up on this post shortly, to answer some questions and explain what wasn't clear in this post. I will also tell what we talked about in the committee the last week, as we are already thinking what to do with your reactions.

In the meanwhile, take a look at the reactions on the fronteers forum and read the article by Martin Kool, who is strongly opposed. If you know of any other post about it, please let me know so that I can link to them.

And to you all, thanks for your opinions. Without those we (the committee) wouldn't know we had to do.

Just a quick warning, if you are the person responsible for this kind of code, I will tell your mom. I really will.

<span 
	class="button-active" 
	id="xf-384">
	<div 
		id="x176901972nav-button" 
		class="xbl-component xbl-fr-button">
		<span 
			id="x176901972nav-button$xf-1369" 
			class="yui-button yui-push-button xforms-group">
			<span 
				class="first-child">
				<button 
					id="x176901972nav-button$xf-1370" 
					class="xforms-control xforms-trigger" 
					type="button" 
					tabindex="0">
					Uw gegevens
				</button>
			</span>
		</span>
	</div>
</span>

This is wrong on so many levels, I can't even begin to describe it. The CSS written to style this is even worse. The sad thing is that this could be done, with just the frigging button and nothing else.

I can't even think of a reason why someone would want to do this, other than complete contempt for the world. This is obviously being written by someone who thinks front end code is very hard to do, like a java developer.

Quick piece of advice, hire a decent front end developer and don't do it your self…

The sad thing is that I saw this on a governmental site, so tax payers will pay for this incompetence.

The proper code for this should of course be this:

<button 
	id="x176901972nav-button$xf-1370">
	Uw gegevens
</button>

Although I think the id could be more logical, but I'll give the back end guys that…

American Censorship Day November 16 - Join the fight to stop SOPA: ""

PROTECT IP Act Breaks The Internet from Fight for the Future on Vimeo.

Recently there was decided that we don't need a <time> element in html5 and it was replaced the utterly not semantical <data> element. I hurried to change my sites code, even if I DON'T agree. Rather than write something about it myself, I'll let the ever so polite mr Bruce Lawson have a go at it.

Why No Time?

<data> is too vague, too bland, it sucks.

I love the daily nerd, it is my first stop when I start the day. A daily list of articles I as a front end developer find interesting. But lazy as I am, I find it too much trouble to open all of those links in new pages. So I wrote a bookmarklet to do that :).

It is not wholly bulletproof, as it depends on the html structure of the daily to never change, but hey, it is easily changed…

Here it is: Open daily nerd drag this to you bookmark bar and when you are on the daily nerd, click it..

In case anyone wants to create one for a different link site, like ppk's linkbait or Roberts read category, here is the code (uncompressed).

// open the dlnrd links in a new window
var odlnrd = function(){
	// get the first article
	var a = document.getElementsByTagName('article')[0],
		// find the article in there
		b = a.getElementsByTagName('article'),
		// calculate the length of those outside the loop
		c = b.length;
	// iterate over them
	for ( var i = -1; ++i < c;){
		// open a new window for each link
		var d = b[i].getElementsByTagName('a'),
			e = d.length;
			for ( var j = -1; ++j < e; ){
				window.open(d[j].getAttribute('href'));
			}
	}
}();

Feel free to take this code and improve on it. I would like to know if you did :).