Hey James, great post! I hope to take some of these tips on board with my current project. You mentioned that "Without specific practices to manage these tendencies teams can become insular and territorial". I have seen these issues first hand even within a single team (one person will build a service then they are shackled to that for life) do you have any suggestions of specific practices people could follow to help avoid these issues? Simply doing cross bounded context MRs? or are there some other tricks of the trade to use?
I am a big fan of Extreme Programming and think some of the practices that come out of that can be really helpful. Specifically I would look at pair programming and team rotations. Team rotations gets more tricky as a team gets larger and if technology diversifies. That would be my most immediate thought for how to counteract the negative effects that microservices can introduce.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey James, great post! I hope to take some of these tips on board with my current project. You mentioned that "Without specific practices to manage these tendencies teams can become insular and territorial". I have seen these issues first hand even within a single team (one person will build a service then they are shackled to that for life) do you have any suggestions of specific practices people could follow to help avoid these issues? Simply doing cross bounded context MRs? or are there some other tricks of the trade to use?
I am a big fan of Extreme Programming and think some of the practices that come out of that can be really helpful. Specifically I would look at pair programming and team rotations. Team rotations gets more tricky as a team gets larger and if technology diversifies. That would be my most immediate thought for how to counteract the negative effects that microservices can introduce.