Slashdot Mirror


When Should You Quit Your Job?

Moe Taxes asks: "I want to hear from Slashdot readers who have quit jobs or turned down offered jobs because it was not what they wanted to do. Why did you do it? Was it ethics, ambition, pride, or disgust? And how did it turn out? Did you get to do what you wanted to do, are you still looking, or did you come back begging for another chance? I have always written software for windows, but never with Microsoft tools. I don't feel like I have enough control over the product when I use Microsoft programming environments. My company was bought recently, and is in the process of becoming a C# VisualStudio shop. I said thanks, but no thanks and left. Am I a fool for giving up steady work and good pay?"

4 of 1,245 comments (clear)

  1. The short answer by PHPee · · Score: 0, Troll

    "Am I a fool for giving up steady work and good pay?"

    Yes. Yes you are.

  2. Re:Better have something inline by heavy+snowfall · · Score: 0, Troll

    You are seriously lame. FU

  3. Re:Never Quit! by flibuste · · Score: 0, Troll

    Actually, I'd like to know if you've sat down in front of VS.net recently... It's quite robust and very mature.

    My manager put me on a project using VS.NET (mixture of ASP, C#, VB...you name it), trying to convert me from the J2EE world.

    Believe me, he gave me the best opportunity to get my hands in .NET and find out that this ..thing..is just but ugly and not suitable for serious development (you know, when you have bewolf clusters of insensitive clods). The great thing is now I have a lots of arguments to sell more J2EE. Yet I hate my .NET job. It's frustrating, messed up all the time and goes nowhere close in quality.

  4. Yes you are a fool. by jotaeleemeese · · Score: 0, Troll

    But fools are a force for progress.

    But still, you are a fool, don't pat yourself in the back.

    --
    IANAL but write like a drunk one.