Skip to main content

Resignation - A Negotiation Tool?

Imagine getting into a fight with your partner. Perhaps you are not happy with something your partner has said or done. What do you do next? Do you talk things out or do you threaten to divorce your partner unless they agree to your demands. Even if they agree in the short-term, do you really think that your relationship would be same as before? Same goes with resignation.

I have seen many of my colleagues stomping feet, saying that they will resign from the organisation if their wishes are not fulfilled. Sometimes these demands are justified, sometimes not. Either way, before resigning or threatening to resign have you talked to your manager about your concerns? Have you gotten no support or only empty promises from your manager? Do you feel that there is no scope of things improving in your workplace? If your answer is yes to any of these, please by all means resign.

This applies to managers as well. If you are not able to support your employees during their tenure; don't offer them carrots once they have resigned. Even if they decide to stay, either you will be distrustful of them and always looking to replace them or vice-versa.

Let me make one thing clear. I am not saying that you should never resign. There is no point in staying in an unhealthy relationship - personal, work or otherwise. Once you have decided to exit, that should be your final decision unless there are exceptional circumstances. Most importantly, learn to accept the fact that resignation is not the start of negotiation. Rather, it is the end of it.

Comments

Popular posts from this blog

Integrating React with SonarQube using Azure DevOps Pipelines

In the world of automation, code quality is of paramount importance. SonarQube and Azure DevOps are two tools which solve this problem in a continuous and automated way. They play well for a majority of languages and frameworks. However, to make the integration work for React applications still remains a challenge. In this post we will explore how we can integrate a React application to SonarQube using Azure DevOps pipelines to continuously build and assess code quality. Creating the React Application Let's start at the beginning. We will use npx to create a Typescript based React app. Why Typescript? I find it easier to work and more maintainable owing to its strongly-typed behavior. You can very well follow this guide for jsx based applications too. We will use the fantastic Create-React-App (CRA) tool to create a React application called ' sonar-azuredevops-app '. > npx create-react-app sonar-azuredevops-app --template typescript Once the project creation is done, we

Centralized Configuration for .NET Core using Azure Cosmos DB and Narad

We are living in a micro services world. All these services are generally hosted in Docker container which are ephemeral. Moreover these service need to start themselves up, talk to each other, etc. All this needs configuration and there are many commercially available configuration providers like Spring Cloud Config Server, Consul etc. These are excellent tools which provide a lot more functionality than just storing configuration data. However all these have a weakness - they have a single point of failure - their storage mechanism be it a file system, database etc. There are ways to work around those but if you want a really simple place to store configuration values and at the same time make it highly available, with guaranteed global availability and millisecond reads, what can be a better tool than Azure Cosmos DB! So I set forth on this journey for ASP.NET Core projects to talk to Cosmos DB to retrieve their configuration data. For inspiration I looked at Steeltoe Con

Add Git Commit Hash and Build Number to a Static React Website using Azure DevOps

While working on a React based static website recently, there was a need to see exactly what was deployed in the Dev/Test environments to reduce confusion amongst teams. I wanted to show something like this: A quick look at the site's footer should show the Git Commit Hash and Build Number which was deployed and click through to actual commits and build results. Let's see how we achieved this using Azure DevOps. Git Commit Hash Azure DevOps exposes a variable called  $(Build.SourceVersion) which contains the hash of the commit. So I defined a variable in the Build Pipeline using it. Build Id and Build Number Azure DevOps also exposes two release time variables  $(Build.BuildId) and  $(Build.BuildNumber) which can be used to define custom variables in the pipeline. So we have a total of 3 variables defined: Next we use these variables in our React App. I created 3 global variables in index.html and assigned a token value to them. < script   type = "text/JavaScript&quo