Bad project with punishing travel schedule - no time for learning [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
-1
down vote
favorite
Just to give a quick overview about myself. When I was still studying at college and taking up a On The Job Training course, I was deployed to a company with a friend's help, so instant work no interview. After I graduated, the company offered me a job since they like my performance. Self Studying while on summer vacation paid off.
When I started working there obviously I learned new things while still self studying while at home. I was deployed to a foreign client and was assigned to different team. It was good. At first, it was all informative and the client assigned me to a bigger project and was impressed. But deep inside me I know for sure that my current skills and knowledge were insufficient plus the deadline wass too close. Luckily, I was reassigned to another foreign client.
The new posting is depressing as I am not using tools that I am interested in and the commute is very difficult. I am unhappy and not growing professionally.
I have a lot of assigned projects for me, but I don't want to do it anymore, as I'm not learning anything new or interesting. My current skills already decaying as I've been stuck using obsolete tools for 6 months now. What are some strategies for dealing with professional stagnation?
career-development
closed as off-topic by Telastyn, Jim G., user9158, scaaahu, keshlam Jan 5 '15 at 6:19
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Telastyn, Jim G., Community, scaaahu, keshlam
suggest improvements |Â
up vote
-1
down vote
favorite
Just to give a quick overview about myself. When I was still studying at college and taking up a On The Job Training course, I was deployed to a company with a friend's help, so instant work no interview. After I graduated, the company offered me a job since they like my performance. Self Studying while on summer vacation paid off.
When I started working there obviously I learned new things while still self studying while at home. I was deployed to a foreign client and was assigned to different team. It was good. At first, it was all informative and the client assigned me to a bigger project and was impressed. But deep inside me I know for sure that my current skills and knowledge were insufficient plus the deadline wass too close. Luckily, I was reassigned to another foreign client.
The new posting is depressing as I am not using tools that I am interested in and the commute is very difficult. I am unhappy and not growing professionally.
I have a lot of assigned projects for me, but I don't want to do it anymore, as I'm not learning anything new or interesting. My current skills already decaying as I've been stuck using obsolete tools for 6 months now. What are some strategies for dealing with professional stagnation?
career-development
closed as off-topic by Telastyn, Jim G., user9158, scaaahu, keshlam Jan 5 '15 at 6:19
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Telastyn, Jim G., Community, scaaahu, keshlam
suggest improvements |Â
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
Just to give a quick overview about myself. When I was still studying at college and taking up a On The Job Training course, I was deployed to a company with a friend's help, so instant work no interview. After I graduated, the company offered me a job since they like my performance. Self Studying while on summer vacation paid off.
When I started working there obviously I learned new things while still self studying while at home. I was deployed to a foreign client and was assigned to different team. It was good. At first, it was all informative and the client assigned me to a bigger project and was impressed. But deep inside me I know for sure that my current skills and knowledge were insufficient plus the deadline wass too close. Luckily, I was reassigned to another foreign client.
The new posting is depressing as I am not using tools that I am interested in and the commute is very difficult. I am unhappy and not growing professionally.
I have a lot of assigned projects for me, but I don't want to do it anymore, as I'm not learning anything new or interesting. My current skills already decaying as I've been stuck using obsolete tools for 6 months now. What are some strategies for dealing with professional stagnation?
career-development
Just to give a quick overview about myself. When I was still studying at college and taking up a On The Job Training course, I was deployed to a company with a friend's help, so instant work no interview. After I graduated, the company offered me a job since they like my performance. Self Studying while on summer vacation paid off.
When I started working there obviously I learned new things while still self studying while at home. I was deployed to a foreign client and was assigned to different team. It was good. At first, it was all informative and the client assigned me to a bigger project and was impressed. But deep inside me I know for sure that my current skills and knowledge were insufficient plus the deadline wass too close. Luckily, I was reassigned to another foreign client.
The new posting is depressing as I am not using tools that I am interested in and the commute is very difficult. I am unhappy and not growing professionally.
I have a lot of assigned projects for me, but I don't want to do it anymore, as I'm not learning anything new or interesting. My current skills already decaying as I've been stuck using obsolete tools for 6 months now. What are some strategies for dealing with professional stagnation?
career-development
edited Jan 5 '15 at 19:37
Myles
25.4k658104
25.4k658104
asked Jan 5 '15 at 2:15


Wesley Brian Lachenal
1055
1055
closed as off-topic by Telastyn, Jim G., user9158, scaaahu, keshlam Jan 5 '15 at 6:19
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Telastyn, Jim G., Community, scaaahu, keshlam
closed as off-topic by Telastyn, Jim G., user9158, scaaahu, keshlam Jan 5 '15 at 6:19
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Telastyn, Jim G., Community, scaaahu, keshlam
suggest improvements |Â
suggest improvements |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
Working within an existing system is a valuable skill as a developer. It helps you learn to read code, value good design and documentation, and fit your solution into a larger whole even when you would rather do it differently. It will also teach you or encourage you to find supporting tools out there to make maintenance tasks simpler.
I can't emphasize the value of being able to read and understand someone else's code enough. A good senior developer should be able to understand how a reasonably complex system works just by exploring the code without the need to set breakpoints and actually step through the code while it's executing.
In short, I think you are underestimating what you can learn from maintenance work in a legacy system, especially at such an early stage in your career. I encourage you to stick it out a while longer and try to develop your "engineering" part of the "software engineering" skillset.
suggest improvements |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Working within an existing system is a valuable skill as a developer. It helps you learn to read code, value good design and documentation, and fit your solution into a larger whole even when you would rather do it differently. It will also teach you or encourage you to find supporting tools out there to make maintenance tasks simpler.
I can't emphasize the value of being able to read and understand someone else's code enough. A good senior developer should be able to understand how a reasonably complex system works just by exploring the code without the need to set breakpoints and actually step through the code while it's executing.
In short, I think you are underestimating what you can learn from maintenance work in a legacy system, especially at such an early stage in your career. I encourage you to stick it out a while longer and try to develop your "engineering" part of the "software engineering" skillset.
suggest improvements |Â
up vote
1
down vote
Working within an existing system is a valuable skill as a developer. It helps you learn to read code, value good design and documentation, and fit your solution into a larger whole even when you would rather do it differently. It will also teach you or encourage you to find supporting tools out there to make maintenance tasks simpler.
I can't emphasize the value of being able to read and understand someone else's code enough. A good senior developer should be able to understand how a reasonably complex system works just by exploring the code without the need to set breakpoints and actually step through the code while it's executing.
In short, I think you are underestimating what you can learn from maintenance work in a legacy system, especially at such an early stage in your career. I encourage you to stick it out a while longer and try to develop your "engineering" part of the "software engineering" skillset.
suggest improvements |Â
up vote
1
down vote
up vote
1
down vote
Working within an existing system is a valuable skill as a developer. It helps you learn to read code, value good design and documentation, and fit your solution into a larger whole even when you would rather do it differently. It will also teach you or encourage you to find supporting tools out there to make maintenance tasks simpler.
I can't emphasize the value of being able to read and understand someone else's code enough. A good senior developer should be able to understand how a reasonably complex system works just by exploring the code without the need to set breakpoints and actually step through the code while it's executing.
In short, I think you are underestimating what you can learn from maintenance work in a legacy system, especially at such an early stage in your career. I encourage you to stick it out a while longer and try to develop your "engineering" part of the "software engineering" skillset.
Working within an existing system is a valuable skill as a developer. It helps you learn to read code, value good design and documentation, and fit your solution into a larger whole even when you would rather do it differently. It will also teach you or encourage you to find supporting tools out there to make maintenance tasks simpler.
I can't emphasize the value of being able to read and understand someone else's code enough. A good senior developer should be able to understand how a reasonably complex system works just by exploring the code without the need to set breakpoints and actually step through the code while it's executing.
In short, I think you are underestimating what you can learn from maintenance work in a legacy system, especially at such an early stage in your career. I encourage you to stick it out a while longer and try to develop your "engineering" part of the "software engineering" skillset.
answered Jan 5 '15 at 2:36
Eric
4,11911125
4,11911125
suggest improvements |Â
suggest improvements |Â