Against Originality

Surely I can’t be the first per­son to say it: Our culture’s demand that every great mind be orig­i­nal has become a sti­fling horror.

First, because the sup­posed traits of “orig­i­nal­ity” are a sham, except among the insane. You’re rid­ing the yel­low line next to “schiz­o­phrenic” if you’ve writ­ten an unin­tel­li­gi­ble con­text­less ram­ble in a pri­vate lan­guage. You may already be a sociopath if you con­sis­tently dis­avow the con­ver­sa­tions and train­ing and cul­tural embed­ded­ness of your work’s greater con­text. You’re prob­a­bly delusional—even though we’re all out to under­mine you—if you keep ignor­ing the fre­quent simul­ta­ne­ous appear­ance of sim­i­lar works in diverse set­tings around the world.

And as any decent crazy per­son should, you will get upset when you see “your” idea pop­ping up all over the world as if other peo­ple had stolen it.

Sec­ond, because orig­i­nal­ity is an arti­fi­cial lim­i­ta­tion on a con­tex­tual but intrin­si­cally unlim­ited resource. Cre­ative problem-​​solving. Could you build me a house for this land­scape unlike other people’s? Could you make me think about the mono­lithic raw fact of the world, at least one facet which con­cerns me today, in a way nobody else ever has? Could you design me a drug for my dis­ease, or a valve for my plumb­ing, or a rocket for my war, or a chair which inspires my aes­thete crowd in a way oth­ers in my salient cul­tural net­work will not have expe­ri­enced? Could you please write a book for me, refer­ring to the touch­stones of my cul­tural iden­tity, but which at the same time takes an eye-​​opening new stance?

But don’t use any weird mate­ri­als or tech­niques or too much other funny stuff, of course. Make it just dif­fer­ent enough.

Third, because the illu­sion that con­tin­gent cre­ativ­ity is lim­ited fos­ters rent-​​seeking behav­ior where no rea­son­able claim exists. Of course I will cite you when I explain to my stu­dents about your evoca­tive imagery of rain­drops on cer­tain vari­eties of flower petals, and also your view on the whiskers on kit­tens. I agree to pay that license fee when­ever I drink from a cup with the open­ing cun­ningly placed at the top, rather than the bot­tom. I will hap­pily relin­quish this thing my peo­ple have known since before the mis­sion­ar­ies came, hav­ing heard of your recent patent of the active com­pounds therein. All I have are these cites, whuffie, money, jail time and pub­lic apolo­gies: please take whichever you feel best ame­lio­rates my mis­take.

Not because yours is sub­stan­tially bet­ter than this other one, but because it has been duly recorded in the Big Book of One Law that you used up the entire fuck­ing idea when you staked your claim.

Fourth, because the rent-​​seeking infra­struc­ture sup­ports leeches. Not much more to say on this, right? We will pur­sue your claim. We will root out the inter­lop­ers. We will cre­ate and main­tain a cen­tral cat­a­log that includes your work. We will mon­i­tor the medium itself so that your priv­i­lege is not under­mined. We will strive cease­lessly to extend your priv­i­lege, indeed until well after you are dead.

For a nom­i­nal frac­tion of the fees you are owed.

These can­not be new sto­ries. And I can’t be both­ered to look up who’s been writ­ing about them.

Except every­body since for­ever.

I’m not rant­ing because I’m tired of the easily-​​ridiculed but oner­ous legal restric­tions, the grow­ing tis­sue of lies cen­tered around “cre­ativ­ity” and “exclu­siv­ity” in our legal frame­work, or any of that old crap. Those are easy. Every­body is mad about them.

Hell, we were mad about all that crap before the rest of you started jump­ing on the band­wagon.

No, I’m upset because I got mad the other day when an ass­hole Ger­man engi­neer I know from a con­fer­ence pub­lished a preprint where he posed an “orig­i­nal” the­ory essen­tially iden­ti­cal to stuff we talked about years ago—and he didn’t cite any­body I think he should have, imply­ing that he is map­ping out some New Fron­tier of Thought.

And because Stephen Wol­fram, the man per­son­ally, pisses me off—because his doorstop rel­e­gates the life’s work of smart peo­ple I know to occa­sional men­tions in the tiny appen­dix, imply­ing to most peo­ple that he invented Sci­ence Itself.

I’m upset because when I look at some­thing in some ran­dom book or web­site, or hear some­thing, or some­body men­tions it to me, and it’s a thing I once felt pride in doing or even know­ing, but now every­body does or knows it —I am dri­ven to feel that they’re doing it wrong.

I know because it was some­thing I invested actual think­ing time in back when. And here it is now, much later, being pop­u­lar­ized! And if you look, none of the “orig­i­nal” cre­ative peo­ple who made it a thing to me are men­tioned. It’s all these new main­stream immigrants.

What right have they to it, with­out giv­ing credit where it’s due? Worse, what right have they to use our words to mis­lead their naive fol­low­ers now?

This has hap­pened through the years with “Chaos the­ory”, “com­plex­ity” research, “bio­com­put­ing” research, “agile” soft­ware devel­op­ment and man­age­ment, “cowork­ing”, the “social Web”, “social net­works”, “Prag­ma­tism”… that’s just a quick off-​​the-​​cuff list for me. I did early work with a thing, and nobody much cared, and then much later some­body else did slightly over­lap­ping work, and now it’s all the fuck­ing rage.

And I think Dammit, in my day we were try­ing to save the world, not just sell wid­gets like this ass­hole. Why are they all lis­ten­ing to him? Doesn’t any­body ever read what we said back then when this was really new?

Your mileage may vary, but I will make you eat your hat if you haven’t expe­ri­enced this same emo­tion when faced with inter­lop­ers and other late­com­ers announc­ing their dis­cov­ery of cer­tain styles and gen­res of “sci­ence fic­tion”, “paint­ing”, “pho­tog­ra­phy”, “local food”, “book arts”, “user expe­ri­ence”, “func­tional pro­gram­ming”, “punk”, “con­ser­vatism”, “pro­gres­sivism”, “min­i­mal­ism”, “sus­tain­abil­ity”, “blog­ging”, “anar­chism”, “free verse”, “that crap they call ‘role­play­ing’ these days”, “that crap they call ‘news’ and ‘jour­nal­ism’ these days”, “eco­nomic devel­op­ment”, “genet­ics”, “peren­nial gar­den­ing”, “aero­nau­tics”, “com­pas­sion”, “Chris­t­ian faith”, “Bud­dhism” and so on.

Some folks might think I’m describ­ing envy; that one has a sense of vio­la­tion because these new­fan­gled pop­u­lar­iz­ers are get­ting all the rents one feels are owed to the “real” inven­tors. But it’s not.

I admit it might be a bit like pride. But a strange sort of pride, where you didn’t real­ize you had any until a plug was pulled and it all drained out.

No. I think not.

I think it’s a lot more like the feel­ing you get—as my wife Bar­bara pointed out a cou­ple of days back (see what I did there?)—when you first real­ize your child is her own per­son, and that she’s made her own deci­sion, and that despite all your early work to bring her up right, she’s going to hare off in her own direction.

Because you know what’s over in that direc­tion. You know the has­sle and dan­ger, the illu­sions and pain, the inef­fi­cien­cies and unsat­is­fy­ing expe­ri­ences she’s head­ing for, because you expe­ri­enced them all years ago. You tried to keep her from doing that stu­pid stuff, and tried to get her to see the cool stuff, the life-​​saving and sim­ple stuff, the right stuff, but she’s thought­lessly skep­ti­cal about any­thing she actu­ally heard. And worse, some­day she will come back and announce as “new” some­thing you knew all along.

I think I’m upset because “orig­i­nal­ity cul­ture” makes me feel that all the time now. Not con­tent to be a mere hip­ster claim­ing to have prior knowl­edge of every cul­tural and intel­lec­tual phe­nom­e­non, I am reduced to some hor­rific recur­sive hip­ster, who feels that sad­ness when­ever I am shown some­body is explor­ing a known thing with their own per­spec­tive.

Because of course it’s “orig­i­nal­ity cul­ture” that makes me imag­ine that my expe­ri­ence of that thing, long ago, which I failed to com­mu­ni­cate to these new­com­ers, is in any way salient to what they have going on in their lives. When I did it, it was new, and we expended valu­able resources and took per­sonal risks to do all that, and coined all these new terms to describe the amaz­ingly insight­ful stuff nobody had ever talked about before.

I like to call this the Tozier Effect.

Of course the ass­hole Ger­man can talk about stuff we both have done, for the same rea­son I can: it’s cool and it will help the world to know more about it. And because I am also an ass­hole Ger­man to somebody.

Of course Wol­fram can be the Edi­son of the Sym­bolic World, for the same rea­son Edi­son could: it’s cool and it will help the world to know more about it. And because I have also played Edi­son in my time.

And the nou­veau “agilists” and “com­plex­ol­o­gists” and “Web 3.0 gurus” and the lat­est Busi­ness Rev­o­lu­tion­ar­ies and TED-​​talking Inspi­ra­tional Crowd are wel­come to carry on.

There’s enough rea­son for me to ques­tion the very notion of orig­i­nal­ity just in the fact that we so rarely ques­tion the vocab­u­lary we use to dis­cuss it.

I don’t care if you keep using those terms and notions… mostly. Why should I waste time striv­ing to under­mine your claims about how “orig­i­nal­ity” works? Espe­cially by fram­ing my argu­ments in that same ques­tion­able lan­guage of uni­ver­sal­ity, exclu­siv­ity and rights? That’s a sucker’s bet.

I have evi­dence that I’m going to turn out being right when I stop think­ing and talk­ing about “orig­i­nal­ity” in your terms. But I also have evi­dence that you do real good by using those terms. And I have evi­dence that we’re both wrong and should use some other words and ideas instead.

’Tis but the nature of the world.

That said, I’m just decid­ing to stop using those words, even around you. Even when you talk about “your” “cul­ture” “need­ing” to “pro­mote” “inno­va­tion”, even when you talk about “eco­nomic” “growth” and your cul­tural “oblig­a­tion” to be “cited”, or how “artists” will “starve” with­out your “support”.

We’re not going to have those con­ver­sa­tions with those ideas any more, you and me, is all I’m saying.

And I will be a bit hap­pier, and you will be sad and confused.

And that’s an improve­ment, in my book.

Well, OK. Except for one thing.

When it becomes clear that your vocab­u­lary about own­er­ship and rights and pri­or­ity and value is clearly hurt­ing peo­ple? That’s when we will inter­vene. Your wounded ego, your claims that imag­i­na­tion is a zero-​​sum game, your rent-​​seeking, your leech squad—they will become our tar­gets when you cross that line.

Not you. We’re not going to tar­get you. But when you sharpen your final vocab­u­lary into a harm­ful tool, or a cage, or a wall—that’s when we are sup­posed to come along with the breaker bars.

It’s OK. There are other ideas and words in the world. There are always other ones. And you’d be sur­prised how help­ful and good it can be, some­times, to just start with a new batch.

Well, not new as such. You know what I mean.

The Mirror Dojo: Genetic Programming for Agile Teams

This is the cur­rent iter­a­tion of the Genetic Pro­gram­ming work­shop née Agile Team Dojo I’ve been work­ing on over the last few years.

I’m look­ing at the Michigan/​Ohio/​Indiana region for an inter­est­ing place to run it. If you’re inter­ested in sched­ul­ing me for a two– or three-​​day work­shop, feel free to con­tact me online.

You know how to do that.

The Mir­ror Dojo: Genetic Pro­gram­ming for Agile Teams

Genetic Pro­gram­ming has been actively researched and pro­moted for more than a quar­ter cen­tury. It’s a broad col­lec­tion of design prac­tices and mod­el­ing tech­niques for the “auto­matic” dis­cov­ery of abstract pat­terns and struc­tures.

And that means full-​​fledged pat­terns and struc­tures: algo­rithms, pre­dic­tive mod­els, com­plete mechan­i­cal and opti­cal and elec­tronic designs, and even blue-​​sky arti­fi­cial intel­li­gence systems.

Some of the field’s big hits include:

Sexy stuff! Nerds like us love it.

Bet­ter yet: I can describe all the basic design prin­ci­ples of Genetic Pro­gram­ming in four sen­tences. It’s so sim­ple to describe that I’m com­pletely con­fi­dent that I can help you you—a com­pe­tent soft­ware devel­oper work­ing on an agile team—write a work­ing GP sys­tem in an hour or so!

And that’s just what we’ll do in this two-​​day workshop.

But there’s one more thing.

You’ve prob­a­bly noticed that I always put extra-​​scary scare-​​quotes around “auto­matic” when­ever it comes up.

Dur­ing this dojo we’ll be approach­ing this mate­r­ial as an agile team. We’ll build at least two full-​​featured genetic pro­gram­ming sys­tems, and we’ll bump very quickly into those scare-​​quotes.

And that’s what this work­shop is about.

See, I’ve been work­ing in this field for most of 20 years. It turns out that even after all that time, there’s a large and trou­bling gap between the tuto­ri­als and demos of genetic pro­gram­ming, and suc­cess­ful problem-​​solving with GP. You can mea­sure that gap in terms of time, or com­pu­ta­tional resources, or expected qual­ity of results.

Sound famil­iar?

Much of the advanced aca­d­e­mic research being done today in Genetic Pro­gram­ming focuses on ways to increase the com­pu­ta­tional power, to bring more proces­sors and faster code to bear so that “auto­matic” problem-​​solving has a bet­ter “chance of suc­cess” on a com­plex problem.

Ah, look; more scare quotes.

See, in this work­shop we’re not advanced aca­d­e­mic researchers in Genetic Pro­gram­ming. We’re much bet­ter pre­pared than they are: we’re an agile team.

In the work­shop we’re going to be explor­ing how to tell our lit­tle arti­fi­cial “team” of “auto­matic devel­op­ers” what it is we want, and how they should go about mak­ing it for us, and (because GP just works) they’ll be “releas­ing soft­ware” for us. What we’ll be doing is design­ing the rules by which they solve our prob­lem: espe­cially the ones that spell out how we want them to inter­act with one another.

Which should explain the name of this dojo. And maybe even why it will take lit­tle bit longer and a bit more effort than most oth­ers you’ll run into.

Scope: This is a two– or three-​​day work­shop, for three to eight soft­ware devel­op­ers, engi­neers, coaches, design­ers, sci­en­tists, and other nerds.

The major­ity of par­tic­i­pants should be famil­iar with com­mon platform-​​agnostic pro­gram­ming lan­guages (Ruby, Python, Java, Smalltalk). They should be com­fort­able work­ing in an agile team: we’ll col­lec­tively work in one shared pro­gram­ming lan­guage, and rely on auto­mated unit and accep­tance tests, rapid release sched­ules, agile plan­ning, and pair pro­gram­ming. There should be enough lap­tops for every pair to code, and net­work con­nec­tiv­ity enough to use github for ver­sion con­trol and coordination.

On the first day of the work­shop (6 hours plus lunch) we’ll estab­lish the social infra­struc­ture, and imple­ment a sim­ple but full-​​scale genetic pro­gram­ming sys­tem for sym­bolic regres­sion. At the end of the day, we’ll choose an advanced project for the next day.

Because we’re all nerds, you and I both know you can’t “stop work­ing” after just five or six hours—and that’s fine. But the work day for the project is six hours plus lunch. So no com­mits overnight!

On the sec­ond day (6 hours plus lunch) , we’ll use genetic pro­gram­ming to address a tech­ni­cal prob­lem where results are obvi­ously practical—and prob­a­bly pub­lish­able.

In three-​​day work­shops, the final day can be used (at the team’s dis­cre­tion) for either refine­ment and pub­lic release of tan­gi­ble prod­uct from the prior days, or for a third project using dif­fer­ent GP design patterns.

Why?: The dojo is just what it says: an expo­sure for agile soft­ware devel­op­ers to a sexy but poorly-​​understood tech­ni­cal prac­tice with great eco­nomic poten­tial in the com­ing years. At the same time they’re learn­ing about the tech, they’ll be sur­fac­ing aspects of their own work, and the way agile prac­tices mold project man­age­ment in the “real world”: require­ments, goal-​​settings, information-​​sharing, met­rics, col­lab­o­ra­tion pat­terns, infra­struc­ture, deliv­ery sched­ules, and even the juris­dic­tion of man­age­ment vs. developers.

Cost: The most impor­tant cost for this exer­cise is the par­tic­i­pants’ inter­est and atten­tion. If those have been made avail­able, the only finan­cial costs are for the venue, travel, food and board (where needed) for the participants.

The only thing coworking needs to be

I seem to have a lot of trou­ble with ter­mi­no­log­i­cal shifts.

When I was a young com­plex­ol­o­gist, “chaos the­ory” meant some­thing about deter­min­is­tic dynam­i­cal sys­tems. But grad­u­ally the spe­cific field of math­e­mat­i­cal research got pop­u­lar, and stu­pid man­age­ment con­sul­tants (I say this with love) decided they would use the phrase to mean some­thing about touchy-​​feely intu­itive­ness and dinosaurs and more like what they and the Ancient Greeks assumed it meant all along, about dis­rup­tion and meaninglessness.

When I was a young the­o­ret­i­cal biol­o­gist, “com­pu­ta­tional biol­ogy” meant some­thing about agent-​​based mod­els of evo­lu­tion­ary and mol­e­c­u­lar dynam­ics, and explor­ing emer­gence. But cheap com­put­ing resources became avail­able to every­body and their brother, and sud­denly the Peo­ple With Too Many Base Pairs On Hand (I name them with respect) decided they would use the phrase to mean some­thing more about sequence align­ment, and not mul­ti­scale struc­tural biology.

When I was a slightly older com­plex­ol­o­gist, “com­plex sys­tems” went through the same exact bull­shi­ti­za­tion process as “chaos the­ory” did before it. Now, to be frank, it’s just mostly powerlaw-​​bullshit-​​on-​​networks (I say that with no lit­tle bitterness).

Luck­ily, “astro­bi­ol­ogy” doesn’t really have an easy map­ping to busi­ness con­sult­ing, so that one was kind of safe. But—amusingly enough—I didn’t get to do it for very long before the good old Ivy League Cell & Mol­e­c­u­lar Biol­ogy Depart­ment I was work­ing in decided that astro­bi­ol­ogy itself was bull­shit, or at least not Cell & Mol­e­c­u­lar Biol­ogy the way they did it, and they kicked me out. What the heck; turn­about is fair play.

Then there’s “social net­work”, which used to be a bunch of cir­cles and arrows, not a street term for “pri­vacy inva­sion”. There’s “genetic pro­gram­ming”, which became just-​​plain-​​symbolic-​​regression. And “agile soft­ware devel­op­ment”, which used to be about bring­ing value and reduc­ing the risk to devel­op­ers work­ing on soft­ware projects, not speed­ing up prod­uct deliv­ery for their god­damned (and I say that with no love what­so­ever) cor­po­rate man­agers. And “anar­chism”, which only a few peo­ple in the whole damned world still remem­ber means some­thing about being nice to one another because it’s the right thing to do, not throw­ing rocks at cof­fee shops. And “con­ser­vatism”, which you may be sur­prised to learn used to mean some­thing a lot more like “being rea­son­able and tak­ing into account people’s dif­fer­ences”, not being an ass­hole about rich peo­ple get­ting richer. And “Prag­ma­tism”, which isn’t about com­pro­mis­ing your prin­ci­ples for the sake of The Law.

And so on. I’m used to it; I’m sure I’ve missed a bunch. “Skep­ti­cism” for example.

And maybe now “coworking.”

Today we learnt of another cowork­ing busi­ness clos­ing down. And it looks and feels and sounds like the same old process of ter­mi­no­log­i­cal fail­ure to me.

You may not have noticed that I’ve been deeply involved with Workan­tile Exchange in Ann Arbor since before it began. It hasn’t come up much. Mike Kessler is the founder of that busi­ness, but it was a mat­ter of coin­ci­dence that Bar­bara and Laura Fisher and I ran into him after we’d spent more than six months look­ing for an afford­able space for our com­mu­nity of infor­mal col­leagues, and he had spent months build­ing out a won­der­ful com­mer­cial space in down­town Ann Arbor on spec, hop­ing for a com­mu­nity to crop up.

The detailed story’s for another day, but the short ver­sion is salient: From the get-​​go, we under­stood the con­tin­gent real­i­ties of the cowork­ing business.

  • You can’t sell jack shit to unem­ployed peo­ple, so don’t expect to make money by “sup­port­ing those tran­si­tion­ing to an inde­pen­dent lifestyle” (aka, “lay­off vic­tims”). Leave that to the gov­ern­ment, and pure non­profit people.
  • Peo­ple who think they want a desk and a phone and a mail­box really just want to project an illu­sion of corporate-​​style suc­cess, and thus they don’t want to cowork, they want a bargain-​​basement price on an office lease, and a fuck­ing but­ler (I say this with a whole heap of wry bon­homie). So send those peo­ple to a land­lord so they can learn the prices and hid­den costs of actual real estate, and not merely leech off your cowork­ing space’s lease and lim­ited staff and ser­vice budget.
  • Diver­sity of mem­ber­ship reduces the risk to every mem­ber, so don’t try to spe­cial­ize in “mak­ers” or “cre­atives” or “star­tups” and fer­chris­sakes not Realtors.
  • 30% of the work­force is an inde­pen­dent. That com­pares to some­thing like 10% that’s a dopey seat-​​of-​​the-​​pants looking-​​for-​​venture-​​capital startup-​​style big-​​E Entre­pre­neur (I say this with love, and the knowl­edge that “entre­pre­neur­ship” is a cog­ni­tive dis­or­der; I myself am a high-​​functioning entre­pre­neur), and besides they don’t want to spend one thin dime, so don’t even bother deal­ing with col­lege kids or the local incubator’s castoffs.
  • Most land­lords (but appar­ently not ours, thank good­ness), the Use­less Cham­ber of Com­merce, the local Eco­nomic Devel­op­ment grant-​​givers, the State Gov­ern­ment, the can­di­dates who want to demon­strate their “effec­tive­ness”, the News­pa­per Busi­ness Colum­nist, any­body who thinks of them­selves as an “angel investor”, and for that mat­ter any per­son who has ever watched an unironic hour of Bloomberg Tele­vi­sion? Those peo­ple do not get it. In their world, the only way to make money is to raise prices and offer improved ser­vices until demand tapers off. Cowork­ing is not about quid pro quo, it’s not a zero-​​sum game, it’s not about being a land­lord or find­ing arbi­trary ten­ants or even—this is impor­tant—mak­ing money. You can­not make a profit by run­ning a cowork­ing space.

That last one’s impor­tant. We’re not com­mu­nists, we’re not anti-​​capitalists and we’re not run­ning some kind of pep club. It’s just that we’ve thought about it. You can­not make a profit sell­ing community.

So the ques­tion is: what the hell is “cowork­ing” then? I mean, I’ve dis­qual­i­fied rent­ing desks to peo­ple, and set­ting up offices for inde­pen­dents, and all that other nor­mal stuff. What is it?

It’s com­mu­nity. Not the kind you join because it “offers good oppor­tu­ni­ties for net­work­ing and pro­fes­sional devel­op­ment”, but the kind you join because it would be neat.

It’s church. Not the kind where you wor­ship, but the kind you go to for fel­low­ship with peo­ple from diverse back­grounds, but who are in the same essen­tial and exis­ten­tial posi­tion you are: Inde­pen­dent in a world that assumes you have a “job title” and a “boss” and “employer health­care” or you can “send a pur­chase order”.

It’s a club. Not the kind you go for help, but—and I’m sorry if this makes me sound like a super­cil­ious ass­hole—the kind of club you join in order to build a strong bar­rier between you and the Pinks, the Nor­mals, the hoi pol­loi. Though in our case, those hoi pol­loi are often the bosses, the politi­cos, the nom­i­nal movers and shak­ers of the “work­ing world”.

We’re not them. We’re the 30% of the peo­ple who are inde­pen­dent of all that.

That 30% is all over the place. But who­ever it is we actu­ally are, we’re also proud. Of who we are, and of what we’re help­ing to create.

I’m not as full of hot air as nor­mal, here. Dur­ing the first two years of Workan­tile Exchange’s exis­tence, Mike Kessler tried sell­ing desks, and sell­ing mail­boxes, and sub­leases, and startup incu­ba­tion, and non­profit meet­ings, and maker spaces, and all the rest of that stuff. You know what broke every one of those busi­ness mod­els? Those peo­ple don’t want to belong to a com­mu­nity. They want ser­vices, and they want dis­counts.

All this boils down to: sus­tain­able cowork­ing isn’t any­thing to do with office space at all. Any moron can buy a cubi­cle and set it up in her garage or her spare bed­room, and sit there and play My Spe­cial Office when­ever she wants.

It’s not about “work” at all. Real cowork­ing is about the “co-​​” part, about being together. Pride. Like-​​mindedness. About avoid­ing the risks and vicis­si­tudes of sit­ting at work by your­self, not being exposed to the exter­nal­i­ties of real life by your­self, about not rein­vent­ing the wheel by your­self every time a com­puter acts weird or a con­tract gets con­fus­ing or a law­suit pops up or your dog needs a play date or you have too much work.

And (because this comes up) it’s not about being some kind of consensus-​​driven co-​​op, either. We remain inde­pen­dent, or we lose our self-​​definition com­pletely and fall back to being mere ama­teurs with “lifestyle businesses”.

Nope. Cowork­ing is a way of eat­ing entropy. Redi­rect­ing risk using com­mu­nity dynam­ics. If you want to think about it in a con­fronta­tional way, it’s about co-​​opting the same social design patterns—colocation, team for­ma­tion, com­ple­men­tary skillsets, tacit knowl­edge bank­ing, and col­lab­o­ra­tive risk balancing—that cor­po­ra­tions bring to bear against us.

It sad­dens me that I never got a chance to visit Car­rboro Cre­ative Cowork­ing, and it sad­dens me more to see them join the ranks of those who have fallen. But it doesn’t sur­prise me.

We’re weird. We’re prob­a­bly weird enough that we’re wrong in a lot of ways. It’s deathly tir­ing to con­stantly have to explain all this to guests and vis­i­tors and peo­ple look­ing for things we’ve decided not to offer, and just have it bounce off their fore­heads’ Cog­ni­tive Dis­so­nance fields. And as Workan­tile Exchange tran­si­tions from a fail­ing for-​​profit to a sta­ble what-​​the-​​hell-​​who-​​cares-​​about-​​money low-​​profit, maybe we’ll fall by the way­side ourselves.

I don’t think so, though.

We have more than 60 mem­bers right now who are diverse, pow­er­ful, enthu­si­as­tic experts in their fields. We have archi­tects, film­mak­ers, authors, edi­tors, busi­ness devel­op­ment peo­ple, lawyers, activists, traders, pro­gram­mers, graphic design­ers, stu­dents, con­sul­tants, remote employ­ees, mar­keters, and even a dilet­tante or two (like me). We have tequila tast­ings and book fairs, art gallery open­ings and Word­Press Users meet­ings. We have the amaz­ing vol­un­teer con­tri­bu­tions of Trek Glowacki, the hon­ored and respected Mem­ber who’s been work­ing for more than two years as our de facto “com­mu­nity man­ager”, and of Tom Brandt and David Erik Nel­son who (with me) are try­ing to “man­age” us into a new, more rea­son­able busi­ness model. And all the many vol­un­teers among the Con­tribut­ing mem­ber­ship, who have given time to mop and tidy and run events and intro­duce peo­ple to one another, share lunch and talk and offer advice, fill the air with music and chatter.

And tol­er­ate one another. And see value in one another.

Any­body can be wrong. But see: the more dif­fer­ent you all are from one another, the less likely that becomes.

Maybe to suc­ceed in the long term we really do need to spe­cial­ize, and exclu­sively rent desks to dudes who wear iden­ti­cal khakis as they work on the Next Google, or mar­ket more to women entre­pre­neurs whose busi­nesses have been sin­gled out by local eco­nomic devel­op­ment experts as lead­ing the way into the 20th Cen­tury, or give dis­counts to poor out-​​of-​​work cor­po­rate lay­off vic­tims who need a hand dur­ing their tran­si­tion to this unfa­mil­iar world that has no “work life bal­ance”, which only includes life, with work as a part of that.

Maybe we’re wrong.

Who cares? If this is wrong, it’ll do for now.

Every day it lasts is wonderful.

What is Workantile Exchange?

[I’m draft­ing an expla­na­tion of Workan­tile Exchange, to be handed out to folks who are vis­it­ing for Out­reach Events. This may not be the final ver­sion, but I see no harm in post­ing it here.]

Workan­tile Exchange is a cowork­ing club for free­lancers and remote employees.

It’s not a cheap office. It’s not just for nerds. And it’s def­i­nitely not an “incubator”.

It’s a pro­fes­sional com­mu­nity of peers.

Mem­bers of the club can use the facil­ity at 118 S. Main Street in Ann Arbor when­ever they want, 24 hours a day. For work or meet­ings, pro­fes­sional or social inter­ac­tion, to get away or to get together.

Cur­rent Mem­bers’ “offi­cial” pro­fes­sions include archi­tec­ture, film pro­duc­tion, busi­ness devel­op­ment, sci­en­tific con­sult­ing, writ­ing, his­tory, graphic arts, music, engi­neer­ing, trad­ing, pub­lish­ing, pro­gram­ming, activism, jour­nal­ism, account­ing and marketing.

And you’ll find most folks around here know a lot of other use­ful stuff as well.

The Mis­sion

Workan­tile Exchange is a social enter­prise, and it’s been in exis­tence for about two years. At the moment there are about 60 Members.

Our mis­sion is to sup­port the exist­ing inde­pen­dence of our Mem­bers by reduc­ing their social and phys­i­cal iso­la­tion from col­leagues. To that end we pro­mote fel­low­ship, col­lab­o­ra­tion, and train­ing among our Mem­bers, and out­reach to the broader com­mu­nity. We help our Mem­bers col­lab­o­rate with one another, and not just in their work.

Why Would Any­one Do That?

Accord­ing to Forbes Mag­a­zine, at least 25% of the cur­rent US work­force are free­lancers. That num­ber is growing.

Our Mem­bers pay their monthly dues to cowork here because they have access to one another. Most of us have offices some­where else. As a rule we’re not look­ing for work, or swap­ping busi­ness cards to “net­work”, or try­ing to “grow”—at least not in the way most other busi­ness asso­ci­a­tions seem to think is crucial.

We don’t even sell stuff to one another. I know! What can we be thinking?

Because we’re tra­di­tion­ally phys­i­cally and socially iso­lated, inde­pen­dent work­ers and remote employ­ees often expe­ri­ence more pro­fes­sional risk than the equiv­a­lent cor­po­rate employ­ees sit­ting in well-​​staffed 9-​​to-​​5 office building.

So we work along­side one another. When you’re at Workan­tile Exchange, it’s not just your cat there in the room, it’s a bunch of real human peo­ple. Pro­fes­sion­als, each with a dif­fer­ent per­spec­tive, who might have already dealt with the same prob­lems you’ve got. Who prob­a­bly have wildly dif­fer­ent and very use­ful skills and experience.

Cowork­ing together lets us bounce ideas off each other, hand off or sim­plify extra work, and draw on one another’s astound­ing col­lec­tive exper­tise. Unlike those sit­ting in their base­ment “home office”, we can inter­act with one another, whether it’s to ask a quick ques­tion or to get together with and form a well-​​staffed project team.

We all still work on dif­fer­ent things. We’re still inde­pen­dents and remote employ­ees. And to be hon­est we’re typ­i­cally very busy.

But by work­ing together, we’re all bet­ter off.

And of course there’s the Pizza Lunch. And the Bour­bon Tast­ing. And Game Night. And Night at the Races. And the Friendly League.…

The Club­house

We main­tain about 3200 square feet of open space in down­town Ann Arbor, in a ren­o­vated 1860s store­front. There are two small con­fer­ence rooms avail­able for Mem­bers to reserve, and a tiny phone room where you can use your cell phone. Oth­er­wise, the space is bro­ken up into two large shared spaces. All the fur­ni­ture is mobile, and Mem­bers are encour­aged to rearrange it to suit their needs. Nobody “gets a desk”.

The large ground floor “Café Level” tends to be the day­time, con­ver­sa­tional work­space. The large mez­za­nine “Train­ing Loft” tends to be the quiet day­time space, but has white­boards and pro­jec­tors so it gets used for events in evenings.

We also have a small kitchen with fridge and cof­feemaker, and of course a bath­room. There are lock­ers for Mem­bers’ day use, a pro­jec­tor for meet­ings, and indoor bike racks for smart com­muters. Some of our Mem­bers are kind enough to share their print­ers and scan­ners for office doc­u­ments. Healthy (and unhealthy) snacks are avail­able for a dona­tion. There’s even a cen­tral­ized speaker sys­tem that lets any Mem­ber play their music in the back­ground. Very soon we’ll be adding a small cir­cu­lat­ing library of books and games: entirely on loan from Mem­bers, made avail­able for other Mem­bers’ use.

Out­reach Events

You’re prob­a­bly read­ing this now because you’re attend­ing one of our Out­reach Events.

We know that space for pub­lic meet­ings in down­town Ann Arbor is at a premium.

We also think it’s cru­cial to bring together free­lancers, inde­pen­dents and remote employ­ees with the rest of the local community.

The best way we know to do that is by sup­port­ing users’ groups, train­ing classes, com­mu­nity fairs and parades, and sim­i­lar social events.

So we make our space avail­able for selected events in keep­ing with our mis­sion, and for events spon­sored by Workan­tile Mem­bers (as long as they don’t dis­rupt oth­ers’ work). We don’t charge much: 10% of fees col­lected. All we ask in return is that you allow inter­ested Workan­tile Mem­bers to attend your event, that you’re respect­ful of the space and the Workan­tile Mem­bers who’ve invited you to share it, and that you leave it at least as clean as you found it.

Con­tact our event coor­di­na­tors by email to ask about sched­ul­ing an event.

Mem­ber­ship

You don’t have to be a free­lancer or a remote employee to join. You just need to be a person.

No, really: Mem­ber­ship is not avail­able to cor­po­ra­tions or other insti­tu­tions. You per­son­ally are enrolling as a mem­ber of the club, even if some­body else is pay­ing for you.

Day Passes cost $15, and allow you to use the pub­lic spaces in the club­house. They don’t allow sched­uled reser­va­tions of the con­fer­ence rooms.

A Sup­port­ing Mem­ber­ship costs $100/​month, and gives you access to the club­house up to six days per month.

A Full Mem­ber­ship costs $160/​month, and gives you 24-​​hour access, 7 days a week. You’ll be expected to spend a cou­ple of hours a week par­tic­i­pat­ing in com­mu­nity events and sup­port­ing the mis­sion of Workan­tile Exchange.

A Nose-​​to-​​the-​​Grindstone Mem­ber­ship costs $250/​month, and gives you the same ben­e­fits as a Full Mem­ber­ship, with no social obligations.

For the time being there’s an infor­mal mem­ber­ship appli­ca­tion process; the con­tact infor­ma­tion is on the website.

For more information

Infor­ma­tion on Workan­tile mem­ber­ship, sched­ul­ing an Out­reach Event, and Cowork­ing in gen­eral is avail­able at http://​workan​tile​.com

Notes for a CodingDojo, 3x power

I’m think­ing this will want to be two or three con­sec­u­tive weeks of our Ann Arbor-​​based Tues­day evening “Crafts­man Guild” meet­ing, but I could be con­vinced to run it on a cou­ple of con­sec­u­tive week­ends, as well. The gaps in between ses­sions are actu­ally use­ful, since I think they give folks a chance to think about stuff that should be both­er­ing them as we proceed.

Devel­op­ing an awe­some Genetic Pro­gram­ming sys­tem… from scratch

The Point:

We often run these agile cod­ing exer­cises as if user sto­ries and accep­tance tests drop from the sky. In real projects, they’re typ­i­cally the biggest source of con­fu­sion and pain—even in projects we’re work­ing on by our­selves. The sub­ject mat­ter we’ll explore here, Genetic Pro­gram­ming, is hugely sexy, tech­ni­cally sim­ple, and offers only triv­ial cod­ing challenges.

You might won­der why so few peo­ple use it, then, after 20 years. Why it hasn’t changed the world and made arti­fi­cial intel­li­gence part of our every­day lives.

The answers to those ques­tions have noth­ing to do with the computer.

The Struc­ture:

Two or three ses­sions, each about 2 hours.

We’ll run the ses­sions in a Cod­ing­Dojo for­mat, much like the “cod­ing ran­dori” we’ve seen in ear­lier Crafts­man­Guild meet­ings, where there’s one “dri­ver” and one “nav­i­ga­tor” pair­ing on a lap­top con­nected to a pro­jec­tor, with the entire “audi­ence” help­ing them along the way as they write code (and do chores).

If it seems prac­ti­cal in a later ses­sion, we may split into two teams (still with one cus­tomer and one project).

I’ll role-​​play “the cus­tomer rep­re­sen­ta­tive” for a cus­tomer who’s off-​​site, with the rest of the group act­ing as “the dev team”.

In addi­tion to the cod­ing com­puter, we’ll set up a pro­jec­tor up show­ing a live Piv­otal­Tracker instance where we can col­lect, sort and make progress on sto­ries as an inte­gral part of the devel­op­ment process.

Dur­ing the first iter­a­tion we’ll decide on lan­guage and infra­struc­ture, based on who’s there and what they want and know.

As code is writ­ten it’ll be com­mit­ted to the github project (so the audi­ence can fork it and work along), but we’ll have for­mal review ses­sions with “the cus­tomer” accept­ing or declin­ing par­tic­u­lar solu­tions after every iter­a­tion, look­ing at the sto­ries we worked on and gath­er­ing new ones as they crop up.

Par­tic­i­pants:

…should have used some mod­ern test­ing frame­work, but they don’t need to be experts (or evan­ge­lists) at either TDD or BDD. They should be com­fort­able, but don’t need to be flu­ent, in at least one mod­ern pro­gram­ming lan­guage like Java, Ruby, Python, &c. They should at least have looked at piv​otal​tracker​.com to famil­iar­ize them­selves with the fea­ture set and story-​​sorting idiom.

The lan­guage we pick should be the one which most par­tic­i­pants are most com­fort­able using when they do real work. What­ever lan­guage and infra­struc­ture we decide on, it shouldn’t be an obsta­cle to take a sim­ple user story like “Adding two num­bers together should return their sum” and actu­ally write the accep­tance test, and then run it.

The Project:

The Customer’s over­all goal is to build a Genetic Pro­gram­ming sys­tem that can accept a set of (x, y) data, a set of math­e­mat­i­cal prim­i­tives, and will evolve math­e­mat­i­cal equa­tions of the form y=f(x) that fit the data. Here’s an (antique!) Java applet that does some­thing along those lines already.

This sort of GP project typ­i­cally breaks down into five chunks:

  • build a sim­ple but full-​​featured inter­preter for a domain-​​specific lan­guage (DSL) intended for math­e­mat­i­cal modeling
  • build an eval­u­a­tor that deter­mines how well an arbi­trary DSL script matches tar­get data
  • write meth­ods to cre­ate ran­dom pro­grams, and also mutate and cross over DSL scripts
  • build a sim­ple sym­bolic regres­sion sys­tem that fits numer­i­cal data with arbi­trary math­e­mat­i­cal models
  • adapt to some minor prob­lems that may arise along the way

These may sound like big, ambi­tious steps, but in fact they’re all tech­ni­cally simple.

The goal of the dojo is not to learn to type some­thing quickly or get as much done as pos­si­ble.

It’s designed so we adapt the emerg­ing code­base and our col­lec­tive under­stand­ing of the prob­lem the cus­tomer is ask­ing for, in a con­text where there are no “tricks” (I won’t be lying to you, except maybe by omis­sion), but where there are plenty of traps.