Bad bugs makes for self assigning issues
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: - it was used in v3.X so there is no need to rewrite everything from scratch - it gives us time to provide better user experience, instead rewriting code (see https://pbs.twimg.com/media/Ce5nYp0W4AAxp5Z.jpg) - each framework has it own + & - , we know knockout very well and it is great to feel comfortable when developing - to be honest each js framework has its own advantages and disadvantages - sometimes rewriting application just to be able to use new fancy framework is just replacing one issues with another.
Comment preview