The myth of Common Knowledge
Recently I have discovered a really sad pattern of behaviour in the webdevelopment world and its communication channels (blogs, mailing lists, forums, IM): People don’t share information as they are afraid that it may sound too trivial, not relevant or has been discussed to death already.
This is happening in companies, too: new developers hold back in asking questions or showing others what they have done and how they solved a certain problem as they fear it may make them sound inexperienced and helpless.
It is an overused expression, but there really are no stupid questions. Repeating them over and over again without taking on information you get in answers makes you appear stupid, but the question in itself stays relevant.
There is no gain in all of us being smug about knowing it all and not really caring to ask for help with small nagging issues in favour of spending days to solve them ourselves. Asking a colleague is not a weakness but simply shows that you care about the problem and you want a second opinion to test your approach (XP fans will remember the pair programming idea).
I have some blog posts here that get an amazing amount of hits that some people asked me why I ever bothered to put them up. Things like “How to remove the border around a linked image“, “Using CSS classes to avoid loops, Printing Background Images or Linking an Icon and a text and apply a roll-over state. This proves to me that the demand is there, and that things we consider “Common Knowledge” might not be that common.
There is a rather cool site that got into the direction of offering information like this, called Bite Size Standards. However, after an initial honeymoon period of posts it seems to have gone back to bed for a beauty sleep.
In my current work, Tom Croucher tries to start implementing something called “Lightning Talks”, which are 5 minute presentations of someone of the team to the team about a certain issue and how to solve it, followed by a 10 minute question and answer session.
Battling the Common Knowledge Myth
Now, as a web site like bitesize standards means work and dedication and filtering, I propose another idea:
Let’s post a lot of these small “Issue - Solution” blog posts and simply use a unified Technorati tag for them, for example “[tag]webdevtrick[/tag]“. That way other bloggers or sites can get the feed on that tag and show them, and we can advertise the idea on mailing lists every time the same question gets asked. Consider it a decentralised FAQ with Technorati as the aggregator.
I’ll publish results here, and simply will start doing that myself, so even if I am wrong with this idea, it doesn’t cost me much time.

September 29th, 2006 at 8:15 pm
Well said -
I think some people fear posting simple things because they have already been said. However, they are forgetting that many of these “basics” have been said in books, articles, or conferences that are not easily accessible on the web.
September 29th, 2006 at 9:51 pm
Brilliant idea! Does “webdevtrick” include other things? like my bete noire: incorrect copyright dates?
September 29th, 2006 at 10:14 pm
Surely, Chris, you shouldn’t tag this article as ‘webdevtrick’ or you are already diluting the knowledge pool ;)
Great idea.
September 30th, 2006 at 11:01 pm
You need RSS feeds that filter out posts on relevancy.
Or search engines that work smart, eg sorted on date, tags etcetera. If you google, you get scattered info. You lose time and track of everything. How about an advanced bookmark extension that eg is connected to your bookmarks and search engine entries?
October 3rd, 2006 at 7:17 pm
Lightning talks!!! What a cool idea!! I would not be the one to give one though because my wife has been known to describe me (accurately) as, “if you want to make a short story long, let Jules tell it”.
My feeling is that many of use on the Evolt list and other places have been around for a while so we are looking for more advanced help and therefore, we tend not to discuss the basics any more.
Perhaps some of us should put together (either individually or together) an introduction to HTML, CSS and JavaScript. Many of the HTML tutorials on the ‘Net are old and not based on proper standards — some of us could work together to replace these.