KuraFire Network


Latest addition: Jan 19, 2007: Times are changing

Log

DEWD meeting aftermath

· By Faruk Ateş on Jul 25, 2005 · 24 comments ·

Yesterday was DEWD day: the july 24th, 2005 meeting for the Dutch Enthousiastic Web Developers. Among other things, we discussed Opera's lousy interface, Javascript and the deprecation of the term "DHTML" and making these social gatherings a monthly event with a theme for each of them.

DEWD meeting july 24th, 2005 - Hayo

The meeting was dominated by a fun atmosphere with lots of jokes and silliness. As you can see in the picture, Hayo had a bit of difficulty with his camera after the first few beers, but a tip from Egor helped him out. Update: okay, so it was Sjors who said that originally, my bad.

We didn't really have an agenda for the meeting, as we generally never do, but I wanted to discuss a few specific topics nonetheless. One of them was my idea for a conference in the Netherlands, much like @media but then slightly different.

Everyone agreed that organizing a conference that aimed itself towards the Dutch audience in particular would be a great step towards finally spreading Web Standards awareness here. One of the things that @media sort of failed at was that it hoped to get an audience that was new to it all, consisting of both developers and executives (a.k.a. the people with money and decision-making powers). However, @media's crowd was nearly entirely made up of people that have long since been using CSS for layout along with semantic XHTML. It was great fun, but it didn't quite reach the audience that Patrick had meant to reach when he set out to organize @media.

For this Dutch conference, we would do a few things differently.

Parallel sessions

Hayo suggested we do parallel sessions, mainly because we would be having several targetted audiences. One audience consists of business executives that need to be convinced of the need and importance of using web standards in today's websites, another consists of web developers that are still using outdated and/or inaccessible techniques (tables, frames, and so forth) that we want to introduce to using CSS for layout (on semantic markup). A third would be the audience as seen at @media, with more challenging, sophisticated presentations for those already doing things pretty damn well.

To keep things interesting for each of the audiences, it would be imperative to separate them and run them parallel of each other. After all, business executives would have no interest in learning how to use CSS to make a 2-column layout, and developers that think CSS is only for styling hyperlinks would get horribly overwhelmed and confused when you start analyzing the accessibility aspects of the Gilder/Levin versus Leahy/Langridge image replacement techniques.

However, there is a problem. We have another audience that we wish to see present at this conference: design schools and similar educations. The people who are currently teaching students how to do graphic design for the web are also the ones teaching them how to create websites. Problem is, the schools themselves in the Netherlands are horribly behind on things. They educate what can only be considered worst practices, and we need to get those people up to date pronto. That means convincing them of the value (and benefits) of using web standards and educating them how to do so at the same time.

Obviously, it'll be a bit of an organizational nightmare to make things work as fluently as we'd like them to, but fortunately we're only still in the very first phase and have plenty of time to work it out.

On the whole, the goal of this conference will be:

  • to get managers and executives willing enough to let their developers spend a lot of time getting re-educated so that they can use web standards instead of old practices;
  • to get said developers intrigued and willing to re-educate themselves;
  • to get schools that teach old practices willing to change, and re-educated so that they can teach new practices to begin with;
  • to further inform those "already in the know" on web standards about the more tricky aspects of accessibility and usability

Should be fun!

People

Rob, Egor, Sjors So who were present anyway? Well, on my left were sitting Rob Mientjes, Egor Kloos and Sjors Rijsdam.

Rob's a young but creative designer and all-round programmer, currently hard at work at making the judges of his Pushing CSS contest finish their jobs so they can announce a winner.

Egor is well-known for his Gemination CSS Zen Garden design, which caused quite a snowball effect. The result of his design was that many people have since started using "MOSe" (coined by Dave Shea of the CSS Zen Garden), or Mozilla/Opera/Safari enhancements. The principle is simple, you just use CSS selectors that IE doesn't understand to add richness to your site for browsers that do. Egor made an entirely separate design using this technique, and as a result he is still receiving e-mails from confused fans, wondering why "the Garden is broken."

Sjors is co-director of Plerion, along with Hayo. Plerion is a Dutch web development agency that solely uses web standards. He's the more technical one of the two, focusing on PHP and databases rather than design.

Sjoerd, Alper, Mark On my right were Sjoerd Visscher, Alper Çuğun and Mark Wubben. Sjoerd and Alper were newcomers to the group, but they fit right in.

Sjoerd works at q42, a company you may have heard of already as both Anne and Mark are working there. Q42 is another Dutch web development company that uses web standards and best practices. Something we need more of.

Alper is a student in Media and Information Technology and is hoping to get the hell out of Delft as soon as possible. Though his site states that he's a great fan of espresso, I caught him drinking only one throughout the entire meeting yesterday. Alper is still in the process of being convinced of the importance of web standards and accessibility, though I think we're doing a good job at it. ;-)

Mark enjoys a fair bit of fame for his excellent work on sIFR, which is now pretty much his Javascript wizardry entirely. He's also refining his skills in Ruby, making himself an excellent all-round programmer. Oh, and if you ever run into him, make sure that whatever JavaScript-application you've created is free of memory leaks.

Then right next to me is the guy you see fumbling with a camera at the top of this post: Hayo Bethlehem. Contrary to what that picture may make you think, Hayo is a great photographer and designer, and is co-director of Plerion with Sjors.

Thoughts and musings

This group of people sparked plenty of thought-provoking discussions, so the meeting was not just about my conference idea. We discussed, in great detail even, the complexity of the Internet as a new medium. I went on a tangent explaining how I feel that most people in this world don't get that the Internet is incomprehensible. A lot of people are trying to understand the workings of the 'Net and act accordingly, but they all misunderstand or underestimate it. They all get it to an extent, but the Internet is too much of a living and breathing organism of its own, by now. It grows organically and exponentially, it goes in directions that nobody expected or even understands. Big companies make claims, such as "in 5 years we'll have the mobile web running all over the web of today" but 5 years ago, similar claims were made and we still see nothing of that. The web will do what the web wants, going 'round predicting major courses of the web is simply futile.

That was my tangent, anyway. We continued on the subject by discussing Google and how they, contrary to most others, seem to have a pretty good clue on what the Internet can and will do.

Alper was unfamiliar with Google's 20% rule, which - for those of you that aren't aware of it, either - means that all Google employees are allowed to use 20% of their work hours on their own projects. Creative innovations have been the result of this rule in many, many cases.

Accessibility in the Netherlands

Eventually we all headed out to Karalis Pizzeria for dinner, where just before the restaurant I encountered the image on the right. It's a wheelchair-ramp placed in front of a building that houses about ten public offices and companies of sorts. The ramp was placed only a few days ago, as it wasn't there when I went to Karalis last monday.

It's good to see some accessibility coming to life in the Netherlands. It's sad to realize that this is still one of the very first happenings of such throughout the country.

Moving on, at Karalis we discussed the official deprecation of the term "DHTML" (or re-using it for Deprecated HTML) as well as gathering anecdotes on bad practices we've heard over the years. "We want to save bandwidth on the menu and footer markup, so let's use frames!" or "the menu has to be visible all the time, so let's use frames!" Oh, is it clear yet that Frames Are The Suck™? We think so, anyway.

One last topic was my idea of turning these meetings into monthly events, as I'd announced on my blog before. People were generally in favor of this, with the following mentions:

  • they should be monthly, but held on saturday and sunday alternatingly, as some people can't participate if it's only held on either day each month;
  • themed meetings are a good idea, putting the focus on one topic each month. The same themes should not be held repeatedly on a sunday or saturday, of course;
  • indications of how sophisticated the meeting will be are going to be useful as we want to make them more public, hopefully drawing some new developers to them who can ask questions about standards-based web development practices. The meetings won't turn into workshops, but the idea is very similar;
  • presentations were quickly shoved off the table, as we'd be unable to hold the meetings in cozy restaurant environments if we were to have presentations

For now, we'll be doing some work behind the scenes, but you'll hear from DEWD again very soon. Perhaps under a different name, though. No, not SWEET (Standards-compliant Web Engineers Eat Toast). A better name.

There's a DEWD meeting pool over on Flickr with images from all of us, including bigger versions of the ones I've used in this post. Check it out for some fun pictures if you'd like, there's an especially silly one of me which may raise some concerns...

Alright NEWD guys, time for you to have your meeting and save your beer bill. :-)

Bookmark: Newsvine del.icio.us Digg

Comments

24 comments

#1 · Arie / Sjors · Jul 25, 2005 (15:15)

Not to be a bitch and all, but I think it was me who made the awesome suggestion to Hayo to remove the lenscap. Or am I gonna be bitchslapped for that as well? That's becoming an unhealthy obsession of you.

#2 · Hayo Bethlehem · Jul 25, 2005 (15:19)

I should probably make some kind of comment right about now.

#3 · Andy Hume · Jul 25, 2005 (15:36)

"all Google employees are allowed to use 20% of their work hours on their own projects. Creative innovations have been the result of this rule in many, many cases."

...which Google then own the sole rights too, along with your ass, bollocks, and any other personal delicacies you may hold dear. What a crock of shit.

Then they sack you when your 25 cos you realise your being shafted. ;)

#4 · AkaXakA · Jul 25, 2005 (16:21)

So what do you have to do to get invited to these meetings?

Andy: Quite right, it's all in Google's best interest!

#5 · Faruk Ateş · Jul 25, 2005 (16:27)

Sjors,
I only recall hearing Egor say something, sorry...

Andy,
Of course, but you'll find that plenty of companies have clauses in their contracts that mean that whatever you do in your own time that falls under work-related material, they can claim as well. Google is far from unique in that, what they're unique in is allowing their employees to just do their own stuff one day of the week.

akaxaka,
Nothing, just show up (and preferrably announce that you're coming beforehand, so that we know to wait for you if you're late). They're open to all!

#6 · Andy Hume · Jul 25, 2005 (16:52)

Of course Faruk - I think that's pretty much the case everywhere.

My point is that it isn't 'your own stuff', it's Google's stuff. What they are doing is blurring the line between work and personal projects - it's very clever, and invariably means that any output during the time you are employed by them is effectively owned by them.

How can you differentiate between your own projects and 'personal projects' that are actually owned by Google. It is very difficult to do - and in most cases impossible.

"Shit... I can't write a blog post/article now cos Google will own it". Obscene and stupid example but you get the point. ;)

There is a sense of freedom surrounding the concept but experience tells me it may be the opposite. And hey... get this. They even hire drivers to take and pick up your car when it needs a service, so you don't need an afternoon off. How cool is that? ...or not - depending on how you look at it. Get my meaning? Freedom - I think not.

Anyway, I've *definitely* said enough. Apologies for ranting in your comments. :)

#7 · Faruk Ateş · Jul 25, 2005 (16:57)

Andy,

True, but that's a matter of semantics. "Your own" -- okay, so it's not YOUR property anymore, even though you came up with it, but you can still see it as your own toy to play around with during work hours. You don't own it, but to them it still feels like their toy and it's more fun. It's a sense of freedom that they get from this rule. You may think of it as an un-free form of freedom, or not freedom at all, but most people will be more than happy to have "the freedom to work on your own ideas at work." I have that freedom to a small extent, and I'm really happy about that. It makes work much more pleasant.

No apologies necessary, this is an interesting discussion and it's exactly what Comments are for :)

#8 · Andy Hume · Jul 25, 2005 (17:05)

You're probably right. Perhaps I'm just an over worked cynic. ;)

Probably comes from my self-employed background, where you sit about waiting to be shafted. ;) I actually think a job with Google would be quite fun - if only to find out what the buggers are up to!

#9 · AkaXakA · Jul 25, 2005 (17:13)

Right Faruk: 'Sence' of freedom. That's the key to it. Andy's of course right that in reality it's really just benefitting Google.

Anyway, my point is, that this doesn't make Google a force for good, nor for evil.

#10 · Faruk Ateş · Jul 25, 2005 (18:32)

Andy,
They didn't want me (I once applied), sadly. Though, I wasn't a well-known weblogger / Standards-evangelist back then yet, had not much to show for my skills that was available or even finished, so I can't blame them ;) Would be fun indeed, I reckon...

AkaXaka,
You're right, this doesn't make Google by definition good nor evil. I didn't mean to indicate that, just that Google's 20% rule has been the cause of many fun innovations. Most of what comes out of Google Labs was crafted initially during that 20%. :)

#11 · Robert Nyman · Jul 25, 2005 (19:52)

I once applied to Google to, and, as Faruk, before my bloggin' days.
They didn't want me either... :-|

#12 · Alper Çuğun · Jul 25, 2005 (19:57)

Hey, I'm just for standards as much as the next guy. I'd like them to be easy and sensible though. Further I think asking questions from a contrarian viewpoint can be very useful at times.

I was aware of the 20% thing, but did not know if anything had come out of that after the Orkut fling.
And to Andy who started this thing off pretty negatively: I get the impression that if you want to be employed somewhere Google is a better place than most. Working there could actually be fun, you know. And being allowed to leverage the resources of a large company to further your ideas might also be fun.

Just a thought.

#13 · Faruk Ateş · Jul 25, 2005 (20:11)

Alper,
Oh definitely, it was great that you raised the question. We had a very fruitful debate coming out of that, so I think it was a very good thing. :)

And good point about how it can simply be great fun to have access to Google's resources and the ability to use them for your own ideas. That's definitely something that makes a big difference.

#14 · Egor Kloos · Jul 25, 2005 (20:28)

1. Sjors was the one to mention that Hayo might be able to take better pictures without the lens cap. I got my que from him and agreed, but I'll gladly take the credit.

2. Google dominates the markets they're active in but are also respected for their ability to truly innovate. Hiring young hopeful's brings in a fresh view and the drive to innovate while at the same driving resource costs down. Google is not only one to do this but they do seem to gain more effect from it. That's the Google magic, driving ideas from lower down the company and help them float to the surface.

3. Deprecating buzzwords is an arrogant thing to assume to be able to do. We'll give it a shot anyway. Not everyone agrees in the case of 'DHTML' but I'll be happy to persuade them to think otherwise. The 'DHTML' phrase does not have forward motion in a marketing and even PR sense. It's solidly anchored in the past. Some bridges need burning.

#15 · Faruk Ateş · Jul 25, 2005 (20:51)

Egor,
3) Agreed. DHTML is just one that really needs to go, gosh-darnit.

#16 · Hayo Bethlehem · Jul 25, 2005 (20:59)

1) Faruk made me take out my camera, in order to shoot a pic of me holding the camera... and so the saga begun..

3) I'm sorry, which ones were we deprecating again? AJAX, Web2.0, DHTML, or all?

#17 · Faruk Ateş · Jul 25, 2005 (21:58)

I didn't make you take out your camera, we all did. :D

AJAX isn't being deprecated because it's being used consistently and has good functional meaning to all who encounter it.

#18 · Sassy · Jul 26, 2005 (01:10)

you need to recruit a woman or two into that group! i know you're dewds and all, but still. :p

also, to those of you who think creating your "own" stuff at Google only benefits Google - maybe ask someone who's worked at a company like that how much that atmosphere benefits their own personal resume and portfolio and in the long run, their career. if you're going to work at a company (and not freelance or run your own company), then being able to work creatively and being encouraged to do your own thing is a rare treat.

#19 · Sassy · Jul 26, 2005 (01:11)

p.s. my god your hair is getting long faruk! try parting it on the side. :)

#20 · Faruk Ateş · Jul 26, 2005 (11:05)

Sassy,

Indeed, and I happen to have such an atmosphere at work, and thus such freedom for creative working. Very pleasant, I say. :-)

And pshaw, you were the one that told me to let my hair grow long!

#21 · Egor Kloos · Jul 26, 2005 (12:34)

Right you are Sassy, we're slowly turning into webhead hippies. Kill me now.

btw. I offered to come in a dress, but the lads were having none of it. So much for the female angle.

#22 · Sassy · Jul 26, 2005 (13:50)

i never said that it was bad that your hair was getting long, faruk. :p i just haven't seen a pic of you in a while.

#23 · AkaXakA · Jul 26, 2005 (14:34)

Web2.0 is dead, long live Web2.0.1 !

Buzzwords will always be invented, so I guess we should just work hard at having buzzwords that will make people use things properly.

#24 · Genry Henz · Dec 24, 2005 (09:35)

I too would want to visit there ;)

All times are in CET. It is now 19:45.