Skip to main content

signs to look for when to leave your job

In relations to resign patterns , im trying help those in a dilemna of trying to determine when is the right time . Like any somewhat-geek would do , i called my bestfriend , Mr. Google. Generously , like he always does ,he gave me a series of points to ponder from different sites . Read on and ask yourself , "Have I seen these signs?".

1. You are getting sick . Stress has gotten into you and your health has been suffering a lot because of tremendous pressures from above. If your health is suffering physically, mentally or both, your job may not be worth it.

2. No room for improvement . If your company's workforce is stagnant, it means that your career won't be able to advance. An environment that offers no room for you to move up or take on more responsibility, no promotions and no rewards is not a good place to be in for long. Possibly the job began with a lot of excitement but now has become mundane with no indication of growth or change. If you are unable to see a future there, it may be time to start searching for an employer where tomorrow
doesn't look so bleak.

3. Your friends notice something's wrong. If the people close to you start noticing that you're "not the same person you used to be" or are often concerned that something is bothering you, it's a major sign that your work is making you unhappy--to the point that your mood and health are suffering (see #1 above).

4. The company is in trouble. It's important to work in a stable, reputable environment. A company that is constantly reorganizing, downsizing or changing leadership may not be a good long-term choice. The same goes for a company that provides no rules and procedures to protect employees (or provides them but they're not followed). Has your company been downsizing year after year? Are there tell-tale signs that financial woes are heading your company's way. If you see signs of financial stress on your company, it's about time to bounce before your paycheck does.

5. Your relationship with your boss/coworkers has been damaged beyond repair. Many disagreements can be resolved, but if, for whatever reason, your relationship with your boss and/or coworkers has been irreparably damaged, it may be time to bail.

6. A better opportunity comes along. There may come a point in your career when a new opportunity presents itself. At this point, make a list weighing the pros and cons of each position, and if the new job comes out on top, don't be afraid to make the switch.

Most of us have seen some of the scenarios presented above in some point of our carreer . But proper timing is still of high priority . You dont want to leave a company with a bad name or you do not want to leave your present job with no definite path to take not financially shape to move on. So before taking the dive and call it a day try to consider the following checklist :

1. Discuss your thoughts about quitting with your spouse and family (it will affect them too.)

2. Think about all your options. Can your current job situation be improved by talking to a manager? If not, have you researched other career options or companies that you'd like to explore?

3. Figure out if you can afford to quit financially. If not, try to line up a new job (even a temporary one) before you leave, or, at the very least, start sending your resume out to potential employers.

4. If necessary, reduce your living expenses to save money before (and after) you quit.

5. Whatever decision you make, try to stay positive about it. It will make it easier to find a new job or improve the one you're already in.

So there, some salient points before making a decision . Its worth looking at these before deciding on something that is so crucial . Take note that its your career that is at stake . Be responsible to whatever actions you will take.


Ryan Garaygay said…
Good one Marv! :)

Marlon said…
good one!!!
Marvin said…
Thanks guys ..
Anonymous said…
kakaloka pero ok yun ha?cge try ko nga tignan kung may mga signs sa akin.

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 :


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, …