Seek to Establish a Corporate Culture of Honesty

In April of this year, an executive of another company told me in a telephone conversation, "Everybody lies. You just have to get used to it."

I was stunned by the statement and have given it a lot of thought since then. It reminded me of a scene from Babylon 5 that went something like this:

Garibaldi: Everybody lies.
Edgars: That's a very sad view of the universe, Mr. Garibaldi.
Garibaldi: Yeah, well, it's the only one I got. And it works for me.
Edgars: The truth will be revealed in a couple of days. How many people can say that?
Garibaldi: I don't know. But I think the last guy got thirty pieces of silver for the same job.

Dishonesty in this technological age has even produced its own vocabulary, specifically the verb "to blag." The third definition of "blag" in the Urban Dictionary:

To convince another person that all the stuff you just made up is in fact true and worthy. Example: "Caught in a tight spot, Harry blagged his way through the conversation and somehow got the job."

I do not wish to accept the dim view that everybody lies. And I certainly do not wish to get used to it, in any way shape or form. And yet there is growing evidence both anecdotally in my own professional career and globally that the enterprise often creates a dishonest culture. Author Brian Amble in Management Issues filed a piece in 2005 entitled Corporate Culture Encourages Lying. The author mentions "blagging" and makes these three very interesting points:

"The rot starts at the top, revealing a surprisingly ambivalent attitude amongst...bosses towards the honesty – or otherwise - of their staff."

"The vast majority of company directors and senior managers believe it is wrong for their employees to lie to them. But almost half are comfortable with those same employees telling untruths on their behalf to their customers – with female bosses even more tolerant of this sort of behavior than their male colleagues."

"[Microsoft] encourages decision-making [using a] technology-based process that creates permanent digital records and maintains the integrity of the information on which those decisions are based."

In my experience blagging is most especially prevalent in the world of software development where management clings to the notion, and consultants sell the latest process magic to reaffirm the assumption, that building software is like building a house, sufficiently predictable and repeatable so as to accurately establish a firm budget, timeline and resource commitment before ground is broken. Software artisans then find themselves in the very uncomfortable position of feeling pressured to lie to their patron bosses who clearly do not wish to know that building software is often as much an unpredictable art as it is in any way a predictable science.

Software craftsmen who boldly stand their ground and declare, "I don't know how long it will take to build that," are more often attacked and labeled malcontent and misfit, shunned by managers who insist that they can bend reality to their will while they ignore what their experts have told them. And lower management who know better are caught in the ultimate catch 22. They may believe their lead developers or software architects when they say, "we cannot deliver all these features on that date," but they cannot report that fact to their own managers or customers, so they choose to lie in order to protect and even advance their own career knowing that if the implementation team fails, they may avoid accountability by throwing the developers under the bus, asserting the implementation team is incompetent and ought to be replaced.

Given the impossible circumstances in which software craftsmen find themselves, they often resort to lying to themselves and their bosses asserting that they can produce some piece of software, despite the general lack of specific requirements and understanding of the problem domain or the target users, within the time budget and resource constraints imposed by management. And then in order to avoid being exposed as just another blagger, the software artisan (or collectively the team) works impossible hours, makes imprudent quality compromises and desperately seeks for external circumstances which can be blamed for delays. Knowing that such responsibility diverting opportunities always arise, the software artisan begins to accept and even embrace the culture of lies produced by her circumstances until she does not even recognize the truth.

I know that this scenario is not universal. There are organizations who take great steps, incorporating technology and constant vigilance, to avoid the traps of dishonesty. These organizations are led by honest people who genuinely listen to their people and avoid the trap of boxing their software craftsmen into a set of assumptions that are untenable at best and downright foolish at worst. Dr. Rhonne Sanderson said it best in an article by Marcia A. Reed-Woodard entitled Don't lie to me: dishonesty can ruin professional and personal relationships:

"Although lying provides an easy out in the short-term, it comes with serious repercussions," says Dr Rhonne Sanderson, a Dallas--Fort Worth area licensed psychotherapist. He maintains that the fallout from lying can hurt others, ruin relationships, as well as rob the liar of integrity, credibility, confidence, and self-esteem. "Lying only exacerbates the real problem."

If we let honesty govern our dealings with our fellow man, we will all be the better for it. We do not need to sacrifice civility for honesty, nor should we mistake an honest disagreement for disrespect or insubordination, for when we do, we encourage others to be dishonest through their silence.

We can boldly speak the truth and expect others to do so. We can hold ourselves and others to account. We need not settle for the notion that everybody lies. And we certainly do not need to get used to it. We can and ought to do and be better.

“Come What May, And Love It” (and Learn to Laugh)

I remember listening to this wise counsel three years ago from Elder Joseph B. Wirthlin Of the Quorum of the Twelve Apostles. Today my mother reminded me of it and I enjoyed reading it again. If you have ever faced tough times or felt like you were on the losing end of a game, in sport, in work, in life, I hope this article will pick you up.

I would like to highlight one of the points Elder Wirthlin makes, perhaps my favorite:

Learn to laugh – When things go wrong, we can choose to be angry or sad or depressed, but if we choose to laugh, we can get through the present difficulty and more easily find a solution.

“The next time you’re tempted to groan, you might try to laugh instead. It will extend your life and make the lives of all those around you more enjoyable.”

When the stresses of work or a commute or a family crisis threaten to bring you down, laugh. It truly is the best medicine!

Keystrokes – Don’t Waste Them

I spend perhaps six hours a day, five days a week, fifty weeks a year hitting the keys. At my slow average typing speed of 30 words per minute (I can type faster but I’m not constantly hitting the keys, so I’m guessing here) and assuming I spend thirty years of my life doing this, my total keystrokes (assuming an average of 6 keystrokes per word) will be:

60 minutes * 6 hours * 5 days * 50 weeks * 30 years * 30 words * 6 keystrokes = 16,200,000 keystrokes

Percentage of my work output firing off an ill conceived email providing advice to someone who does not care or want the advice and will certainly not waste time reading the missive: 0.01%

Today I wasted 0.01% of my available productivity.

I’ve already consumed nearly 50% of my available keystrokes, so I’m posting this to remind myself to conserve my energy and use what remains of my personal utility more wisely.

Important note to self. Do not waste time writing perfectly good advice and sending it to someone who could not care less about your opinion. Instead, read a good book. Write a new blog post. Refactor some old code. Or just watch the leaves in the trees dance in the wind. This would be a more valuable use of that time. Time that cannot ever be recaptured.

Desktop Book Inventory of an Amazon and Borders Addict

Every few months I give up on stacking everything on my desk and begin the arduous task of cleaning it up. In my most recent battle with desktop clutter, I came to realize that I am a book addict. Set aside the numerous entertaining novels I've bought and read over the last few months because they don't make it to my work desk. If they did, I'd never get any work done.

Here's a list of just the books currently floating in the stacks on my desk. No, I am not making this up. And no, I'm not going to give you a link to each one of them. You can always hit www.amazon.com or your favorite alternative and look them up. Many of these come from my local Borders store and others from Amazon. My Amazon Prime account has more than paid for itself.

I must also confess that some of these were not purchased recently but have somehow made their way back off my shelf and onto my desk in recent months. The order is of no particular import except to note that it is essentially a LIFO list which may provide a quasi reverse chronological order to my wandering interests and/or problems/challenges.

  • Agile Principles, Patterns and Practices in C# by Martin and Martin
  • The Data Model Resource Book Volume 1 by Silverston
  • The Data Model Resource Book Volume 2 by Silverston
  • The Data Model Resource Book Volume 3 by Silverston and Agnew
  • Pro ASP.NET 2.0 in C# 2005 by MacDonald and Szpuszla
  • SQL Server Analysis Services 2005 with MDX by Harrinath and Quinn
  • Windows Workflow Foundation by Scribner
  • Programming WCF Services by Lowy
  • Pro C# 2008 and the .NET 3.5 Platform by Troelsen
  • jQuery in Action by Bibeault and Katz
  • Building a Data Warehouse by Rainardi
  • Programming Collective Intelligence by Segaran
  • Workflow in the 2007 Microsoft Office System by Mann
  • Pro SharePoint 2007 Development Techniques by Bruggeman and Bruggeman
  • Regular Expressions by Friedl
  • Regular Expression Recipes for Windows Developers by Good
  • Microsoft SharePoint Buidling Office 2007 Solutions in C# 2005 by Hillier
  • C# Cookbook by Teilhet and Hilyard
  • Refactoring Databases Evolutionary Database Design by Ambler and Sadalage
  • SharePoint Server 2007 Best Practices by Curry and English

Update: Wandering through the house, I found several more at various favorite reading spots. They've now taken their proper place on my desk piles. Here they are:

  • Pro Silverlight 2 in C# 2008 by MacDonald
  • Thinking in C++ Second Edition Volume 1 by Eckel
  • Chris Crawford on Interactive Storytelling by Crawford
  • A Programmer's Introduction to C# Second Edition by Gunnerson
  • Visual C# 2005: The Base Class Library by Balena (I won this one)

Yes, this is a sad but not unhealthy addiction. The only detriment here is to my pocketbook and the fact that I'm running out of shelf space. Do you any of you have similar addictions?

MSDN Subscription - Zupancic Heroic MVP

Props, kudos, and thanks a million to my good friend Aaron Zupancic, one of Microsoft's most valuable MVPs. Last week I pinged him to ask his opinion about a site I'd found adversting an VS 2008 Pro MSDN Pro 2 year sub for $999. It was a decent price but the site seemed a bit sketchy. He seemed to agree with my assessment and then asked if I'd like one of the complimentary VSTS 2008 MSDN Premium subscriptions that Microsoft had sent him with his MVP package. Wow!

That's over $10,000 worth of tools!

Thanks ten thousand times over, Aaron! You're awesome!

In exchange, I promise to faithfully attend the Utah user group meetings!

And before you inundate Aaron with begging, let me dispell the rumor that he has an unlimited supply. Aaron gave the other complinetary sub to another friend and user group supporter. And please don't nag him for picking me over you. Blame me, blind luck, and accidentally perfect timing!

Serenity and Leukemia: An Angel's Battle with Cancer

One of my very best friends, Phil Burns, whom I love like a brother, called me Friday afternoon. But it wasn't him.

It was his phone but I did not recognize the voice on the phone. The voice belonged to a woman whom I assume was a hospital emergency room employee. She informed me that Phil's wife Adria was boarding an ambulance with their 22 month old daughter Serenity to be transported from the American Fork Hospital to the Primary Childrens Hospital in Salt Lake City. I asked what was wrong and she told me that Serenity was very sick and may have leukemia.

I was stunned. I told her to let Phil know I'd be in touch very soon or to call me when he was able with more news. I cut short a business lunch and walked back to the office from the food court and let my boss know that I'd be gone the rest of the afternoon. On the way home, Phil called me and was very upset. He told me some of the story that you can find on his blog.

Between sobs of grief and fear, Phil begain to tell me the story. His tiny little angel named Serenity, not yet two years old, was on her way to the best childrens hospital in the intermountain west. A helicopter was on standby in case her breathing became more shallow. Phil was on his way home to pick up some things for a hospital stay that he was told would be at least three or more days. I told him I'd meet him there.

Serenity is the very definition of purity and beauty. Here large brown eyes, which you can see here on a site that a friend has put together, can melt your heart and make you want to do anything you can to alleviate her suffering.

The good news is that her prognosis is very hopeful but she will have to go through a lot to get there. She will get through it with a mountain of love and sea of patience from her parents and family and friends. But it will take one more thing: a Greengotts vault full of gold. The Burns family has no health insurance. And the hospital calls leukemia babies "Million Dollar Babies." The Burns family will need every bit of assistance we can give them. You and I can help. A donation account has been setup. Please open your wallet as far as this bright little angel can open your heart. If you have the courage to look into her eyes and wonder what the rest of her life holds in store, opening your wallet to help with the bills will be something you cannot avoid.

Starting Something New -- The Forseti Project

I've recently taken a position with a company as Principal Technologist which means I'll be doing more writing and more meetings than I have in the last few years. It also means I'll be writing less code during the work day. The great part about that is that I'll be able to focus more of my own time on writing code that I want to write.

So what is it that I'm writing? Well, I can't tell you that right now, but I'll tell you the name of the project, the name of this code: The Forseti Project.

No, I don't own the domain name. It's specifically designed to take advantage of some of the things I've learned in the last couple of years and to explore things I've not had time to work on because of a very hectic coding schedule. Now that the coding schedule seems to be lightening up, I'll be exploring some things I've wanted to delve into.

And that's all I have to say about it for the moment. As I move along, I'm sure I'll be sharing some of the things that I learn and discover as I work on this exciting new project.

I'll keep you posted.