Recently I have delivered a presentation Journey from procedural to reactive with stops at several conferences. One question I received after a presentation I have not answered very well.
What part of the journey caused the most objections from the new developers?
I have answered this question from my own perspective
I had trouble abandoning the returned values, especially as we switched to promises. Other people had difficulty there as well.
This answer is true for me, but the question can be answered much better in my opinion, now that I had time to think about it. The true question I want to answer is
I think the above question is a lot more important one, than figuring out a specific problem spot along the journey.
I am smart, I have experience; I have endured 5-6 hours of interviews just to get hired; I know what I am doing.
- A new employee does not feel like a noob trying to catch up
- Current employees can fill knowledge gaps without feeling like an impostor.
No matter where you start, going through a training together helps the team's cohesiveness and spirit.
The original author of the question Tomek Borek has expanded on this blog post, read How do you get folks to come to book-reading meeting?.