Stories about Software


Honesty and the Workaday Blogger’s Connundrum

Last night I got an email asking for some perspective on something, and it’s prompting me to go “meta” and write a post about being a techie blogger. The question basically boiled down to “how do I make a cathartic blog post about Expert Beginner coworkers without getting myself in hot water at work?” If you’re a blogger with a 9-5 and coworkers, this is a pretty valid concern. After all, your coworkers will certainly provide you with the most material about which to write, simply by virtue of the fact that so much of your relevant experience will involve them directly. Add to that the fact that blogging (really, writing in general) can be a nice outlet for saying things that are politically untenable in situ, and this is something that matters to bloggers.

So, here are my thoughts on the subject.

Is This Thing On?

First up is asking yourself the sometimes awkward question, “is anyone even reading this?” In the first year or so that I was blogging, I’m pretty sure almost no one was reading except for spam bots and search engine spiders. If none of your coworkers are likely to read your blog in the near future, it’s a moot point and you can probably write whatever you want.

Now, you may think to yourself, “sure, but what about later if it becomes more popular with them or in general?” That’s a possibility (and in terms of readership a good problem to have), but it’s actually kind of unrealistic to think that people/coworkers are going to peruse everything in your archives in encyclopedic fashion. Most likely they’ll think, “look at that, Erik has a blog — I’ll go read half of a post.” If the title isn’t somehow indicative of the conflict/subject-matter, it’s not likely to attract notice. Additionally, Expert Beginner types tend not to spend a lot of time reading blogs and concerning themselves with the opinions of others, so they’re even less likely than the average person to go browsing through your opinions.

Of course, there is always a risk when you take the “whatever, no one will notice” attitude.

Surely That’s Not Me

This won’t apply if you’re relating an anecdote, but if you’re describing personality traits, never underestimate someone’s ability to gloss over their own shortcomings. For instance, let’s say you write a post describing someone as:

  • Short-sighted and myopic in big picture thinking.
  • Averse to new ideas and afraid of change.
  • An organizational cancer.
  • A passive aggressive malingerer.
  • An unending source of misery for coworkers.

It’s not very likely that someone will read that and think, “oh, that must be me.”  A lot of people have a blindspot for not only their weaknesses but for how they are perceived by others.  This is often doubly true of the kind of tone-deaf people that go around upsetting those around them — self-perception and external perception are often wildly out of touch.

Like the previous section, this is no guarantee that people won’t know who you’re talking about.  If you supply an anecdote making it clear who the parties involved are or if your antipathy toward that person is commonly known, they might recognize themselves being described.  But they honestly, really might not.


I have myself submitted entries to The Daily WTF, so I can speak to the anonymyzing that takes place when you do so. They change details about your story while leaving intact in terms of meaning. So maybe the language is Java instead of C++ where applicable. Maybe a telecom client becomes an aerospace client. Maybe a female coworker becomes a male. When they’re done, you recognize your story but take comfort knowing that nobody else would. At best, they’d think, “that’s weird, I remember something similar but in different circumstances.”


You can do that with your blog too. Take a current story and superimpose it over the people and techs at your previous job. Be nebulous about dates when something happened recently — “some time back, I…” Make the “Project Manager” a “Business Analyst” or describe a “Software Engineer” as a “Senior Software Engineer.” You can also insert some vivid details that are false flags but not important to the meaning of the story.

The line you walk when doing this is the line of sacrificing an element of how genuine you are. Personally, when I’ve obfuscated to protect the people involved (or myself), I’ve done so more with intentional vagueness of timelines and places than anything else. As far as strategies for not suffering blowback go, this is a pretty effective one. Even if the person/people in question suspect, you have complete plausible deniability. But you do sacrifice an element of honesty.

Whatever, I Do What I Want!

Short, sweet, simple. Print it and make no attempt to hide it. Go forward with the mantra that people doing stupid things ought to be called out for their behavior. The blowback for this may be intense, but so too, I’d imagine, is the catharsis. And hey, perhaps it’s the fire you need to light under yourself to move things along a bit toward a better option if you’re really unhappy.


Type it Up, Leave it in Drafts

Finally, here’s an option for you. You can type up the most scathing, biting post imaginable, omitting no details. View it as a preview and read and re-read it, relishing in the dressing down that you’re issuing. And then… leave it in your drafts folder for a rainy day. Maybe that day comes when you put in your notice. Maybe it comes a month later. Maybe a year later. Or, maybe you read it after a lot of elapsed time and wonder what you were so upset about.

Time smooths over a lot of wrinkles, and time may be your best ally for for sorting out, in retrospect, whether you were having a bad week or whether you really have something important to say about workplace dynamics and technical discussions. And, it almost goes without saying that this is the option with the least potential fallout for you.

Of course, if all else fails, you can always go to the preposterously elaborate length of starting a twitter account that tweets all of the dumb things to which you’ve been subjected over the years in 140 character increments. But you’d probably have to be pretty demented to do something like that.

  • dave falkner

    The cynical side of me often wonders when people have written completely constructive, non-critical blog posts (perhaps about simple “how-to” coding topics), if they were actually using their blog as an outlet to keep from boiling over about something they were dealing with in their day-to-day coding life.

    • Wouldn’t surprise me at all, though that isn’t specifically my style. Generally, when I write simple how-to posts, they’re just for my reference and anyone else who might find them helpful — no agenda. The ones of mine that are more catharsis posts are usually probably easy to spot. I guess I do a lot of different types: series of posts that satisfy my collector instincts, catharsis posts, how to/reference posts. However the mood moves me. I like to think that cynicism isn’t necessarily a prime motivator.