3 ms·
I've been in this industry for three decades now, and one thing that I've observed in a number of teams is that when someone has a really strongly held belief a
by llm_nerd 2y ago
I've been in this industry for three decades now, and one thing that I've observed in a number of teams is that when someone has a really strongly held belief about something in this field -- microservices, languages, web frameworks, where to put the trailing curly brace, indentation, etc -- a good percentage of the time it can be traced back to some interpersonal issue/conflict they had with someone else in their workplace/team/peer group.
I could watch it happen in real time. Person A would advocate a position on one of those items, and their nemesis on the team, B, would then build their whole personality around being against that position. They would adjust every existing belief to now fit their new perspective. It would become boringly predictable.
So when someone is really passionate and certain about something like this, my natural thought is "who hurt you?". Especially on something as amorphous and hard to pin down like microservices where it's easy to attack it from a hundred angles that likely have no relevance to an actual implementation.
Like, it really doesn't matter that much. You can make an excellent solution using almost any approach. You can use all sorts of frameworks and languages and platforms, etc. It'll all be okay.
- whstl 2y agoThis is interesting. I agree. I never really thought much about it but I definitely remember some people doubling down on whatever preference they had after a certain discussion. I remember one guy screaming at me because I didn't use the pattern he wanted in a certain project. I didn't really care, but later I found he had a fight with the CTO the day before about said pattern. > Like, it really doesn't matter that much. You can make an excellent solution using almost any approach Yep. One can also make a horrible solution with almost any approach. ;)