Skip to main content

Bored? Now what?

It's no secret that I've been unemployed since the end of May. And although I'm sticking by my decision to take my time and find the right position that satisfies both my responsibility to provide for my family and my desire for career growth, I won't deny that the past few months have been tough. In fact, with my wife having her own, home-based business, we are frequently ready to maim each other simply due to my ennui and our constant exposure to each other.

This "I'm so bored that I want to gnaw my fingers off" feeling can happen at other times too. Several years ago, during the last business downturn (or, more specifically, during the Internet bust that occurred earlier this decade), I was working for a small company that produced web-based software. Our pipeline was in the dump and there was little to do, which was scary considering that we had 150 people and a rapidly dwindling bank balance.

To put it bluntly, even though we had some small consulting engagements that kept my team busy some of the time, there was never enough work to engage all of us on a regular basis so we did things to keep us busy. There should be no surprises here: one colleague played an acoustic guitar; another (a foodie) took us to various (and excellent) places for lunch; the rest did other things like surf the net; I played games and chatted with my family via instant messenger.

Even though it was no surprise that the company was going down no one in the development side of the house seemed to take the news seriously even after two rounds of layoffs. And when the company finally made the really hard decision to let go of 50% of the remaining staff (starting with the resignation of the executive management team), we found ourselves wondering how we were going to bounce back.

Well, I didn't (not quickly at least). I was out of work for 4 months, used a significant portion of our savings, and only because a friend of mine had a lot of contacts did I start work again as an independent consultant doing application development at one of the media companies.

If I had the wisdom to do so, there were several things that I could have done that would have lessened the blow of my layoff.

Education. .NET was already in the late stages of its beta and was already generating huge amounts of buzz. I had not bothered to look at it (mostly due to Microsoft's never ending reputation of not being able to release something worthwhile in its first release; I decided to wait until version 1.1), yet I could have been on the cusp of one of the biggest software development movements in recent memory.

Adapt. My colleagues in sales, marketing, and other areas of the business were busy to some degree but not so busy that they wouldn't have been able to show me what their job entailed and especially how they fulfilled the responsibilities that their position carried. This exposure, while it would not have made me an expert, would have added to my overall value to the organizations that I worked for in the future.

Market. I knew that my position didn't have enough activity to warrant me staying at the company (unless the company's fortunes reversed), yet I didn't take the opportunity to sell my worth to the decision makers in the company. And while blogs weren't yet all the rage, there were still other ways to get on people's radar (namely the USENET groups, writing letters to the editors of major trade publications, etc.) that I didn't take advantage of.

Look. By the same token, I knew that my job was in jeopardy. I wasn't willing to admit that the job market, though, was in such a sad state that it would take a few months to find something comparable. Had I done so, I could have started looking for a new position much sooner.

My point is that in depressing times it is easy to allow yourself to give in to despair, yet this is exactly the time when you can take advantage of slower periods of activity to better yourself as a professional. Louis Pasteur once said, "luck favors the prepared mind." Prepare yourself, then, for changes ahead and you'll be able to focus on the execution when those changes occur rather than lose your focus as you wonder what to do next.

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