DaedTech

Stories about Software

By

The Aspiring Free Agent Survival Guide

It often feels as though I have no idea what I’m talking about.  I don’t say this in an attempt to garner sympathy and I’m not really suffering from impostor syndrome (at least not in this domain).  It’s more that running my own show, business-wise, has demanded of me a form of trial-by-fire, just-in-time learning.  It’s as though I moved to a small village in Germany, in spite of the fact that I don’t speak a lick of the language.

But in muddling my way through all of the details, large and small, I’ve actually managed to pick up a fair bit.  What I’d like to offer today is a preparedness guide of sorts.  The free agent’s life is an attractive one in a lot of ways, and I definitely recommend at least considering it.

I have no regrets, myself.  But I do acknowledge that it can seem like a pretty daunting leap, particularly if you’re well established in life and have responsibilities.  People telling you to take the plunge probably seem like friends swimming in an chilly lake, already used to the water, telling you that it’s fine.   I’m not that used to the water yet, though, so I can still appreciate your position.  It’s cold, but it’s refreshing.  And I’d like to offer some thoughts before I get too acclimated to the temperature.

ColdSwimming

So here are those thoughts.  These are things to be aware of if you contemplate, however idly, the free agent life. Read More

By

Building Superior Code … Is It Achievable?

Editorial Note: this post was originally written for the SmartBear blog.  You can read the original here, on their site.  As I’ve mentioned before, they have some good authors that I respect writing over there, so give it a look!

I’ve made stops in a lot of software development shops in my career, both as an employee and as a consultant. This has afforded me to the opportunity to learn that some questions and concerns are universal in the industry. One such question, asked by Fortune 500 CTOs and tiny startups alike, is “How do I make sure we have good code?” If that seems like it’d be hard to answer, rest assured that it definitely is. As much collective practice as the world has writing software, we’ve not managed to agree on the answer to a deceptively difficult question: what is good code?

David Starr wrote about this topic some time back in an excellent article entitled “Defining Code Quality.” It’s hard to opine about how a software group can have and maintain superior code quality when, as David points out, it’s difficult even to reach consensus on what it means to have superior code quality. So let’s talk about that first.

Unicorn

Read More

By

If You Promote Bad People, You Promote Bad Culture

Most of my cynicism toward the corporate world is safely directed into my new book these days, so there’s not a ton of spillage onto the blog.  But I’m going to make an exception today and talk about corporate culture.  To understand some of the terms I’m about to use, you can buy the book, if you’re so inclined, but you can also see an original definition here in this post.

I originally intended for my notes on this topic to make it into the book, but one of the main uplifting themes of the book is that I see programmers creating a professional working arrangement in which the corporate idealist doesn’t exist.  And since deliberate company culture, which I’ll refer to as “corporate religion,” is largely theater for idealists, spending a lot of time talking about it in the book would be somewhat superfluous (I do mention it, but not extensively).  But that’s not to say that corporate culture and religion don’t matter.  And, all these half-formed notes I have ought to go somewhere.  So, here they are.

Corporate culture is more or less defined by three things: what it takes to advance within the company, and what it takes to stay in the same role within the company, and what it takes to be walked out by the company.  Paintball outings and “bring your pet to work” don’t define or even describe company culture.  Perhaps more surprisingly, neither do things like company “mission,” “values,” and “principles.”  These things, which constitute corporate religion, are mainly orthogonal to culture.  Corporate religion consists of ceremonies, outreach activities, and the official canon (mission statements and expressions of “official values”).  But none of these things are culture, any more than the Ten Commandments, New Testament, and church bake sales are the ‘culture’ of a rural evangelical town in the USA.

If you look up the definition of the word culture, you’ll have to scroll all the way down to definition number 5 to get to an actual definition of corporate culture.

The behaviors and beliefs characteristic of a particular social, ethnic,or age group: the youth culture; the drug culture.

For our purposes here, we’re talking about the social group “people who have opted to work at this company.”  This means that we’re talking about behaviors and beliefs of employees when we talk about culture, and this is why culture and religion are disparate and sometimes orthogonal entities.  Corporate employees are forced to attend religious ceremonies and memorize the canon, but what they actually believe and do outside of structured activities is another matter altogether.  Plenty of people who show up to church every Sunday go forth immediately afterward and pound beer and gamble on football.

ArmchairQuarterback Read More

By

Quiet Isn’t Always Anti-Social

There’s a common tale I hear that seems to epitomize being adrift in a sea of corporate anonymity. It is some variant on the theme that people are using asynchronous communication media when actually (to their knowledge or not) seated pretty close to one another. At its most facepalm, it’s perhaps two people who sit within 20 feet of one another dialing into a webex for a scheduled meeting between the two of them. But at its most deceptively understandable, it’s two people in a similar situation exchanging emails.

“Just get up and talk to each other!” exclaims an exasperated witness to the exchange.

In the case of the webex, the communication barrier seems legitimately hard to justify.  It’s like calling someone in the next room to watch TV together or something.  But in the case of email, I can offer justification, though perhaps not the justification you might think.  I’ll circle back around to this.

Programmer

Susan Cain on Introverts

I’ve written a few posts on the subject of introversion over the last few years, including this first one that was relatively popular.  In response to these posts, I’ve gotten some recommendations to purchase Susan Cain’s “Quiet: The Power of Introverts in a World that Can’t Stop Talking.”  Her audio book now resides on my phone and I’m listening to it as I travel.  It’s worth a listen/read, and I’m definitely going to be writing more on this topic, particularly as I wrestle with the friction that has been created by making extroversion the new hotness in the programming world.

The book has offered an explanation of my own psyche that is downright eerie in how well it describes me.  Introversion, apparently is marked by a good bit more than just needing alone time to “recharge one’s batteries” after spending time in social situations.  Here are the themes from my post that Cain predicts of introverts (and, this apparently describes me quite well, as I got a 20 out of 20 on the informal “are you an introvert” quiz near the beginning).

  • Fine with public speaking (potentially).
  • Risk aversion.
  • Over-thinking and over-preparing for social interactions.
  • Impatience with small talk with strangers (e.g. about the weather).
  • Introverts as highly analytical.
  • Strong preference for written communication.

That last one is kind of interesting, eh?  An introvert will tend to favor the written word as a means of communicating ideas. Read More

By

Standards Organizations Illustrated

I’m on the road this week, and typing this wearily at about 11:30 PM from a Marriott. In addition to traveling, I’m finishing up a pretty blistering stretch of work for a variety of clients, so suffice it to say my bandwidth for composing posts is rather limited.

Because of that, and because 3 of the last 4 posts I’ve made have gotten massive influxes of traffic and generated a lot of comments, I’m going light-touch here today, both in terms of effort and tone. This is my first foray into comics. I claim responsibility for the words and concepts but not the illustration. That is the work of my wife who is, by the way, a now full-time freelancer, specializing in edits and design.

So please enjoy this cartoon representation of what standards organizations seem like to me: a maniacally impatient tinkerer with a bureaucracy tolerance level that asymptotically approaches zero.

Standards Organizations Illustrated