Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

+ - How do you deal with programmers who have not stayed current? 1

Submitted by skaffen42
skaffen42 (579313) writes "The recent Ask Slashdot about becoming a programmer later in life got me thinking about a related question. How do you deal with programmers who have not stayed current with new technologies?

In the hiring process this is easy, you simply don't hire them. However, at most companies I have worked at there are usually a few programmers who have been employed there for long enough that the skill-set they were originally hired for has become irrelevant. At the same time they have not bothered to stay current with newer technologies. They usually have enough business knowledge that they provide some value to the company, but from a technical perspective they are a slowly increasing liability. As an example, I work with a developer who is 10 years my senior, but still doesn't understand how to write concurrent code and cannot be trusted to use a revision control system without causing a mess that somebody else will have to clean up. On top of that he is really resistant to the idea of code reviews, which I think is due to him disliking people he considers junior to him making suggestion about how to improve his code.

So how do my fellow Slashdotters handle situations like this? How do you help somebody like this to improve their skill-sets? And most importantly, how do you do so without stepping on anybody's feelings?"
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

How do you deal with programmers who have not stayed current?

Comments Filter:
  • 80% of the job is not dependant on code technologies in most shops.. Its tasks that have been the same throughout time at every development shop 1. Understanding the problem at Hand. Reading and clarifying the spec, delivering a timeline that can be achieved. 2. Simplifying the problem into Component Parts that can be completed with minimal effort along acceptable timeline. Reuse what might already be sitting there in the libraries and open source world. 3. Selection of the tool set to quickest so

The moon is a planet just like the Earth, only it is even deader.

Working...