Haha,
I'm also at a bank as a lead and contractor...so I've seen some things.
Some managers/leads hate giving constructive criticism (or "bad reviews") on people so those developers go on with their career continuing bad habits. I've seen some people turn it around after a review...sometimes they just need to be told straight up about certain things and they work to fix it. One "Ron" I worked with came to me asking specifically for constructive criticism because he couldn't believe the manger only had good things to say about him.
With the proper feedback, team structure, etc, some developers like "Ron" can grow and improve. Hopefully your Ron is one of those. But...
I've also been on the receiving end of developer angst who hate constructive criticism and turn constructive feedback into a "all you accept are 10x developers" kind of drama.
After the CMS project went live, the bank offered me a salaried position as a Development Manager. For some stupid reason, I accepted.
Hah, so I'm not the only one who sees it. As an outsider who does this as a hobby, I regularly find myself... confused... by the behavior of many developers. There's certain behaviors and egos you see far more often in this field than in others.
As a long time dev myself who does this for fun and for profit, it would be easy to assume that I'm a dyed-in-the-wool "developer advocate". But I know my colleagues. Hell, I even know myself. And I know that sometimes devs are not the most rational people in the world to deal with.
It reminds me of surgeons, actually. Only in medicine surgeons are a minority, and nurses tend to be good about giving attitude back to keep things in check. Where's the collaborative checks in development? From what I hear, designers, testers, documenters, etc, largely operate as entirely seperate groups.
IMHO, the "checks" employed by most companies come down to minimizing the dev role. In other words, they tend to avoid any problems from the devs' attitudes by excluding the devs from as much of the app-design process as possible.
As you can imagine, this approach causes... other negative side effects.
I've been debating whether I want to work professionally in this field. Advancement in medicine has high costs, and I quite like programming. Been doing it as a hobby for fifteen years now. You've definitely given me a question I want to ask at interviews.
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.
Haha,
I'm also at a bank as a lead and contractor...so I've seen some things.
Some managers/leads hate giving constructive criticism (or "bad reviews") on people so those developers go on with their career continuing bad habits. I've seen some people turn it around after a review...sometimes they just need to be told straight up about certain things and they work to fix it. One "Ron" I worked with came to me asking specifically for constructive criticism because he couldn't believe the manger only had good things to say about him.
With the proper feedback, team structure, etc, some developers like "Ron" can grow and improve. Hopefully your Ron is one of those. But...
I've also been on the receiving end of developer angst who hate constructive criticism and turn constructive feedback into a "all you accept are 10x developers" kind of drama.
:)
.. waiting for part 2
Feedback is always a touchy subject. When you mix feedback with developer egos, there's a distinct danger of it turning explosive.
Hah, so I'm not the only one who sees it. As an outsider who does this as a hobby, I regularly find myself... confused... by the behavior of many developers. There's certain behaviors and egos you see far more often in this field than in others.
As a long time dev myself who does this for fun and for profit, it would be easy to assume that I'm a dyed-in-the-wool "developer advocate". But I know my colleagues. Hell, I even know myself. And I know that sometimes devs are not the most rational people in the world to deal with.
It reminds me of surgeons, actually. Only in medicine surgeons are a minority, and nurses tend to be good about giving attitude back to keep things in check. Where's the collaborative checks in development? From what I hear, designers, testers, documenters, etc, largely operate as entirely seperate groups.
IMHO, the "checks" employed by most companies come down to minimizing the dev role. In other words, they tend to avoid any problems from the devs' attitudes by excluding the devs from as much of the app-design process as possible.
As you can imagine, this approach causes... other negative side effects.
I've been debating whether I want to work professionally in this field. Advancement in medicine has high costs, and I quite like programming. Been doing it as a hobby for fifteen years now. You've definitely given me a question I want to ask at interviews.