My 2 cents. You are stressed both from the new job and the pregnancy, and you are bit confused by what's lying ahead. This is normal and would be weird if you

My 2 cents. You are stressed both from the new job and the pregnancy, and you are bit confused by what's lying ahead. This is normal and would be weird if you were not reflecting on yourself at this time of your life. Getting a child will in any case change your life rather dramatically, but this is really not such a big deal, many people have been there before, in a few weeks/months you'll have adapted to the new normal. However, I don't think it makes sense to try to change your situation right now. I would wait at least 15 months (pregnancy + some time to make some adjustments to your life). You'll probably have a clearer view at that time of what is important to you, how is your new schedule. You will discover new priorities you can't imagine or that you overestimate today. So the question is, are you ready to keep your job for another 15 months ? The second point of your post seems to be your dissatisfaction with your new role, and that you can't find your place in your new team. > Being the guy constantly trying to change how work get’s done makes people not like you. Which sucks. It does not have to be this way. People tend to resist change because they are afraid of what is lying ahead, afraid of a loss of power or responsibility, etc. If you have been an expert on X for years, you are not really enthusiast if the whole team is moving to Y. I would advise to read some books on change management: try to get the support from key stakeholders, identify why people are resisting change, try to find what would appease the reluctant one (training, promotion, etc), identify the early adopters, communicate your early success, etc. If you are really moving to Y, why not putting the expert on X in charge of the new technology ? Rather than seeing the change as a threat, it could become a great personal challenge. If you show clearly to people what they will gain by changing in their everyday life : easier debugging, lesser cost, easier deployment, less hassle, etc , they will like you. You also need to tailor your discourse to your audience, the boss is likely not interested by the same thing than a developer. Also keep in mind that even if your new framework is the best technology ever, it does not mean that it will convince people. Convincing people to change is almost orthogonal to the technical merit of the solution. Your job sounds pretty interesting! You might only be missing a few concepts/skills (or you are working with very grumpy people which is also possible) For what's it worth, I am also trying to introduce new tools/technology in my bigCo SW team. It does not feel as bad as what you are describing, but I have the distinct feeling that I am sometimes considered as the crazy annoying guy (for trying to introduce things that have been mainstream for 10 years... whatever) PS : Sorry for my spelling/grammar, I have only slept a few hours last night because of my newborn son. So it is likely worse than usual.