How do you know when you should change the programming domain you're working in?
Posted
by thecoop
on Stack Overflow
See other posts from Stack Overflow
or by thecoop
Published on 2010-03-24T15:46:31Z
Indexed on
2010/03/24
15:53 UTC
Read the original article
Hit count: 185
I've recently become one of the most senior developers in one division of the company, and am generally the 'go-to' guy about questions in the problem domain the division works in, however I feel I'm not learning anything new. To continue to learn new things I would have to change division and work on something competely different, but then my current domain knowledge would be useless & I would start off with knowing nothing again.
Obviously, this is quite a large decision & I'm hesitant to lost my 'status'; and the knowledge I do have would be useless.
How do you know when you should change the programming domain you work in?
© Stack Overflow or respective owner