<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Why I&#8217;m sometimes a bad bug reporter</title>
	<atom:link href="http://blog.objectteams.org/2010/02/why-im-sometimes-a-bad-bug-reporter/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.objectteams.org/2010/02/why-im-sometimes-a-bad-bug-reporter/</link>
	<description>Everthing Object Teams - adding team spirit to your objects.</description>
	<pubDate>Fri, 10 Feb 2012 06:18:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Better bug reporting &#171; Dark Views</title>
		<link>http://blog.objectteams.org/2010/02/why-im-sometimes-a-bad-bug-reporter/#comment-121</link>
		<dc:creator>Better bug reporting &#171; Dark Views</dc:creator>
		<pubDate>Wed, 03 Mar 2010 19:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.objectteams.org/?p=3#comment-121</guid>
		<description>[...] at 20:17 &#124; In Software &#124; Leave a Comment Tags: Bug Reporting, Bugs, Software, Software Development In his blog, stephan writes about the problems you can have as a bug reporter. Basically, when you encounter a bug, [...]</description>
		<content:encoded><![CDATA[<p>[...] at 20:17 | In Software | Leave a Comment Tags: Bug Reporting, Bugs, Software, Software Development In his blog, stephan writes about the problems you can have as a bug reporter. Basically, when you encounter a bug, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Digulla</title>
		<link>http://blog.objectteams.org/2010/02/why-im-sometimes-a-bad-bug-reporter/#comment-120</link>
		<dc:creator>Aaron Digulla</dc:creator>
		<pubDate>Wed, 03 Mar 2010 16:54:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.objectteams.org/?p=3#comment-120</guid>
		<description>I've opened a new bug for this: 

https://bugs.eclipse.org/bugs/show_bug.cgi?id=304544</description>
		<content:encoded><![CDATA[<p>I&#8217;ve opened a new bug for this: </p>
<p><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=304544" rel="nofollow">https://bugs.eclipse.org/bugs/show_bug.cgi?id=304544</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Digulla</title>
		<link>http://blog.objectteams.org/2010/02/why-im-sometimes-a-bad-bug-reporter/#comment-94</link>
		<dc:creator>Aaron Digulla</dc:creator>
		<pubDate>Fri, 26 Feb 2010 16:09:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.objectteams.org/?p=3#comment-94</guid>
		<description>I like the idea of a "save bug context" button which asks for a (short) description and saves the current state of Eclipse (= Java memory dump). I'm not sure it's possible to return to this state but a screen shot and a way to browse the memory would help a lot.

I often run in p2 bugs and I can't produce useful bug reports because the UI just doesn't give me any. So if I could save the state of the resolver, the involved repositories and a screen shot, that would already help a lot.</description>
		<content:encoded><![CDATA[<p>I like the idea of a &#8220;save bug context&#8221; button which asks for a (short) description and saves the current state of Eclipse (= Java memory dump). I&#8217;m not sure it&#8217;s possible to return to this state but a screen shot and a way to browse the memory would help a lot.</p>
<p>I often run in p2 bugs and I can&#8217;t produce useful bug reports because the UI just doesn&#8217;t give me any. So if I could save the state of the resolver, the involved repositories and a screen shot, that would already help a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stephan</title>
		<link>http://blog.objectteams.org/2010/02/why-im-sometimes-a-bad-bug-reporter/#comment-10</link>
		<dc:creator>stephan</dc:creator>
		<pubDate>Thu, 11 Feb 2010 00:02:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.objectteams.org/?p=3#comment-10</guid>
		<description>Thomas, thanks for your kind words.

I've indeed followed the Mylar work pretty much from the beginning and I highly appreciate everything about it. Actually I'm still looking for an enthusiast you writes a bridge for OT/J in Mylyn. I already spoke to Mik about this but never found the student who was eager to jump in. Maybe you know somebody for this task? :)

OTOH, even with the best Mylyn the dilemma doesn't just disappear. As I said, during this big refactoring session I did report a couple of bugs. Unfortunately, after the refactoring was done, one of the bugs was no longer reproduceable. It had to be analyzed right in the second it occurred or never.

Sometimes I just wonder whether it is normal that right when my work requires ultimate concentration I don't just hit one bug but they are seeming to have a party on my computer, they just keep coming.

Put still differently: I'd really like to appreciate each bug that unveils itself, because with the right steps this will mean the software will be improved. Just in some situations that appreciation is hampered a bit by the limitations of my very self in its linear universe :)</description>
		<content:encoded><![CDATA[<p>Thomas, thanks for your kind words.</p>
<p>I&#8217;ve indeed followed the Mylar work pretty much from the beginning and I highly appreciate everything about it. Actually I&#8217;m still looking for an enthusiast you writes a bridge for OT/J in Mylyn. I already spoke to Mik about this but never found the student who was eager to jump in. Maybe you know somebody for this task? <img src='http://blog.objectteams.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>OTOH, even with the best Mylyn the dilemma doesn&#8217;t just disappear. As I said, during this big refactoring session I did report a couple of bugs. Unfortunately, after the refactoring was done, one of the bugs was no longer reproduceable. It had to be analyzed right in the second it occurred or never.</p>
<p>Sometimes I just wonder whether it is normal that right when my work requires ultimate concentration I don&#8217;t just hit one bug but they are seeming to have a party on my computer, they just keep coming.</p>
<p>Put still differently: I&#8217;d really like to appreciate each bug that unveils itself, because with the right steps this will mean the software will be improved. Just in some situations that appreciation is hampered a bit by the limitations of my very self in its linear universe <img src='http://blog.objectteams.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Ehrnhoefer</title>
		<link>http://blog.objectteams.org/2010/02/why-im-sometimes-a-bad-bug-reporter/#comment-2</link>
		<dc:creator>Thomas Ehrnhoefer</dc:creator>
		<pubDate>Wed, 10 Feb 2010 18:47:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.objectteams.org/?p=3#comment-2</guid>
		<description>Hi Stephan

I know the feeling of not reporting bugs because one would get distracted too much, or a handy workaround already became a habit. Guess everybody experiences this once in a while.
You have the right idea to at least minimize occurrences of this problem, by using Mylyn. If everything you work on is captured as a task (and that task not being "work", but a very specific item, preferably finish-able in a day or less), you will find that the context getting saved might just be enough to get you back into the right state after submitting or fixing that bug that just came up.

Sometimes, when I realize that I will be distracted longer, or I had some things in my mind I wanted to do but can't right away, I just make some notes in the private section of the Task Editor, to help me remember when I get back to the task.

If a lot of your tasks are not just developing, but various other things, like researching in the web, or grading papers (in case you are still teaching at the TU Berlin - I had the pleasure attending some courses of yours), you might want to give Tasktop a try as it captures a much broader context.

So I hope you find some time to try out Mylyn. A colleague of mine, David, wrote some nice articles about best practices with Mylyn (and Tasktop):
http://tasktop.com/resources/tutorials/</description>
		<content:encoded><![CDATA[<p>Hi Stephan</p>
<p>I know the feeling of not reporting bugs because one would get distracted too much, or a handy workaround already became a habit. Guess everybody experiences this once in a while.<br />
You have the right idea to at least minimize occurrences of this problem, by using Mylyn. If everything you work on is captured as a task (and that task not being &#8220;work&#8221;, but a very specific item, preferably finish-able in a day or less), you will find that the context getting saved might just be enough to get you back into the right state after submitting or fixing that bug that just came up.</p>
<p>Sometimes, when I realize that I will be distracted longer, or I had some things in my mind I wanted to do but can&#8217;t right away, I just make some notes in the private section of the Task Editor, to help me remember when I get back to the task.</p>
<p>If a lot of your tasks are not just developing, but various other things, like researching in the web, or grading papers (in case you are still teaching at the TU Berlin - I had the pleasure attending some courses of yours), you might want to give Tasktop a try as it captures a much broader context.</p>
<p>So I hope you find some time to try out Mylyn. A colleague of mine, David, wrote some nice articles about best practices with Mylyn (and Tasktop):<br />
<a href="http://tasktop.com/resources/tutorials/" rel="nofollow">http://tasktop.com/resources/tutorials/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

