I found out that I made a bug in production after deploying the app, what's the most professional way to handle this? Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar ManaraShould I reveal my mistake after project delivery?Boss decisions are pushing backwards our productProper response after finding out that another team works on the projectBoss yelling at me after asking about seeking a promotion in the future. How to handle this?Did I overstep my bounds by creating a tool “behind my manager's back”, during non-work hours?Discovered a bug that cost the client money. How do we resolve this with the client?
AI positioning circles within an arc at equal distances and heights
Align column where each cell has two decimals with siunitx
My admission is revoked after accepting the admission offer
Why is there a performance penalty for nested subroutines in Delphi?
Is accepting an invalid credit card number a security issue?
Do I need to protect SFP ports and optics from dust/contaminants? If so, how?
What is "leading note" and what does it mean to "raise a note"?
Protagonist's race is hidden - should I reveal it?
Error: Syntax error. Missing ')' for CASE Statement
What if Force was not Mass times Acceleration?
My bank got bought out, am I now going to have to start filing tax returns in a different state?
What's parked in Mil Moscow helicopter plant?
What was Apollo 13's "Little Jolt" after MECO?
What is it called when you ride around on your front wheel?
Could moose/elk survive in the Amazon forest?
Are all CP/M-80 implementations binary compatible?
What do you call the part of a novel that is not dialog?
Why didn't the Space Shuttle bounce back into space many times as possible so that it loose lot of kinetic energy over there?
Will I lose my paid in full property
Is Diceware more secure than a long passphrase?
All ASCII characters with a given bit count
Has a Nobel Peace laureate ever been accused of war crimes?
Multiple fireplaces in an apartment building?
Raising a bilingual kid. When should we introduce the majority language?
I found out that I made a bug in production after deploying the app, what's the most professional way to handle this?
Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar ManaraShould I reveal my mistake after project delivery?Boss decisions are pushing backwards our productProper response after finding out that another team works on the projectBoss yelling at me after asking about seeking a promotion in the future. How to handle this?Did I overstep my bounds by creating a tool “behind my manager's back”, during non-work hours?Discovered a bug that cost the client money. How do we resolve this with the client?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I deployed a very important app (internal business application) last week; over the weekend, I realized that there is a bug in my code but I already deployed the app.
The bug is very trivial and it's completely oversight on my part. The bug is simply missing a null check (don’t laugh at me). I already know how to fix this bug and it would only take me a few minutes to fix it, but there's a whole convoluted process for pushing changes to production at my job. Many people have to sign off on it and the changes need to be re-tested.
Users have not reported the bug. I think I should own up to my mistake and admit that I cause the bug but I'm worried that people will get mad at me. What is the best way to go about this?
software-industry software-development
edited 42 mins ago
Sam Hanley
1,2651316
asked Feb 17 at 2:55
SallySally
383
|
show 3 more comments
I deployed a very important app (internal business application) last week; over the weekend, I realized that there is a bug in my code but I already deployed the app.
The bug is very trivial and it's completely oversight on my part. The bug is simply missing a null check (don’t laugh at me). I already know how to fix this bug and it would only take me a few minutes to fix it, but there's a whole convoluted process for pushing changes to production at my job. Many people have to sign off on it and the changes need to be re-tested.
Users have not reported the bug. I think I should own up to my mistake and admit that I cause the bug but I'm worried that people will get mad at me. What is the best way to go about this?
software-industry software-development
edited 42 mins ago
Sam Hanley
1,2651316
asked Feb 17 at 2:55
SallySally
383
Does your employer have a system or process for submitting bug reports?
– Seth R
Feb 17 at 3:40
Can you edit your quest to clarify: You say the bug is “trivial” but how trivial? Also, what kind of app is this? An app that end users get to download and install on a device like an iPhone or Android device? Or something like a web-based app that can only be accessed via a web browser.
– JakeGould
Feb 17 at 3:44
JakeGould, I have updated my question to include these details. Thank you
– Sally
Feb 17 at 3:59
5
This happens to every programmer, every five minutes - it;'s astonishing it is novel to you, OP ! Obviously you just log it (or whatever) as a bug and start fixing it.
– Fattie
Feb 17 at 14:11
4
"but there's a whole convoluted process for pushing changes to production at my job" that's like saying "we have chairs" or "surprisingly, our office contains Air". Heh!
– Fattie
Feb 17 at 14:11
|
show 3 more comments
I deployed a very important app (internal business application) last week; over the weekend, I realized that there is a bug in my code but I already deployed the app.
The bug is very trivial and it's completely oversight on my part. The bug is simply missing a null check (don’t laugh at me). I already know how to fix this bug and it would only take me a few minutes to fix it, but there's a whole convoluted process for pushing changes to production at my job. Many people have to sign off on it and the changes need to be re-tested.
Users have not reported the bug. I think I should own up to my mistake and admit that I cause the bug but I'm worried that people will get mad at me. What is the best way to go about this?
software-industry software-development
edited 42 mins ago
Sam Hanley
1,2651316
asked Feb 17 at 2:55
SallySally
383
I deployed a very important app (internal business application) last week; over the weekend, I realized that there is a bug in my code but I already deployed the app.
The bug is very trivial and it's completely oversight on my part. The bug is simply missing a null check (don’t laugh at me). I already know how to fix this bug and it would only take me a few minutes to fix it, but there's a whole convoluted process for pushing changes to production at my job. Many people have to sign off on it and the changes need to be re-tested.
Users have not reported the bug. I think I should own up to my mistake and admit that I cause the bug but I'm worried that people will get mad at me. What is the best way to go about this?
software-industry software-development
software-industry software-development
edited 42 mins ago
Sam Hanley
1,2651316
asked Feb 17 at 2:55
SallySally
383
edited 42 mins ago
Sam Hanley
1,2651316
asked Feb 17 at 2:55
SallySally
383
edited 42 mins ago
Sam Hanley
1,2651316
edited 42 mins ago
Sam Hanley
1,2651316
edited 42 mins ago
Sam Hanley
1,2651316
1,2651316
asked Feb 17 at 2:55
SallySally
383
asked Feb 17 at 2:55
SallySally
383
asked Feb 17 at 2:55
SallySally
383
383
Does your employer have a system or process for submitting bug reports?
– Seth R
Feb 17 at 3:40
Can you edit your quest to clarify: You say the bug is “trivial” but how trivial? Also, what kind of app is this? An app that end users get to download and install on a device like an iPhone or Android device? Or something like a web-based app that can only be accessed via a web browser.
– JakeGould
Feb 17 at 3:44
JakeGould, I have updated my question to include these details. Thank you
– Sally
Feb 17 at 3:59
5
This happens to every programmer, every five minutes - it;'s astonishing it is novel to you, OP ! Obviously you just log it (or whatever) as a bug and start fixing it.
– Fattie
Feb 17 at 14:11
4
"but there's a whole convoluted process for pushing changes to production at my job" that's like saying "we have chairs" or "surprisingly, our office contains Air". Heh!
– Fattie
Feb 17 at 14:11
|
show 3 more comments
Does your employer have a system or process for submitting bug reports?
– Seth R
Feb 17 at 3:40
Can you edit your quest to clarify: You say the bug is “trivial” but how trivial? Also, what kind of app is this? An app that end users get to download and install on a device like an iPhone or Android device? Or something like a web-based app that can only be accessed via a web browser.
– JakeGould
Feb 17 at 3:44
JakeGould, I have updated my question to include these details. Thank you
– Sally
Feb 17 at 3:59
5
This happens to every programmer, every five minutes - it;'s astonishing it is novel to you, OP ! Obviously you just log it (or whatever) as a bug and start fixing it.
– Fattie
Feb 17 at 14:11
4
"but there's a whole convoluted process for pushing changes to production at my job" that's like saying "we have chairs" or "surprisingly, our office contains Air". Heh!
– Fattie
Feb 17 at 14:11
Does your employer have a system or process for submitting bug reports?
– Seth R
Feb 17 at 3:40
Does your employer have a system or process for submitting bug reports?
– Seth R
Feb 17 at 3:40
Can you edit your quest to clarify: You say the bug is “trivial” but how trivial? Also, what kind of app is this? An app that end users get to download and install on a device like an iPhone or Android device? Or something like a web-based app that can only be accessed via a web browser.
– JakeGould
Feb 17 at 3:44
Can you edit your quest to clarify: You say the bug is “trivial” but how trivial? Also, what kind of app is this? An app that end users get to download and install on a device like an iPhone or Android device? Or something like a web-based app that can only be accessed via a web browser.
– JakeGould
Feb 17 at 3:44
JakeGould, I have updated my question to include these details. Thank you
– Sally
Feb 17 at 3:59
JakeGould, I have updated my question to include these details. Thank you
– Sally
Feb 17 at 3:59
5
5
This happens to every programmer, every five minutes - it;'s astonishing it is novel to you, OP ! Obviously you just log it (or whatever) as a bug and start fixing it.
– Fattie
Feb 17 at 14:11
This happens to every programmer, every five minutes - it;'s astonishing it is novel to you, OP ! Obviously you just log it (or whatever) as a bug and start fixing it.
– Fattie
Feb 17 at 14:11
4
4
"but there's a whole convoluted process for pushing changes to production at my job" that's like saying "we have chairs" or "surprisingly, our office contains Air". Heh!
– Fattie
Feb 17 at 14:11
"but there's a whole convoluted process for pushing changes to production at my job" that's like saying "we have chairs" or "surprisingly, our office contains Air". Heh!
– Fattie
Feb 17 at 14:11
|
show 3 more comments
4 Answers
4
active
oldest
votes
Report it to your manager. Your manager can decide how to proceed with pushing out the fix. If the bug is somehow more urgent than you realize, your manager will be able to escalate appropriately.
No one (or rather, no reasonable person) is going to get mad at you for making a mistake. Presumably QA and the code reviewers did not catch this bug either, so the blame doesn't lie entirely on you anyway. They will of course be more upset to find that you discovered the bug and didn't tell anyone
answered Feb 17 at 3:36
C_Z_C_Z_
368210
7
"No one is going to get mad at you for making a mistake", that's a bit presumptuous. Don't you think what you mean is: "No one is going to get mad at you, but if they do they don't deserve you in the first place"? ;)
– Sander Verhagen
Feb 17 at 3:39
If there's a chance that someone will get mad at OP for self-reporting a bug, then they'll certainly be much more mad if OP waits for it to have actual customer impact before it gets reported.
– Sam Hanley
Feb 18 at 15:32
+1 - any reasonable manager will accept that people make mistakes, own them, and resolve them. If OP ignores it, a customer finds it, and the response to the manager is, "oh yeah, I saw it, but didn't say anything" ...that can't possibly end well for OP. If the manager doesn't accept that people make mistakes, they're not a good manager :)
– darkside
35 mins ago
add a comment |
It feels like your company's processes are part of the problem. Ideally, if the bug is not causing any actual consequences for your end-users, you should be able to get a fix into the master branch, along with an automated test to verify the fix, and leave it for your managers to decide if it needs an immediate deployment or can be saved for a future release (the latter being more likely if it isn't actually manifesting, or the consequences are no more than an irritation).
However, reading between the lines it sounds like there's a lot of manual testing and no policy of master always being releasable. Would you be in a position to push for practices to change?
answered Feb 17 at 9:54
Julia HaywardJulia Hayward
13.5k73942
add a comment |
I would see if I could trigger the bug in the deploted code. Then try to write a reproducible instruction for doing so.
Once I quickly (less than an hour idealy) did that I would, regardless of success in reproducing, report it either in a bugtracker or to your manager.
answered Feb 17 at 6:41
lijatlijat
1374
add a comment |
Any non-trivial bit of software will have bugs in it. Spotting the bug just after issuing a release is unfortunate, but that's just the way it is.
If your organization has a bug-tracking system, then log it. If it's not affecting users, then it's a low priority bug. It may just sit in the bug-tracker until it gets fixed in the next release.
Don't cover it up, but at the same time, there's no need to make a big song-and-dance about it.
answered Feb 17 at 19:09
Simon BSimon B
3,0162917
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "423"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: false,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f129318%2fi-found-out-that-i-made-a-bug-in-production-after-deploying-the-app-whats-the%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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();
);
);
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Report it to your manager. Your manager can decide how to proceed with pushing out the fix. If the bug is somehow more urgent than you realize, your manager will be able to escalate appropriately.
No one (or rather, no reasonable person) is going to get mad at you for making a mistake. Presumably QA and the code reviewers did not catch this bug either, so the blame doesn't lie entirely on you anyway. They will of course be more upset to find that you discovered the bug and didn't tell anyone
answered Feb 17 at 3:36
C_Z_C_Z_
368210
7
"No one is going to get mad at you for making a mistake", that's a bit presumptuous. Don't you think what you mean is: "No one is going to get mad at you, but if they do they don't deserve you in the first place"? ;)
– Sander Verhagen
Feb 17 at 3:39
If there's a chance that someone will get mad at OP for self-reporting a bug, then they'll certainly be much more mad if OP waits for it to have actual customer impact before it gets reported.
– Sam Hanley
Feb 18 at 15:32
+1 - any reasonable manager will accept that people make mistakes, own them, and resolve them. If OP ignores it, a customer finds it, and the response to the manager is, "oh yeah, I saw it, but didn't say anything" ...that can't possibly end well for OP. If the manager doesn't accept that people make mistakes, they're not a good manager :)
– darkside
35 mins ago
add a comment |
Report it to your manager. Your manager can decide how to proceed with pushing out the fix. If the bug is somehow more urgent than you realize, your manager will be able to escalate appropriately.
No one (or rather, no reasonable person) is going to get mad at you for making a mistake. Presumably QA and the code reviewers did not catch this bug either, so the blame doesn't lie entirely on you anyway. They will of course be more upset to find that you discovered the bug and didn't tell anyone
answered Feb 17 at 3:36
C_Z_C_Z_
368210
7
"No one is going to get mad at you for making a mistake", that's a bit presumptuous. Don't you think what you mean is: "No one is going to get mad at you, but if they do they don't deserve you in the first place"? ;)
– Sander Verhagen
Feb 17 at 3:39
If there's a chance that someone will get mad at OP for self-reporting a bug, then they'll certainly be much more mad if OP waits for it to have actual customer impact before it gets reported.
– Sam Hanley
Feb 18 at 15:32
+1 - any reasonable manager will accept that people make mistakes, own them, and resolve them. If OP ignores it, a customer finds it, and the response to the manager is, "oh yeah, I saw it, but didn't say anything" ...that can't possibly end well for OP. If the manager doesn't accept that people make mistakes, they're not a good manager :)
– darkside
35 mins ago
add a comment |
Report it to your manager. Your manager can decide how to proceed with pushing out the fix. If the bug is somehow more urgent than you realize, your manager will be able to escalate appropriately.
No one (or rather, no reasonable person) is going to get mad at you for making a mistake. Presumably QA and the code reviewers did not catch this bug either, so the blame doesn't lie entirely on you anyway. They will of course be more upset to find that you discovered the bug and didn't tell anyone
answered Feb 17 at 3:36
C_Z_C_Z_
368210
Report it to your manager. Your manager can decide how to proceed with pushing out the fix. If the bug is somehow more urgent than you realize, your manager will be able to escalate appropriately.
No one (or rather, no reasonable person) is going to get mad at you for making a mistake. Presumably QA and the code reviewers did not catch this bug either, so the blame doesn't lie entirely on you anyway. They will of course be more upset to find that you discovered the bug and didn't tell anyone
answered Feb 17 at 3:36
C_Z_C_Z_
368210
edited Feb 17 at 17:26
answered Feb 17 at 3:36
C_Z_C_Z_
368210
answered Feb 17 at 3:36
C_Z_C_Z_
368210
answered Feb 17 at 3:36
C_Z_C_Z_
368210
368210
7
"No one is going to get mad at you for making a mistake", that's a bit presumptuous. Don't you think what you mean is: "No one is going to get mad at you, but if they do they don't deserve you in the first place"? ;)
– Sander Verhagen
Feb 17 at 3:39
If there's a chance that someone will get mad at OP for self-reporting a bug, then they'll certainly be much more mad if OP waits for it to have actual customer impact before it gets reported.
– Sam Hanley
Feb 18 at 15:32
+1 - any reasonable manager will accept that people make mistakes, own them, and resolve them. If OP ignores it, a customer finds it, and the response to the manager is, "oh yeah, I saw it, but didn't say anything" ...that can't possibly end well for OP. If the manager doesn't accept that people make mistakes, they're not a good manager :)
– darkside
35 mins ago
add a comment |
7
"No one is going to get mad at you for making a mistake", that's a bit presumptuous. Don't you think what you mean is: "No one is going to get mad at you, but if they do they don't deserve you in the first place"? ;)
– Sander Verhagen
Feb 17 at 3:39
If there's a chance that someone will get mad at OP for self-reporting a bug, then they'll certainly be much more mad if OP waits for it to have actual customer impact before it gets reported.
– Sam Hanley
Feb 18 at 15:32
+1 - any reasonable manager will accept that people make mistakes, own them, and resolve them. If OP ignores it, a customer finds it, and the response to the manager is, "oh yeah, I saw it, but didn't say anything" ...that can't possibly end well for OP. If the manager doesn't accept that people make mistakes, they're not a good manager :)
– darkside
35 mins ago
7
7
"No one is going to get mad at you for making a mistake", that's a bit presumptuous. Don't you think what you mean is: "No one is going to get mad at you, but if they do they don't deserve you in the first place"? ;)
– Sander Verhagen
Feb 17 at 3:39
"No one is going to get mad at you for making a mistake", that's a bit presumptuous. Don't you think what you mean is: "No one is going to get mad at you, but if they do they don't deserve you in the first place"? ;)
– Sander Verhagen
Feb 17 at 3:39
If there's a chance that someone will get mad at OP for self-reporting a bug, then they'll certainly be much more mad if OP waits for it to have actual customer impact before it gets reported.
– Sam Hanley
Feb 18 at 15:32
If there's a chance that someone will get mad at OP for self-reporting a bug, then they'll certainly be much more mad if OP waits for it to have actual customer impact before it gets reported.
– Sam Hanley
Feb 18 at 15:32
+1 - any reasonable manager will accept that people make mistakes, own them, and resolve them. If OP ignores it, a customer finds it, and the response to the manager is, "oh yeah, I saw it, but didn't say anything" ...that can't possibly end well for OP. If the manager doesn't accept that people make mistakes, they're not a good manager :)
– darkside
35 mins ago
+1 - any reasonable manager will accept that people make mistakes, own them, and resolve them. If OP ignores it, a customer finds it, and the response to the manager is, "oh yeah, I saw it, but didn't say anything" ...that can't possibly end well for OP. If the manager doesn't accept that people make mistakes, they're not a good manager :)
– darkside
35 mins ago
add a comment |
It feels like your company's processes are part of the problem. Ideally, if the bug is not causing any actual consequences for your end-users, you should be able to get a fix into the master branch, along with an automated test to verify the fix, and leave it for your managers to decide if it needs an immediate deployment or can be saved for a future release (the latter being more likely if it isn't actually manifesting, or the consequences are no more than an irritation).
However, reading between the lines it sounds like there's a lot of manual testing and no policy of master always being releasable. Would you be in a position to push for practices to change?
answered Feb 17 at 9:54
Julia HaywardJulia Hayward
13.5k73942
add a comment |
It feels like your company's processes are part of the problem. Ideally, if the bug is not causing any actual consequences for your end-users, you should be able to get a fix into the master branch, along with an automated test to verify the fix, and leave it for your managers to decide if it needs an immediate deployment or can be saved for a future release (the latter being more likely if it isn't actually manifesting, or the consequences are no more than an irritation).
However, reading between the lines it sounds like there's a lot of manual testing and no policy of master always being releasable. Would you be in a position to push for practices to change?
answered Feb 17 at 9:54
Julia HaywardJulia Hayward
13.5k73942
add a comment |
It feels like your company's processes are part of the problem. Ideally, if the bug is not causing any actual consequences for your end-users, you should be able to get a fix into the master branch, along with an automated test to verify the fix, and leave it for your managers to decide if it needs an immediate deployment or can be saved for a future release (the latter being more likely if it isn't actually manifesting, or the consequences are no more than an irritation).
However, reading between the lines it sounds like there's a lot of manual testing and no policy of master always being releasable. Would you be in a position to push for practices to change?
answered Feb 17 at 9:54
Julia HaywardJulia Hayward
13.5k73942
It feels like your company's processes are part of the problem. Ideally, if the bug is not causing any actual consequences for your end-users, you should be able to get a fix into the master branch, along with an automated test to verify the fix, and leave it for your managers to decide if it needs an immediate deployment or can be saved for a future release (the latter being more likely if it isn't actually manifesting, or the consequences are no more than an irritation).
However, reading between the lines it sounds like there's a lot of manual testing and no policy of master always being releasable. Would you be in a position to push for practices to change?
answered Feb 17 at 9:54
Julia HaywardJulia Hayward
13.5k73942
answered Feb 17 at 9:54
Julia HaywardJulia Hayward
13.5k73942
answered Feb 17 at 9:54
Julia HaywardJulia Hayward
13.5k73942
answered Feb 17 at 9:54
Julia HaywardJulia Hayward
13.5k73942
13.5k73942
add a comment |
add a comment |
I would see if I could trigger the bug in the deploted code. Then try to write a reproducible instruction for doing so.
Once I quickly (less than an hour idealy) did that I would, regardless of success in reproducing, report it either in a bugtracker or to your manager.
answered Feb 17 at 6:41
lijatlijat
1374
add a comment |
I would see if I could trigger the bug in the deploted code. Then try to write a reproducible instruction for doing so.
Once I quickly (less than an hour idealy) did that I would, regardless of success in reproducing, report it either in a bugtracker or to your manager.
answered Feb 17 at 6:41
lijatlijat
1374
add a comment |
I would see if I could trigger the bug in the deploted code. Then try to write a reproducible instruction for doing so.
Once I quickly (less than an hour idealy) did that I would, regardless of success in reproducing, report it either in a bugtracker or to your manager.
answered Feb 17 at 6:41
lijatlijat
1374
I would see if I could trigger the bug in the deploted code. Then try to write a reproducible instruction for doing so.
Once I quickly (less than an hour idealy) did that I would, regardless of success in reproducing, report it either in a bugtracker or to your manager.
answered Feb 17 at 6:41
lijatlijat
1374
answered Feb 17 at 6:41
lijatlijat
1374
answered Feb 17 at 6:41
lijatlijat
1374
answered Feb 17 at 6:41
lijatlijat
1374
1374
add a comment |
add a comment |
Any non-trivial bit of software will have bugs in it. Spotting the bug just after issuing a release is unfortunate, but that's just the way it is.
If your organization has a bug-tracking system, then log it. If it's not affecting users, then it's a low priority bug. It may just sit in the bug-tracker until it gets fixed in the next release.
Don't cover it up, but at the same time, there's no need to make a big song-and-dance about it.
answered Feb 17 at 19:09
Simon BSimon B
3,0162917
add a comment |
Any non-trivial bit of software will have bugs in it. Spotting the bug just after issuing a release is unfortunate, but that's just the way it is.
If your organization has a bug-tracking system, then log it. If it's not affecting users, then it's a low priority bug. It may just sit in the bug-tracker until it gets fixed in the next release.
Don't cover it up, but at the same time, there's no need to make a big song-and-dance about it.
answered Feb 17 at 19:09
Simon BSimon B
3,0162917
add a comment |
Any non-trivial bit of software will have bugs in it. Spotting the bug just after issuing a release is unfortunate, but that's just the way it is.
If your organization has a bug-tracking system, then log it. If it's not affecting users, then it's a low priority bug. It may just sit in the bug-tracker until it gets fixed in the next release.
Don't cover it up, but at the same time, there's no need to make a big song-and-dance about it.
answered Feb 17 at 19:09
Simon BSimon B
3,0162917
Any non-trivial bit of software will have bugs in it. Spotting the bug just after issuing a release is unfortunate, but that's just the way it is.
If your organization has a bug-tracking system, then log it. If it's not affecting users, then it's a low priority bug. It may just sit in the bug-tracker until it gets fixed in the next release.
Don't cover it up, but at the same time, there's no need to make a big song-and-dance about it.
answered Feb 17 at 19:09
Simon BSimon B
3,0162917
answered Feb 17 at 19:09
Simon BSimon B
3,0162917
answered Feb 17 at 19:09
Simon BSimon B
3,0162917
answered Feb 17 at 19:09
Simon BSimon B
3,0162917
3,0162917
add a comment |
add a comment |
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f129318%2fi-found-out-that-i-made-a-bug-in-production-after-deploying-the-app-whats-the%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Does your employer have a system or process for submitting bug reports?
– Seth R
Feb 17 at 3:40
Can you edit your quest to clarify: You say the bug is “trivial” but how trivial? Also, what kind of app is this? An app that end users get to download and install on a device like an iPhone or Android device? Or something like a web-based app that can only be accessed via a web browser.
– JakeGould
Feb 17 at 3:44
JakeGould, I have updated my question to include these details. Thank you
– Sally
Feb 17 at 3:59
5
This happens to every programmer, every five minutes - it;'s astonishing it is novel to you, OP ! Obviously you just log it (or whatever) as a bug and start fixing it.
– Fattie
Feb 17 at 14:11
4
"but there's a whole convoluted process for pushing changes to production at my job" that's like saying "we have chairs" or "surprisingly, our office contains Air". Heh!
– Fattie
Feb 17 at 14:11