Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

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

skaffen42 (579313) writes | about a year ago


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?"

cancel ×

1 comment

Sorry! There are no comments related to the filter you selected.

80% of the job is not NEW code technologies (1)

nevermindme (912672) | about a year ago | (#43694977)

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 solve the problem/build the component code. 4. Testing, Testing and Testing and then declaring it ready for testing in front of the client. 5. Deliver of Product on Time and at Budget, with comments and documented and supportable. Teaching younger staff to do these things regardless of what framework, language used and tempest in a teacup office politics that are going on is handy for just about any project. The Good to better Greybeards have seen it all.... nothing is new... technology is now faster and cheaper but man hours are more expensive than ever, They also typically enjoy the client meeting than the fresh code guns.
Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>