Skip to main content

The Exit Door

A few years ago , I wrote about the concept of singleton and eventually mentioned the term "Resign Patterns" in the process.  In the realm of software engineering, design pattern is a general reusable solution to a commonly occurring problem within a given context in  software design. Similarly, resignation has been a general solution to a commonly occurring problem within a workplace.  Having only passed two resignation letters since I started working, clearly shows that I was never a fan of this solution. However, it does not mean that I am not fascinated by it and that my mind is not cheerfully entertaining and  playing with the idea of bidding goodbye to my bosses at some point.

This morning, while waiting for my colleagues, my attention was caught by a seemingly regular signage. The glowing red light that reads "EXIT"  got my imagination running. 
  • Are there better opportunities beyond the exit door? 
  • Have I been playing too safe by just staying on a defined comfort zone for years?
  • Do I have the courage to explore the world beyond the door?
  • Did the door  prevent  me from reaching further possibilities? or even reaching higher grounds?
  • Are the opportunities within too enticing that I did bother getting out?

My mind continued to fly as it  searched for answers.

 
If there is one thing  the "resign patterns" have taught me is that, sometimes,  it is not the greener lands that leads us to the exit door.  Often, it is the breeding disappointment within that pushes us to run towards the nearest way out.  The tempting call from the outside can easily be countered by camaraderie and friendship that binds a team ( not to mention counter offers that is hard to resist ). But when the team that you stood for over the years abandons you and the organization that you served well continues to disappoint you, the way towards the exit door becomes easier to find.  If the workplace has become a breeding ground of tension, dissapointments and misunderstanding thats the time we have to bid goodbye.  Organizations never realized your true worth until you are long gone.

Yet, decisions like this, is not a simple walk in the park. When we start to think about all the things that we have to consider, we realize that the path towards the exit door is not easy. The exit sign will remain to hang on top of that door. Everyday, I will walk pass it and tease my mind to go beyond it.I will entertain the idea, I will savor the feeling of farewell and I will continue to laugh about..Till I have all my reasons and all the strenght needed to walk pass through it....

 

Labels:

Comments

Post a Comment

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...
Post a Comment
Read more

How to Kill a Slow Process using DOS Batch File Script with TaskKill and TaskList

If you are still trapped in the era of batch files and command lines in Windows environment, here is something you can add to your DOS cheat codes.  Lucky for us here, we are still using DOS batch file to implement installation of some updates to our system. Here is a simple batch file script that is designed for slow systems that requires a significant amount of time to kill a particular process. The requirement is simple,  do not start any copying or moving of files until  the process ( i.e. MyProcess.exe) is totally killed by DOS. The simplest solution would be to use TASKKILL to kill the process, wait for a few seconds  then start copying/ moving of files there after. Unfortunately, while we were testing this simple step on a slow machine, DOS would take an awful lot of minutes to kill the process in question. Thus, when our delay is reached, we would encounter error on copying/moving files that is currently used by the unkilled process causing a failure on ...
1 comment
Read more

The Story Behind the Name C#

I remember one time in an exam for employment , the first question was - who is the father of C#? I have been working with the language but never did I ask myself who actually started the language ( of course Mirosoft was the brainchild , right? ) . After a googling expedition I found out who was the culprit - Microsofts Anders Hejlsberg . I was not interested why it was called C# then , but opening my VS2008 today , I stumbled on one of the articles being shown at the VS2008 opening page - "Computer World: The A-Z of Programming : C#". Its an interview with Anders discussing the history and beyond of C# . Heres the cool part , the name for C# prior to its release was actually COOL (C like Object Oriented Language) . Below are some lines taken from the interview: Why was the language originally named Cool, and what promoted the change to C#? The code name was Cool, which stood for ‘C like Object Oriented Language’. We kind of liked that name: all of our files were called .coo...
Post a Comment
Read more