Wednesday, October 28, 2009

Situational Luddism

Personally, I have a pretty strong independent streak, so the time-worn adage "Take in laundry before you take in partners" probably makes more sense to me than it does to others. But the whole point of partners (or, rather, their money, which you don't have ready to hand) is that they are effectively outsourcing their work ethic and judgement to you. In short, it's delayed gratification with interest.

In the long term, being a Luddite doesn't make sense. Then again, just because something's powered by machinery doesn't necessarily make it superior to what humans can do. Buying and selling the same stock within seconds--if, indeed, it actually takes that long--strikes me as one of those cases. The chiefest reason being that it doesn't make any sense from the standpoint of management...and partners are ultimately managers.

Admittedly, it's not an original management principle--in fact, I'm shamelessly stealing it wholesale from Joel Spolsky's Joel on Software blog. But the central idea is this: When you establish metrics, people (and in this case whole companies) will work toward those metrics--but the metrics are in fact only a sliver of what you actually want to accomplish. To illustrate: You want your call center to be more "productive," and you define that as the number of calls taken per caller per hour. So you establish rewards and punishments based upon the metric of calls/hour. Congratulations: You've just incentivized (to used management-speak) your phone-jock minions to hang up on your customers. Moron.

The one thing you need to understand about the buy/sell decisions of stock trades measured in microseconds is that computer programs--a.k.a. the algorithms--are just metrics. Ham fisted metrics. Why? Because algorithms can only model so much human behavior. Or, more to the point, so many possible outcomes. If you don't believe me, snag a Computer Science graduate and have her/him explain, say, the classic "Traveling Salesman" problem to you. It's an eye-opener regarding what algorithms can and can't do. Then throw in the tendency of options-compensated CEOs to cook the books, and you'll have as much faith in the base numbers as you should in sports records in the age of steroids.

So, in the meantime, I trust that you'll forgive me for not mistaking trades driven by algorithms as a functional substitute for actual investment guidance. Because so far as I'm concerned, that ain't capitalism. And, moreover, it's not something I'll gamble my golden years on.

Tuesday, October 27, 2009

Instructor, teach thyself

This certainly isn't an original thought, but there's nothing like having to teach something to other people to force you to learn it. I'll be the first to admit that my business card should bear the title "Professional Dilettante," and the programming facet of my life is no exception. Too many times, adding a new trick to my bag works something like this:

  1. Find code that does something similar (either from the work repository or the internet).
  2. Copy and paste.
  3. Tweak until I break it so badly that I have to learn just enough to un-break it.
  4. Convince myself that I actually know what I'm doing.

Then comes the moment of truth, when I have to explain the technology/technique to someone else. Which is when I realize just how much chewing gum and bailing wire is holding my understanding together...and how many assumptions I've made that don't necessarily withstand questioning.

But for all that, that's not a bad experience to have. Not that I'm offering, y'understand, but it'd do me whole buckets o' good to have to pitch a presentation at my fellow programmers every month.

Monday, October 26, 2009

The freedom to fail

I think I've already riffed on the ridiculousness of thinking that any software can be bulletproofed with tools or processes or incentives. Or by convincing yourself that you can hire a team that's too smart to blow anything up. Or that a new language platform will come along that will make failure impossible. So, alas, there are no silver bullets there. Plus, the fact that too many technologies have self-appointed "evangelists" doesn't help when it comes time to make a management decision on the direction a development team will take. Particularly if you yourself don't spend a whole lot of (if any) time in the coding trenches.

But here's one thing that I can confidently recommend, something that probably won't be limited by language, platform, tools, or even so much the quality of programmer: Give your developers room to fail without bringing other people's work down with them.

Practical example: At my first "real" programming job, we each had our own copy of the database, the website and the compiled code that did the heavy lifting for the web pages. Our copies of the code was automatically backed up to the server before the server itself was backed up to tape. The "authoritative" copy of the code was checked in and out of source control, and the "authoritative" version was pushed up to a server for integration & testing before it was demo'd to a potential client or pushed up to the live server for the paying customers.

For the programmer, having your own little universe meant that you could do your work without worrying about tripping up anyone else. Which--perhaps counter-intuitively--is a great incentive to create higher-quality code. Two main reasons behind this reasoning:

  1. The programmer has complete freedom to fiddle with other parts of the system (be they database values) or code that, technically, is not "hers" or "his," but affects or is affected by what s/he is currently workingone thing that's drilled into you when you have to take on.
  2. Reason #1 removes any excuse for not performing these kinds of sanity checks. Sure, there's every possibility that another programmer could have changed the upstream/downstream code, but that's why its' all pulled together on an internal testing server before anyone else sees it. And if the other programmer wasn't regularly checking in her/his code, then there's no doubt where the finger needs to be pointed, hey?

Mind you, giving each programmer her/his own sandbox doesn't come without cost. Some of it may be in licensing, depending on what languages/platforms. More likely it will be from setup/maintenance. But the fact is that the cost of a software bug grows as it moves (undetected) up the development cycle. And by "grows" I mean like the archetypal Giant Irradiated Critter straight from the Cold War era monster-flicks.

The fact is, nobody wants to spend the day as "The one who blew up the database." Or "The one who forgot to check for ..." But when you give people the freedom to fail often but also the means to fix it before anyone else finds out, they should be more likely to spend their time checking out those what-ifs, rather than convincing themselves that their code is too l33t to worry about it.

Sunday, October 25, 2009

Another sign that you're a computer geek

You accidentally kick over your water glass while working from the couch, and your first reflexive response is to hit CTRL + S to save your work before setting down the laptop and fetching a rag to sop up the mess.

A lesson from camp

No, not computer camp. We're just home from a friend's birthday party, the theme of which was truly bad movies. (That kind of camp.) We arrived in time to polish off an MST3K (an episode that mocked one of the worst movies I've seen, actually--which is saying something). Then we proceeded to do our own MST3King of that 1938 (cough) "classic" now known as Reefer Madness. (I don't think I exaggerate by much when I say that its writing values were so low that you almost feel relieved for our forebears in that they shortly had WWII to take their minds off its sheer dreckishness.) And so on.

But I can forgive the awfulness of a movie when it's evident that the people making it didn't take themselves seriously and were obviously having fun with it. To me, that speaks more of professionalism than a group that clocked its time and hoped that the whole mess went direct to video before anyone noticed.

One of the buzzwords of software, particularly in the startup space, is MVP, or "minimum viable product" The gist of MVP is that you release only the absolute bare-bones of the produc and let the customer decide what should be fleshed out next. Which is a wonderful tonic for bloatware and all, but I think that the austerity of the principle neglects the fact that fully-fleshed out human beings are writing the code, creating the graphics, pulling together the documentation, etc. And people like to have fun--not as an excuse to not work, but as part of work itself. In fact, if the main point of shoving a lean product out the door is to be first to market, that urgency will create more stress than usual for a software release. If the culture frowns on making the process fun, that only adds to the stress. Because that kind of culture is ultimately frowning on a facet of the creative process itself. Which might work long enough to roll out version 1.0. But I strongly believe that the cost will be not only felt, but compounded as well, with each subsequent release.

So if there's a certain amount of campiness to the process, relax. People who can work and play hard at the same time are the professionals you want for your team.

Friday, October 23, 2009

Frivolous Friday, 10.23.2009: Dueling metaphors

First off, apologies to those who have already viewed this YouTube video where marketing's Master Yoda (a.k.a. Seth Godin) responds to a question about the value of social networking in business. The takeaway sound byte:

The internet is this giant cocktail party, with all these people swarming around connecting much as they can because they're keeping score: "Who likes me today?" "Who's talking about me today?" But one day when you need to ask them to authorize a $100,000 contract, it doesn't matter. What matters is: Where are the real relationships?

I've been turning that metaphor--social media as a cocktail party--over in my head earlier today. The thing is, I can't even remember being to a bona-fide "cocktail party," ever. If I eventually do attend one, I'm liable to be disappointed, thanks to my co-workers. Because sometime in late 2005, The Teasing That Would Not Die led to an upping of the ante that has become the tradition of the Liquid Potluck. Which is as close as I've come to the cocktail party ritual that was part of the mysterious grown-up world when I was a squirt in the '70s.

And to me, the Liquid Potluck seems more to the point than cocktail party, mainly because the "liquid" part is sort of a misnomer. Sure, the wine/beer/etc. has pride of place--that was originally the point of the joke, after all. But (come to think of it) I still need to snag the recipe for the artichoke/spinach dip that C. brought. Then, too, M's girlfriend has a standing invitation--and it's because we like her. Honestly! Although the taco dip she brings tends to vanish pretty quickly. Certainly, no one objected to being a guinea pig for J's salsa recipe. And it's fun to see people's eyes light up (and the 'fridge mysteriously fill with refreshment over the lunch hour) after the crockpot of artery-clogging Lil' Smokies is fired up around 11 in the morning. Ditto seeing how adventurous some taste-buds can be, even with oddities like pickled garlic.

Initially, there were a few kinks to work out, namely the folks who didn't grasp that this was a true "potluck," rather than an on-the-house treat. And a few potlucks have been co-opted for other purposes. Oh yes--and some attempt was made to regularize the scheduling once upon a time. But, ultimately, they just happen. When they do, you can sometimes learn things that you never would have guessed about people you thought you knew. And you also learn things that you wouldn't have thought to ask about in the first place.

All of which sounds awfully like social media, at least as I've experienced it. Yes, there will always be folks who expect to consume more than they contribute. On the flip-side, the medium lends itself to the tendency to "overshare," certainly. Clicques coalesce, break up, and re-align in the not-quite-predictable patterns of a kaleidoscope. When the Important People put in an appearance, the dynamic changes...albeit not as much as it should. There have been a few times when someone's missed the bus back to The Real World. In other cases, people who would have much to give and gain from the swirl of chatter choose to stay away.

It's not that the original cocktail party metaphor isn't apt; I just don't run in the same circles as oracles of marketing--that's all. I've spent my life in the Upper Midwest with extensive family on both sides (and that before marrying someone with a similar abundance of cousins), so the "potluck" meme just feels more natural.

Thursday, October 22, 2009

A tune from the B-side

One of the important folks was in the office today to talk financial stuff with us all. Theoretically, I could have blown his presentation off, but when I saw the alpha-geek (who is never not insanely busy) grabbing a front row seat, I scurried into the conference room to claim my own.

I'm glad I did. Obviously, management's job is to rephrase anything negative. You all know the song 'n dance: This economy doesn't "suck"; its "challenges" present us with "opportunities." But apart from that, the numbers were laid out in layperson's terms, and the reasoning behind certain strategic decisions was explained quite credibly. And when I had a question that visitor couldn't answer, his response was to insist that I email the CFO. (Which I did, btw, and received a reply within a couple of hours.)

I think--but don't quote me--that it was Robert Townsend ("Up the Organization") who wrote that the mark of a good manager was not how soon you hear the good news; it's how readily your underlings will deliver the bad news. I didn't really think about it until today, but that maxim has a B-side that basically works in reverse. If we'd had to attend that "lunch & learn" on our own time, I think it would still have been worth it. Partly to understand how the firm is managed at the global level. (Hey, anytime you can figure out how those who sign you paycheck are gonna jump, it's A Good Thing.) But also because I picked up a couple inside statistics that will come in very handy for indie. work. But don't tell The Powers That Be I said that. ;-)