I was surprised because he said we didn't do what actually did for him many times. Not sure if that answers your question. For more context: I'm 8 years at the

I was surprised because he said we didn't do what actually did for him many times. Not sure if that answers your question. For more context: I'm 8 years at the project, it's multi-stack, we have some conventions worked out through years that more or less work for us. You don't want to adapt new ideas with every new developer as that would become a mess. But we are also open for changes, but they have to be reasonable and worth spending time on them. The guy is/was ok in regards of front-end skills, but he lacks a lot about how to connect the dots from business logic perspective. He never got the point about making code friendly to get through instead of easy to write at the moment when he was working on it. He also wasn't good at abstractions, and I didn't expect him to be since he was hired for junior role, but he either never wanted to accept that we want him to be better at it. One of many examples: he wanted to use BEM in Vue's single-file components. I showed that him that even Vue tells that scoping could be done by `scoped` attribute _or_ BEM. Since we use scoped, using BEM is overlapping the need of scoping. He was like "fine, but I will do it my way anyway, because I like BEM"... And then I will need to explain it somehow to some other developer who would ask - "Hey, why we have double scoping? What was the reasoning behind it?"