Skip to main content

A Tale of Tails

Every weekday morning, my family goes through the same routine:  I get up first and head downstairs for coffee; then our 4 year old wakes up and kicks my wife out of bed; at 8 am, I let the dog out back to relieve himself and get his morning meal ready while he is doing so; etc.

This morning, I observed something rather fascinating about our dog's behavior.  Due to the layout of our house and the orientation of the back deck, when I let him back in he takes off like a rocket.  Because we have hardwood floors, he can't turn at that speed and has to take a very circuitous route to get to the kitchen where his breakfast awaits.  I found this amusing because this is not an uncommon behavior in the professional world either.

Over the years, people often question what is more important:  design or execution.  I first encountered this seemingly philosophical (using that term very loosely) subject in college, where my professor in VLSI design stated unequivocally that a good design could be fatally hampered by poor execution.  My dog would seem to confirm this as well because even though his thought of going straight to the kitchen for breakfast is a good one, his inability to execute properly (i.e. slow down) forces him to take the most inefficient route to get to his food.

Balance is necessary
That's not to say that the act of focusing on goals should be relegated to the back burner completely.  Contrast the behavior of our canine pal with that of the Canadian rock band, Rush.  For over 30 years they have focused on one thing only:  making what they feel is the best music possible without regard to airtime on the radio or awards that they could possibly be given.  In spite of the fact that they have a rabid fan base, it is only now that they are finally nominated for induction into the Rock and Roll Hall of Fame.

Could they have arrived at this point sooner?  Yes, if they were willing to sacrifice the design of their band and focus instead on what the media expected (more radio friendly vocalist and songs to match).  But they didn't change their design even though it meant that they could possibly have never been nominated.

Careful planning to avoid unnecessary risk by developing contingency plans is a necessity to allow you to avoid making whimsical decisions on the fly that could eventually unravel your bigger plans.  But too much planning can yield an inability to execute due to a fear of never being ready.  The point here is that a healthy balance of design and execution is the ying and yang of business whether this applies to a product you are creating; your career; your ability to make a sale; etc.

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...