Skip to main content

The Bigger Picture

Yesterday morning, I panicked because I had not written a blog entry for this week. When I first started this blog, I had so many things that I wanted to share with the world, but new topics weren't arriving as fast as I had been spending my philosophical coin.

There have been plenty of distractions here too: I've been out of work since the end of May; we have (as of this month) depleted our savings account and in fact are a few thousand dollars in short-term debt so that we could meet our financial obligations for the month; we accepted an offer on our apartment out of necessity (since we didn't know when we'd get the next offer...we had already been on the market for 18 months) that resulted in a 27% loss in two years; we're moving from NY to a location in NJ that is a few hours away; etc.

This isn't an excuse, but it is worth noting that the stress level that I have been exposed to on a constant basis has been quite high. And while I've been trying to keep my chin up, it's difficult and my frustration at the state of my life (especially my inability to provide for my family) has spilled out into my marriage.

I wanted to write this blog entry because, regardless of what's going on in your life, you cannot forget the bigger picture. Granted, this doesn't necessarily apply directly to those of you who aren't married, but I think you'll get the idea. The bigger picture is that there are always things to be thankful for in one's life, and even though it's tough to plod on day after day those positive aspects should be enough to give you the energy to continue.

Of course, this means you have to see and value what you have first. I had forgotten for a time that this woman living with me is my wife and the mother of our child; worse, I had forgotten why I married her in the first place. And it wasn't until we were fighting for a few days straight that I gave myself a time-out; put myself in the corner; and gave myself a few moments to think. Only then did I realize what had happened.

So I wrote her a love letter, and told her all of the things about her that I love. And it wasn't until then that the bigger picture came in focus once again.

The next time you're on yet another business trip because you travel 75% of the time; or you're working until all hours of the night; or you're upset because you were stuck in traffic and drove a total of 6 hours for a 2 hour meeting; etc. take a few moments to step back and admire what it is you have in your life already. You won't be sorry that you did, and neither will those that love you.

Popular posts from this blog

"Ni jiang yi yang de hua ma?"

Last week, I wrote about the necessity of having a clear message . Because this topic is so important I decided to follow-up with another entry on this general subject. This week we will approach it from another angle. (For the curious, the title says " Do you speak the same language? " in pinyin, which is a transliterated Mandarin Chinese.) Recently, a good friend of mine (who is Chinese, ironically) and I were playing pool. He had to bank the 8-ball in the pocket to win the game, and since it was an informal game and bank shots are my area of expertise, he asked me for advice. I told him, "you just need to strike the cue ball with medium speed so that it hits the 8-ball right in the middle." He didn't believe me so we marked the positions of the balls, and then he took his shot only to watch the 8-ball sail past the pocket. "A-ha!" he exclaimed. "I told you it wasn't that easy." But when we reset the positions and I made an attemp

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 that

Is No/Low-Code the Key to IT Nirvana?

 Unless you've had your head in the sand for the past year or so, you've seen the phrases low-code  and no-code  bandied about quite frequently everywhere you look.  You've probably wondered if this is something new that's here to stay or just a "flash in the pan."  Although the terms have been in the fore of the IT trade publications recently, Low Code Development Platforms (LCDP) (and the corresponding No Code Development Platforms) have been in existence since 2011.  Their roots can be traced to the 90's with 4th generation programming languages and GUI-assisted programming paradigms, e.g. IBM VisualAge for Basic, which was discontinued in 1998. For those of you who aren't familiar with either, the premise is that these platforms allow someone to quickly build applications using a WYSIWYG interface and a "click and configure" paradigm to Isn't this the source code to Roblox? rapidly build full applications with little or no coding requ