Mixing
How can I politely reply when I made a mistake because of my bad assumption? [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
0
down vote
favorite
1
I am a Software Engineer. Today, I received a mail from my senior with my boss in cc, stating that I have made a mistake in some work done a long time ago.
It is effected and found on my Project Production now. They gave me some serious warnings in the mail.
Now, I should reply to them, recognizing my mistake but I want to minimize it so that it doesn't affect me too badly.
How can this be done?
professionalism communication email manager
asked Feb 17 '16 at 5:49
Dot Net Developer
10616
closed as off-topic by Dawny33, Lilienthal♦, IDrinkandIKnowThings, Chris E, user8365 Feb 17 '16 at 19:04
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." – Dawny33, Lilienthal, IDrinkandIKnowThings, Chris E, Community
 |Â
show 4 more comments
up vote
0
down vote
favorite
1
I am a Software Engineer. Today, I received a mail from my senior with my boss in cc, stating that I have made a mistake in some work done a long time ago.
It is effected and found on my Project Production now. They gave me some serious warnings in the mail.
Now, I should reply to them, recognizing my mistake but I want to minimize it so that it doesn't affect me too badly.
How can this be done?
professionalism communication email manager
asked Feb 17 '16 at 5:49
Dot Net Developer
10616
closed as off-topic by Dawny33, Lilienthal♦, IDrinkandIKnowThings, Chris E, user8365 Feb 17 '16 at 19:04
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." – Dawny33, Lilienthal, IDrinkandIKnowThings, Chris E, Community
I do not understand to whom you should write to? The customer or your boss?
– Bougret
Feb 17 '16 at 5:51
To my senior and my boss.. @Bougret
– Dot Net Developer
Feb 17 '16 at 5:52
What is done is done. Your reply is not going to change much. Heed the warning in the email.
– paparazzo
Feb 17 '16 at 6:55
You can apologise and either add that your code wasn't reviewed by anyone (which would be the standard procedure and should have caught the problem), which makes it a management problem, or you should add that the code was reviewed by XYZ, which is where the problem should have been found.
– gnasher729
Feb 17 '16 at 9:02
2
@gnasher729 I would not start trying to spread the blame. Unless a formal investigation is undertaken by the company just say nothing and move on. Taking heed of whatever the unspecified warnings are.
– Loofer
Feb 17 '16 at 10:48
 |Â
show 4 more comments
up vote
0
down vote
favorite
1
up vote
0
down vote
favorite
1
1
I am a Software Engineer. Today, I received a mail from my senior with my boss in cc, stating that I have made a mistake in some work done a long time ago.
It is effected and found on my Project Production now. They gave me some serious warnings in the mail.
Now, I should reply to them, recognizing my mistake but I want to minimize it so that it doesn't affect me too badly.
How can this be done?
professionalism communication email manager
asked Feb 17 '16 at 5:49
Dot Net Developer
10616
I am a Software Engineer. Today, I received a mail from my senior with my boss in cc, stating that I have made a mistake in some work done a long time ago.
It is effected and found on my Project Production now. They gave me some serious warnings in the mail.
Now, I should reply to them, recognizing my mistake but I want to minimize it so that it doesn't affect me too badly.
How can this be done?
professionalism communication email manager
asked Feb 17 '16 at 5:49
Dot Net Developer
10616
edited Feb 17 '16 at 9:56
user29055
asked Feb 17 '16 at 5:49
Dot Net Developer
10616
asked Feb 17 '16 at 5:49
Dot Net Developer
10616
asked Feb 17 '16 at 5:49
Dot Net Developer
10616
10616
closed as off-topic by Dawny33, Lilienthal♦, IDrinkandIKnowThings, Chris E, user8365 Feb 17 '16 at 19:04
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." – Dawny33, Lilienthal, IDrinkandIKnowThings, Chris E, Community
closed as off-topic by Dawny33, Lilienthal♦, IDrinkandIKnowThings, Chris E, user8365 Feb 17 '16 at 19:04
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." – Dawny33, Lilienthal, IDrinkandIKnowThings, Chris E, Community
I do not understand to whom you should write to? The customer or your boss?
– Bougret
Feb 17 '16 at 5:51
To my senior and my boss.. @Bougret
– Dot Net Developer
Feb 17 '16 at 5:52
What is done is done. Your reply is not going to change much. Heed the warning in the email.
– paparazzo
Feb 17 '16 at 6:55
You can apologise and either add that your code wasn't reviewed by anyone (which would be the standard procedure and should have caught the problem), which makes it a management problem, or you should add that the code was reviewed by XYZ, which is where the problem should have been found.
– gnasher729
Feb 17 '16 at 9:02
2
@gnasher729 I would not start trying to spread the blame. Unless a formal investigation is undertaken by the company just say nothing and move on. Taking heed of whatever the unspecified warnings are.
– Loofer
Feb 17 '16 at 10:48
 |Â
show 4 more comments
I do not understand to whom you should write to? The customer or your boss?
– Bougret
Feb 17 '16 at 5:51
To my senior and my boss.. @Bougret
– Dot Net Developer
Feb 17 '16 at 5:52
What is done is done. Your reply is not going to change much. Heed the warning in the email.
– paparazzo
Feb 17 '16 at 6:55
You can apologise and either add that your code wasn't reviewed by anyone (which would be the standard procedure and should have caught the problem), which makes it a management problem, or you should add that the code was reviewed by XYZ, which is where the problem should have been found.
– gnasher729
Feb 17 '16 at 9:02
2
@gnasher729 I would not start trying to spread the blame. Unless a formal investigation is undertaken by the company just say nothing and move on. Taking heed of whatever the unspecified warnings are.
– Loofer
Feb 17 '16 at 10:48
I do not understand to whom you should write to? The customer or your boss?
– Bougret
Feb 17 '16 at 5:51
I do not understand to whom you should write to? The customer or your boss?
– Bougret
Feb 17 '16 at 5:51
To my senior and my boss.. @Bougret
– Dot Net Developer
Feb 17 '16 at 5:52
To my senior and my boss.. @Bougret
– Dot Net Developer
Feb 17 '16 at 5:52
What is done is done. Your reply is not going to change much. Heed the warning in the email.
– paparazzo
Feb 17 '16 at 6:55
What is done is done. Your reply is not going to change much. Heed the warning in the email.
– paparazzo
Feb 17 '16 at 6:55
You can apologise and either add that your code wasn't reviewed by anyone (which would be the standard procedure and should have caught the problem), which makes it a management problem, or you should add that the code was reviewed by XYZ, which is where the problem should have been found.
– gnasher729
Feb 17 '16 at 9:02
You can apologise and either add that your code wasn't reviewed by anyone (which would be the standard procedure and should have caught the problem), which makes it a management problem, or you should add that the code was reviewed by XYZ, which is where the problem should have been found.
– gnasher729
Feb 17 '16 at 9:02
2
2
@gnasher729 I would not start trying to spread the blame. Unless a formal investigation is undertaken by the company just say nothing and move on. Taking heed of whatever the unspecified warnings are.
– Loofer
Feb 17 '16 at 10:48
@gnasher729 I would not start trying to spread the blame. Unless a formal investigation is undertaken by the company just say nothing and move on. Taking heed of whatever the unspecified warnings are.
– Loofer
Feb 17 '16 at 10:48
 |Â
show 4 more comments
3 Answers
3
active
oldest
votes
up vote
4
down vote
accepted
This happened to me, and what I did was this.
- Apologized for what I did wrong. (Acknowledges the mistake)
- Describe the mistake I made and where where I went wrong. (shows you understand the mistake)
- Describe what I should have done(Shows that you have learned from your mistake)
- Describe how I would ensure that it would not happen again (shows you're committed)
always take that approach.
edited Feb 17 '16 at 14:19
mhoran_psprep
40.1k461143
answered Feb 17 '16 at 14:09
Richard U
77.5k56201308
suggest improvements |Â
up vote
7
down vote
First, you should apologize as it is your mistake.
If your code reviewed by your boss or another employee but the mistake was not seen, you can minimize the error visibility but do not share explicitly the blame.
Explain the reasons of your mistake
Explain how to fix it
Explain what you should have done to avoid it
You want to show that you learned from this error.
edited Feb 17 '16 at 11:02
Jane S♦
40.8k17125159
answered Feb 17 '16 at 6:11
Bougret
48128
As I already mentioned in my question, he is my senior from my team.
– Dot Net Developer
Feb 17 '16 at 6:13
I mean, you got into trouble because the code went live, isn't it?
– Bougret
Feb 17 '16 at 6:16
2
If it was only your error, and if it was caught in the standard reviewing procedure of your company, there is little else to do other than take the blame, alone. Of course say you will be more careful, try to explain the reason of your mistakes and how you could have done to mitigate it. It will show you are learning from mistakes.
– Bougret
Feb 17 '16 at 6:31
1
@DotNetDeveloper "can you please suggest more?" - Propose an improvement that will help you and others to find this kind of mistake in the future? E.g. better review, better testing procedures. Make a specific proposal though. We're human, anyone could make mistakes, even your seniors.
– Brandin
Feb 17 '16 at 8:53
1
Everyone makes mistakes, and by personally working on a project, sometimes we miss the mistakes due to being to close to it. This is why there are code reviews and extensive testing; problems are not wanted, but they happen, the important thing is learning from them. As the other guys have said here, you should chalk this up to experience, apologise and learn from it.
– nickson104
Feb 17 '16 at 9:56
 |Â
show 1 more comment
up vote
0
down vote
Just send back a short reply along the lines of 'Noted' and leave it at that, don't make it any bigger than it already is. You can't turn back time, all you can do is move forwards.
answered Feb 17 '16 at 10:50
Kilisi
94.6k50216376
suggest improvements |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
accepted
This happened to me, and what I did was this.
- Apologized for what I did wrong. (Acknowledges the mistake)
- Describe the mistake I made and where where I went wrong. (shows you understand the mistake)
- Describe what I should have done(Shows that you have learned from your mistake)
- Describe how I would ensure that it would not happen again (shows you're committed)
always take that approach.
edited Feb 17 '16 at 14:19
mhoran_psprep
40.1k461143
answered Feb 17 '16 at 14:09
Richard U
77.5k56201308
suggest improvements |Â
up vote
4
down vote
accepted
This happened to me, and what I did was this.
- Apologized for what I did wrong. (Acknowledges the mistake)
- Describe the mistake I made and where where I went wrong. (shows you understand the mistake)
- Describe what I should have done(Shows that you have learned from your mistake)
- Describe how I would ensure that it would not happen again (shows you're committed)
always take that approach.
edited Feb 17 '16 at 14:19
mhoran_psprep
40.1k461143
answered Feb 17 '16 at 14:09
Richard U
77.5k56201308
suggest improvements |Â
up vote
4
down vote
accepted
up vote
4
down vote
accepted
This happened to me, and what I did was this.
- Apologized for what I did wrong. (Acknowledges the mistake)
- Describe the mistake I made and where where I went wrong. (shows you understand the mistake)
- Describe what I should have done(Shows that you have learned from your mistake)
- Describe how I would ensure that it would not happen again (shows you're committed)
always take that approach.
edited Feb 17 '16 at 14:19
mhoran_psprep
40.1k461143
answered Feb 17 '16 at 14:09
Richard U
77.5k56201308
This happened to me, and what I did was this.
- Apologized for what I did wrong. (Acknowledges the mistake)
- Describe the mistake I made and where where I went wrong. (shows you understand the mistake)
- Describe what I should have done(Shows that you have learned from your mistake)
- Describe how I would ensure that it would not happen again (shows you're committed)
always take that approach.
edited Feb 17 '16 at 14:19
mhoran_psprep
40.1k461143
answered Feb 17 '16 at 14:09
Richard U
77.5k56201308
edited Feb 17 '16 at 14:19
mhoran_psprep
40.1k461143
edited Feb 17 '16 at 14:19
mhoran_psprep
40.1k461143
edited Feb 17 '16 at 14:19
mhoran_psprep
40.1k461143
40.1k461143
answered Feb 17 '16 at 14:09
Richard U
77.5k56201308
answered Feb 17 '16 at 14:09
Richard U
77.5k56201308
answered Feb 17 '16 at 14:09
Richard U
77.5k56201308
77.5k56201308
suggest improvements |Â
suggest improvements |Â
up vote
7
down vote
First, you should apologize as it is your mistake.
If your code reviewed by your boss or another employee but the mistake was not seen, you can minimize the error visibility but do not share explicitly the blame.
Explain the reasons of your mistake
Explain how to fix it
Explain what you should have done to avoid it
You want to show that you learned from this error.
edited Feb 17 '16 at 11:02
Jane S♦
40.8k17125159
answered Feb 17 '16 at 6:11
Bougret
48128
As I already mentioned in my question, he is my senior from my team.
– Dot Net Developer
Feb 17 '16 at 6:13
I mean, you got into trouble because the code went live, isn't it?
– Bougret
Feb 17 '16 at 6:16
2
If it was only your error, and if it was caught in the standard reviewing procedure of your company, there is little else to do other than take the blame, alone. Of course say you will be more careful, try to explain the reason of your mistakes and how you could have done to mitigate it. It will show you are learning from mistakes.
– Bougret
Feb 17 '16 at 6:31
1
@DotNetDeveloper "can you please suggest more?" - Propose an improvement that will help you and others to find this kind of mistake in the future? E.g. better review, better testing procedures. Make a specific proposal though. We're human, anyone could make mistakes, even your seniors.
– Brandin
Feb 17 '16 at 8:53
1
Everyone makes mistakes, and by personally working on a project, sometimes we miss the mistakes due to being to close to it. This is why there are code reviews and extensive testing; problems are not wanted, but they happen, the important thing is learning from them. As the other guys have said here, you should chalk this up to experience, apologise and learn from it.
– nickson104
Feb 17 '16 at 9:56
 |Â
show 1 more comment
up vote
7
down vote
First, you should apologize as it is your mistake.
If your code reviewed by your boss or another employee but the mistake was not seen, you can minimize the error visibility but do not share explicitly the blame.
Explain the reasons of your mistake
Explain how to fix it
Explain what you should have done to avoid it
You want to show that you learned from this error.
edited Feb 17 '16 at 11:02
Jane S♦
40.8k17125159
answered Feb 17 '16 at 6:11
Bougret
48128
As I already mentioned in my question, he is my senior from my team.
– Dot Net Developer
Feb 17 '16 at 6:13
I mean, you got into trouble because the code went live, isn't it?
– Bougret
Feb 17 '16 at 6:16
2
If it was only your error, and if it was caught in the standard reviewing procedure of your company, there is little else to do other than take the blame, alone. Of course say you will be more careful, try to explain the reason of your mistakes and how you could have done to mitigate it. It will show you are learning from mistakes.
– Bougret
Feb 17 '16 at 6:31
1
@DotNetDeveloper "can you please suggest more?" - Propose an improvement that will help you and others to find this kind of mistake in the future? E.g. better review, better testing procedures. Make a specific proposal though. We're human, anyone could make mistakes, even your seniors.
– Brandin
Feb 17 '16 at 8:53
1
Everyone makes mistakes, and by personally working on a project, sometimes we miss the mistakes due to being to close to it. This is why there are code reviews and extensive testing; problems are not wanted, but they happen, the important thing is learning from them. As the other guys have said here, you should chalk this up to experience, apologise and learn from it.
– nickson104
Feb 17 '16 at 9:56
 |Â
show 1 more comment
up vote
7
down vote
up vote
7
down vote
First, you should apologize as it is your mistake.
If your code reviewed by your boss or another employee but the mistake was not seen, you can minimize the error visibility but do not share explicitly the blame.
Explain the reasons of your mistake
Explain how to fix it
Explain what you should have done to avoid it
You want to show that you learned from this error.
edited Feb 17 '16 at 11:02
Jane S♦
40.8k17125159
answered Feb 17 '16 at 6:11
Bougret
48128
First, you should apologize as it is your mistake.
If your code reviewed by your boss or another employee but the mistake was not seen, you can minimize the error visibility but do not share explicitly the blame.
Explain the reasons of your mistake
Explain how to fix it
Explain what you should have done to avoid it
You want to show that you learned from this error.
edited Feb 17 '16 at 11:02
Jane S♦
40.8k17125159
answered Feb 17 '16 at 6:11
Bougret
48128
edited Feb 17 '16 at 11:02
Jane S♦
40.8k17125159
edited Feb 17 '16 at 11:02
Jane S♦
40.8k17125159
edited Feb 17 '16 at 11:02
Jane S♦
40.8k17125159
40.8k17125159
answered Feb 17 '16 at 6:11
Bougret
48128
answered Feb 17 '16 at 6:11
Bougret
48128
answered Feb 17 '16 at 6:11
Bougret
48128
48128
As I already mentioned in my question, he is my senior from my team.
– Dot Net Developer
Feb 17 '16 at 6:13
I mean, you got into trouble because the code went live, isn't it?
– Bougret
Feb 17 '16 at 6:16
2
If it was only your error, and if it was caught in the standard reviewing procedure of your company, there is little else to do other than take the blame, alone. Of course say you will be more careful, try to explain the reason of your mistakes and how you could have done to mitigate it. It will show you are learning from mistakes.
– Bougret
Feb 17 '16 at 6:31
1
@DotNetDeveloper "can you please suggest more?" - Propose an improvement that will help you and others to find this kind of mistake in the future? E.g. better review, better testing procedures. Make a specific proposal though. We're human, anyone could make mistakes, even your seniors.
– Brandin
Feb 17 '16 at 8:53
1
Everyone makes mistakes, and by personally working on a project, sometimes we miss the mistakes due to being to close to it. This is why there are code reviews and extensive testing; problems are not wanted, but they happen, the important thing is learning from them. As the other guys have said here, you should chalk this up to experience, apologise and learn from it.
– nickson104
Feb 17 '16 at 9:56
 |Â
show 1 more comment
As I already mentioned in my question, he is my senior from my team.
– Dot Net Developer
Feb 17 '16 at 6:13
I mean, you got into trouble because the code went live, isn't it?
– Bougret
Feb 17 '16 at 6:16
2
If it was only your error, and if it was caught in the standard reviewing procedure of your company, there is little else to do other than take the blame, alone. Of course say you will be more careful, try to explain the reason of your mistakes and how you could have done to mitigate it. It will show you are learning from mistakes.
– Bougret
Feb 17 '16 at 6:31
1
@DotNetDeveloper "can you please suggest more?" - Propose an improvement that will help you and others to find this kind of mistake in the future? E.g. better review, better testing procedures. Make a specific proposal though. We're human, anyone could make mistakes, even your seniors.
– Brandin
Feb 17 '16 at 8:53
1
Everyone makes mistakes, and by personally working on a project, sometimes we miss the mistakes due to being to close to it. This is why there are code reviews and extensive testing; problems are not wanted, but they happen, the important thing is learning from them. As the other guys have said here, you should chalk this up to experience, apologise and learn from it.
– nickson104
Feb 17 '16 at 9:56
As I already mentioned in my question, he is my senior from my team.
– Dot Net Developer
Feb 17 '16 at 6:13
As I already mentioned in my question, he is my senior from my team.
– Dot Net Developer
Feb 17 '16 at 6:13
I mean, you got into trouble because the code went live, isn't it?
– Bougret
Feb 17 '16 at 6:16
I mean, you got into trouble because the code went live, isn't it?
– Bougret
Feb 17 '16 at 6:16
2
2
If it was only your error, and if it was caught in the standard reviewing procedure of your company, there is little else to do other than take the blame, alone. Of course say you will be more careful, try to explain the reason of your mistakes and how you could have done to mitigate it. It will show you are learning from mistakes.
– Bougret
Feb 17 '16 at 6:31
If it was only your error, and if it was caught in the standard reviewing procedure of your company, there is little else to do other than take the blame, alone. Of course say you will be more careful, try to explain the reason of your mistakes and how you could have done to mitigate it. It will show you are learning from mistakes.
– Bougret
Feb 17 '16 at 6:31
1
1
@DotNetDeveloper "can you please suggest more?" - Propose an improvement that will help you and others to find this kind of mistake in the future? E.g. better review, better testing procedures. Make a specific proposal though. We're human, anyone could make mistakes, even your seniors.
– Brandin
Feb 17 '16 at 8:53
@DotNetDeveloper "can you please suggest more?" - Propose an improvement that will help you and others to find this kind of mistake in the future? E.g. better review, better testing procedures. Make a specific proposal though. We're human, anyone could make mistakes, even your seniors.
– Brandin
Feb 17 '16 at 8:53
1
1
Everyone makes mistakes, and by personally working on a project, sometimes we miss the mistakes due to being to close to it. This is why there are code reviews and extensive testing; problems are not wanted, but they happen, the important thing is learning from them. As the other guys have said here, you should chalk this up to experience, apologise and learn from it.
– nickson104
Feb 17 '16 at 9:56
Everyone makes mistakes, and by personally working on a project, sometimes we miss the mistakes due to being to close to it. This is why there are code reviews and extensive testing; problems are not wanted, but they happen, the important thing is learning from them. As the other guys have said here, you should chalk this up to experience, apologise and learn from it.
– nickson104
Feb 17 '16 at 9:56
 |Â
show 1 more comment
up vote
0
down vote
Just send back a short reply along the lines of 'Noted' and leave it at that, don't make it any bigger than it already is. You can't turn back time, all you can do is move forwards.
answered Feb 17 '16 at 10:50
Kilisi
94.6k50216376
suggest improvements |Â
up vote
0
down vote
Just send back a short reply along the lines of 'Noted' and leave it at that, don't make it any bigger than it already is. You can't turn back time, all you can do is move forwards.
answered Feb 17 '16 at 10:50
Kilisi
94.6k50216376
suggest improvements |Â
up vote
0
down vote
up vote
0
down vote
Just send back a short reply along the lines of 'Noted' and leave it at that, don't make it any bigger than it already is. You can't turn back time, all you can do is move forwards.
answered Feb 17 '16 at 10:50
Kilisi
94.6k50216376
Just send back a short reply along the lines of 'Noted' and leave it at that, don't make it any bigger than it already is. You can't turn back time, all you can do is move forwards.
answered Feb 17 '16 at 10:50
Kilisi
94.6k50216376
answered Feb 17 '16 at 10:50
Kilisi
94.6k50216376
answered Feb 17 '16 at 10:50
Kilisi
94.6k50216376
answered Feb 17 '16 at 10:50
Kilisi
94.6k50216376
94.6k50216376
suggest improvements |Â
suggest improvements |Â
I do not understand to whom you should write to? The customer or your boss?
– Bougret
Feb 17 '16 at 5:51
To my senior and my boss.. @Bougret
– Dot Net Developer
Feb 17 '16 at 5:52
What is done is done. Your reply is not going to change much. Heed the warning in the email.
– paparazzo
Feb 17 '16 at 6:55
You can apologise and either add that your code wasn't reviewed by anyone (which would be the standard procedure and should have caught the problem), which makes it a management problem, or you should add that the code was reviewed by XYZ, which is where the problem should have been found.
– gnasher729
Feb 17 '16 at 9:02
2
@gnasher729 I would not start trying to spread the blame. Unless a formal investigation is undertaken by the company just say nothing and move on. Taking heed of whatever the unspecified warnings are.
– Loofer
Feb 17 '16 at 10:48