Skip to main content

"Lazy-fare"

Quick note: last week I didn't write an entry here - it was intentional. I keep writing about the same nonsense, news articles, and I am starting to become hypersensitive to the fact that I sound like a broken record. So I wanted to step back; write less frequently; and write about more quality topics.

My oldest daughter visited last week. As I am wont to do, I took the opportunity to help her increase her vocabulary as we spent time together. This visit, the words of the day were vernacular, diction, and colloquialism. (I also explained the difference between a clutch and a klatch since she is a fashion minded social butterfly, but I digress...)

To explain vernacular I used the examples of borough vs. boro, doughnut vs. donut, and light vs. lite. To hone the point, I essentially described the latter word in each pair as an expression (pun intended) of laziness in communication. In fact, I said, so many people were lazy in their desire to communicate that these words eventually made their way into the language, i.e. the vernacular.

laissez faire (n.) - the practice or doctrine of noninterference in the affairs of others, esp. with reference to individual conduct or freedom of action.

(Or, as my Economics professor once summarized the concept: "if it isn't broken, don't fix it." This could be used to describe the slothfulness that I'm describing; I hope this sheds some light on this week's title.)

Being lazy is a common problem in many aspects of our lives. Of course, we can easily look at everyone else and chuckle to ourselves how others do a job "half assed," but it's always easier to do that than to look in the mirror. I recall a particular experience when I was 10 years old or so. My favorite music group at the time was the rock group KISS and I would frequently draw pictures of the photographs of them. One time, I saw a particularly moving picture of them in concert, in full fig, with pyrotechnics ablaze behind them, and I quickly sketched a simile of this photograph. After finishing I ran to my father to show him. His response to my hastily drawn picture? "If something isn't done right, it isn't worth doing at all."

How many times have we done things "just good enough" and then expected to be rewarded in some grandiose fashion as if we just cured cancer? This guy seems to think he should be allowed to skate into senior management just because he thinks he's good at what he does. He doesn't seem to think that leaving at 4:30pm every day to pick up his kids from afterschool is a problem even though he drops them off in the morning as well.

Here's a hint: just good enough isn't good enough unless you are quite content to stagnate in your professional career. If you don't have trigger finger sensitivity to what your management feels is the value you bring to the organization then you will not be able to successfully ensure that they realize that you are indeed valuable.

In his book How to Become CEO, Jeffrey Fox says that you should always arrive first and that you should stay latest among your peer group. (But, he adds, you shouldn't stay terribly late since that indicates an inability to stay on top of your workload.) The very pertinent example is that you'd never arrive for a movie 15 minutes late or, if I may extrapolate this further, leave before the now ubiquitous outtakes have been played after the movie credits. In my opinion, spending a few minutes extra in the morning and late afternoon shows a dedication to your role and a desire to excel at what you do. This sends an unmistakable message to management that you take your responsibilities seriously, which (when coupled with delivering results) is the greatest "value prop" that you can convey as a contributing employee.

Popular posts from this blog

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While t...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...

Application Development Done Right

In a previous article, entitled DevOps as the Ultimate Panacea? , I described how developing code without thinking about the current needs of the end user as well as the future needs once they've become accustomed to using your application ends up not only frustrating them but also can result in customer churn and ultimately lower revenues.  In this article, I'd like to describe something simple that I came across today that shows a definite degree of effort to do quite the opposite. Recently, we had a severe snowstorm, one with blizzard-like conditions, which is unheard of in central New Jersey.  Being responsible adults, my wife and I went to the grocery store to stock up on essentials (read:  chips, chocolate, etc.) in case we get stuck at home. As we were ringing up our order, the cashier mentioned to us that the store has a mobile application.  Since both of us are in technology oriented professions, we were skeptical about the need for a grocery store mob...