Mixing
![Is it okay for Work to constantly place me in a high playing job position and be paid the same lower salary as my previous job position? [closed]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjbpfN9tAutmK93bJRC3ZoROZzi2TJDms5n8_qJuhgE0a9b52OOHayv3NGT8igAdFL7byXNst-_1DZK5SjrIJ28_6RQPUpBROqMs5s6jo-ZsjX8kjDwfxJufIitH3TaQRXWaGSQKRQib-f/s72-c/1.jpg)
How to thank colleagues helped over the Christmas weekend on very big prod issue? [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
6
down vote
favorite
Office location: CA, USA
Issue started on Last Friday and many had already gone for vacation. Issue started in production due to my code, committed years back. Many colleagues joined the bridge and helped a lot. As production deployment had to be done, it was across different teams too. It had top management also. I would like to thank them. I considered lunch/drink, but I can't afford.
Cards + chocolate (or any other good option also fine) @desk - I am fine with this idea, have seen people doing it. It may be opt as new year is on the way.
But what shall I write in there? Any decent, very good thank you note? Also shall I add sorry also in there? Which will be the best?
software-industry colleagues offices
edited Dec 29 '14 at 16:19
Chris E
40.4k22129166
asked Dec 29 '14 at 15:57
Vaandu
1395
closed as primarily opinion-based by Chris E, gnat, Jan Doggen, Garrison Neely, Jim G. Dec 31 '14 at 5:51
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
 |Â
show 1 more comment
up vote
6
down vote
favorite
Office location: CA, USA
Issue started on Last Friday and many had already gone for vacation. Issue started in production due to my code, committed years back. Many colleagues joined the bridge and helped a lot. As production deployment had to be done, it was across different teams too. It had top management also. I would like to thank them. I considered lunch/drink, but I can't afford.
Cards + chocolate (or any other good option also fine) @desk - I am fine with this idea, have seen people doing it. It may be opt as new year is on the way.
But what shall I write in there? Any decent, very good thank you note? Also shall I add sorry also in there? Which will be the best?
software-industry colleagues offices
edited Dec 29 '14 at 16:19
Chris E
40.4k22129166
asked Dec 29 '14 at 15:57
Vaandu
1395
closed as primarily opinion-based by Chris E, gnat, Jan Doggen, Garrison Neely, Jim G. Dec 31 '14 at 5:51
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
2
Shake hands, "Seriously, thanks for all your help this weekend. I really appreciate it."
– Joel Etherton
Dec 29 '14 at 16:25
1
Whats with the random downvotes without comment?
– abelenky
Dec 29 '14 at 16:59
13
Just because you committed the code "years ago" doesn't mean that you should feel like you're the lone person responsible for this happening. That's several years of testing that missed the problem in that code and probably a half-dozen or more other people who overlooked it too. The few programmers who have written anything approaching perfect non-trivial code are named Knuth or built the Space Shuttle
– alroc
Dec 29 '14 at 19:02
3
Chocolate and a "thank you" card would be as far as I'd go - and even then it might be overkill. If everyone who ever committed code with a bug in it brought in chocolate, we'd all be overweight. (Oh, we are all overweight. Huh. Just goes to show... :-). First, don't feel bad - any developer with any length of experience has done this. You fix it, you say "thanks", you move forward. Sometimes, just on a whim, I bring in pastry or something similar. Kind of covers me for this kind of "aw, sh*t!" moment. So...chocolate, pastry, brownies...whatever. :-)
– Bob Jarvis
Dec 29 '14 at 23:51
1
I believe that the company has benefitted from your combined efforts, hence it's up to the company management to show its appreciation of those endeavours. The ball is squarely in management's court and your efforts should be restricted to suggesting to your boss that a practical demonstration of that appreciation would be in order. From their viewpoint, it will also build morale and make personnel happier to repeat the effort in the inevitable future cases of similar problems.
– Magoo
Dec 30 '14 at 3:26
 |Â
show 1 more comment
up vote
6
down vote
favorite
up vote
6
down vote
favorite
Office location: CA, USA
Issue started on Last Friday and many had already gone for vacation. Issue started in production due to my code, committed years back. Many colleagues joined the bridge and helped a lot. As production deployment had to be done, it was across different teams too. It had top management also. I would like to thank them. I considered lunch/drink, but I can't afford.
Cards + chocolate (or any other good option also fine) @desk - I am fine with this idea, have seen people doing it. It may be opt as new year is on the way.
But what shall I write in there? Any decent, very good thank you note? Also shall I add sorry also in there? Which will be the best?
software-industry colleagues offices
edited Dec 29 '14 at 16:19
Chris E
40.4k22129166
asked Dec 29 '14 at 15:57
Vaandu
1395
Office location: CA, USA
Issue started on Last Friday and many had already gone for vacation. Issue started in production due to my code, committed years back. Many colleagues joined the bridge and helped a lot. As production deployment had to be done, it was across different teams too. It had top management also. I would like to thank them. I considered lunch/drink, but I can't afford.
Cards + chocolate (or any other good option also fine) @desk - I am fine with this idea, have seen people doing it. It may be opt as new year is on the way.
But what shall I write in there? Any decent, very good thank you note? Also shall I add sorry also in there? Which will be the best?
software-industry colleagues offices
edited Dec 29 '14 at 16:19
Chris E
40.4k22129166
asked Dec 29 '14 at 15:57
Vaandu
1395
edited Dec 29 '14 at 16:19
Chris E
40.4k22129166
edited Dec 29 '14 at 16:19
Chris E
40.4k22129166
edited Dec 29 '14 at 16:19
Chris E
40.4k22129166
40.4k22129166
asked Dec 29 '14 at 15:57
Vaandu
1395
asked Dec 29 '14 at 15:57
Vaandu
1395
asked Dec 29 '14 at 15:57
Vaandu
1395
1395
closed as primarily opinion-based by Chris E, gnat, Jan Doggen, Garrison Neely, Jim G. Dec 31 '14 at 5:51
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as primarily opinion-based by Chris E, gnat, Jan Doggen, Garrison Neely, Jim G. Dec 31 '14 at 5:51
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
2
Shake hands, "Seriously, thanks for all your help this weekend. I really appreciate it."
– Joel Etherton
Dec 29 '14 at 16:25
1
Whats with the random downvotes without comment?
– abelenky
Dec 29 '14 at 16:59
13
Just because you committed the code "years ago" doesn't mean that you should feel like you're the lone person responsible for this happening. That's several years of testing that missed the problem in that code and probably a half-dozen or more other people who overlooked it too. The few programmers who have written anything approaching perfect non-trivial code are named Knuth or built the Space Shuttle
– alroc
Dec 29 '14 at 19:02
3
Chocolate and a "thank you" card would be as far as I'd go - and even then it might be overkill. If everyone who ever committed code with a bug in it brought in chocolate, we'd all be overweight. (Oh, we are all overweight. Huh. Just goes to show... :-). First, don't feel bad - any developer with any length of experience has done this. You fix it, you say "thanks", you move forward. Sometimes, just on a whim, I bring in pastry or something similar. Kind of covers me for this kind of "aw, sh*t!" moment. So...chocolate, pastry, brownies...whatever. :-)
– Bob Jarvis
Dec 29 '14 at 23:51
1
I believe that the company has benefitted from your combined efforts, hence it's up to the company management to show its appreciation of those endeavours. The ball is squarely in management's court and your efforts should be restricted to suggesting to your boss that a practical demonstration of that appreciation would be in order. From their viewpoint, it will also build morale and make personnel happier to repeat the effort in the inevitable future cases of similar problems.
– Magoo
Dec 30 '14 at 3:26
 |Â
show 1 more comment
2
Shake hands, "Seriously, thanks for all your help this weekend. I really appreciate it."
– Joel Etherton
Dec 29 '14 at 16:25
1
Whats with the random downvotes without comment?
– abelenky
Dec 29 '14 at 16:59
13
Just because you committed the code "years ago" doesn't mean that you should feel like you're the lone person responsible for this happening. That's several years of testing that missed the problem in that code and probably a half-dozen or more other people who overlooked it too. The few programmers who have written anything approaching perfect non-trivial code are named Knuth or built the Space Shuttle
– alroc
Dec 29 '14 at 19:02
3
Chocolate and a "thank you" card would be as far as I'd go - and even then it might be overkill. If everyone who ever committed code with a bug in it brought in chocolate, we'd all be overweight. (Oh, we are all overweight. Huh. Just goes to show... :-). First, don't feel bad - any developer with any length of experience has done this. You fix it, you say "thanks", you move forward. Sometimes, just on a whim, I bring in pastry or something similar. Kind of covers me for this kind of "aw, sh*t!" moment. So...chocolate, pastry, brownies...whatever. :-)
– Bob Jarvis
Dec 29 '14 at 23:51
1
I believe that the company has benefitted from your combined efforts, hence it's up to the company management to show its appreciation of those endeavours. The ball is squarely in management's court and your efforts should be restricted to suggesting to your boss that a practical demonstration of that appreciation would be in order. From their viewpoint, it will also build morale and make personnel happier to repeat the effort in the inevitable future cases of similar problems.
– Magoo
Dec 30 '14 at 3:26
2
2
Shake hands, "Seriously, thanks for all your help this weekend. I really appreciate it."
– Joel Etherton
Dec 29 '14 at 16:25
Shake hands, "Seriously, thanks for all your help this weekend. I really appreciate it."
– Joel Etherton
Dec 29 '14 at 16:25
1
1
Whats with the random downvotes without comment?
– abelenky
Dec 29 '14 at 16:59
Whats with the random downvotes without comment?
– abelenky
Dec 29 '14 at 16:59
13
13
Just because you committed the code "years ago" doesn't mean that you should feel like you're the lone person responsible for this happening. That's several years of testing that missed the problem in that code and probably a half-dozen or more other people who overlooked it too. The few programmers who have written anything approaching perfect non-trivial code are named Knuth or built the Space Shuttle
– alroc
Dec 29 '14 at 19:02
Just because you committed the code "years ago" doesn't mean that you should feel like you're the lone person responsible for this happening. That's several years of testing that missed the problem in that code and probably a half-dozen or more other people who overlooked it too. The few programmers who have written anything approaching perfect non-trivial code are named Knuth or built the Space Shuttle
– alroc
Dec 29 '14 at 19:02
3
3
Chocolate and a "thank you" card would be as far as I'd go - and even then it might be overkill. If everyone who ever committed code with a bug in it brought in chocolate, we'd all be overweight. (Oh, we are all overweight. Huh. Just goes to show... :-). First, don't feel bad - any developer with any length of experience has done this. You fix it, you say "thanks", you move forward. Sometimes, just on a whim, I bring in pastry or something similar. Kind of covers me for this kind of "aw, sh*t!" moment. So...chocolate, pastry, brownies...whatever. :-)
– Bob Jarvis
Dec 29 '14 at 23:51
Chocolate and a "thank you" card would be as far as I'd go - and even then it might be overkill. If everyone who ever committed code with a bug in it brought in chocolate, we'd all be overweight. (Oh, we are all overweight. Huh. Just goes to show... :-). First, don't feel bad - any developer with any length of experience has done this. You fix it, you say "thanks", you move forward. Sometimes, just on a whim, I bring in pastry or something similar. Kind of covers me for this kind of "aw, sh*t!" moment. So...chocolate, pastry, brownies...whatever. :-)
– Bob Jarvis
Dec 29 '14 at 23:51
1
1
I believe that the company has benefitted from your combined efforts, hence it's up to the company management to show its appreciation of those endeavours. The ball is squarely in management's court and your efforts should be restricted to suggesting to your boss that a practical demonstration of that appreciation would be in order. From their viewpoint, it will also build morale and make personnel happier to repeat the effort in the inevitable future cases of similar problems.
– Magoo
Dec 30 '14 at 3:26
I believe that the company has benefitted from your combined efforts, hence it's up to the company management to show its appreciation of those endeavours. The ball is squarely in management's court and your efforts should be restricted to suggesting to your boss that a practical demonstration of that appreciation would be in order. From their viewpoint, it will also build morale and make personnel happier to repeat the effort in the inevitable future cases of similar problems.
– Magoo
Dec 30 '14 at 3:26
 |Â
show 1 more comment
4 Answers
4
active
oldest
votes
up vote
1
down vote
accepted
Never ever shout about issues that came up because of something you did which had a negative impact on system.
You may want to act nice to let everyone know but then you going to degrade your performance.
It's a workplace - get over it. They helped you, you help them when they are in trouble that's how you balance such matters... Not by buying people gifts..
answered Dec 30 '14 at 10:32
NULL
2,65331125
suggest improvements |Â
up vote
18
down vote
Send a thank you email to each person, and cc their boss as well. Let the leadership know how much you appreciate their help, because that is something that can translate to raises. Bosses need to know when their people go above and beyond.
answered Dec 29 '14 at 16:49
thursdaysgeek
24.1k103998
Taking the group out for lunch as well would be a nice gesture. I don't know anyone who dislikes free food.
– alroc
Dec 29 '14 at 17:02
4
True, but the OP specifically mentioned that lunch was out of his budget.
– thursdaysgeek
Dec 29 '14 at 18:56
1
Expressing your gratitude in person would also go a long way -- in addition to the emails, taking the time and effort to visit each participating colleague at their desk and personally thank them with a smile and a handshake underlines the sincerity of your gratitude (and has no budgetary requirement!).
– Doktor J
Dec 29 '14 at 22:00
1
+1000 for copying their boss on the thanks, or sending thanks to their boss with copy to them. Going beyond requirements to help the company should always help their annual review scores ... at least, if management is sane.
– keshlam
Dec 30 '14 at 5:25
suggest improvements |Â
up vote
6
down vote
There are two basic goals you should have in your thanking your peers here.
Getting them the recognition they want/deserve
While by all means it's "their job" to step in when things go to hell, even on holidays, it's still something they should get an extra nod for. Why things happened isn't important here, only that there was a failure and people stepped up and fixed it.
For me, I would take the time to write up a nice email. Ideally you want this email to reach the respective people and their managers. You may want to make sure it's okay to contact their managers through your manager. The email should be very brief. Simply pointing out who you'd like to thank, that there was an outage and despite being on vacation people stepped up to see it fixed.
Expressing your gratitude
Your code blew up in production, it may have been a mistake, or could have been just what was right then was wrong now, regardless these people could have just ignored the issue and left it as "your problem".
They didn't, they rolled up their sleeves and helped you out. Again arguable that's "their job" but again they could have just not answered the phone, or just said "sorry man, I'm no where near a computer to help" (or other excuse)
So you feel both thankful and guilty they had to work during their vacation. You should contact them as individually as practical to give them a personal thank you. If we're talking a dozen or so people contacting them individually would be best, if we're talking like fifty you're probably better off thanking them based on team, etc.
I wouldn't apologize per se, we all make mistakes, but do make a point to thank them for helping you out with the issue despite being on vacation and that you truly appreciate it.
edited Dec 30 '14 at 12:18
BCdotWEB
1153
answered Dec 29 '14 at 21:38
RualStorge
9,5372231
suggest improvements |Â
up vote
2
down vote
I would not go about it as a I messed up and these people helped bail me out.
I don't think you should buy gifts out of your pocket.
I would couch it as a report:
Over the holiday we experienced a critical bug X in production.
The bug originated in Y.
The fix was Z.
Members that contributed include a,b,c, ...
Sorry if I missed anyone
Thank you all for your help
answered Dec 29 '14 at 19:24
paparazzo
33.3k657106
suggest improvements |Â
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Never ever shout about issues that came up because of something you did which had a negative impact on system.
You may want to act nice to let everyone know but then you going to degrade your performance.
It's a workplace - get over it. They helped you, you help them when they are in trouble that's how you balance such matters... Not by buying people gifts..
answered Dec 30 '14 at 10:32
NULL
2,65331125
suggest improvements |Â
up vote
1
down vote
accepted
Never ever shout about issues that came up because of something you did which had a negative impact on system.
You may want to act nice to let everyone know but then you going to degrade your performance.
It's a workplace - get over it. They helped you, you help them when they are in trouble that's how you balance such matters... Not by buying people gifts..
answered Dec 30 '14 at 10:32
NULL
2,65331125
suggest improvements |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Never ever shout about issues that came up because of something you did which had a negative impact on system.
You may want to act nice to let everyone know but then you going to degrade your performance.
It's a workplace - get over it. They helped you, you help them when they are in trouble that's how you balance such matters... Not by buying people gifts..
answered Dec 30 '14 at 10:32
NULL
2,65331125
Never ever shout about issues that came up because of something you did which had a negative impact on system.
You may want to act nice to let everyone know but then you going to degrade your performance.
It's a workplace - get over it. They helped you, you help them when they are in trouble that's how you balance such matters... Not by buying people gifts..
answered Dec 30 '14 at 10:32
NULL
2,65331125
answered Dec 30 '14 at 10:32
NULL
2,65331125
answered Dec 30 '14 at 10:32
NULL
2,65331125
answered Dec 30 '14 at 10:32
NULL
2,65331125
2,65331125
suggest improvements |Â
suggest improvements |Â
up vote
18
down vote
Send a thank you email to each person, and cc their boss as well. Let the leadership know how much you appreciate their help, because that is something that can translate to raises. Bosses need to know when their people go above and beyond.
answered Dec 29 '14 at 16:49
thursdaysgeek
24.1k103998
Taking the group out for lunch as well would be a nice gesture. I don't know anyone who dislikes free food.
– alroc
Dec 29 '14 at 17:02
4
True, but the OP specifically mentioned that lunch was out of his budget.
– thursdaysgeek
Dec 29 '14 at 18:56
1
Expressing your gratitude in person would also go a long way -- in addition to the emails, taking the time and effort to visit each participating colleague at their desk and personally thank them with a smile and a handshake underlines the sincerity of your gratitude (and has no budgetary requirement!).
– Doktor J
Dec 29 '14 at 22:00
1
+1000 for copying their boss on the thanks, or sending thanks to their boss with copy to them. Going beyond requirements to help the company should always help their annual review scores ... at least, if management is sane.
– keshlam
Dec 30 '14 at 5:25
suggest improvements |Â
up vote
18
down vote
Send a thank you email to each person, and cc their boss as well. Let the leadership know how much you appreciate their help, because that is something that can translate to raises. Bosses need to know when their people go above and beyond.
answered Dec 29 '14 at 16:49
thursdaysgeek
24.1k103998
Taking the group out for lunch as well would be a nice gesture. I don't know anyone who dislikes free food.
– alroc
Dec 29 '14 at 17:02
4
True, but the OP specifically mentioned that lunch was out of his budget.
– thursdaysgeek
Dec 29 '14 at 18:56
1
Expressing your gratitude in person would also go a long way -- in addition to the emails, taking the time and effort to visit each participating colleague at their desk and personally thank them with a smile and a handshake underlines the sincerity of your gratitude (and has no budgetary requirement!).
– Doktor J
Dec 29 '14 at 22:00
1
+1000 for copying their boss on the thanks, or sending thanks to their boss with copy to them. Going beyond requirements to help the company should always help their annual review scores ... at least, if management is sane.
– keshlam
Dec 30 '14 at 5:25
suggest improvements |Â
up vote
18
down vote
up vote
18
down vote
Send a thank you email to each person, and cc their boss as well. Let the leadership know how much you appreciate their help, because that is something that can translate to raises. Bosses need to know when their people go above and beyond.
answered Dec 29 '14 at 16:49
thursdaysgeek
24.1k103998
Send a thank you email to each person, and cc their boss as well. Let the leadership know how much you appreciate their help, because that is something that can translate to raises. Bosses need to know when their people go above and beyond.
answered Dec 29 '14 at 16:49
thursdaysgeek
24.1k103998
answered Dec 29 '14 at 16:49
thursdaysgeek
24.1k103998
answered Dec 29 '14 at 16:49
thursdaysgeek
24.1k103998
answered Dec 29 '14 at 16:49
thursdaysgeek
24.1k103998
24.1k103998
Taking the group out for lunch as well would be a nice gesture. I don't know anyone who dislikes free food.
– alroc
Dec 29 '14 at 17:02
4
True, but the OP specifically mentioned that lunch was out of his budget.
– thursdaysgeek
Dec 29 '14 at 18:56
1
Expressing your gratitude in person would also go a long way -- in addition to the emails, taking the time and effort to visit each participating colleague at their desk and personally thank them with a smile and a handshake underlines the sincerity of your gratitude (and has no budgetary requirement!).
– Doktor J
Dec 29 '14 at 22:00
1
+1000 for copying their boss on the thanks, or sending thanks to their boss with copy to them. Going beyond requirements to help the company should always help their annual review scores ... at least, if management is sane.
– keshlam
Dec 30 '14 at 5:25
suggest improvements |Â
Taking the group out for lunch as well would be a nice gesture. I don't know anyone who dislikes free food.
– alroc
Dec 29 '14 at 17:02
4
True, but the OP specifically mentioned that lunch was out of his budget.
– thursdaysgeek
Dec 29 '14 at 18:56
1
Expressing your gratitude in person would also go a long way -- in addition to the emails, taking the time and effort to visit each participating colleague at their desk and personally thank them with a smile and a handshake underlines the sincerity of your gratitude (and has no budgetary requirement!).
– Doktor J
Dec 29 '14 at 22:00
1
+1000 for copying their boss on the thanks, or sending thanks to their boss with copy to them. Going beyond requirements to help the company should always help their annual review scores ... at least, if management is sane.
– keshlam
Dec 30 '14 at 5:25
Taking the group out for lunch as well would be a nice gesture. I don't know anyone who dislikes free food.
– alroc
Dec 29 '14 at 17:02
Taking the group out for lunch as well would be a nice gesture. I don't know anyone who dislikes free food.
– alroc
Dec 29 '14 at 17:02
4
4
True, but the OP specifically mentioned that lunch was out of his budget.
– thursdaysgeek
Dec 29 '14 at 18:56
True, but the OP specifically mentioned that lunch was out of his budget.
– thursdaysgeek
Dec 29 '14 at 18:56
1
1
Expressing your gratitude in person would also go a long way -- in addition to the emails, taking the time and effort to visit each participating colleague at their desk and personally thank them with a smile and a handshake underlines the sincerity of your gratitude (and has no budgetary requirement!).
– Doktor J
Dec 29 '14 at 22:00
Expressing your gratitude in person would also go a long way -- in addition to the emails, taking the time and effort to visit each participating colleague at their desk and personally thank them with a smile and a handshake underlines the sincerity of your gratitude (and has no budgetary requirement!).
– Doktor J
Dec 29 '14 at 22:00
1
1
+1000 for copying their boss on the thanks, or sending thanks to their boss with copy to them. Going beyond requirements to help the company should always help their annual review scores ... at least, if management is sane.
– keshlam
Dec 30 '14 at 5:25
+1000 for copying their boss on the thanks, or sending thanks to their boss with copy to them. Going beyond requirements to help the company should always help their annual review scores ... at least, if management is sane.
– keshlam
Dec 30 '14 at 5:25
suggest improvements |Â
up vote
6
down vote
There are two basic goals you should have in your thanking your peers here.
Getting them the recognition they want/deserve
While by all means it's "their job" to step in when things go to hell, even on holidays, it's still something they should get an extra nod for. Why things happened isn't important here, only that there was a failure and people stepped up and fixed it.
For me, I would take the time to write up a nice email. Ideally you want this email to reach the respective people and their managers. You may want to make sure it's okay to contact their managers through your manager. The email should be very brief. Simply pointing out who you'd like to thank, that there was an outage and despite being on vacation people stepped up to see it fixed.
Expressing your gratitude
Your code blew up in production, it may have been a mistake, or could have been just what was right then was wrong now, regardless these people could have just ignored the issue and left it as "your problem".
They didn't, they rolled up their sleeves and helped you out. Again arguable that's "their job" but again they could have just not answered the phone, or just said "sorry man, I'm no where near a computer to help" (or other excuse)
So you feel both thankful and guilty they had to work during their vacation. You should contact them as individually as practical to give them a personal thank you. If we're talking a dozen or so people contacting them individually would be best, if we're talking like fifty you're probably better off thanking them based on team, etc.
I wouldn't apologize per se, we all make mistakes, but do make a point to thank them for helping you out with the issue despite being on vacation and that you truly appreciate it.
edited Dec 30 '14 at 12:18
BCdotWEB
1153
answered Dec 29 '14 at 21:38
RualStorge
9,5372231
suggest improvements |Â
up vote
6
down vote
There are two basic goals you should have in your thanking your peers here.
Getting them the recognition they want/deserve
While by all means it's "their job" to step in when things go to hell, even on holidays, it's still something they should get an extra nod for. Why things happened isn't important here, only that there was a failure and people stepped up and fixed it.
For me, I would take the time to write up a nice email. Ideally you want this email to reach the respective people and their managers. You may want to make sure it's okay to contact their managers through your manager. The email should be very brief. Simply pointing out who you'd like to thank, that there was an outage and despite being on vacation people stepped up to see it fixed.
Expressing your gratitude
Your code blew up in production, it may have been a mistake, or could have been just what was right then was wrong now, regardless these people could have just ignored the issue and left it as "your problem".
They didn't, they rolled up their sleeves and helped you out. Again arguable that's "their job" but again they could have just not answered the phone, or just said "sorry man, I'm no where near a computer to help" (or other excuse)
So you feel both thankful and guilty they had to work during their vacation. You should contact them as individually as practical to give them a personal thank you. If we're talking a dozen or so people contacting them individually would be best, if we're talking like fifty you're probably better off thanking them based on team, etc.
I wouldn't apologize per se, we all make mistakes, but do make a point to thank them for helping you out with the issue despite being on vacation and that you truly appreciate it.
edited Dec 30 '14 at 12:18
BCdotWEB
1153
answered Dec 29 '14 at 21:38
RualStorge
9,5372231
suggest improvements |Â
up vote
6
down vote
up vote
6
down vote
There are two basic goals you should have in your thanking your peers here.
Getting them the recognition they want/deserve
While by all means it's "their job" to step in when things go to hell, even on holidays, it's still something they should get an extra nod for. Why things happened isn't important here, only that there was a failure and people stepped up and fixed it.
For me, I would take the time to write up a nice email. Ideally you want this email to reach the respective people and their managers. You may want to make sure it's okay to contact their managers through your manager. The email should be very brief. Simply pointing out who you'd like to thank, that there was an outage and despite being on vacation people stepped up to see it fixed.
Expressing your gratitude
Your code blew up in production, it may have been a mistake, or could have been just what was right then was wrong now, regardless these people could have just ignored the issue and left it as "your problem".
They didn't, they rolled up their sleeves and helped you out. Again arguable that's "their job" but again they could have just not answered the phone, or just said "sorry man, I'm no where near a computer to help" (or other excuse)
So you feel both thankful and guilty they had to work during their vacation. You should contact them as individually as practical to give them a personal thank you. If we're talking a dozen or so people contacting them individually would be best, if we're talking like fifty you're probably better off thanking them based on team, etc.
I wouldn't apologize per se, we all make mistakes, but do make a point to thank them for helping you out with the issue despite being on vacation and that you truly appreciate it.
edited Dec 30 '14 at 12:18
BCdotWEB
1153
answered Dec 29 '14 at 21:38
RualStorge
9,5372231
There are two basic goals you should have in your thanking your peers here.
Getting them the recognition they want/deserve
While by all means it's "their job" to step in when things go to hell, even on holidays, it's still something they should get an extra nod for. Why things happened isn't important here, only that there was a failure and people stepped up and fixed it.
For me, I would take the time to write up a nice email. Ideally you want this email to reach the respective people and their managers. You may want to make sure it's okay to contact their managers through your manager. The email should be very brief. Simply pointing out who you'd like to thank, that there was an outage and despite being on vacation people stepped up to see it fixed.
Expressing your gratitude
Your code blew up in production, it may have been a mistake, or could have been just what was right then was wrong now, regardless these people could have just ignored the issue and left it as "your problem".
They didn't, they rolled up their sleeves and helped you out. Again arguable that's "their job" but again they could have just not answered the phone, or just said "sorry man, I'm no where near a computer to help" (or other excuse)
So you feel both thankful and guilty they had to work during their vacation. You should contact them as individually as practical to give them a personal thank you. If we're talking a dozen or so people contacting them individually would be best, if we're talking like fifty you're probably better off thanking them based on team, etc.
I wouldn't apologize per se, we all make mistakes, but do make a point to thank them for helping you out with the issue despite being on vacation and that you truly appreciate it.
edited Dec 30 '14 at 12:18
BCdotWEB
1153
answered Dec 29 '14 at 21:38
RualStorge
9,5372231
edited Dec 30 '14 at 12:18
BCdotWEB
1153
edited Dec 30 '14 at 12:18
BCdotWEB
1153
edited Dec 30 '14 at 12:18
BCdotWEB
1153
1153
answered Dec 29 '14 at 21:38
RualStorge
9,5372231
answered Dec 29 '14 at 21:38
RualStorge
9,5372231
answered Dec 29 '14 at 21:38
RualStorge
9,5372231
9,5372231
suggest improvements |Â
suggest improvements |Â
up vote
2
down vote
I would not go about it as a I messed up and these people helped bail me out.
I don't think you should buy gifts out of your pocket.
I would couch it as a report:
Over the holiday we experienced a critical bug X in production.
The bug originated in Y.
The fix was Z.
Members that contributed include a,b,c, ...
Sorry if I missed anyone
Thank you all for your help
answered Dec 29 '14 at 19:24
paparazzo
33.3k657106
suggest improvements |Â
up vote
2
down vote
I would not go about it as a I messed up and these people helped bail me out.
I don't think you should buy gifts out of your pocket.
I would couch it as a report:
Over the holiday we experienced a critical bug X in production.
The bug originated in Y.
The fix was Z.
Members that contributed include a,b,c, ...
Sorry if I missed anyone
Thank you all for your help
answered Dec 29 '14 at 19:24
paparazzo
33.3k657106
suggest improvements |Â
up vote
2
down vote
up vote
2
down vote
I would not go about it as a I messed up and these people helped bail me out.
I don't think you should buy gifts out of your pocket.
I would couch it as a report:
Over the holiday we experienced a critical bug X in production.
The bug originated in Y.
The fix was Z.
Members that contributed include a,b,c, ...
Sorry if I missed anyone
Thank you all for your help
answered Dec 29 '14 at 19:24
paparazzo
33.3k657106
I would not go about it as a I messed up and these people helped bail me out.
I don't think you should buy gifts out of your pocket.
I would couch it as a report:
Over the holiday we experienced a critical bug X in production.
The bug originated in Y.
The fix was Z.
Members that contributed include a,b,c, ...
Sorry if I missed anyone
Thank you all for your help
answered Dec 29 '14 at 19:24
paparazzo
33.3k657106
answered Dec 29 '14 at 19:24
paparazzo
33.3k657106
answered Dec 29 '14 at 19:24
paparazzo
33.3k657106
answered Dec 29 '14 at 19:24
paparazzo
33.3k657106
33.3k657106
suggest improvements |Â
suggest improvements |Â
2
Shake hands, "Seriously, thanks for all your help this weekend. I really appreciate it."
– Joel Etherton
Dec 29 '14 at 16:25
1
Whats with the random downvotes without comment?
– abelenky
Dec 29 '14 at 16:59
13
Just because you committed the code "years ago" doesn't mean that you should feel like you're the lone person responsible for this happening. That's several years of testing that missed the problem in that code and probably a half-dozen or more other people who overlooked it too. The few programmers who have written anything approaching perfect non-trivial code are named Knuth or built the Space Shuttle
– alroc
Dec 29 '14 at 19:02
3
Chocolate and a "thank you" card would be as far as I'd go - and even then it might be overkill. If everyone who ever committed code with a bug in it brought in chocolate, we'd all be overweight. (Oh, we are all overweight. Huh. Just goes to show... :-). First, don't feel bad - any developer with any length of experience has done this. You fix it, you say "thanks", you move forward. Sometimes, just on a whim, I bring in pastry or something similar. Kind of covers me for this kind of "aw, sh*t!" moment. So...chocolate, pastry, brownies...whatever. :-)
– Bob Jarvis
Dec 29 '14 at 23:51
1
I believe that the company has benefitted from your combined efforts, hence it's up to the company management to show its appreciation of those endeavours. The ball is squarely in management's court and your efforts should be restricted to suggesting to your boss that a practical demonstration of that appreciation would be in order. From their viewpoint, it will also build morale and make personnel happier to repeat the effort in the inevitable future cases of similar problems.
– Magoo
Dec 30 '14 at 3:26