The world of ideas is a very fractal place.

Fractals, you’ll recall, are geometric constructs in which the same forms recur at different levels of magnification. At close range boulders look like mountains, rocks look like boulders, and grains of sand look like rocks. You have a hard time recognizing which scale you’re looking at.

Ideas are like that too. The same notions and forms recur in wildly different situations, scales, and contexts.

Years ago I read an article contrasting polling and interrupt-driven protocols. I remember little about it other than that the two, although different from an engineering perspective, led to the same user experience when implemented.

Here’s an idea you can take to the bank: Two radically different ways of doing things can sometimes lead to indistinguishable results. It’s enough to make you stop worrying whether Ethernet or Token Ring is better.

What’s that? You’ve already stopped worrying? That’s great, because you can pay closer attention to another fractal recurrence of the polling/interrupt question: the hype over “push” technology.

Pull/push is just polling/interrupt all over again. (I could be wrong, but I doubt it, as Mike Royko used to say.) Push is an interrupt-driven protocol – it’s intrusive. Pull, in the form of offline browsers, is polling – your system initiates the request. Either way you get new information, sorted into channels (another the-name-is-new-and-not-much-else concept), without your having to manually intervene. The only difference I can see is that offline browsers adhere to existing Internet standards instead of introducing proprietary technology.

Push technology should have some network engineering advantages, but even here the situation is pretty blurry. You can implement pull technology so it has no more impact on bandwidth than push, by designing your Intranet so employees stay inside your firewall. The logic behind this is to treat cyberspace the same way we deal with real space.

When William Gibson introduced the term “cyberspace” in his groundbreaking novel Neuromancer, he gave us a valuable way to look at what we do (sadly, the cyberspace metaphor has since been beaten into a cliche). When employees interact with their computers, they are working in the corner of cyberspace we happen to manage.

Let’s compare how we approach company real space and cyberspace. In real space, we pay attention to color schemes, cubicle height, ergonomics, file storage, and some of the aesthetics. We expect employees to personalize their space, recognizing that they spend a lot of their lives inside. Dilbert, and sometimes even this column, get put on the cubicle walls.

In cyberspace we begrudge employees the right to select their own wallpaper, screen resolution, screen savers, and reading matter, calling it “futzing.” It’s supposed to be a colossal corporate expense, and we gripe around the coffee pot about users wasting corporate bandwidth surfing the Web.

Here’s a new mission statement for you: Your job is to turn your company’s little corner of cyberspace into a rich, fulfilling, pleasant, productive place to work. Set up your Intranet so employees don’t want to go to a PointCast server. Give them the news, weather, stock prices, and commuting times. Heck, try designing mission-critical systems so they’re fun to use.

Before you fly off the handle, put yourself on the receiving end of the deal. Who do you want running your company cafeteria, a chef or a dietitian? You have to eat there; employees have to work in your part of cyberspace.

Yes, I know we’re talking about a “waste” of company resources. So is your company newsletter. And employees could survive by eating duckweed salad and tofu burgers (yuck!) in the cafeteria, too. The same idea applies in more than one context: If making your cafeteria a pleasant environment isn’t a waste, then making your corner of cyberspace pleasant isn’t a waste, either.

We seem to have forgotten one of the basics: Making the time employees spend at work pleasant and enjoyable can reap large benefits, whether or not accounting can tally them up in the general ledger.

Should employees really be spending their time reading Web pages that don’t directly relate to their jobs? I don’t know, but I do know that lots of executives spend company time reading The Wall Street Journal, and I’d bet that time has more impact on their career advancement and personal investment portfolios than it does advancing the company strategy.

If you’ve looked for a job recently you know the awful statistics: fewer than three out of every ten jobs are filled through normal channels.

Let me translate this for you: trying to get a job by sending your resume to Human Resources in response to an employment ad is a sucker bet.

The system is broken … badly broken … and the numbers prove it. What’s truly pitiful is that hiring managers don’t like the current state of affairs any more than job seekers do. If they did, the numbers would be very different.

Don’t believe me? Keep an eye out for “Ask the Headhunter: reinventing the interview to win the job” by Nick Corcodilos, which should be hitting the bookshelves this August. Nick has been in the headhunting game a long time, and has succeeded by ignoring most of the nonsense spouted by what he calls “the employment industry”. As Nick points out, “You will encounter many people who are not really the person who will hire you – they are the go-betweens who want you to hunt for a job in a way that’s convenient for them.”

Actually, he’s talking to both the applicant and the hiring manager, because when you’re hiring you’ll also deal with go-betweens.

That’s exactly what you want from HR, whether you’re looking or hiring: To connect the applicants most likely to succeed with the hiring managers who need them. Far too often, HR screens out the very people most likely to succeed instead: people who are stretching, who want a new challenge, who haven’t done the job you’re posting but who will do whatever it takes to succeed at it.

What’s the problem? In most companies, HR has an unstated mission: keep the company out of court. It does so in any number of ways: ensuring compliance with various employment laws; creating personnel handbooks so everyone “knows the rules”; helping managers define position requirements in terms of “objective” evaluation criteria; screening resumes to ensure hiring is done by strict skill-to-task matching … (which is now an automated process, give me strength!).

Keeping the company out of court is a Good Thing (GT, to use the acronym). Of course, people will sue you anyway, and in the meantime you’ve hired and promoted a lot of the wrong people, damaging your company’s ability to compete.

(Now before you flame me, let me draw a clear distinction between individual human resources professionals and the HR industry. I have quite a few friends who work in HR and as a whole they’re goodhearted people who seriously want to help both their employer and their coworkers succeed. Few are given a chance: their industry conspires to prevent it.)

Years ago a friend of mine, new to management, asked the most important consideration when hiring. “Hire a person, not a resume,” I told him. “The skills you’re looking for today won’t be the ones you’ll need next year, so find people with the right aptitude and a habit of succeeding. They’ll acquire whatever skills they need to succeed. Even better, they’ll do the jobs that need doing, not just the ones you think are important.”

I still think that was good advice. Here’s some more: when writing a job description be specific when it comes to attitude and tangible results, and as general as you can when defining skills. If you’re hiring a database administrator, for example, you don’t want someone who will turn into the “data police” and do want someone who thinks of the job as a way to make programmers more effective. Do you really care that her ten years of experience are in Sybase and Oracle while you use Informix?

Turn it around: if you’re a database administrator who knows Sybase and Oracle, do you avoid positions that will cause you to use Informix?

Nick Corcodilos will tell you more: that both applicant and hiring manager need to conduct interviews that are about doing the job. The applicant should do the job in the interview. The hiring manager should ask the applicant to do the job in the interview.

Because, in the end, you want to hire someone who can do the job, not someone who can do the interview.

Right?