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

 

Comments

Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :

"**/*.pyc":{"when":"$(basename).py"},"**/__pycache__":true

renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!



I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Automatic Properties and Object Initializers in .Net 3.5

With the release of .Net 3.5 alongside with Visual Studio 2008 , new enhancements was again introduced . Some maybe well pronounced such as the inclusion of WCF, WPF , LINQ in .Net 3.0 and some just came unnoticed. If you have been accustomed of using a particular method or technique in implementing a certain code in .Net 2.0 , because of backward compatibility , you may not even notice that there are new ways of implementing it in .Net 3.5.

Here are two new concepts in .Net 3.5 that a developer may not notice ( at least in my opinion ) : Automatic Properties and Object Initializers . To illustrate these two , I am going to present the pre-.Net 3.5 way (.Net 2.0) and the .Net 3.5 way in creating a simple class with simple properties.

Automatic Properties

Creating a class can be tedious , especially when working with a list of properties , . One way to get around having to type the code for a private field and its public property getter and setter is to use a refactoring tool. However, …