Collaborating with Developrs and Other Geekery

I picked up a little inspiration for a post that has been marinating in my brains for a little while now, which is to lay out some effective techniques I've gained in working with (don't use the "m" word) developers or as the article I referenced so endearingly puts it - geeks. And if you don't know already, geek is in fact an endearing term, and "uber-geek" quite an honor...more on that later.

Little background on myself. I was a math major in college, took a bunch of comp sci classes, and got into my first web developer position out of college. I too, am a geek....or was, well I'm not really sure which. So in all fairness it does help me quite a bit because I understand the lingo and have a similar brain chemistry to the geekdom - but really more than that I think its that I understand the common problems plaguing developers, how one feels as a developer, and simple ways to work with them in a non-intruding manner.

First off, I'd say you definitely want to have a casual style. Tech's aren't impressed by fluff or pomp and circumstance, they like to get right down to the meat of the matter, and it matters to them what you think, the content of your argument or statement. They just don't enjoy formal business attitudes or fronts very much at all.

Be nice. This one should be obvious but in the midst of urgent situations, fires that need to be put out, or clients that are confused and flailing their arms about looking for a solution, it can be easy to pass tasks off to them without acknowledging their effort or that they are busy with something else. So if you're going to ask for some help - something like "hey man, if this isn't a good time lemme know but I had a question for you". Also recognize the kinds of things that they don't like to do - repetitive or simple things that are a distraction from the complex work they are focused on - and try to work around their level of concentration at any given moment.

Communication Protocol. Tech's are most likely going to prefer to communicate by IM or email, even if they're sitting five feet away from you. They prefer it because it forces you to be more specific in your requests, and it can be much more efficient for them to respond to. And again, concentration. You have to realize this is a developer's currency - without concentration they can't get anything done, and what they do get done will be buggy, which....well that's a whole 'nother topic. So if they repeatedly ask you to IM or email them some detail, or to submit it by an online bug tracker, just get used to it - you're going to get more mileage out of their time, and they'll enjoy interacting with you much more.

Respect their time. You need to realize and really internalize that these guys are very smart and talented and they're doing important work. Think twice before asking them a question - especially if it has to do with troubleshooting Outlook, they most likely hate troubleshooting Outlook, or I don't know....maybe that was just me. And the stuff that you do need to pass off to them, do it in batches - don't give them onesy twoesy's all day long. That way, when you need something important, you'll have a good track record with them and they'll be willing to help because they realize you don't cry wolf all the time.

Hope some of these tips are useful....look forward to feedback on either side of the fence.