+972 52-548-6969
Bad bugs makes for self assigning issues
time to read 1 min | 144 words
One of our developers just added the following bug:
This is in an area that of the code that this particular developer is not regularly traversing*. The image above includes the full contents of the bug. And that caused me to immediately assign it back to its opener.
The problem? If you say that you got an error, include the error. In many cases, you can save a lot of time and guessing.
For an internal bug, where the person who opened it is available, we have much lower bar for bug report quality. Most bugs are closed relatively quickly anyway. But lower bar for bug report quality still means there is a bar.
* I started to say, not responsible for, but we don’t have code ownership, so that wouldn’t have been right.
Comments
Hey ayende,
offtopic but maybe worth a blog post: why did you stick to knockoutjs for the Raven Manageent Studio?
@Tobias Zürcher, I don't know Raven's Team members motivations, however Knockout is an actively developed technology, it's used for Azure Portal and it greatly evolved because of it over the years.
@Tobias Zürcher
We stick with knockout for few reasons:
Comment preview