tag:blogger.com,1999:blog-5512311610334754148.post1733653926016646802..comments2023-04-20T12:46:11.858-06:00Comments on The Ancestry Insider: More Problems Viewing ImagesThe Ancestry Insiderhttp://www.blogger.com/profile/02490682912125335188noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5512311610334754148.post-31991730152961879042008-07-21T08:53:00.000-06:002008-07-21T08:53:00.000-06:00Insider,Why should customers have to contact a dev...Insider,<BR/><BR/>Why should customers have to contact a developer/programmer directly? Why can't Ancestry customer support task someone to fix these things? Or are you suggesting that Ancestry is not committed as an organization to fixing bugs in "features" (often unwanted/unappreciated) that it serves up, and/or has some magic number of error rate/bugs that it thinks is "normal"?<BR/><BR/>Is this kind of apparent attitude toward software bugs an industry standard? I mean apart from Microsoft.<BR/><BR/>MikeAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-62345442512874352422008-07-21T06:47:00.000-06:002008-07-21T06:47:00.000-06:00I can't speak to Ancestry.com, but in other softwa...I can't speak to Ancestry.com, but in other software companies I've worked, your suggestion about contacting product management is the way to go.<BR/><BR/>Most developers feel a strong sense of ownership over their code, but slipping a bug fix in outside the normal PM process requires not only finding the bug, but that the developer do the work on their personal time, lest they fall behind on their feature development work. Furthermore, every change requires testing, so that developer may be signing up a tester for extra work by fixing the bug outside channels.Ben W. Brumfieldhttps://www.blogger.com/profile/08363399128262210534noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-27624454141271886192008-07-21T05:08:00.000-06:002008-07-21T05:08:00.000-06:00Actually, I think Firefox V3 may be part of the An...Actually, I think Firefox V3 may be part of the Ancestry viewing problem. I was having various problems - not only at Ancestry - with V3. When I went back to V2 everything worked like it is supposed to.Jack Coffeehttps://www.blogger.com/profile/03649768599179736262noreply@blogger.com