![]() Very often, we don't understand management's choices because we don't have all the needed information to build our opinion. Yes, they may have their own reasons for keeping those technologies. It may makes things more difficult and you should always avoid to hurt other feelings as much as you can (I like to make the association here with Emotional Intelligence). Telling that you leave because you think they are locked into a Blub may not be appropriate for two reasons, even if honesty is usually the best option in most situations:įirst it may hurt them, in their feelings, and adopt a defensive position against you. Don't forget that he will probably be called by your new employer (most serious ones do it). Unless you can make a data-driven case for a change, why should the business change?įirst you don't have to justify yourself when you quit a job, but it's generally what you should do to keep good professionnal relationships with your employer. (Yes, I had an engineering manager who believed this). After all it may be more "productive" to not have to write the tests for the new code or to fix broken tests. Lastly, how are you defining "productivity". Unless you have data about the productivity question, you just have an uninformed opinion. The things that slip through the cracks now don't. I make a point of documenting productivity barriers and their time cost every day. I am not saying you shouldn't move on if Blub does not work for you, just don't confuse your feelings with the business' needs. It is far cheaper to replace you with someone who thinks that Blub is awesome. I don't understand why you would expect the business owner to discard their investment in the existing (functioning) code base just because the language/framework does not mesh well with your brain. The Blub framework may still meet the business needs of the business owner. Someone not familiar with it is probably going to think you're just one of those platform elitists and ignore overt messages, and someone who is familiar with Blub and doesn't like it, or is on the fence, will either already sway to your side after more experience, wouldn't have applied to the position, or would ignore your "stay away!" messages, anyway. ![]() Explain in comments why you did something a certain way and be matter-of-fact about it - "doing it this way because our version of Blub doesn't support Alternative Method X." If your successor is familiar with Blub and doesn't mind it, then they're not going to heed any kind of "stay away!" messages. Try to keep in touch with them as part of your professional network.Īs for your successor and documentation, simply make sure all the issues/quirks that you know of are documented somewhere, either in the code or in a wiki or some other structured documentation platform. ![]() Offer to connect with them on LinkedIn if you haven't already. Make sure your boss and coworkers know that you enjoyed working with them. Make it clear that it's not the office environment. As Paul said in his answer, it keeps the reasons for you leaving close to you and reduces the chance of people taking it personally. This allows you to say something along the lines of "I don't like it," without getting into the religious debate of code languages/platforms. Explain that you would prefer to work on a different platform and that Blub isn't your cup of tea. Say you want to take your career in a different direction. Granted, this doesn't necessarily help your current company, but it's also not entirely up to you to fix the matter. This gives you an easy out - "I've been offered a position that better suits my career goals" (or some other more neutral line). You've dealt with it until now, so find a new job and wait to leave until you get an offer. Obviously, this won't work if he's in love with it and thinks it's the future of technology.) It will also give you a gauge of whether it's worth sticking out through it, if the company has decided to change technologies. You may also gain some insight into why the company is using Blub and sticking with it. This will allow you to voice your concerns and gauge how your boss responds and how open he is to different technologies (or, how married he is to Blub). Suggest an alternative that you feel is superior and be ready to back it up with facts (remember - objective data). Provide specific cases and instances where it's hurting the company (or where some other platform would help the company better). Explain to your boss that you think Blub is a bad decision for the health and growth of the company. I don't know anything about Blub itself, but I've been in a similar situation where there was something about my job that I think should be fixed, but don't want to burn bridges.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |