After years of procrastination, I’ve decided to start self-publishing short essays on topics concerning technology management that interest me. Based on my varied experiences over the last three decades in the business, I know my posts are probably going to be too long for the prevailing short attention spans, but what the heck, I just can’t bring myself to write in sentence fragments.
Part of the impetus for this blog is staying linguistically fit, but from a professional point of view, these essays will help me organize my thoughts and strategies. As those that know me will attest, I often “think by writing” and “lead by email”, so writing, leading, and problem solving are all the same for me.
Hopefully, my opinions will be of interest to any readers who find their way here, and I hope they will initiate some interesting conversation. Such conversations with my colleagues, clients and correspondents always keep me motivated and energized to learn. After all, working with smart people is *the* great reward for professional technology managers. (And by “managers”, I mean: Someone who gets someone else to do the work.)
I am about to enter my fourth decade in tech, and by “tech” I include the entire range of computer hardware, software and communications creations that have transformed the world so profoundly. If you look over my vitae, you’ll see I have worked as a developer and manager in all three disciplines, and I am a generalist to the core. For the most part, my posts will be at a fairly high business level, highly cross-disciplinary, and rarely a geeky deep-dive.
I am also writing from a more personal motivation. Most all the tech writing I read is really quite bad: Sterile, hyperbolic, narrow-cast, a-historical, with anything like an individual point of view vigorously scrubbed. There is little or no fun to be had reading the stuff, and most of it is only intended to be quickly scanned in combination with slideware, all in tune with an industry that has made attention deficit disorder a job requirement.
Bad tech writing is a tax on us all, because consistent reading about our field is a necessity. All-in research to prepare for a discussion in depth can take weeks. Our situation is similar to a programmer forced to read another’s poorly formatted and uncommented code; the sheer effort it takes to understand obscure new ideas and vocabulary via poor writing make you very crabby.
So I’m going to share a few discoveries and disappointments, amuse myself and hopefully any readers, sort out my thoughts on management issues and hopefully initiate some discussion.
Which brings me to history of my title: Any Wino Theory.