A Techie survives - Hard work or Talent

A programmer who has survived a dot-com bust of 2001 and a severe recession that threatened to relapse into the The Great Depression of the 1920s during the past decade will tell you they have done reasonably well. But it was not easy at all - you had to keep pushing yourself to the limits and beyond with tenacity, iron-clad will and sheer hard work to keep pace with your naturally talented colleagues, hiring and spending freeze, mass layoffs and also in general with the technology in a state of constant flux. There were endless days with minimal sleep trying to scrape through those ever-elusive deadlines that even had greater impact on health and social engagements. And then there were days when it was a do or die situation when the client production system would be down impacting their business and all eyes from the CIO to your Direct Report fixated right on you and you under tremendous pressure to deliver.

It is one thing to be solving a complex problem on your own and totally opposite when that complex problem is under the constant hammer of surveillance. The neural synapses in a state of panic go into a huddle mustering all they can to troubleshoot the issue and save your client from losing millions. Barring an odd failure here and there, when you manage to bail them out on numerous occasions, you start to command their respect and become their go to guy. While this comes with the territory and there are so many techies out there who have have gone through the same rigors and probably did better, it surely has been a satisfying experience for me on a personal level. Recently I got an achievement letter for being the most billable consultant in my company last year by a stretch along with a $200 gift certificate. While this may not sound a big deal, these small tokens of appreciation keep you going.

A high-profile entrepreneur Jonathan Gheller (CEO Mixtent) asked me on Storylane - What is my greatest talent? How do you use it? - I would say I am not so sure (may be knack for problem solving) but I do know that I have bundles of sheer perseverance and grit, that never give-up attitude that has bailed me out on countless occasions. And on those occasions when I have sent emails out at 3 or 4 in the morning notifying your VPs and CIOs that you did it and their praising rejoinders on a Job well done - that sense of accomplishment has been unparalleled to date.

Even the most exciting talents in the world are invariably wasted sans hard work.

 

Dilemma of an IT Architect

At a time when my IT career appears to be stuck in the second gear, a few questions have been springing up lately in my mental corridors. The dreaded of them all is – Have I hit the colossal wall of career stagnation? Being an IT architect have I run up the steps of the corporate IT ladder? Do I have to settle for this for the rest of my career lifespan?

In a typical IT hemisphere, graduating to a Solution Architect or an Enterprise Architect comes with some healthy perks and a degree of job satisfaction depending on what kind of work you are involved in. If you are an Architect in Google or Amazon, clearly you have your hands full and you may be working on the next big thing like a Google Glass or bolstering Amazon’s Cloud offering. Technology dances on your fingertips while you conceptualize and model the products. Breaking new ground and constantly moving towards that finish line adds to the daily thrills along with the pure job satisfaction. The innovation quotient keeps you on your toes all the time. However there are times when Solution Architect role in another Fortune 500 company may lack that excitement buzz. While you may be engaged in some cool stuff like modeling and automating a mortgage business process on an IBM middleware, your innovativeness is hampered by the scope of the project and the choice of the enabler. Even a slightly aging technology starts to hamper your own growth as you see your Google peers hurtle by you.

Before I start digressing too much, the point I am trying to put across is when you are already positioned as an Architect, there is hardly any room to move up the ladder, and when you are stuck working on the same platform/technology for couple of years, your skill-sets start to depreciate and eventually become dated. This sense of discomfiture leaves you wondering – Jeez!! What do I need to do to get my career throttle into the third or fourth gear?

Should one move out into a parallel role in an innovation-centric work culture where the best brains huddle up to write the next Dropbox or an Open Table. Or should one fork out into a managerial position by pursuing an MBA. Even if you land a manager position in some company will you keep up with the agile driven projects, tight deadlines and managing the allotted budget. Bottom line you are sort of severed from the technology landscape specially designing and coding apps. Or should one branch out into an entrepreneurial role by engendering a business idea that you have the conviction to launch as your startup knowing fully well, finding that ever-elusive angel investor might feel like climbing the Everest.

Some of the counter-questions boomerang back - Can you handle the rigors of sustaining a startup, work the long hours, be ready to sacrifice your social outings and ride the storm out during the ebbs with your coworkers/co-founders. Or can you pay for your MBA program and land a decent job Will it bring a sense of closure? Will you not miss writing some beautiful code on your favorite IDE.

The answers to these myriad of options and the dilemma surrounding them will eventually come from within knowing fully well who you are and what you are capable of.