Taking holiday 2 weeks into new job to develop skills [closed]

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;

up vote
-2
down vote

favorite

I just joined a organisation two weeks ago and I am already feeling stressed as work is too tough, and I might lack the needed skills.

I see two options: either I quit or I tell my manager I need to polish my skills.

What effect will this have on my job? Could they just turn me down or terminate me?

The business is an online store, and as a developer I have every responsibility. I have learned a lot since joining, but I'm not sure about my skills. I was hired through a recruitment agency and they told the employer that I have been out of work for six months and have rusty skills, but I can learn quickly. A part of me asks why they have hired me in the first place when I don't have the skills needed.

But back to my question what should I do? Should I quit or ask for time off to learn. How much time can they afford to lend me?
Edit : I was bought in when ex developer was leaving and everything was told me in 1-2 days and I had to deal a lot of responsibility. From Db, Git, to everything. I don't take a direct approach in removing something and windup in a situation where I say "oh funk", instead I understand and experiment before saying "yes I know it", will it make the people get frustrated or make me look responsible?

edited Apr 28 '16 at 10:14

JJosaur

1,6551422

asked Apr 27 '16 at 12:23

cookieMonster

2,23662035

closed as off-topic by gnat, Dawny33, jimm101, Chris E, HopelessN00b Apr 29 '16 at 21:47

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." â€“ gnat, Dawny33, jimm101, Chris E, HopelessN00b

If this question can be reworded to fit the rules in the help center, please edit the question.

@JoeStrazzere what if i don't give them work, they will fire me. I have learned a lot in 6 months, but i am just stressed because like someone gave me work and i am not able to do it. They would be angry and lead to my termination? Just asking maybe i am too much panic
â€“Â cookieMonster
Apr 27 '16 at 12:48

@Nofel make some kind of progesss every day. If you are really worried, study in the evenings. But if they hired you knowing your skills are rusty, unless you lied to them in the interviews they know you are no rock star right now. Take a deep breath and focus on one task at a time.
â€“Â adeady
Apr 27 '16 at 13:05

Your two options are too narrow. If you don't quit and you can't take leave, you can learn each task that is needed. For example, suppose you've gotten the requirement to implement an online payment system, but you don't know how or have forgotten how. You could say "I need to research how to do this", and then do it. If the task in question is too big, you need to break it into smaller ones and do the same thing for each of the small tasks.
â€“Â Brandin
Apr 27 '16 at 13:10

Change to a profession you can handle, if you've been fired once, and two weeks into another job you're falling to bits, then that profession doesn't suit you.
â€“Â Kilisi
Apr 27 '16 at 13:25

@Kilisi i wasn't fired for work, it was due to the fact i wasn't a team player as my peer made me look bad, despite he was the bad fish.
â€“Â cookieMonster
Apr 27 '16 at 13:41

Â |Â
show 5 more comments

up vote
-2
down vote

favorite

I just joined a organisation two weeks ago and I am already feeling stressed as work is too tough, and I might lack the needed skills.

I see two options: either I quit or I tell my manager I need to polish my skills.

What effect will this have on my job? Could they just turn me down or terminate me?

edited Apr 28 '16 at 10:14

JJosaur

1,6551422

asked Apr 27 '16 at 12:23

cookieMonster

2,23662035

closed as off-topic by gnat, Dawny33, jimm101, Chris E, HopelessN00b Apr 29 '16 at 21:47

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." â€“ gnat, Dawny33, jimm101, Chris E, HopelessN00b

If this question can be reworded to fit the rules in the help center, please edit the question.

@JoeStrazzere what if i don't give them work, they will fire me. I have learned a lot in 6 months, but i am just stressed because like someone gave me work and i am not able to do it. They would be angry and lead to my termination? Just asking maybe i am too much panic
â€“Â cookieMonster
Apr 27 '16 at 12:48

@Nofel make some kind of progesss every day. If you are really worried, study in the evenings. But if they hired you knowing your skills are rusty, unless you lied to them in the interviews they know you are no rock star right now. Take a deep breath and focus on one task at a time.
â€“Â adeady
Apr 27 '16 at 13:05

Your two options are too narrow. If you don't quit and you can't take leave, you can learn each task that is needed. For example, suppose you've gotten the requirement to implement an online payment system, but you don't know how or have forgotten how. You could say "I need to research how to do this", and then do it. If the task in question is too big, you need to break it into smaller ones and do the same thing for each of the small tasks.
â€“Â Brandin
Apr 27 '16 at 13:10

Change to a profession you can handle, if you've been fired once, and two weeks into another job you're falling to bits, then that profession doesn't suit you.
â€“Â Kilisi
Apr 27 '16 at 13:25

@Kilisi i wasn't fired for work, it was due to the fact i wasn't a team player as my peer made me look bad, despite he was the bad fish.
â€“Â cookieMonster
Apr 27 '16 at 13:41

Â |Â
show 5 more comments

up vote
-2
down vote

favorite

I just joined a organisation two weeks ago and I am already feeling stressed as work is too tough, and I might lack the needed skills.

I see two options: either I quit or I tell my manager I need to polish my skills.

What effect will this have on my job? Could they just turn me down or terminate me?

edited Apr 28 '16 at 10:14

JJosaur

1,6551422

asked Apr 27 '16 at 12:23

cookieMonster

2,23662035

I just joined a organisation two weeks ago and I am already feeling stressed as work is too tough, and I might lack the needed skills.

I see two options: either I quit or I tell my manager I need to polish my skills.

What effect will this have on my job? Could they just turn me down or terminate me?

edited Apr 28 '16 at 10:14

JJosaur

1,6551422

asked Apr 27 '16 at 12:23

cookieMonster

2,23662035

edited Apr 28 '16 at 10:14

JJosaur

1,6551422

edited Apr 28 '16 at 10:14

JJosaur

1,6551422

edited Apr 28 '16 at 10:14

JJosaur

1,6551422

asked Apr 27 '16 at 12:23

cookieMonster

2,23662035

asked Apr 27 '16 at 12:23

cookieMonster

2,23662035

asked Apr 27 '16 at 12:23

cookieMonster

2,23662035

closed as off-topic by gnat, Dawny33, jimm101, Chris E, HopelessN00b Apr 29 '16 at 21:47

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." â€“ gnat, Dawny33, jimm101, Chris E, HopelessN00b

If this question can be reworded to fit the rules in the help center, please edit the question.

closed as off-topic by gnat, Dawny33, jimm101, Chris E, HopelessN00b Apr 29 '16 at 21:47

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." â€“ gnat, Dawny33, jimm101, Chris E, HopelessN00b

If this question can be reworded to fit the rules in the help center, please edit the question.

@JoeStrazzere what if i don't give them work, they will fire me. I have learned a lot in 6 months, but i am just stressed because like someone gave me work and i am not able to do it. They would be angry and lead to my termination? Just asking maybe i am too much panic
â€“Â cookieMonster
Apr 27 '16 at 12:48

@Nofel make some kind of progesss every day. If you are really worried, study in the evenings. But if they hired you knowing your skills are rusty, unless you lied to them in the interviews they know you are no rock star right now. Take a deep breath and focus on one task at a time.
â€“Â adeady
Apr 27 '16 at 13:05

Your two options are too narrow. If you don't quit and you can't take leave, you can learn each task that is needed. For example, suppose you've gotten the requirement to implement an online payment system, but you don't know how or have forgotten how. You could say "I need to research how to do this", and then do it. If the task in question is too big, you need to break it into smaller ones and do the same thing for each of the small tasks.
â€“Â Brandin
Apr 27 '16 at 13:10

Change to a profession you can handle, if you've been fired once, and two weeks into another job you're falling to bits, then that profession doesn't suit you.
â€“Â Kilisi
Apr 27 '16 at 13:25

@Kilisi i wasn't fired for work, it was due to the fact i wasn't a team player as my peer made me look bad, despite he was the bad fish.
â€“Â cookieMonster
Apr 27 '16 at 13:41

Â |Â
show 5 more comments

@JoeStrazzere what if i don't give them work, they will fire me. I have learned a lot in 6 months, but i am just stressed because like someone gave me work and i am not able to do it. They would be angry and lead to my termination? Just asking maybe i am too much panic
â€“Â cookieMonster
Apr 27 '16 at 12:48

@Nofel make some kind of progesss every day. If you are really worried, study in the evenings. But if they hired you knowing your skills are rusty, unless you lied to them in the interviews they know you are no rock star right now. Take a deep breath and focus on one task at a time.
â€“Â adeady
Apr 27 '16 at 13:05

Your two options are too narrow. If you don't quit and you can't take leave, you can learn each task that is needed. For example, suppose you've gotten the requirement to implement an online payment system, but you don't know how or have forgotten how. You could say "I need to research how to do this", and then do it. If the task in question is too big, you need to break it into smaller ones and do the same thing for each of the small tasks.
â€“Â Brandin
Apr 27 '16 at 13:10

Change to a profession you can handle, if you've been fired once, and two weeks into another job you're falling to bits, then that profession doesn't suit you.
â€“Â Kilisi
Apr 27 '16 at 13:25

@Kilisi i wasn't fired for work, it was due to the fact i wasn't a team player as my peer made me look bad, despite he was the bad fish.
â€“Â cookieMonster
Apr 27 '16 at 13:41

@JoeStrazzere what if i don't give them work, they will fire me. I have learned a lot in 6 months, but i am just stressed because like someone gave me work and i am not able to do it. They would be angry and lead to my termination? Just asking maybe i am too much panic
â€“Â cookieMonster
Apr 27 '16 at 12:48

@Nofel make some kind of progesss every day. If you are really worried, study in the evenings. But if they hired you knowing your skills are rusty, unless you lied to them in the interviews they know you are no rock star right now. Take a deep breath and focus on one task at a time.
â€“Â adeady
Apr 27 '16 at 13:05

Your two options are too narrow. If you don't quit and you can't take leave, you can learn each task that is needed. For example, suppose you've gotten the requirement to implement an online payment system, but you don't know how or have forgotten how. You could say "I need to research how to do this", and then do it. If the task in question is too big, you need to break it into smaller ones and do the same thing for each of the small tasks.
â€“Â Brandin
Apr 27 '16 at 13:10

Change to a profession you can handle, if you've been fired once, and two weeks into another job you're falling to bits, then that profession doesn't suit you.
â€“Â Kilisi
Apr 27 '16 at 13:25

@Kilisi i wasn't fired for work, it was due to the fact i wasn't a team player as my peer made me look bad, despite he was the bad fish.
â€“Â cookieMonster
Apr 27 '16 at 13:41

Â |Â
show 5 more comments

3 Answers
3

active

oldest

votes

up vote
14
down vote

accepted

Whenever I start a new job I find that it takes anywhere between 6 months to a year before I start feeling truly comfortable with the code base, database structure, and technologies. Until that point some frustration and stress is only natural. Even more so in your situation, where you're the only developer.

Now let's establish a few things: asking for time off is absolutely off the table. You've only been there for two weeks! Equally, what do you think you would accomplish by asking for more time off when you've already spent six months at home? No, my friend, you need to suppress your fears and insecurities and take this challenge on.

What you need to do is establish a very clear line of communication with your manager.

Ask them what they need done, and which objectives should be your priority. Don't be afraid to offer a different opinion on priority levels if your technical knowledge gives you a better understanding of the issue at hand.

Give timelines which are as realistic as possible. Any issue can be solved with enough research and effort. If you need to learn a new skill or technology in order to get the job done there's no shame in admitting as much - as long as you communicate this!

Remember that sometimes the "perfect" is the enemy of the "good enough". However, a balance must be struck, because a shortcut taken today can lead to huge maintenance problems tomorrow. Explain when you need to take more time to get a feature to work well in order to make things easier for the future. Since you're the only developer try not to fall in the trap of writing spaghetti code that only you know the ins and outs of. Comment and document your projects. You have a lot more responsibility, but it will also look very good in your resume when you eventually move on.

Make sure to maintain realistic expectations of what management should expect. This ties in with offering realistic deadlines. A few months down the line, if you feel that you need help, explain that a second developer might well be required. But first establish your credentials as a hard working and dedicated employee. You may consider working overtime (even unpaid) for the first few months.

(this is based on your comment below) Try to avoid saying that something "can't be done". Maybe from a technical standpoint it really can't be - however don't use those words. Be diplomatic. Be sneaky. First of all, analyze the code, and establish why feature X can't be implemented (maybe you lack rigorous historical data, or some other system doesn't have the ability to interface with the one you need it to). Next, communicate the issue in such a way that it doesn't seem like you are being incompetent or defeatist:

Hey boss. So I took a look at what it would take to implement feature X in system Y. At first glance you'd think that we could get it set up with a minimal amount of fuss, but that's unfortunately not the case. In order to generate the information for this feature we would need to read information from system Z, and I'm afraid that the data logs that it's been generating for the past year are missing a few key pieces of information which make it very difficult to get the job done. I would need to normalize the database, add some new tables establishing relationships between records, and modify system Z before I could even touch system Y. We're talking about a couple of months worth of work to get this off the ground.

See what I did there? Never, ever say that something is impossible. Anything is possible. Some things are simply not worth the time and effort to do them. Let your boss be the judge of that, however. Simply offer him the information to make an informed decision.

Most of all, learn to relax a little bit. You're employed! Sure, you face some challenges, but who doesn't? Take a deep breath, and just get the job done.

edited Apr 27 '16 at 14:55

answered Apr 27 '16 at 14:36

AndreiROM

44.1k21101173

i love what you said "Remember that sometimes the "perfect" is the enemy of the "good enough"." I been there and got layed off coz other guy was good enough. I am afarid to tell my manager about "This is gonna this long because i need to understand" and he telling me "Last dev didn't took this long" or we need it quick so "we need to hire another one etc", am just assuming but open communication is the way, just like i told my manager's boss i am understanding but i need till end of next week to get it done. Made me nervous but happy.
â€“Â cookieMonster
Apr 27 '16 at 14:44

I was given spaghetti code today to make it something else, i tried but failed and i told my manager's boss (as he assigned it to me i can't) which made me think, what he will say to my manager (perhaps he is useless)?
â€“Â cookieMonster
Apr 27 '16 at 14:45

@Nofel - I have been lucky to work with managers who had some development background and understood that code has to be maintainable, not simply work for the user. However, I'm also aware (and I've been told by the senior dev here) that I sometimes take too long to polish my code instead of just getting the job done. It's always a tricky balance between great, reusable, and maintainable code, and a project that just gets the job done. I'll add some more information to my answer regarding jobs that "can't be done".
â€“Â AndreiROM
Apr 27 '16 at 14:49

So you failed the first attempt. Try again. Very few folks write perfect code the first time they tackle a problem. If it was easy, they wouldn't have needed to hire you.
â€“Â keshlam
Apr 27 '16 at 14:49

@AndreiROM Is it wise to learn while at work? suppose i feel awkward or insecure when i am reading a tutorial, or blog about it. Mainly related to my work or what is coming. Can there be complaints about it? As i am on probation, i panic about all this, like might get booted before probation period, maybe he is too weak in this skill or he is always on stackoverflow etc.
â€“Â cookieMonster
Apr 27 '16 at 15:03

Â |Â
show 7 more comments

up vote
3
down vote

Everyone spends their first weeks -- or months! -- on a new job learning about it. Two weeks is much, much too early to panic.

Relax. Give yourself permission to spend time learning what they need you to know. Expect everything to go slowly until you have learned more.

If you're stuck on something after making a serious effort to deal with it on your own, ask more experienced co-workers to point you in the right direction. Ask them if there are any wiki pages or recorded presentations or other orientation material you should look at to help bring yourself up to speed. Part of showing initiative is doing it yourself, but another part is recognizing when you really are stuck and finding someone who can help you get unstuck.

The company believes you can do this, or they wouldn't have hired you. They have a lot more experience making that judgement than you do. They're probably right. They also don't expect you to hit the ground running at full speed; it's enough to start by walking in the right direction.

answered Apr 27 '16 at 12:53

keshlam

41.5k1267144

I don't have a senior peer, as i am the only one. As the last person left spend 2 days giving me things and the amount of work handed to me or i think is a lot or maybe the turnaround timing.
â€“Â cookieMonster
Apr 27 '16 at 12:56

Nobody expects you to do it all before Friday. Get it into priority order -- your manager can help with that -- then pick the simplest of the most-important items and do that. Take the next-simplest of the most important and do that, learning what you need as you go. Don't try to swallow the whole elephant at once; take it one bite at a time.
â€“Â keshlam
Apr 27 '16 at 13:06

suggest improvementsÂ |Â

up vote
2
down vote

It is common as a developer to learn on the job. The main thing you need to do is have open communication with your boss. In software development, people always seem to want more yesterday than a developer can do. There are tactics you can use to help give your boss reasonable expectations of what you can do.

When your boss gives you tasks, start a list. When he starts asking for updates, remind him that you are on task3 and task17 needs to wait. Encourage him to help prioritize your work.

Give your boss reasonable updates that show you making some kind of progress. This can be daily or weekly but the point is to show what you have done since he last got an update. Learning is making progress, and as an experienced I have spent a week trying to get libraries talking to each other.

As keshlam said, don't panic and don't quit. The worst they can do is fire you and at least you will be paid for as long as possible and learn. But if you set reasonable expectations you might be pleasantly surprised.

answered Apr 27 '16 at 12:58

adeady

1,567713

suggest improvementsÂ |Â

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

up vote
14
down vote

accepted

What you need to do is establish a very clear line of communication with your manager.

Ask them what they need done, and which objectives should be your priority. Don't be afraid to offer a different opinion on priority levels if your technical knowledge gives you a better understanding of the issue at hand.

Give timelines which are as realistic as possible. Any issue can be solved with enough research and effort. If you need to learn a new skill or technology in order to get the job done there's no shame in admitting as much - as long as you communicate this!

Remember that sometimes the "perfect" is the enemy of the "good enough". However, a balance must be struck, because a shortcut taken today can lead to huge maintenance problems tomorrow. Explain when you need to take more time to get a feature to work well in order to make things easier for the future. Since you're the only developer try not to fall in the trap of writing spaghetti code that only you know the ins and outs of. Comment and document your projects. You have a lot more responsibility, but it will also look very good in your resume when you eventually move on.

Make sure to maintain realistic expectations of what management should expect. This ties in with offering realistic deadlines. A few months down the line, if you feel that you need help, explain that a second developer might well be required. But first establish your credentials as a hard working and dedicated employee. You may consider working overtime (even unpaid) for the first few months.

(this is based on your comment below) Try to avoid saying that something "can't be done". Maybe from a technical standpoint it really can't be - however don't use those words. Be diplomatic. Be sneaky. First of all, analyze the code, and establish why feature X can't be implemented (maybe you lack rigorous historical data, or some other system doesn't have the ability to interface with the one you need it to). Next, communicate the issue in such a way that it doesn't seem like you are being incompetent or defeatist:

Hey boss. So I took a look at what it would take to implement feature X in system Y. At first glance you'd think that we could get it set up with a minimal amount of fuss, but that's unfortunately not the case. In order to generate the information for this feature we would need to read information from system Z, and I'm afraid that the data logs that it's been generating for the past year are missing a few key pieces of information which make it very difficult to get the job done. I would need to normalize the database, add some new tables establishing relationships between records, and modify system Z before I could even touch system Y. We're talking about a couple of months worth of work to get this off the ground.

Most of all, learn to relax a little bit. You're employed! Sure, you face some challenges, but who doesn't? Take a deep breath, and just get the job done.

edited Apr 27 '16 at 14:55

answered Apr 27 '16 at 14:36

AndreiROM

44.1k21101173

i love what you said "Remember that sometimes the "perfect" is the enemy of the "good enough"." I been there and got layed off coz other guy was good enough. I am afarid to tell my manager about "This is gonna this long because i need to understand" and he telling me "Last dev didn't took this long" or we need it quick so "we need to hire another one etc", am just assuming but open communication is the way, just like i told my manager's boss i am understanding but i need till end of next week to get it done. Made me nervous but happy.
â€“Â cookieMonster
Apr 27 '16 at 14:44

I was given spaghetti code today to make it something else, i tried but failed and i told my manager's boss (as he assigned it to me i can't) which made me think, what he will say to my manager (perhaps he is useless)?
â€“Â cookieMonster
Apr 27 '16 at 14:45

@Nofel - I have been lucky to work with managers who had some development background and understood that code has to be maintainable, not simply work for the user. However, I'm also aware (and I've been told by the senior dev here) that I sometimes take too long to polish my code instead of just getting the job done. It's always a tricky balance between great, reusable, and maintainable code, and a project that just gets the job done. I'll add some more information to my answer regarding jobs that "can't be done".
â€“Â AndreiROM
Apr 27 '16 at 14:49

So you failed the first attempt. Try again. Very few folks write perfect code the first time they tackle a problem. If it was easy, they wouldn't have needed to hire you.
â€“Â keshlam
Apr 27 '16 at 14:49

@AndreiROM Is it wise to learn while at work? suppose i feel awkward or insecure when i am reading a tutorial, or blog about it. Mainly related to my work or what is coming. Can there be complaints about it? As i am on probation, i panic about all this, like might get booted before probation period, maybe he is too weak in this skill or he is always on stackoverflow etc.
â€“Â cookieMonster
Apr 27 '16 at 15:03

Â |Â
show 7 more comments

up vote
14
down vote

accepted

What you need to do is establish a very clear line of communication with your manager.

Ask them what they need done, and which objectives should be your priority. Don't be afraid to offer a different opinion on priority levels if your technical knowledge gives you a better understanding of the issue at hand.

Give timelines which are as realistic as possible. Any issue can be solved with enough research and effort. If you need to learn a new skill or technology in order to get the job done there's no shame in admitting as much - as long as you communicate this!

Remember that sometimes the "perfect" is the enemy of the "good enough". However, a balance must be struck, because a shortcut taken today can lead to huge maintenance problems tomorrow. Explain when you need to take more time to get a feature to work well in order to make things easier for the future. Since you're the only developer try not to fall in the trap of writing spaghetti code that only you know the ins and outs of. Comment and document your projects. You have a lot more responsibility, but it will also look very good in your resume when you eventually move on.

Make sure to maintain realistic expectations of what management should expect. This ties in with offering realistic deadlines. A few months down the line, if you feel that you need help, explain that a second developer might well be required. But first establish your credentials as a hard working and dedicated employee. You may consider working overtime (even unpaid) for the first few months.

(this is based on your comment below) Try to avoid saying that something "can't be done". Maybe from a technical standpoint it really can't be - however don't use those words. Be diplomatic. Be sneaky. First of all, analyze the code, and establish why feature X can't be implemented (maybe you lack rigorous historical data, or some other system doesn't have the ability to interface with the one you need it to). Next, communicate the issue in such a way that it doesn't seem like you are being incompetent or defeatist:

Hey boss. So I took a look at what it would take to implement feature X in system Y. At first glance you'd think that we could get it set up with a minimal amount of fuss, but that's unfortunately not the case. In order to generate the information for this feature we would need to read information from system Z, and I'm afraid that the data logs that it's been generating for the past year are missing a few key pieces of information which make it very difficult to get the job done. I would need to normalize the database, add some new tables establishing relationships between records, and modify system Z before I could even touch system Y. We're talking about a couple of months worth of work to get this off the ground.

Most of all, learn to relax a little bit. You're employed! Sure, you face some challenges, but who doesn't? Take a deep breath, and just get the job done.

edited Apr 27 '16 at 14:55

answered Apr 27 '16 at 14:36

AndreiROM

44.1k21101173

i love what you said "Remember that sometimes the "perfect" is the enemy of the "good enough"." I been there and got layed off coz other guy was good enough. I am afarid to tell my manager about "This is gonna this long because i need to understand" and he telling me "Last dev didn't took this long" or we need it quick so "we need to hire another one etc", am just assuming but open communication is the way, just like i told my manager's boss i am understanding but i need till end of next week to get it done. Made me nervous but happy.
â€“Â cookieMonster
Apr 27 '16 at 14:44

I was given spaghetti code today to make it something else, i tried but failed and i told my manager's boss (as he assigned it to me i can't) which made me think, what he will say to my manager (perhaps he is useless)?
â€“Â cookieMonster
Apr 27 '16 at 14:45

@Nofel - I have been lucky to work with managers who had some development background and understood that code has to be maintainable, not simply work for the user. However, I'm also aware (and I've been told by the senior dev here) that I sometimes take too long to polish my code instead of just getting the job done. It's always a tricky balance between great, reusable, and maintainable code, and a project that just gets the job done. I'll add some more information to my answer regarding jobs that "can't be done".
â€“Â AndreiROM
Apr 27 '16 at 14:49

So you failed the first attempt. Try again. Very few folks write perfect code the first time they tackle a problem. If it was easy, they wouldn't have needed to hire you.
â€“Â keshlam
Apr 27 '16 at 14:49

@AndreiROM Is it wise to learn while at work? suppose i feel awkward or insecure when i am reading a tutorial, or blog about it. Mainly related to my work or what is coming. Can there be complaints about it? As i am on probation, i panic about all this, like might get booted before probation period, maybe he is too weak in this skill or he is always on stackoverflow etc.
â€“Â cookieMonster
Apr 27 '16 at 15:03

Â |Â
show 7 more comments

up vote
14
down vote

accepted

What you need to do is establish a very clear line of communication with your manager.

Ask them what they need done, and which objectives should be your priority. Don't be afraid to offer a different opinion on priority levels if your technical knowledge gives you a better understanding of the issue at hand.

Give timelines which are as realistic as possible. Any issue can be solved with enough research and effort. If you need to learn a new skill or technology in order to get the job done there's no shame in admitting as much - as long as you communicate this!

Remember that sometimes the "perfect" is the enemy of the "good enough". However, a balance must be struck, because a shortcut taken today can lead to huge maintenance problems tomorrow. Explain when you need to take more time to get a feature to work well in order to make things easier for the future. Since you're the only developer try not to fall in the trap of writing spaghetti code that only you know the ins and outs of. Comment and document your projects. You have a lot more responsibility, but it will also look very good in your resume when you eventually move on.

Make sure to maintain realistic expectations of what management should expect. This ties in with offering realistic deadlines. A few months down the line, if you feel that you need help, explain that a second developer might well be required. But first establish your credentials as a hard working and dedicated employee. You may consider working overtime (even unpaid) for the first few months.

(this is based on your comment below) Try to avoid saying that something "can't be done". Maybe from a technical standpoint it really can't be - however don't use those words. Be diplomatic. Be sneaky. First of all, analyze the code, and establish why feature X can't be implemented (maybe you lack rigorous historical data, or some other system doesn't have the ability to interface with the one you need it to). Next, communicate the issue in such a way that it doesn't seem like you are being incompetent or defeatist:

Hey boss. So I took a look at what it would take to implement feature X in system Y. At first glance you'd think that we could get it set up with a minimal amount of fuss, but that's unfortunately not the case. In order to generate the information for this feature we would need to read information from system Z, and I'm afraid that the data logs that it's been generating for the past year are missing a few key pieces of information which make it very difficult to get the job done. I would need to normalize the database, add some new tables establishing relationships between records, and modify system Z before I could even touch system Y. We're talking about a couple of months worth of work to get this off the ground.

Most of all, learn to relax a little bit. You're employed! Sure, you face some challenges, but who doesn't? Take a deep breath, and just get the job done.

edited Apr 27 '16 at 14:55

answered Apr 27 '16 at 14:36

AndreiROM

44.1k21101173

What you need to do is establish a very clear line of communication with your manager.

Ask them what they need done, and which objectives should be your priority. Don't be afraid to offer a different opinion on priority levels if your technical knowledge gives you a better understanding of the issue at hand.

Give timelines which are as realistic as possible. Any issue can be solved with enough research and effort. If you need to learn a new skill or technology in order to get the job done there's no shame in admitting as much - as long as you communicate this!

Remember that sometimes the "perfect" is the enemy of the "good enough". However, a balance must be struck, because a shortcut taken today can lead to huge maintenance problems tomorrow. Explain when you need to take more time to get a feature to work well in order to make things easier for the future. Since you're the only developer try not to fall in the trap of writing spaghetti code that only you know the ins and outs of. Comment and document your projects. You have a lot more responsibility, but it will also look very good in your resume when you eventually move on.

Make sure to maintain realistic expectations of what management should expect. This ties in with offering realistic deadlines. A few months down the line, if you feel that you need help, explain that a second developer might well be required. But first establish your credentials as a hard working and dedicated employee. You may consider working overtime (even unpaid) for the first few months.

(this is based on your comment below) Try to avoid saying that something "can't be done". Maybe from a technical standpoint it really can't be - however don't use those words. Be diplomatic. Be sneaky. First of all, analyze the code, and establish why feature X can't be implemented (maybe you lack rigorous historical data, or some other system doesn't have the ability to interface with the one you need it to). Next, communicate the issue in such a way that it doesn't seem like you are being incompetent or defeatist:

Hey boss. So I took a look at what it would take to implement feature X in system Y. At first glance you'd think that we could get it set up with a minimal amount of fuss, but that's unfortunately not the case. In order to generate the information for this feature we would need to read information from system Z, and I'm afraid that the data logs that it's been generating for the past year are missing a few key pieces of information which make it very difficult to get the job done. I would need to normalize the database, add some new tables establishing relationships between records, and modify system Z before I could even touch system Y. We're talking about a couple of months worth of work to get this off the ground.

Most of all, learn to relax a little bit. You're employed! Sure, you face some challenges, but who doesn't? Take a deep breath, and just get the job done.

edited Apr 27 '16 at 14:55

answered Apr 27 '16 at 14:36

AndreiROM

44.1k21101173

edited Apr 27 '16 at 14:55

answered Apr 27 '16 at 14:36

AndreiROM

44.1k21101173

answered Apr 27 '16 at 14:36

AndreiROM

44.1k21101173

answered Apr 27 '16 at 14:36

AndreiROM

44.1k21101173

i love what you said "Remember that sometimes the "perfect" is the enemy of the "good enough"." I been there and got layed off coz other guy was good enough. I am afarid to tell my manager about "This is gonna this long because i need to understand" and he telling me "Last dev didn't took this long" or we need it quick so "we need to hire another one etc", am just assuming but open communication is the way, just like i told my manager's boss i am understanding but i need till end of next week to get it done. Made me nervous but happy.
â€“Â cookieMonster
Apr 27 '16 at 14:44

I was given spaghetti code today to make it something else, i tried but failed and i told my manager's boss (as he assigned it to me i can't) which made me think, what he will say to my manager (perhaps he is useless)?
â€“Â cookieMonster
Apr 27 '16 at 14:45

@Nofel - I have been lucky to work with managers who had some development background and understood that code has to be maintainable, not simply work for the user. However, I'm also aware (and I've been told by the senior dev here) that I sometimes take too long to polish my code instead of just getting the job done. It's always a tricky balance between great, reusable, and maintainable code, and a project that just gets the job done. I'll add some more information to my answer regarding jobs that "can't be done".
â€“Â AndreiROM
Apr 27 '16 at 14:49

So you failed the first attempt. Try again. Very few folks write perfect code the first time they tackle a problem. If it was easy, they wouldn't have needed to hire you.
â€“Â keshlam
Apr 27 '16 at 14:49

@AndreiROM Is it wise to learn while at work? suppose i feel awkward or insecure when i am reading a tutorial, or blog about it. Mainly related to my work or what is coming. Can there be complaints about it? As i am on probation, i panic about all this, like might get booted before probation period, maybe he is too weak in this skill or he is always on stackoverflow etc.
â€“Â cookieMonster
Apr 27 '16 at 15:03

Â |Â
show 7 more comments

i love what you said "Remember that sometimes the "perfect" is the enemy of the "good enough"." I been there and got layed off coz other guy was good enough. I am afarid to tell my manager about "This is gonna this long because i need to understand" and he telling me "Last dev didn't took this long" or we need it quick so "we need to hire another one etc", am just assuming but open communication is the way, just like i told my manager's boss i am understanding but i need till end of next week to get it done. Made me nervous but happy.
â€“Â cookieMonster
Apr 27 '16 at 14:44

I was given spaghetti code today to make it something else, i tried but failed and i told my manager's boss (as he assigned it to me i can't) which made me think, what he will say to my manager (perhaps he is useless)?
â€“Â cookieMonster
Apr 27 '16 at 14:45

@Nofel - I have been lucky to work with managers who had some development background and understood that code has to be maintainable, not simply work for the user. However, I'm also aware (and I've been told by the senior dev here) that I sometimes take too long to polish my code instead of just getting the job done. It's always a tricky balance between great, reusable, and maintainable code, and a project that just gets the job done. I'll add some more information to my answer regarding jobs that "can't be done".
â€“Â AndreiROM
Apr 27 '16 at 14:49

So you failed the first attempt. Try again. Very few folks write perfect code the first time they tackle a problem. If it was easy, they wouldn't have needed to hire you.
â€“Â keshlam
Apr 27 '16 at 14:49

@AndreiROM Is it wise to learn while at work? suppose i feel awkward or insecure when i am reading a tutorial, or blog about it. Mainly related to my work or what is coming. Can there be complaints about it? As i am on probation, i panic about all this, like might get booted before probation period, maybe he is too weak in this skill or he is always on stackoverflow etc.
â€“Â cookieMonster
Apr 27 '16 at 15:03

i love what you said "Remember that sometimes the "perfect" is the enemy of the "good enough"." I been there and got layed off coz other guy was good enough. I am afarid to tell my manager about "This is gonna this long because i need to understand" and he telling me "Last dev didn't took this long" or we need it quick so "we need to hire another one etc", am just assuming but open communication is the way, just like i told my manager's boss i am understanding but i need till end of next week to get it done. Made me nervous but happy.
â€“Â cookieMonster
Apr 27 '16 at 14:44

I was given spaghetti code today to make it something else, i tried but failed and i told my manager's boss (as he assigned it to me i can't) which made me think, what he will say to my manager (perhaps he is useless)?
â€“Â cookieMonster
Apr 27 '16 at 14:45

@Nofel - I have been lucky to work with managers who had some development background and understood that code has to be maintainable, not simply work for the user. However, I'm also aware (and I've been told by the senior dev here) that I sometimes take too long to polish my code instead of just getting the job done. It's always a tricky balance between great, reusable, and maintainable code, and a project that just gets the job done. I'll add some more information to my answer regarding jobs that "can't be done".
â€“Â AndreiROM
Apr 27 '16 at 14:49

So you failed the first attempt. Try again. Very few folks write perfect code the first time they tackle a problem. If it was easy, they wouldn't have needed to hire you.
â€“Â keshlam
Apr 27 '16 at 14:49

@AndreiROM Is it wise to learn while at work? suppose i feel awkward or insecure when i am reading a tutorial, or blog about it. Mainly related to my work or what is coming. Can there be complaints about it? As i am on probation, i panic about all this, like might get booted before probation period, maybe he is too weak in this skill or he is always on stackoverflow etc.
â€“Â cookieMonster
Apr 27 '16 at 15:03

Â |Â
show 7 more comments

up vote
3
down vote

Everyone spends their first weeks -- or months! -- on a new job learning about it. Two weeks is much, much too early to panic.

Relax. Give yourself permission to spend time learning what they need you to know. Expect everything to go slowly until you have learned more.

answered Apr 27 '16 at 12:53

keshlam

41.5k1267144

I don't have a senior peer, as i am the only one. As the last person left spend 2 days giving me things and the amount of work handed to me or i think is a lot or maybe the turnaround timing.
â€“Â cookieMonster
Apr 27 '16 at 12:56

Nobody expects you to do it all before Friday. Get it into priority order -- your manager can help with that -- then pick the simplest of the most-important items and do that. Take the next-simplest of the most important and do that, learning what you need as you go. Don't try to swallow the whole elephant at once; take it one bite at a time.
â€“Â keshlam
Apr 27 '16 at 13:06

suggest improvementsÂ |Â

up vote
3
down vote

Everyone spends their first weeks -- or months! -- on a new job learning about it. Two weeks is much, much too early to panic.

Relax. Give yourself permission to spend time learning what they need you to know. Expect everything to go slowly until you have learned more.

answered Apr 27 '16 at 12:53

keshlam

41.5k1267144

I don't have a senior peer, as i am the only one. As the last person left spend 2 days giving me things and the amount of work handed to me or i think is a lot or maybe the turnaround timing.
â€“Â cookieMonster
Apr 27 '16 at 12:56

Nobody expects you to do it all before Friday. Get it into priority order -- your manager can help with that -- then pick the simplest of the most-important items and do that. Take the next-simplest of the most important and do that, learning what you need as you go. Don't try to swallow the whole elephant at once; take it one bite at a time.
â€“Â keshlam
Apr 27 '16 at 13:06

suggest improvementsÂ |Â

up vote
3
down vote

Everyone spends their first weeks -- or months! -- on a new job learning about it. Two weeks is much, much too early to panic.

Relax. Give yourself permission to spend time learning what they need you to know. Expect everything to go slowly until you have learned more.

answered Apr 27 '16 at 12:53

keshlam

41.5k1267144

Everyone spends their first weeks -- or months! -- on a new job learning about it. Two weeks is much, much too early to panic.

Relax. Give yourself permission to spend time learning what they need you to know. Expect everything to go slowly until you have learned more.

answered Apr 27 '16 at 12:53

keshlam

41.5k1267144

answered Apr 27 '16 at 12:53

keshlam

41.5k1267144

answered Apr 27 '16 at 12:53

keshlam

41.5k1267144

answered Apr 27 '16 at 12:53

keshlam

41.5k1267144

I don't have a senior peer, as i am the only one. As the last person left spend 2 days giving me things and the amount of work handed to me or i think is a lot or maybe the turnaround timing.
â€“Â cookieMonster
Apr 27 '16 at 12:56

Nobody expects you to do it all before Friday. Get it into priority order -- your manager can help with that -- then pick the simplest of the most-important items and do that. Take the next-simplest of the most important and do that, learning what you need as you go. Don't try to swallow the whole elephant at once; take it one bite at a time.
â€“Â keshlam
Apr 27 '16 at 13:06

suggest improvementsÂ |Â

I don't have a senior peer, as i am the only one. As the last person left spend 2 days giving me things and the amount of work handed to me or i think is a lot or maybe the turnaround timing.
â€“Â cookieMonster
Apr 27 '16 at 12:56

Nobody expects you to do it all before Friday. Get it into priority order -- your manager can help with that -- then pick the simplest of the most-important items and do that. Take the next-simplest of the most important and do that, learning what you need as you go. Don't try to swallow the whole elephant at once; take it one bite at a time.
â€“Â keshlam
Apr 27 '16 at 13:06

I don't have a senior peer, as i am the only one. As the last person left spend 2 days giving me things and the amount of work handed to me or i think is a lot or maybe the turnaround timing.
â€“Â cookieMonster
Apr 27 '16 at 12:56

Nobody expects you to do it all before Friday. Get it into priority order -- your manager can help with that -- then pick the simplest of the most-important items and do that. Take the next-simplest of the most important and do that, learning what you need as you go. Don't try to swallow the whole elephant at once; take it one bite at a time.
â€“Â keshlam
Apr 27 '16 at 13:06

suggest improvementsÂ |Â

up vote
2
down vote

When your boss gives you tasks, start a list. When he starts asking for updates, remind him that you are on task3 and task17 needs to wait. Encourage him to help prioritize your work.

Give your boss reasonable updates that show you making some kind of progress. This can be daily or weekly but the point is to show what you have done since he last got an update. Learning is making progress, and as an experienced I have spent a week trying to get libraries talking to each other.

answered Apr 27 '16 at 12:58

adeady

1,567713

suggest improvementsÂ |Â

up vote
2
down vote

When your boss gives you tasks, start a list. When he starts asking for updates, remind him that you are on task3 and task17 needs to wait. Encourage him to help prioritize your work.

Give your boss reasonable updates that show you making some kind of progress. This can be daily or weekly but the point is to show what you have done since he last got an update. Learning is making progress, and as an experienced I have spent a week trying to get libraries talking to each other.

answered Apr 27 '16 at 12:58

adeady

1,567713

suggest improvementsÂ |Â

up vote
2
down vote

When your boss gives you tasks, start a list. When he starts asking for updates, remind him that you are on task3 and task17 needs to wait. Encourage him to help prioritize your work.

Give your boss reasonable updates that show you making some kind of progress. This can be daily or weekly but the point is to show what you have done since he last got an update. Learning is making progress, and as an experienced I have spent a week trying to get libraries talking to each other.

answered Apr 27 '16 at 12:58

adeady

1,567713

When your boss gives you tasks, start a list. When he starts asking for updates, remind him that you are on task3 and task17 needs to wait. Encourage him to help prioritize your work.

Give your boss reasonable updates that show you making some kind of progress. This can be daily or weekly but the point is to show what you have done since he last got an update. Learning is making progress, and as an experienced I have spent a week trying to get libraries talking to each other.

answered Apr 27 '16 at 12:58

adeady

1,567713

answered Apr 27 '16 at 12:58

adeady

1,567713

answered Apr 27 '16 at 12:58

adeady

1,567713

answered Apr 27 '16 at 12:58

adeady

1,567713

suggest improvementsÂ |Â

Search This Blog

Iyfjky