How to approach boss that keeps hiring temp workers only to have me finish something?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
35
down vote
favorite
Long story short we've recently had a lot of work to do at my job and in order to fill that vacuum my boss has been hiring temp workers. At first he hired 3 which stayed for about 2 months, but after the client moved up a deadline he hired 1 back recently.
I've been very cautious about delegating work to them as they've been making a huge mess of the code base and then when a push to production approaches I'm approached about making it workable. My boss is getting a little picky about this and made a comment to me about them being here to help and I need to give them something to do. The problem is he's not a developer, so he doesn't have the perspective of what it can take to fix or patch together bad code, he only has the perspective that he's paying for them.
I wouldn't have a problem giving them things to do if I didn't know (as it's happened numerous times now) that in a few weeks they'll leave and when something breaks I'll be the one who's tasked to fix it in record time. The last time this happened a temp spent almost 2 weeks writing out code that I was then expected to fix in 1 days time.
How do I convey this without seeming like a perfectionist who just wants to do it all himself?
professionalism management manager conflict-resolution
 |Â
show 7 more comments
up vote
35
down vote
favorite
Long story short we've recently had a lot of work to do at my job and in order to fill that vacuum my boss has been hiring temp workers. At first he hired 3 which stayed for about 2 months, but after the client moved up a deadline he hired 1 back recently.
I've been very cautious about delegating work to them as they've been making a huge mess of the code base and then when a push to production approaches I'm approached about making it workable. My boss is getting a little picky about this and made a comment to me about them being here to help and I need to give them something to do. The problem is he's not a developer, so he doesn't have the perspective of what it can take to fix or patch together bad code, he only has the perspective that he's paying for them.
I wouldn't have a problem giving them things to do if I didn't know (as it's happened numerous times now) that in a few weeks they'll leave and when something breaks I'll be the one who's tasked to fix it in record time. The last time this happened a temp spent almost 2 weeks writing out code that I was then expected to fix in 1 days time.
How do I convey this without seeming like a perfectionist who just wants to do it all himself?
professionalism management manager conflict-resolution
5
"I wouldn't have a problem giving them things to do if I didn't know (as it's happened numerous times now) that in a few weeks they'll leave and when something breaks I'll be the one who's tasked to fix it in record time. " - so can you get all the work done by yourself within the time frame required by the client? If so, just tell your boss that you'll do it all. Otherwise, find a way to make the temps as useful as possible, or hire better temps.
â Joe Strazzere
10 hours ago
5
Wow, what a nightmare. So basically other people are being paid to create opportunity cost (your time training them, answering questions, etc.), negative work (you're having to fix it), technological debt (it's two steps backward that you have to make up, but it's initially borrowed as opportunity cost, then paid by you, presumably with your free time). They'd be better off padding your salary with what their paying these temps and just staying out of your way.. You don't say what your software does, but I'd especially fear logical bugs that may remain hidden, waiting to strike!
â elrobis
8 hours ago
4
I write tests for the temps, and have them work red to green.
â Carl
8 hours ago
3
Adding people to a late project makes it later. Also how do you ever let people push to production ??? review pull request, make them write tests, don't accept the pull request until things are done (and don't break other things).
â xyious
8 hours ago
11
Have you ever asked him if 9 women would be able to deliver a baby in one month?
â PlasmaHH
7 hours ago
 |Â
show 7 more comments
up vote
35
down vote
favorite
up vote
35
down vote
favorite
Long story short we've recently had a lot of work to do at my job and in order to fill that vacuum my boss has been hiring temp workers. At first he hired 3 which stayed for about 2 months, but after the client moved up a deadline he hired 1 back recently.
I've been very cautious about delegating work to them as they've been making a huge mess of the code base and then when a push to production approaches I'm approached about making it workable. My boss is getting a little picky about this and made a comment to me about them being here to help and I need to give them something to do. The problem is he's not a developer, so he doesn't have the perspective of what it can take to fix or patch together bad code, he only has the perspective that he's paying for them.
I wouldn't have a problem giving them things to do if I didn't know (as it's happened numerous times now) that in a few weeks they'll leave and when something breaks I'll be the one who's tasked to fix it in record time. The last time this happened a temp spent almost 2 weeks writing out code that I was then expected to fix in 1 days time.
How do I convey this without seeming like a perfectionist who just wants to do it all himself?
professionalism management manager conflict-resolution
Long story short we've recently had a lot of work to do at my job and in order to fill that vacuum my boss has been hiring temp workers. At first he hired 3 which stayed for about 2 months, but after the client moved up a deadline he hired 1 back recently.
I've been very cautious about delegating work to them as they've been making a huge mess of the code base and then when a push to production approaches I'm approached about making it workable. My boss is getting a little picky about this and made a comment to me about them being here to help and I need to give them something to do. The problem is he's not a developer, so he doesn't have the perspective of what it can take to fix or patch together bad code, he only has the perspective that he's paying for them.
I wouldn't have a problem giving them things to do if I didn't know (as it's happened numerous times now) that in a few weeks they'll leave and when something breaks I'll be the one who's tasked to fix it in record time. The last time this happened a temp spent almost 2 weeks writing out code that I was then expected to fix in 1 days time.
How do I convey this without seeming like a perfectionist who just wants to do it all himself?
professionalism management manager conflict-resolution
professionalism management manager conflict-resolution
asked 11 hours ago
Kyle
35024
35024
5
"I wouldn't have a problem giving them things to do if I didn't know (as it's happened numerous times now) that in a few weeks they'll leave and when something breaks I'll be the one who's tasked to fix it in record time. " - so can you get all the work done by yourself within the time frame required by the client? If so, just tell your boss that you'll do it all. Otherwise, find a way to make the temps as useful as possible, or hire better temps.
â Joe Strazzere
10 hours ago
5
Wow, what a nightmare. So basically other people are being paid to create opportunity cost (your time training them, answering questions, etc.), negative work (you're having to fix it), technological debt (it's two steps backward that you have to make up, but it's initially borrowed as opportunity cost, then paid by you, presumably with your free time). They'd be better off padding your salary with what their paying these temps and just staying out of your way.. You don't say what your software does, but I'd especially fear logical bugs that may remain hidden, waiting to strike!
â elrobis
8 hours ago
4
I write tests for the temps, and have them work red to green.
â Carl
8 hours ago
3
Adding people to a late project makes it later. Also how do you ever let people push to production ??? review pull request, make them write tests, don't accept the pull request until things are done (and don't break other things).
â xyious
8 hours ago
11
Have you ever asked him if 9 women would be able to deliver a baby in one month?
â PlasmaHH
7 hours ago
 |Â
show 7 more comments
5
"I wouldn't have a problem giving them things to do if I didn't know (as it's happened numerous times now) that in a few weeks they'll leave and when something breaks I'll be the one who's tasked to fix it in record time. " - so can you get all the work done by yourself within the time frame required by the client? If so, just tell your boss that you'll do it all. Otherwise, find a way to make the temps as useful as possible, or hire better temps.
â Joe Strazzere
10 hours ago
5
Wow, what a nightmare. So basically other people are being paid to create opportunity cost (your time training them, answering questions, etc.), negative work (you're having to fix it), technological debt (it's two steps backward that you have to make up, but it's initially borrowed as opportunity cost, then paid by you, presumably with your free time). They'd be better off padding your salary with what their paying these temps and just staying out of your way.. You don't say what your software does, but I'd especially fear logical bugs that may remain hidden, waiting to strike!
â elrobis
8 hours ago
4
I write tests for the temps, and have them work red to green.
â Carl
8 hours ago
3
Adding people to a late project makes it later. Also how do you ever let people push to production ??? review pull request, make them write tests, don't accept the pull request until things are done (and don't break other things).
â xyious
8 hours ago
11
Have you ever asked him if 9 women would be able to deliver a baby in one month?
â PlasmaHH
7 hours ago
5
5
"I wouldn't have a problem giving them things to do if I didn't know (as it's happened numerous times now) that in a few weeks they'll leave and when something breaks I'll be the one who's tasked to fix it in record time. " - so can you get all the work done by yourself within the time frame required by the client? If so, just tell your boss that you'll do it all. Otherwise, find a way to make the temps as useful as possible, or hire better temps.
â Joe Strazzere
10 hours ago
"I wouldn't have a problem giving them things to do if I didn't know (as it's happened numerous times now) that in a few weeks they'll leave and when something breaks I'll be the one who's tasked to fix it in record time. " - so can you get all the work done by yourself within the time frame required by the client? If so, just tell your boss that you'll do it all. Otherwise, find a way to make the temps as useful as possible, or hire better temps.
â Joe Strazzere
10 hours ago
5
5
Wow, what a nightmare. So basically other people are being paid to create opportunity cost (your time training them, answering questions, etc.), negative work (you're having to fix it), technological debt (it's two steps backward that you have to make up, but it's initially borrowed as opportunity cost, then paid by you, presumably with your free time). They'd be better off padding your salary with what their paying these temps and just staying out of your way.. You don't say what your software does, but I'd especially fear logical bugs that may remain hidden, waiting to strike!
â elrobis
8 hours ago
Wow, what a nightmare. So basically other people are being paid to create opportunity cost (your time training them, answering questions, etc.), negative work (you're having to fix it), technological debt (it's two steps backward that you have to make up, but it's initially borrowed as opportunity cost, then paid by you, presumably with your free time). They'd be better off padding your salary with what their paying these temps and just staying out of your way.. You don't say what your software does, but I'd especially fear logical bugs that may remain hidden, waiting to strike!
â elrobis
8 hours ago
4
4
I write tests for the temps, and have them work red to green.
â Carl
8 hours ago
I write tests for the temps, and have them work red to green.
â Carl
8 hours ago
3
3
Adding people to a late project makes it later. Also how do you ever let people push to production ??? review pull request, make them write tests, don't accept the pull request until things are done (and don't break other things).
â xyious
8 hours ago
Adding people to a late project makes it later. Also how do you ever let people push to production ??? review pull request, make them write tests, don't accept the pull request until things are done (and don't break other things).
â xyious
8 hours ago
11
11
Have you ever asked him if 9 women would be able to deliver a baby in one month?
â PlasmaHH
7 hours ago
Have you ever asked him if 9 women would be able to deliver a baby in one month?
â PlasmaHH
7 hours ago
 |Â
show 7 more comments
5 Answers
5
active
oldest
votes
up vote
56
down vote
You might want to take some arguments from the book The Mythical Man-Month by Frederick Brooks. Although it was originally written back in 1975 (overhauled in 1995), it is still one of the most important works regarding management of software development teams.
It is most known for codifying Brook's Law:
adding human resources to a late software project makes it later
The reasons are:
- New developers must be taught about the existing architecture of the project before they can do something useful. This takes time away from the existing development team.
- There is an upper bound to how many people will be able to make useful contributions to a software development project at the same time. It is often not possible to find reasonable sub-tasks to assign to new people.
Good software development requires a stable core team which works together from start to finish.
Your manager might not be aware of this rule. So he tries to help you in the only way he can think of: Add more people to your project.
45
+1000. I'm running into this now on the project I'm on. My boss understands this. Project management types don't. The best way I've heard this phrased "just because it takes one woman nine months to make a baby does not mean that nine women can do in one month".
â JimmyB
10 hours ago
6
@JimmyB challenge accepted ;)
â UKMonkey
9 hours ago
4
Seems like good advice and a good resource; however, your answer doesn't seem to directly address the question of 'how to approach the boss' who doesn't understand this. I.e. would you drop a copy of this book on their desk?
â Time4Tea
7 hours ago
@Time4Tea It's simple enough for a boss to comprehend, although some of the book is obsolescent (very few people care about old-style batch and time-sharing programming any more), and there's a few stinkers in there (the biggest one is his idea to not do information hiding). Still, there's a lot in there that is true but not common knowledge.
â David Thornley
7 hours ago
2
Adding developers to a task to get it done faster is like trying to have a baby in a month by getting 9 women pregnant.
â Kevin
5 hours ago
 |Â
show 4 more comments
up vote
18
down vote
The issue with temps and contractors (disclosure, I am one) is that there is often no comeback if the delivery is awful.
It may be worth having a chat with your boss about the quality of the temps. Hiring cheap means moving the costs further down the road, but eventually he'll be paying to fix the code.
You might also ask to be involved in the hiring process by providing a small coding test to make sure the temps are actually worth hiring. Nothing too dramatic, less than an hour of work to get an idea of ability.
add a comment |Â
up vote
3
down vote
This ventures into general software development advice....
1) If the code anyone writes breaks something add an automated test so that you can see it earlier next time.
2) Review pull requests, don't merge anything until you're sure nothing else breaks.
3) Tests make a good spec. TDD is a good way to ensure that what you're getting is what you want. Give someone a task to write the code you need (as exemplified by the tests you already wrote).
4) peer programming might be an option. You can correct things immediately and answer questions as things go on.
add a comment |Â
up vote
2
down vote
The skill level of the temps is likely dependant upon the amount of money your manager is investing into them. As they are only temps he obviously doesn't want to be wasting too much funding. As you say your boss is not a developer and likely just assumes that a coder can code.
However, if it's increasing your work load in the long term and it's affecting your current work. You need to pull him for a 1x1 and just convey your issues and the reason that you are not delegating as much work down to them and your worries for the future if you do delegate work to them
You want to make sure you don't come across as if you're having a go at your boss but at the same time you need to get the message across as he doesn't understand what happens within development. If you simply mention that you would be happy to delegate the work but only when you feel safe to do so.
add a comment |Â
up vote
1
down vote
How to approach boss that keeps hiring temp workers only to have me finish something?
You already have. All you can do is persevere with telling the boss.
Meanwhile there is a solution, the reason you're having to redo work is because you found out it was rubbish too late. You have an opportunity to practice some skills and take on more responsibility, but you're not doing it. It's not an esoteric problem, it's just a way of looking at a problem and resolution methodology. Well worth learning.
This is one of those times that micromanaging is critical. Assess the situation as a whole (including the people, they're a resource) and make a plan of resolution, use the manpower efficiently on those terms. This is the ONLY way to do it, you don't let even experienced people deviate from your plan, they don't have the full picture, you give them small tasks and check everything they do, they report to you at every step.
The most important bit is to understand the problem wholly and have a solid plan. Then break it up into simpler tasks wherever possible and don't rely on anyone to do their bit unsupervised.
add a comment |Â
StackExchange.ready(function ()
$("#show-editor-button input, #show-editor-button button").click(function ()
var showEditor = function()
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
;
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True')
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup(
url: '/post/self-answer-popup',
loaded: function(popup)
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
)
else
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true)
showEditor();
);
);
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
56
down vote
You might want to take some arguments from the book The Mythical Man-Month by Frederick Brooks. Although it was originally written back in 1975 (overhauled in 1995), it is still one of the most important works regarding management of software development teams.
It is most known for codifying Brook's Law:
adding human resources to a late software project makes it later
The reasons are:
- New developers must be taught about the existing architecture of the project before they can do something useful. This takes time away from the existing development team.
- There is an upper bound to how many people will be able to make useful contributions to a software development project at the same time. It is often not possible to find reasonable sub-tasks to assign to new people.
Good software development requires a stable core team which works together from start to finish.
Your manager might not be aware of this rule. So he tries to help you in the only way he can think of: Add more people to your project.
45
+1000. I'm running into this now on the project I'm on. My boss understands this. Project management types don't. The best way I've heard this phrased "just because it takes one woman nine months to make a baby does not mean that nine women can do in one month".
â JimmyB
10 hours ago
6
@JimmyB challenge accepted ;)
â UKMonkey
9 hours ago
4
Seems like good advice and a good resource; however, your answer doesn't seem to directly address the question of 'how to approach the boss' who doesn't understand this. I.e. would you drop a copy of this book on their desk?
â Time4Tea
7 hours ago
@Time4Tea It's simple enough for a boss to comprehend, although some of the book is obsolescent (very few people care about old-style batch and time-sharing programming any more), and there's a few stinkers in there (the biggest one is his idea to not do information hiding). Still, there's a lot in there that is true but not common knowledge.
â David Thornley
7 hours ago
2
Adding developers to a task to get it done faster is like trying to have a baby in a month by getting 9 women pregnant.
â Kevin
5 hours ago
 |Â
show 4 more comments
up vote
56
down vote
You might want to take some arguments from the book The Mythical Man-Month by Frederick Brooks. Although it was originally written back in 1975 (overhauled in 1995), it is still one of the most important works regarding management of software development teams.
It is most known for codifying Brook's Law:
adding human resources to a late software project makes it later
The reasons are:
- New developers must be taught about the existing architecture of the project before they can do something useful. This takes time away from the existing development team.
- There is an upper bound to how many people will be able to make useful contributions to a software development project at the same time. It is often not possible to find reasonable sub-tasks to assign to new people.
Good software development requires a stable core team which works together from start to finish.
Your manager might not be aware of this rule. So he tries to help you in the only way he can think of: Add more people to your project.
45
+1000. I'm running into this now on the project I'm on. My boss understands this. Project management types don't. The best way I've heard this phrased "just because it takes one woman nine months to make a baby does not mean that nine women can do in one month".
â JimmyB
10 hours ago
6
@JimmyB challenge accepted ;)
â UKMonkey
9 hours ago
4
Seems like good advice and a good resource; however, your answer doesn't seem to directly address the question of 'how to approach the boss' who doesn't understand this. I.e. would you drop a copy of this book on their desk?
â Time4Tea
7 hours ago
@Time4Tea It's simple enough for a boss to comprehend, although some of the book is obsolescent (very few people care about old-style batch and time-sharing programming any more), and there's a few stinkers in there (the biggest one is his idea to not do information hiding). Still, there's a lot in there that is true but not common knowledge.
â David Thornley
7 hours ago
2
Adding developers to a task to get it done faster is like trying to have a baby in a month by getting 9 women pregnant.
â Kevin
5 hours ago
 |Â
show 4 more comments
up vote
56
down vote
up vote
56
down vote
You might want to take some arguments from the book The Mythical Man-Month by Frederick Brooks. Although it was originally written back in 1975 (overhauled in 1995), it is still one of the most important works regarding management of software development teams.
It is most known for codifying Brook's Law:
adding human resources to a late software project makes it later
The reasons are:
- New developers must be taught about the existing architecture of the project before they can do something useful. This takes time away from the existing development team.
- There is an upper bound to how many people will be able to make useful contributions to a software development project at the same time. It is often not possible to find reasonable sub-tasks to assign to new people.
Good software development requires a stable core team which works together from start to finish.
Your manager might not be aware of this rule. So he tries to help you in the only way he can think of: Add more people to your project.
You might want to take some arguments from the book The Mythical Man-Month by Frederick Brooks. Although it was originally written back in 1975 (overhauled in 1995), it is still one of the most important works regarding management of software development teams.
It is most known for codifying Brook's Law:
adding human resources to a late software project makes it later
The reasons are:
- New developers must be taught about the existing architecture of the project before they can do something useful. This takes time away from the existing development team.
- There is an upper bound to how many people will be able to make useful contributions to a software development project at the same time. It is often not possible to find reasonable sub-tasks to assign to new people.
Good software development requires a stable core team which works together from start to finish.
Your manager might not be aware of this rule. So he tries to help you in the only way he can think of: Add more people to your project.
answered 10 hours ago
Philipp
20.6k34986
20.6k34986
45
+1000. I'm running into this now on the project I'm on. My boss understands this. Project management types don't. The best way I've heard this phrased "just because it takes one woman nine months to make a baby does not mean that nine women can do in one month".
â JimmyB
10 hours ago
6
@JimmyB challenge accepted ;)
â UKMonkey
9 hours ago
4
Seems like good advice and a good resource; however, your answer doesn't seem to directly address the question of 'how to approach the boss' who doesn't understand this. I.e. would you drop a copy of this book on their desk?
â Time4Tea
7 hours ago
@Time4Tea It's simple enough for a boss to comprehend, although some of the book is obsolescent (very few people care about old-style batch and time-sharing programming any more), and there's a few stinkers in there (the biggest one is his idea to not do information hiding). Still, there's a lot in there that is true but not common knowledge.
â David Thornley
7 hours ago
2
Adding developers to a task to get it done faster is like trying to have a baby in a month by getting 9 women pregnant.
â Kevin
5 hours ago
 |Â
show 4 more comments
45
+1000. I'm running into this now on the project I'm on. My boss understands this. Project management types don't. The best way I've heard this phrased "just because it takes one woman nine months to make a baby does not mean that nine women can do in one month".
â JimmyB
10 hours ago
6
@JimmyB challenge accepted ;)
â UKMonkey
9 hours ago
4
Seems like good advice and a good resource; however, your answer doesn't seem to directly address the question of 'how to approach the boss' who doesn't understand this. I.e. would you drop a copy of this book on their desk?
â Time4Tea
7 hours ago
@Time4Tea It's simple enough for a boss to comprehend, although some of the book is obsolescent (very few people care about old-style batch and time-sharing programming any more), and there's a few stinkers in there (the biggest one is his idea to not do information hiding). Still, there's a lot in there that is true but not common knowledge.
â David Thornley
7 hours ago
2
Adding developers to a task to get it done faster is like trying to have a baby in a month by getting 9 women pregnant.
â Kevin
5 hours ago
45
45
+1000. I'm running into this now on the project I'm on. My boss understands this. Project management types don't. The best way I've heard this phrased "just because it takes one woman nine months to make a baby does not mean that nine women can do in one month".
â JimmyB
10 hours ago
+1000. I'm running into this now on the project I'm on. My boss understands this. Project management types don't. The best way I've heard this phrased "just because it takes one woman nine months to make a baby does not mean that nine women can do in one month".
â JimmyB
10 hours ago
6
6
@JimmyB challenge accepted ;)
â UKMonkey
9 hours ago
@JimmyB challenge accepted ;)
â UKMonkey
9 hours ago
4
4
Seems like good advice and a good resource; however, your answer doesn't seem to directly address the question of 'how to approach the boss' who doesn't understand this. I.e. would you drop a copy of this book on their desk?
â Time4Tea
7 hours ago
Seems like good advice and a good resource; however, your answer doesn't seem to directly address the question of 'how to approach the boss' who doesn't understand this. I.e. would you drop a copy of this book on their desk?
â Time4Tea
7 hours ago
@Time4Tea It's simple enough for a boss to comprehend, although some of the book is obsolescent (very few people care about old-style batch and time-sharing programming any more), and there's a few stinkers in there (the biggest one is his idea to not do information hiding). Still, there's a lot in there that is true but not common knowledge.
â David Thornley
7 hours ago
@Time4Tea It's simple enough for a boss to comprehend, although some of the book is obsolescent (very few people care about old-style batch and time-sharing programming any more), and there's a few stinkers in there (the biggest one is his idea to not do information hiding). Still, there's a lot in there that is true but not common knowledge.
â David Thornley
7 hours ago
2
2
Adding developers to a task to get it done faster is like trying to have a baby in a month by getting 9 women pregnant.
â Kevin
5 hours ago
Adding developers to a task to get it done faster is like trying to have a baby in a month by getting 9 women pregnant.
â Kevin
5 hours ago
 |Â
show 4 more comments
up vote
18
down vote
The issue with temps and contractors (disclosure, I am one) is that there is often no comeback if the delivery is awful.
It may be worth having a chat with your boss about the quality of the temps. Hiring cheap means moving the costs further down the road, but eventually he'll be paying to fix the code.
You might also ask to be involved in the hiring process by providing a small coding test to make sure the temps are actually worth hiring. Nothing too dramatic, less than an hour of work to get an idea of ability.
add a comment |Â
up vote
18
down vote
The issue with temps and contractors (disclosure, I am one) is that there is often no comeback if the delivery is awful.
It may be worth having a chat with your boss about the quality of the temps. Hiring cheap means moving the costs further down the road, but eventually he'll be paying to fix the code.
You might also ask to be involved in the hiring process by providing a small coding test to make sure the temps are actually worth hiring. Nothing too dramatic, less than an hour of work to get an idea of ability.
add a comment |Â
up vote
18
down vote
up vote
18
down vote
The issue with temps and contractors (disclosure, I am one) is that there is often no comeback if the delivery is awful.
It may be worth having a chat with your boss about the quality of the temps. Hiring cheap means moving the costs further down the road, but eventually he'll be paying to fix the code.
You might also ask to be involved in the hiring process by providing a small coding test to make sure the temps are actually worth hiring. Nothing too dramatic, less than an hour of work to get an idea of ability.
The issue with temps and contractors (disclosure, I am one) is that there is often no comeback if the delivery is awful.
It may be worth having a chat with your boss about the quality of the temps. Hiring cheap means moving the costs further down the road, but eventually he'll be paying to fix the code.
You might also ask to be involved in the hiring process by providing a small coding test to make sure the temps are actually worth hiring. Nothing too dramatic, less than an hour of work to get an idea of ability.
answered 11 hours ago
JohnHC
11.9k83043
11.9k83043
add a comment |Â
add a comment |Â
up vote
3
down vote
This ventures into general software development advice....
1) If the code anyone writes breaks something add an automated test so that you can see it earlier next time.
2) Review pull requests, don't merge anything until you're sure nothing else breaks.
3) Tests make a good spec. TDD is a good way to ensure that what you're getting is what you want. Give someone a task to write the code you need (as exemplified by the tests you already wrote).
4) peer programming might be an option. You can correct things immediately and answer questions as things go on.
add a comment |Â
up vote
3
down vote
This ventures into general software development advice....
1) If the code anyone writes breaks something add an automated test so that you can see it earlier next time.
2) Review pull requests, don't merge anything until you're sure nothing else breaks.
3) Tests make a good spec. TDD is a good way to ensure that what you're getting is what you want. Give someone a task to write the code you need (as exemplified by the tests you already wrote).
4) peer programming might be an option. You can correct things immediately and answer questions as things go on.
add a comment |Â
up vote
3
down vote
up vote
3
down vote
This ventures into general software development advice....
1) If the code anyone writes breaks something add an automated test so that you can see it earlier next time.
2) Review pull requests, don't merge anything until you're sure nothing else breaks.
3) Tests make a good spec. TDD is a good way to ensure that what you're getting is what you want. Give someone a task to write the code you need (as exemplified by the tests you already wrote).
4) peer programming might be an option. You can correct things immediately and answer questions as things go on.
This ventures into general software development advice....
1) If the code anyone writes breaks something add an automated test so that you can see it earlier next time.
2) Review pull requests, don't merge anything until you're sure nothing else breaks.
3) Tests make a good spec. TDD is a good way to ensure that what you're getting is what you want. Give someone a task to write the code you need (as exemplified by the tests you already wrote).
4) peer programming might be an option. You can correct things immediately and answer questions as things go on.
answered 8 hours ago
xyious
1844
1844
add a comment |Â
add a comment |Â
up vote
2
down vote
The skill level of the temps is likely dependant upon the amount of money your manager is investing into them. As they are only temps he obviously doesn't want to be wasting too much funding. As you say your boss is not a developer and likely just assumes that a coder can code.
However, if it's increasing your work load in the long term and it's affecting your current work. You need to pull him for a 1x1 and just convey your issues and the reason that you are not delegating as much work down to them and your worries for the future if you do delegate work to them
You want to make sure you don't come across as if you're having a go at your boss but at the same time you need to get the message across as he doesn't understand what happens within development. If you simply mention that you would be happy to delegate the work but only when you feel safe to do so.
add a comment |Â
up vote
2
down vote
The skill level of the temps is likely dependant upon the amount of money your manager is investing into them. As they are only temps he obviously doesn't want to be wasting too much funding. As you say your boss is not a developer and likely just assumes that a coder can code.
However, if it's increasing your work load in the long term and it's affecting your current work. You need to pull him for a 1x1 and just convey your issues and the reason that you are not delegating as much work down to them and your worries for the future if you do delegate work to them
You want to make sure you don't come across as if you're having a go at your boss but at the same time you need to get the message across as he doesn't understand what happens within development. If you simply mention that you would be happy to delegate the work but only when you feel safe to do so.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
The skill level of the temps is likely dependant upon the amount of money your manager is investing into them. As they are only temps he obviously doesn't want to be wasting too much funding. As you say your boss is not a developer and likely just assumes that a coder can code.
However, if it's increasing your work load in the long term and it's affecting your current work. You need to pull him for a 1x1 and just convey your issues and the reason that you are not delegating as much work down to them and your worries for the future if you do delegate work to them
You want to make sure you don't come across as if you're having a go at your boss but at the same time you need to get the message across as he doesn't understand what happens within development. If you simply mention that you would be happy to delegate the work but only when you feel safe to do so.
The skill level of the temps is likely dependant upon the amount of money your manager is investing into them. As they are only temps he obviously doesn't want to be wasting too much funding. As you say your boss is not a developer and likely just assumes that a coder can code.
However, if it's increasing your work load in the long term and it's affecting your current work. You need to pull him for a 1x1 and just convey your issues and the reason that you are not delegating as much work down to them and your worries for the future if you do delegate work to them
You want to make sure you don't come across as if you're having a go at your boss but at the same time you need to get the message across as he doesn't understand what happens within development. If you simply mention that you would be happy to delegate the work but only when you feel safe to do so.
edited 11 hours ago
answered 11 hours ago
Twyxz
5,12852151
5,12852151
add a comment |Â
add a comment |Â
up vote
1
down vote
How to approach boss that keeps hiring temp workers only to have me finish something?
You already have. All you can do is persevere with telling the boss.
Meanwhile there is a solution, the reason you're having to redo work is because you found out it was rubbish too late. You have an opportunity to practice some skills and take on more responsibility, but you're not doing it. It's not an esoteric problem, it's just a way of looking at a problem and resolution methodology. Well worth learning.
This is one of those times that micromanaging is critical. Assess the situation as a whole (including the people, they're a resource) and make a plan of resolution, use the manpower efficiently on those terms. This is the ONLY way to do it, you don't let even experienced people deviate from your plan, they don't have the full picture, you give them small tasks and check everything they do, they report to you at every step.
The most important bit is to understand the problem wholly and have a solid plan. Then break it up into simpler tasks wherever possible and don't rely on anyone to do their bit unsupervised.
add a comment |Â
up vote
1
down vote
How to approach boss that keeps hiring temp workers only to have me finish something?
You already have. All you can do is persevere with telling the boss.
Meanwhile there is a solution, the reason you're having to redo work is because you found out it was rubbish too late. You have an opportunity to practice some skills and take on more responsibility, but you're not doing it. It's not an esoteric problem, it's just a way of looking at a problem and resolution methodology. Well worth learning.
This is one of those times that micromanaging is critical. Assess the situation as a whole (including the people, they're a resource) and make a plan of resolution, use the manpower efficiently on those terms. This is the ONLY way to do it, you don't let even experienced people deviate from your plan, they don't have the full picture, you give them small tasks and check everything they do, they report to you at every step.
The most important bit is to understand the problem wholly and have a solid plan. Then break it up into simpler tasks wherever possible and don't rely on anyone to do their bit unsupervised.
add a comment |Â
up vote
1
down vote
up vote
1
down vote
How to approach boss that keeps hiring temp workers only to have me finish something?
You already have. All you can do is persevere with telling the boss.
Meanwhile there is a solution, the reason you're having to redo work is because you found out it was rubbish too late. You have an opportunity to practice some skills and take on more responsibility, but you're not doing it. It's not an esoteric problem, it's just a way of looking at a problem and resolution methodology. Well worth learning.
This is one of those times that micromanaging is critical. Assess the situation as a whole (including the people, they're a resource) and make a plan of resolution, use the manpower efficiently on those terms. This is the ONLY way to do it, you don't let even experienced people deviate from your plan, they don't have the full picture, you give them small tasks and check everything they do, they report to you at every step.
The most important bit is to understand the problem wholly and have a solid plan. Then break it up into simpler tasks wherever possible and don't rely on anyone to do their bit unsupervised.
How to approach boss that keeps hiring temp workers only to have me finish something?
You already have. All you can do is persevere with telling the boss.
Meanwhile there is a solution, the reason you're having to redo work is because you found out it was rubbish too late. You have an opportunity to practice some skills and take on more responsibility, but you're not doing it. It's not an esoteric problem, it's just a way of looking at a problem and resolution methodology. Well worth learning.
This is one of those times that micromanaging is critical. Assess the situation as a whole (including the people, they're a resource) and make a plan of resolution, use the manpower efficiently on those terms. This is the ONLY way to do it, you don't let even experienced people deviate from your plan, they don't have the full picture, you give them small tasks and check everything they do, they report to you at every step.
The most important bit is to understand the problem wholly and have a solid plan. Then break it up into simpler tasks wherever possible and don't rely on anyone to do their bit unsupervised.
edited 1 hour ago
answered 2 hours ago
Kilisi
101k56227396
101k56227396
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f120528%2fhow-to-approach-boss-that-keeps-hiring-temp-workers-only-to-have-me-finish-somet%23new-answer', 'question_page');
);
Post as a guest
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
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
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
5
"I wouldn't have a problem giving them things to do if I didn't know (as it's happened numerous times now) that in a few weeks they'll leave and when something breaks I'll be the one who's tasked to fix it in record time. " - so can you get all the work done by yourself within the time frame required by the client? If so, just tell your boss that you'll do it all. Otherwise, find a way to make the temps as useful as possible, or hire better temps.
â Joe Strazzere
10 hours ago
5
Wow, what a nightmare. So basically other people are being paid to create opportunity cost (your time training them, answering questions, etc.), negative work (you're having to fix it), technological debt (it's two steps backward that you have to make up, but it's initially borrowed as opportunity cost, then paid by you, presumably with your free time). They'd be better off padding your salary with what their paying these temps and just staying out of your way.. You don't say what your software does, but I'd especially fear logical bugs that may remain hidden, waiting to strike!
â elrobis
8 hours ago
4
I write tests for the temps, and have them work red to green.
â Carl
8 hours ago
3
Adding people to a late project makes it later. Also how do you ever let people push to production ??? review pull request, make them write tests, don't accept the pull request until things are done (and don't break other things).
â xyious
8 hours ago
11
Have you ever asked him if 9 women would be able to deliver a baby in one month?
â PlasmaHH
7 hours ago