Multiple documentation issues in a single bug
It is clearly a bad practice to incorporate several issues in a single bug. It is not convenient, hard to maintain, difficult to keep track of what is done and what is not, etc.
Multiple documentation issues in a single bug
It is clearly a bad practice to incorporate several issues in a single bug. It is not convenient, hard to maintain, difficult to keep track of what is done and what is not, etc.
Multiple documentation issues in a single bug
It is clearly a bad practice to incorporate several issues in a single bug. It is not convenient, hard to maintain, difficult to keep track of what is done and what is not, etc.
Multiple documentation issues in a single bug
It is clearly a bad practice to incorporate several issues in a single bug. It is not convenient, hard to maintain, difficult to keep track of what is done and what is not, etc.
I am making 4-5x more story points than average, but producing bugs at half the rate. Graphs say it’s 2x more bugs, how to deal with that?
So it is generally accepted that top tier programmers can produce an order of magnitude more/better code than their more average peers.
I am making 4-5x more story points than average, but producing bugs at half the rate. Graphs say it’s 2x more bugs, how to deal with that?
So it is generally accepted that top tier programmers can produce an order of magnitude more/better code than their more average peers.
Theoretically bug-free programs
I have read lot of articles which state that code can’t be bug-free, and they are talking about these theorems:
What does “trivial” mean? [duplicate]
This question already has answers here: How to differentiate between trivial and non-trivial software? [closed] (10 answers) Closed 9 years ago. You often see statements like “all non-trivial software has bugs” or “all non-trivial abstractions are leaky”. But what makes a program “trivial” instead of non-trivial? Where is the cut-off line at which we can […]
What does “trivial” mean? [duplicate]
This question already has answers here: How to differentiate between trivial and non-trivial software? [closed] (10 answers) Closed 9 years ago. You often see statements like “all non-trivial software has bugs” or “all non-trivial abstractions are leaky”. But what makes a program “trivial” instead of non-trivial? Where is the cut-off line at which we can […]
Customer is “deeply disappointed” in our software because of one bug. How to reply? [duplicate]
This question already has answers here: How do you respond to: “Ever since the update…” questions from clients? [closed] (7 answers) Getting users to write decent and useful bug reports (6 answers) Closed 9 years ago. We have been building custom software for one of our customer for a few years now. Everything is going […]