After years of working alone, other developers will finally see my (buggy) code. What should I do? [duplicate]
This question already has answers here: How would you react if someone told you your code is a mess? (21 answers) Closed 10 years ago. I have been working on a system alone for about four years. I have built it from the ground up. It is not a perfect system. It is very complex, […]
After years of working alone, other developers will finally see my (buggy) code. What should I do? [duplicate]
This question already has answers here: How would you react if someone told you your code is a mess? (21 answers) Closed 10 years ago. I have been working on a system alone for about four years. I have built it from the ground up. It is not a perfect system. It is very complex, […]
After years of working alone, other developers will finally see my (buggy) code. What should I do? [duplicate]
This question already has answers here: How would you react if someone told you your code is a mess? (21 answers) Closed 10 years ago. I have been working on a system alone for about four years. I have built it from the ground up. It is not a perfect system. It is very complex, […]
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.