3 ms·

> He was very hesitant to learn, he always knew better, and any PR feedback ended always with 2 hours-long calls, trying to explain him the comments there. Aft

by tasuki 6y ago

> He was very hesitant to learn, he always knew better, and any PR feedback ended always with 2 hours-long calls, trying to explain him the comments there. After this, it's totally clear where this is headed. Why were you surprised? You said he was hesitant to learn and always knew better. That struck me as a little incongruous? He was opinionated, and his opinions were different than yours. You wanted to do things your way, he wanted to do things his way. I imagine he might also describe you as hesitant to learn. From what you wrote, it really isn't clear which of you was "more right", but it's clear it wasn't a good fit.

jarek83 6y ago
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?"
- tasuki 6y ago
  That makes more sense to me, thank you. With the attitude "fine but I will do it my way anyway" I'm surprised you didn't fire him. Probably a good thing he left? It wasn't a good fit.
  - jarek83 6y ago
    Well, I was willing to continue, I was kind of waiting for the covid to fade-away so I could start working with him in an office (we live close each other) which I believe would have helped either helping him to progress or helping us to see him not a good fit. It is also that our project is quite complex, that we give a new person about a year to get to know it. But from the perspective of what just happened, yeah, it seems that we should consider firing him.

by tasuki 6y ago

jarek83 6y ago

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?"

tasuki 6y ago
That makes more sense to me, thank you. With the attitude "fine but I will do it my way anyway" I'm surprised you didn't fire him. Probably a good thing he left? It wasn't a good fit.
- jarek83 6y ago
  Well, I was willing to continue, I was kind of waiting for the covid to fade-away so I could start working with him in an office (we live close each other) which I believe would have helped either helping him to progress or helping us to see him not a good fit. It is also that our project is quite complex, that we give a new person about a year to get to know it. But from the perspective of what just happened, yeah, it seems that we should consider firing him.