Comments on: What Is A Bug? http://www.codesimplicity.com/post/what-is-a-bug/ Thu, 29 Jul 2010 19:07:27 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Max Kanat-Alexander http://www.codesimplicity.com/post/what-is-a-bug/comment-page-1/#comment-384 Max Kanat-Alexander Tue, 22 Jul 2008 11:45:09 +0000 http://www.codesimplicity.com/?p=36#comment-384 I definitely agree. I wrote <a href="/archives/24" rel="nofollow">an article on pretty much exactly that</a> (though your specific point about it happening as "assumptions about usability" is a good one, people definitely do that!). -Max I definitely agree. I wrote an article on pretty much exactly that (though your specific point about it happening as “assumptions about usability” is a good one, people definitely do that!).

-Max

]]> By: Max Kanat-Alexander http://www.codesimplicity.com/post/what-is-a-bug/comment-page-1/#comment-383 Max Kanat-Alexander Tue, 22 Jul 2008 11:42:50 +0000 http://www.codesimplicity.com/?p=36#comment-383 Well, I think that could be classified under the "specifiers intentions," which is basically like the programmer's intentions but on a wider-scale project where the implementer isn't the "intender." However, it's important to not be so dogmatic to a spec that you violate common and reasonable user expectations. It's exactly the same point I made above in the blog, but expanded slightly to also apply to any intention, whether it's the implementer's or the spec writer's. -Max Well, I think that could be classified under the “specifiers intentions,” which is basically like the programmer’s intentions but on a wider-scale project where the implementer isn’t the “intender.”

However, it’s important to not be so dogmatic to a spec that you violate common and reasonable user expectations. It’s exactly the same point I made above in the blog, but expanded slightly to also apply to any intention, whether it’s the implementer’s or the spec writer’s.

-Max

]]> By: Nitin Reddy Katkam http://www.codesimplicity.com/post/what-is-a-bug/comment-page-1/#comment-382 Nitin Reddy Katkam Tue, 22 Jul 2008 10:47:51 +0000 http://www.codesimplicity.com/?p=36#comment-382 Another definition for a bug is: "Anything that isn't according to specification" If the design document says you click on the button and there ought to be a modal popup but in the implementation the popup isn't modal, you've got a bug! The programmer probably skipped over the line that said in bold with italics and underlined: "This popup should be modal". Another definition for a bug is: “Anything that isn’t according to specification”

If the design document says you click on the button and there ought to be a modal popup but in the implementation the popup isn’t modal, you’ve got a bug! The programmer probably skipped over the line that said in bold with italics and underlined: “This popup should be modal”.

]]> By: kasper graversen http://www.codesimplicity.com/post/what-is-a-bug/comment-page-1/#comment-380 kasper graversen Tue, 22 Jul 2008 09:52:48 +0000 http://www.codesimplicity.com/?p=36#comment-380 Or sometimes because you want the app to be as good or userfriendly as possible, you risk assuming things are bugs in usability, when in fact they aren't. The problem is your assumptions made without involving the customer. If you're interested in this point of view of what a bug is see http://firstclassthoughts.co.uk/misc/creativity_killed_the_app.html cheers, kasper Or sometimes because you want the app to be as good or userfriendly as possible, you risk assuming things are bugs in usability, when in fact they aren’t. The problem is your assumptions made without involving the customer. If you’re interested in this point of view of what a bug is see http://firstclassthoughts.co.uk/misc/creativity_killed_the_app.html

cheers,
kasper

]]>