Illegible work

When James Scott uses the word legible, he doesn't refer to handwriting that is clear enough to read. He uses the word more broadly to mean something that is easy to classify, something that is bureaucrat-friendly. A thing is illegible if it is hard to pigeonhole. I first heard the term from Venkatesh Rao's essay A Big Little Idea Called Legibility.

Much of the work I do is illegible. If the work were legible, companies would have an employee who does it [1] and they wouldn't call a consultant.

Here's a template for a conversation I've had a few times:

We've got kind of an unusual problem. It's related to some things I've seen you write about. Have you heard of ...?"

No, what's that?"

Never mind. We'd like you to help us with a project. ..."

Years ago, when people heard that I worked in statistics they'd ask what programming language I worked in. They expected me to say R or SAS or something like that, but I'd say C++. Not that I recommend doing statistics in C++ [2] in general, but people came to me with unusual projects that they couldn't get done with standard tools. If an R module would have done what they wanted, they wouldn't have knocked on my door.

Doing illegible work is a lot of fun, but it's hard to market. Try typing Someone who can help with with a kinda off the wall math / computer science project" into Google. It's not helpful. Search engines can only answer questions that are legible to search engines. Illegible work is more likely to come from word of mouth than from a search engine.

***

[1] Sometimes companies call a consultant because they have occasional need for some skill, something they do not need often enough to justify hiring a full-time employee to do. Or maybe they have the skills in house to do a project but don't have anyone available. Or maybe they want an outside auditor. But in this post I'm focusing on weird projects.

[2] When I mention C++, I know some people are thinking But isn't C++ terribly complex?" Why yes, yes it is. But my colleagues and I already knew C++, and we stuck to a sane subset of the language. It was not unusual to rewrite R code in C++ and make it 100x faster.

Why don't you just use C?" These days I'm more likely to write C than C++. Clients don't want me to write enterprise applications, just small numerical libraries, and they usually ask for C.

The post Illegible work first appeared on John D. Cook.