How do you know when you should change the programming domain you're working in?
- by thecoop
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?