Childish developers
-
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
-
Demote him to making coffee.
Truth is the subjection of reality to an individuals perception
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.
-
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
-
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.
As if I would trust the recipe for the Sacred Swill™ to any of my coworkers :rolleyes:.
Software Zen:
delete this; -
As if I would trust the recipe for the Sacred Swill™ to any of my coworkers :rolleyes:.
Software Zen:
delete this;"It's all in the grind, all in the grind."
regards, Paul Watson Ireland & South Africa
Shog9 wrote:
I don't see it happening, at least not until it becomes pointless.
-
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.
-
concur. Sounds like someone is forgetting who actually owns the code. Now, if you busted it, then that's another matter :). But sounds like to me a tantrum. If *I* were the project manager, we would have a "we don't seem to be communicating" meeting...
Charlie Gilley Will program for food... Whoever said children were cheaper by the dozen... lied. My son's PDA is an M249 SAW. My other son commutes in an M1A2 Abrams
-
Mark Nischalke wrote:
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.
this is unacceptable in a professional work environment. you should resolve this with the help of your boss or your team leader; have him arrange a meeting with both of you, and discuss this. If that behaviour continues, the boss and/or team leader should fire that programmer.
Maximilien Lincourt Your Head A Splode - Strong Bad
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
-
concur. Sounds like someone is forgetting who actually owns the code. Now, if you busted it, then that's another matter :). But sounds like to me a tantrum. If *I* were the project manager, we would have a "we don't seem to be communicating" meeting...
Charlie Gilley Will program for food... Whoever said children were cheaper by the dozen... lied. My son's PDA is an M249 SAW. My other son commutes in an M1A2 Abrams
As a PM, I don't deal with these issues lightheartly. It is the one thing that can drive a steak through the heart of a team. That person will usually be given some of the worst assignments for a while to make sure he/she appreciates the peaceful/pleasurable environment I like to keep.
-
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:
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
-
As a PM, I don't deal with these issues lightheartly. It is the one thing that can drive a steak through the heart of a team. That person will usually be given some of the worst assignments for a while to make sure he/she appreciates the peaceful/pleasurable environment I like to keep.
-
As a PM, I don't deal with these issues lightheartly. It is the one thing that can drive a steak through the heart of a team. That person will usually be given some of the worst assignments for a while to make sure he/she appreciates the peaceful/pleasurable environment I like to keep.
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
-
Vikram A Punathambekar wrote:
I know I'm tackling the symptom rather than the cause, but isn't it possible for the admin to release his lock on the file?
Talking of source control, I've been waiting 40 minutes for VSS to complete whatever the heck it is doing. It is doing stuff, but it is just taking a long time. Talking about admin releases on locks. At the last place I worked I once went on holiday with a couple of files checked out by accident. On my retutn I was told that they had to have the admin release them and my changes were lost. I was also told that I had to pay a penalty. So, I had to buy donuts for everyone.
Upcoming Scottish Developers events: * Glasgow: Tell us what you want to see in 2007 My: Website | Blog | Photos
1. Get Vault or another source control tool. Almost anything is better than VSS. 2. Use your better source control tool in edit/merge/commit mode (if you have a choice of modes). No exclusive locks = faster working, no danger of losing changes. Note that even if you took an exclusive lock and it was released by an administrator, Vault remembers which version you were basing your changes on and tells you you need to perform a merge. It doesn't overwrite your changes unless you tell it to, and even if it does it makes a backup copy of the files. You can't check in until you resolve the merge status.
Stability. What an interesting concept. -- Chris Maunder
-
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
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
-
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)