Struggling Senior Developer
I am senior developer (working as a consultant and manager) with over a decade of experience. I find that I enjoy helping teams with communication, learning about new ideas (architecture, patterns, frameworks, etc), working with junior members, etc. The best way to summarize this would be the soft skills.
When it comes to development, I find that once I put an architecture in place and couple of small examples I no longer want to develop. Team members are expecting me to help out with the day to day development which I can do but after a couple of days I loose interest in the project. I am willing to jump in and help out on small changes.
Is this a sign of burnout? A need for a need career or career path? Is there a position for someone like me.
career-development burnout
New contributor
add a comment |
I am senior developer (working as a consultant and manager) with over a decade of experience. I find that I enjoy helping teams with communication, learning about new ideas (architecture, patterns, frameworks, etc), working with junior members, etc. The best way to summarize this would be the soft skills.
When it comes to development, I find that once I put an architecture in place and couple of small examples I no longer want to develop. Team members are expecting me to help out with the day to day development which I can do but after a couple of days I loose interest in the project. I am willing to jump in and help out on small changes.
Is this a sign of burnout? A need for a need career or career path? Is there a position for someone like me.
career-development burnout
New contributor
I think it’s a sign of you being more bored or sense of purpose. One thing you could do is provide feedback in peer reviews. You can also peer review their findings or designs. That’s the type of stuff that a senior person should be doing. Ensuring the ship stays afloat
– Brian
3 hours ago
It may be sign of carrier need of change. Perhaps software architecture / project management etc could be the way
– Strader
2 hours ago
add a comment |
I am senior developer (working as a consultant and manager) with over a decade of experience. I find that I enjoy helping teams with communication, learning about new ideas (architecture, patterns, frameworks, etc), working with junior members, etc. The best way to summarize this would be the soft skills.
When it comes to development, I find that once I put an architecture in place and couple of small examples I no longer want to develop. Team members are expecting me to help out with the day to day development which I can do but after a couple of days I loose interest in the project. I am willing to jump in and help out on small changes.
Is this a sign of burnout? A need for a need career or career path? Is there a position for someone like me.
career-development burnout
New contributor
I am senior developer (working as a consultant and manager) with over a decade of experience. I find that I enjoy helping teams with communication, learning about new ideas (architecture, patterns, frameworks, etc), working with junior members, etc. The best way to summarize this would be the soft skills.
When it comes to development, I find that once I put an architecture in place and couple of small examples I no longer want to develop. Team members are expecting me to help out with the day to day development which I can do but after a couple of days I loose interest in the project. I am willing to jump in and help out on small changes.
Is this a sign of burnout? A need for a need career or career path? Is there a position for someone like me.
career-development burnout
career-development burnout
New contributor
New contributor
New contributor
asked 5 hours ago
Matt Thomas
161
161
New contributor
New contributor
I think it’s a sign of you being more bored or sense of purpose. One thing you could do is provide feedback in peer reviews. You can also peer review their findings or designs. That’s the type of stuff that a senior person should be doing. Ensuring the ship stays afloat
– Brian
3 hours ago
It may be sign of carrier need of change. Perhaps software architecture / project management etc could be the way
– Strader
2 hours ago
add a comment |
I think it’s a sign of you being more bored or sense of purpose. One thing you could do is provide feedback in peer reviews. You can also peer review their findings or designs. That’s the type of stuff that a senior person should be doing. Ensuring the ship stays afloat
– Brian
3 hours ago
It may be sign of carrier need of change. Perhaps software architecture / project management etc could be the way
– Strader
2 hours ago
I think it’s a sign of you being more bored or sense of purpose. One thing you could do is provide feedback in peer reviews. You can also peer review their findings or designs. That’s the type of stuff that a senior person should be doing. Ensuring the ship stays afloat
– Brian
3 hours ago
I think it’s a sign of you being more bored or sense of purpose. One thing you could do is provide feedback in peer reviews. You can also peer review their findings or designs. That’s the type of stuff that a senior person should be doing. Ensuring the ship stays afloat
– Brian
3 hours ago
It may be sign of carrier need of change. Perhaps software architecture / project management etc could be the way
– Strader
2 hours ago
It may be sign of carrier need of change. Perhaps software architecture / project management etc could be the way
– Strader
2 hours ago
add a comment |
1 Answer
1
active
oldest
votes
I don't know why someone downvoted you. This isn't that uncommon a problem. Could it be burnout? Yes. But it could also be that your work behaviors are maturing in different ways. As those new skills develop, you find you want to pursue them. There's no problem there. In a sense...
Welcome to middle age...
You get to make a choice. For me, it was (a) stay with microelectronic design, (b) move into engineering management, (c) or change careers (I took (c) and went into technical marketing, corporate training, and documentation).
To be fair to your current employer, unless you want to sit down and have a long talk with them, you need to meet their expectations. If that includes regular coding, do it. Burning a bridge is never a good idea if it can be avoided.
On the other hand, it sounds like you do need a chance to experience some spreading of the wings. If your employer is large enough, it would be advantageous to talk to them about your career path. Many employers love the idea that you want to invest to stay with them, and so they will pay/supply education for your new interests and skills. Examples include:
- Busines MBA degrees
- Customer alliance/service training
- Trainer certifications
And many others. In other words, your company may want you to look into those new interests to see if they can leverage your newfound love (for example) of training others to build a stronger overall base of programmers.
Heaven forbid it might lead to a promotion...
If, however, you work for a small company that lacks those resources (or one of the big ones that don't offer such perks, gratefully they're disappearing), then you have some hard choices to make. In this case, you can take advantage of local university/college career counseling services (some will accept non-students for a fee) or career-based services (are you a member of IEEE?) that can help you.
I do recommend that you not take too long waffling about it. That might get noticed by your employer and it's probably not part of your job desciption.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "423"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Matt Thomas is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f125615%2fstruggling-senior-developer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I don't know why someone downvoted you. This isn't that uncommon a problem. Could it be burnout? Yes. But it could also be that your work behaviors are maturing in different ways. As those new skills develop, you find you want to pursue them. There's no problem there. In a sense...
Welcome to middle age...
You get to make a choice. For me, it was (a) stay with microelectronic design, (b) move into engineering management, (c) or change careers (I took (c) and went into technical marketing, corporate training, and documentation).
To be fair to your current employer, unless you want to sit down and have a long talk with them, you need to meet their expectations. If that includes regular coding, do it. Burning a bridge is never a good idea if it can be avoided.
On the other hand, it sounds like you do need a chance to experience some spreading of the wings. If your employer is large enough, it would be advantageous to talk to them about your career path. Many employers love the idea that you want to invest to stay with them, and so they will pay/supply education for your new interests and skills. Examples include:
- Busines MBA degrees
- Customer alliance/service training
- Trainer certifications
And many others. In other words, your company may want you to look into those new interests to see if they can leverage your newfound love (for example) of training others to build a stronger overall base of programmers.
Heaven forbid it might lead to a promotion...
If, however, you work for a small company that lacks those resources (or one of the big ones that don't offer such perks, gratefully they're disappearing), then you have some hard choices to make. In this case, you can take advantage of local university/college career counseling services (some will accept non-students for a fee) or career-based services (are you a member of IEEE?) that can help you.
I do recommend that you not take too long waffling about it. That might get noticed by your employer and it's probably not part of your job desciption.
New contributor
add a comment |
I don't know why someone downvoted you. This isn't that uncommon a problem. Could it be burnout? Yes. But it could also be that your work behaviors are maturing in different ways. As those new skills develop, you find you want to pursue them. There's no problem there. In a sense...
Welcome to middle age...
You get to make a choice. For me, it was (a) stay with microelectronic design, (b) move into engineering management, (c) or change careers (I took (c) and went into technical marketing, corporate training, and documentation).
To be fair to your current employer, unless you want to sit down and have a long talk with them, you need to meet their expectations. If that includes regular coding, do it. Burning a bridge is never a good idea if it can be avoided.
On the other hand, it sounds like you do need a chance to experience some spreading of the wings. If your employer is large enough, it would be advantageous to talk to them about your career path. Many employers love the idea that you want to invest to stay with them, and so they will pay/supply education for your new interests and skills. Examples include:
- Busines MBA degrees
- Customer alliance/service training
- Trainer certifications
And many others. In other words, your company may want you to look into those new interests to see if they can leverage your newfound love (for example) of training others to build a stronger overall base of programmers.
Heaven forbid it might lead to a promotion...
If, however, you work for a small company that lacks those resources (or one of the big ones that don't offer such perks, gratefully they're disappearing), then you have some hard choices to make. In this case, you can take advantage of local university/college career counseling services (some will accept non-students for a fee) or career-based services (are you a member of IEEE?) that can help you.
I do recommend that you not take too long waffling about it. That might get noticed by your employer and it's probably not part of your job desciption.
New contributor
add a comment |
I don't know why someone downvoted you. This isn't that uncommon a problem. Could it be burnout? Yes. But it could also be that your work behaviors are maturing in different ways. As those new skills develop, you find you want to pursue them. There's no problem there. In a sense...
Welcome to middle age...
You get to make a choice. For me, it was (a) stay with microelectronic design, (b) move into engineering management, (c) or change careers (I took (c) and went into technical marketing, corporate training, and documentation).
To be fair to your current employer, unless you want to sit down and have a long talk with them, you need to meet their expectations. If that includes regular coding, do it. Burning a bridge is never a good idea if it can be avoided.
On the other hand, it sounds like you do need a chance to experience some spreading of the wings. If your employer is large enough, it would be advantageous to talk to them about your career path. Many employers love the idea that you want to invest to stay with them, and so they will pay/supply education for your new interests and skills. Examples include:
- Busines MBA degrees
- Customer alliance/service training
- Trainer certifications
And many others. In other words, your company may want you to look into those new interests to see if they can leverage your newfound love (for example) of training others to build a stronger overall base of programmers.
Heaven forbid it might lead to a promotion...
If, however, you work for a small company that lacks those resources (or one of the big ones that don't offer such perks, gratefully they're disappearing), then you have some hard choices to make. In this case, you can take advantage of local university/college career counseling services (some will accept non-students for a fee) or career-based services (are you a member of IEEE?) that can help you.
I do recommend that you not take too long waffling about it. That might get noticed by your employer and it's probably not part of your job desciption.
New contributor
I don't know why someone downvoted you. This isn't that uncommon a problem. Could it be burnout? Yes. But it could also be that your work behaviors are maturing in different ways. As those new skills develop, you find you want to pursue them. There's no problem there. In a sense...
Welcome to middle age...
You get to make a choice. For me, it was (a) stay with microelectronic design, (b) move into engineering management, (c) or change careers (I took (c) and went into technical marketing, corporate training, and documentation).
To be fair to your current employer, unless you want to sit down and have a long talk with them, you need to meet their expectations. If that includes regular coding, do it. Burning a bridge is never a good idea if it can be avoided.
On the other hand, it sounds like you do need a chance to experience some spreading of the wings. If your employer is large enough, it would be advantageous to talk to them about your career path. Many employers love the idea that you want to invest to stay with them, and so they will pay/supply education for your new interests and skills. Examples include:
- Busines MBA degrees
- Customer alliance/service training
- Trainer certifications
And many others. In other words, your company may want you to look into those new interests to see if they can leverage your newfound love (for example) of training others to build a stronger overall base of programmers.
Heaven forbid it might lead to a promotion...
If, however, you work for a small company that lacks those resources (or one of the big ones that don't offer such perks, gratefully they're disappearing), then you have some hard choices to make. In this case, you can take advantage of local university/college career counseling services (some will accept non-students for a fee) or career-based services (are you a member of IEEE?) that can help you.
I do recommend that you not take too long waffling about it. That might get noticed by your employer and it's probably not part of your job desciption.
New contributor
New contributor
answered 4 hours ago
JBH
74111
74111
New contributor
New contributor
add a comment |
add a comment |
Matt Thomas is a new contributor. Be nice, and check out our Code of Conduct.
Matt Thomas is a new contributor. Be nice, and check out our Code of Conduct.
Matt Thomas is a new contributor. Be nice, and check out our Code of Conduct.
Matt Thomas is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f125615%2fstruggling-senior-developer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I think it’s a sign of you being more bored or sense of purpose. One thing you could do is provide feedback in peer reviews. You can also peer review their findings or designs. That’s the type of stuff that a senior person should be doing. Ensuring the ship stays afloat
– Brian
3 hours ago
It may be sign of carrier need of change. Perhaps software architecture / project management etc could be the way
– Strader
2 hours ago