Coding Horror

programming and human factors

Lazyweb Calling

It's hard to pin down the exact etymology of the word Lazyweb, but it seems to have one primary meaning:

  1. Asking a question of an internet audience in the hopes that they will be able to find a solution that you were too lazy or inexperienced to find yourself.

The word is attributed to old-school internet ultrageek jwz, which I could totally believe. Or it might have been designer Matt Jones. It can also have a more specific meaning in the context of writing code, as Clay Shirky notes.

  1. Waiting for someone else on the internet to write/build/design what you were thinking of.
  2. Describing something in the hopes that someone else on the internet will write/build/design it.

Of course, this kind of feature daydreaming can have amusing results.

The common theme of all Lazyweb requests is a tacit acknowledgement that none of us is as dumb as all of us.

demotivational poster: Lazyweb. None of us is as dumb as all of us.

I don't mind Lazyweb requests, within reason. Contrary to popular belief, there is such a thing as a stupid question. It's asked by people who failed to do even the most basic kind of research on their question before they asked. I'm not expecting everyone to read a 32 page document prior to asking any questions, but at least cover the basics before casually deciding to make your problem everyone's problem.

There's nothing wrong with harnessing the collective power of the internet to solve a problem you tried-- and failed-- to solve yourself. Assuming you get an answer, once web crawlers find and index your problem, that question and answer is part of the fabric of the web and can potentially help any future travellers as well. Done right, Lazyweb is a part of the net public good.

Written by Jeff Atwood

Indoor enthusiast. Co-founder of Stack Exchange and Discourse. Disclaimer: I have no idea what I'm talking about. Find me here: http://twitter.com/codinghorror