4 Fixed grammar and phrasing
source | link

Dealing with institutionalizedinflexible programmers.

Some timesSometimes programmers who work inon a project for long time tend to get institutionalized. It isinflexible, and it becomes difficult to convince themreason with reasoningthem. Even if we do manage to convince them, they willcan be adamantunlikely to take suggestion on boardimplement our suggestions. How do we handle the situation without developing friction in team?

Institutionalized in terms of practices. IFor instance, I recently joined in a project where the build &release& release process was made sois too complicated withand has unnecessary roadblocks. My suggestion was

I suggested that we can get rid of some of the development overheadsoverhead (like filling a few spreadsheets) just by integrating defect management and version controllingcontrol tools (both are IBM-Rational tools so integration can be a very easy and one-off effort). Also by using Also, if we use tools like Maven & Ant (projectthe project involves javaJava and some COTS products) build & release can be simplified andwhich should reduce manual errors&errors & intervention. I

I managed to convince others and I'm ready to put efforts for developingin the effort to develop a proof of concept. But the ‘Senior’ developer is not willing to take it on board. One reason could be, possibly because the current process makes him more valuable.

How do we handle this situation without developing friction in the team. ?

Dealing with institutionalized programmers.

Some times programmers who work in a project for long time tend to get institutionalized. It is difficult to convince them with reasoning. Even if we manage to convince them they will be adamant to take suggestion on board. How do we handle the situation without developing friction in team?

Institutionalized in terms of practices. I recently joined in a project where build &release process was made so complicated with unnecessary roadblocks. My suggestion was we can get rid of some of the development overheads(like filling few spreadsheets) just by integrating defect management and version controlling tools (both are IBM-Rational tools integration can be very easy and one-off effort). Also by using tools like Maven & Ant (project involves java and some COTS products) build & release can be simplified and reduce manual errors& intervention. I managed to convince and ready to put efforts for developing proof of concept. But the ‘Senior’ developer is not willing to take it on board. One reason could be the current process makes him valuable in team.

Dealing with inflexible programmers.

Sometimes programmers who work on a project for long time get inflexible, and it becomes difficult to reason with them. Even if we do manage to convince them, they can be unlikely to implement our suggestions.

For instance, I recently joined a project where the build & release process is too complicated and has unnecessary roadblocks.

I suggested that we get rid of some of the development overhead (like filling a few spreadsheets) just by integrating defect management and version control tools (both are IBM-Rational tools so integration can be a very easy one-off effort). Also, if we use tools like Maven & Ant (the project involves Java and some COTS products) build & release can be simplified which should reduce manual errors & intervention.

I managed to convince others and I'm ready to put in the effort to develop a proof of concept. But the ‘Senior’ developer is not willing, possibly because the current process makes him more valuable.

How do we handle this situation without developing friction in the team?

3 added 780 characters in body
source | link

Some times programmers who work in a project for long time tend to get institutionalized. It is difficult to convince them with reasoning. Even if we manage to convince them they will be adamant to take suggestion on board. How do we handle the situation without developing friction in team?

Institutionalized in terms of practices. I recently joined in a project where build &release process was made so complicated with unnecessary roadblocks. My suggestion was we can get rid of some of the development overheads(like filling few spreadsheets) just by integrating defect management and version controlling tools (both are IBM-Rational tools integration can be very easy and one-off effort). Also by using tools like Maven & Ant (project involves java and some COTS products) build & release can be simplified and reduce manual errors& intervention. I managed to convince and ready to put efforts for developing proof of concept. But the ‘Senior’ developer is not willing to take it on board. One reason could be the current process makes him valuable in team.

Some times programmers who work in a project for long time tend to get institutionalized. It is difficult to convince them with reasoning. Even if we manage to convince them they will be adamant to take suggestion on board. How do we handle the situation without developing friction in team?

Some times programmers who work in a project for long time tend to get institutionalized. It is difficult to convince them with reasoning. Even if we manage to convince them they will be adamant to take suggestion on board. How do we handle the situation without developing friction in team?

Institutionalized in terms of practices. I recently joined in a project where build &release process was made so complicated with unnecessary roadblocks. My suggestion was we can get rid of some of the development overheads(like filling few spreadsheets) just by integrating defect management and version controlling tools (both are IBM-Rational tools integration can be very easy and one-off effort). Also by using tools like Maven & Ant (project involves java and some COTS products) build & release can be simplified and reduce manual errors& intervention. I managed to convince and ready to put efforts for developing proof of concept. But the ‘Senior’ developer is not willing to take it on board. One reason could be the current process makes him valuable in team.

    Tweeted twitter.com/#!/StackProgrammer/status/37471932328706048
2 edited tags
| link
1
source | link