developers! we're people too.

Let's talk about time-zones

We're living in interesting times. In the past - and I don't know whether this was just because I was younger, and not paying attention, or if it really was like that - you could get away as an engineer/programmer/developer/whatever by being good at what you did, and social skills didn't matter. You didn't have to get on well with anyone, make eye contact or talk about anything other than code and ideas.

Over time though, this has changed. Maybe it's got something to do with dev going mainstream - but the socially awkward developer stereotype is a thing of the past.

I'd say, these days, "full stack" means not only front-end-back-end-db-os capable, but also consensus-building-client-relationship-strengthening.

I'm pretty much an introvert, and if given the choice between working on some code and going out for dinner/drinks, would naturally choose the code. Of course, once you've dragged me away from the code, I enjoy the interaction, but would find it difficult to do that sort of thing every day. This social-animal stuff got me thinking. Watching.

And really: like 75% of work is social skills. Gone are the days when folks could slide pizza and a spec under a door and get code in return. Things are moving too fast to wait for exhaustive documentation. Now, we're pretty much refining as we go. As a dev, it's incredibly productive to sit right next to the designer or suit, and work with them to decide what to build, make, iterate, abandon, change.

As a lazy developer, I found out: it turns out it's often less work to negotiate or dig a bit more or try a couple of spikes and refine/shape what's going to be built than to wait for the complete spec.

If you're a dev - realise, we're people too. With all the responsibilities and obligations attached to that. Like making a bit of small-talk, or giving people the time of day to discuss an idea they've had. And to be polite in shutting it down, even if it's really stupid. Work those social muscles. Doing so gives you significant advantage.

And if you're dealing with developers, try bringing them into conversations when you're planning or thinking. Rather give them the option of dialling down their involvement. Let them prattle on about ... all those tech details. They really love the room to do that. With more and more regular people becoming devs, you'll frequently be pleasantly surprised at the humanity to be found, if you only look.

Socially correct is much more difficult to achieve than Technically correct. But everything old is new again, and the skills that got us to the top of the food chain as hairless apes are at a premium. Computer processing power, storage and baked in capabilities are cheaper than they've ever been, which means the expensive thing is the human involvement. It is only logical to get as good at the humanity part as you are at the coding part for maximum overall benefit..