Taking the Leave Option

I posted a little while ago about IDE choice based on a developer having to use IntelliJ in secret because his shop mandated all developers must use Eclipse at all times. To avoid this sort of situation I pointed out that you should always have an automated build that has no IDE dependencies. Chances are if you have that no one can argue that you must use one particular IDE.

Then there’s the second option:

Then there’s the shops that believe everything must be standardized. Avoid these standardization-happy shops.

Apparently the developer went with the second option and is looking to be successful elsewhere.

6 comments to Taking the Leave Option

  • Hi Ed,

    It’s funny that your following my soap opera of a situation. Maybe you could be my therapist. I gotta say, it has been interesting if nothing else. I probably should put a post up back on my site giving others an update.

    Here’s the latest thing I’ve noticed and a source of some angst and concern — you interview with a few shops and everyone is interviewing in the same manner. They’re asking all sorts of technical minutia questions (the type of stuff you can look up). They want you know every possible API in some level of detail and want you to have experience in *everything*. So you pass the interview (by either luck or divine intervention) and then realize they aren’t DOING any of these things they were questioning you on. They fail to adhere to even the simplest of best practices.

    So, the road to my next employer is taking a little longer because I am being more selective about where I go next. I don’t want a “job”, I want a place where I can be productive and engaged in the work I do.

    Cheers…

  • Yeah, I’ve been through that before. They ask trivia questions. My favorite ever was what does ASP stand for?

    It’s always better to find a shop where you can be happy, but it can definitely be a longer hunt.

  • Exactly right. If you make it clear up front that the build must work outside of any particular IDE, then standardizing on an IDE becomes a moot point.

    We chose maven as a build tool just for that reason. It has some useful plugins that make IDE integration very easy. Maven plugins to generate Eclipse, IDEA, etc. projects and IDE plugins that allow developers to run an embedded maven. Gotta love that.

  • Hi Ed,

    I thought I’d come back one day and update you on that situation that plagued me at the use-Eclipse-or-die shop I was at. Yes, I left and ended up taking a job as a dev manager somewhere else.

    I couldn’t be happier.

    In house, we have people on Linux, Windows and Macs. Some use Eclipse, some IntelliJ.

    And it’s peaceful.

    By being such a Nazi about it, my former shop actually caused me to land a better paying job with more responsibilities.

    Go figure.

  • I should add that I landed my new position months ago and there was no break in employment (unemployment time).

  • Great to hear you found better gig. And welcome to the world of technical management. If you can’t change your job, change your job.