Childish developers
-
ednrgc wrote:
given some of the worst assignments
But VB coding would be considered cruel and unusual punishment in some places ;P
only two letters away from being an asset
-
Mark Nischalke wrote:
See above, the team lead isn't really up on modern development practices himself.
It's not modern practices !!! That developer is sabotaging your environment by preventing other developers to work on some source files.
Maximilien Lincourt Your Head A Splode - Strong Bad
I agree. Prior to this there were two people here, now there are six, but the original two still haven't fully gotten the concept of team work.
only two letters away from being an asset
-
It's long been my perspective that coding is easy. People are hard. Especially the creative sorts, like developers. That's why I've focused my writing and speaking over the years on practical strategies for dealing with bosses / coworkers / users / etc. who exhibit less than reasonable attributes. It ain't as sexy as coding, but I find that it's rarely the techie issues that screw up a project. It almost always comes down to people. (I can actually think of more descriptive words for folks of this type, but I'm trying to be on my best behavior here. :-D)
Author of The Career Programmer and Unite the Tribes www.PracticalStrategyConsulting.com
You're right, people are hard from time to time. I have found that a workplace where people are awarded for achievements. Even small compliments go a long way. People are awarded by comp time, etc. for going above and beyond. We have team meetings to discuss items, and learn who needs help to meet a deadline. Developers are also present at design meetings. It gives them a sense of being part of the larger goal. Many times they see things that may become issues down the road. So, it's really a win/win situation.
-
You're right, people are hard from time to time. I have found that a workplace where people are awarded for achievements. Even small compliments go a long way. People are awarded by comp time, etc. for going above and beyond. We have team meetings to discuss items, and learn who needs help to meet a deadline. Developers are also present at design meetings. It gives them a sense of being part of the larger goal. Many times they see things that may become issues down the road. So, it's really a win/win situation.
You're right, people work for money but they'll walk on water for recognition. These are the sorts of the things I focused on when I wrote Tribes. Once you answer a person's question of "what's in it for me" you have an enthusiastic team member for life.
Author of The Career Programmer and Unite the Tribes www.PracticalStrategyConsulting.com
-
Demote him to a mission critical role?!?!? Are you mad!
regards, Paul Watson Ireland & South Africa
Shog9 wrote:
I don't see it happening, at least not until it becomes pointless.
:laugh:
Author of The Career Programmer and Unite the Tribes www.PracticalStrategyConsulting.com
-
As if I would trust the recipe for the Sacred Swill™ to any of my coworkers :rolleyes:.
Software Zen:
delete this;Gary Wheeler wrote:
for the Sacred Swill™
Black Jet Coffee! mmmmmmmmm Pity they don't sell it any more.... closest they have now is black satin espresso.... Olive Branch Coffee in NM[^]
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Sorry bit of a rant. While one of the developers on the team was out for two weeks I had to modify his code, make some improvements I had talked to him about earlier and he never understood or thought it was necessry. Now that he is back to work he is upset because I did it and now refuses to check the files in to VSS so no one can modify them. :sigh: :((
only two letters away from being an asset
I've worked with this type before. The only solution was to place him on unpaid leave.
My Blog A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. - -Lazarus Long
-
I've worked with this type before. The only solution was to place him on unpaid leave.
My Blog A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. - -Lazarus Long
-
Sorry bit of a rant. While one of the developers on the team was out for two weeks I had to modify his code, make some improvements I had talked to him about earlier and he never understood or thought it was necessry. Now that he is back to work he is upset because I did it and now refuses to check the files in to VSS so no one can modify them. :sigh: :((
only two letters away from being an asset
-
See above, the team lead isn't really up on modern development practices himself. Myself and the PM have tried to educate them but there is resistance, especially with things they don't understand. Even after showing the samples and articles. I'm sure it has something to do with job security and feeling threaten by newer techniques (and people) But the good news is I'm just a consultant, I don't have to stay after the project is finished.
only two letters away from being an asset
Mark Nischalke wrote:
But the good news is I'm just a consultant, I don't have to stay after the project is finished.
Aha! You do realize that as soon as you go all the changes you did that the guy didn't like are going to be reverted?! Just take the check and move on... :suss: