Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We called it RAID because it kills bugs dead

devblogs.microsoft.com

Post reply on HN
Print view View original

31–40 of 128 posts

Re: We called it RAID because it kills bugs dead

#31

Post by AceJohnny2 »

why_only_15 wrote: post #25
jkcorrea wrote: post #9

Fun fact: Apple's internal bug tracking tool, Radar, traces its origins to a pen-and-paper tracking system from the very early days. In a similar fashion to RAID from the article, it's use expanded way beyond the original use case and is now used by nearly every team at Apple, from hardware, to test, to marketing, retail, and everything in between. It's often the butt of a lot of jokes as most people hate its dated a…

It even has a cute avatar, Annika the Anteater, that a bunch of people have plushes of

And shirts!

Re: We called it RAID because it kills bugs dead

#32

Post by rwc »

swrobel wrote: post #28
why_only_15 wrote: post #25

Earlier quoted context omitted.

It even has a cute avatar, Annika the Anteater, that a bunch of people have plushes of

Tried to find a pic... Does Apple secrecy really extend that far?

you mean the first image to come up in a google image search for [Annika the Anteater apple radar]?

https://twitter.com/macshome/status/1028996446903783426

Re: We called it RAID because it kills bugs dead

#33

Post by AceJohnny2 »

swrobel wrote: post #28
why_only_15 wrote: post #25

Earlier quoted context omitted.

It even has a cute avatar, Annika the Anteater, that a bunch of people have plushes of

Tried to find a pic... Does Apple secrecy really extend that far?

Here's an old version: https://images.app.goo.gl/zxbGoJuVHxSd2dhGA

Re: We called it RAID because it kills bugs dead

#34

Post by bitwize »

bentcorner wrote: post #17

Sometimes I think bug tracking doesn't get enough attention. It's gotten a lot better these days but compared to source control, bug tracking seems to remain the red-headed step-child. Bugs can be just as important as source code - if a line of code is changed and all the comment says is "bug 1234", then hopefully bug 1234 has context about the scenario that was broken, a history of a conversation between QA and deve…

That is because Industry Best Practice these days is to use JIRA, which lumps bugs in with stories and spikes and other agileshit. They must be planned, prioritized, and pointed alongside all the other work. Ceremonies must be done. The idea that they are defects, and that tracking them and their fixes specially is important, tends to be lost.

Re: We called it RAID because it kills bugs dead

#36

Post by asveikau »

shepwalker wrote: post #3

Oh lord, product studio. Back in 2013 the preferred method of filing workitems for a given "wave" was to load this spreadsheet, do weiiird formatting, and indentation, type up all the workitems you foresee for the next sprint and then press a magic "send to product studio" button." God help you if you messed up some of the nesting or wanted to reorder anything - honestly I would just wipe it clean and start from scra…

I had absolutely zero problems with product studio when I used it from 2008-2011. It was a very 1990s style MDI application, somewhat representing the peak of win32 ux design, short and to the point, and as long as the servers were happy it "just worked".

Re: We called it RAID because it kills bugs dead

#37

Post by Paul-ish »

kaibee wrote: post #29
hermitdev wrote: post #24

Earlier quoted context omitted.

What ammuses me is looking at some of the hard-coded "end of time" dates at previous employers. Instead of using null as an unbounded upper bound (because nulls are hard /s), there are hard coded "end dates". One was 2032-12-31, another 2037-12-31 and usually 9999-12-31. Obviously, these all have problems, especially when used in finance. 2037 makes sense, because 2037 is the year that 32bit linux overflows. 9999 als…

Now that it's 2020, I've been looking for a new year to think of as "the future". 2040 seems too obvious and maybe too far away to really imagine, what just add 20 years? Boring. I think I'll take 2032.

2049, for the year the blade runner sequel is set in.

Re: We called it RAID because it kills bugs dead

#38

Post by JadeNB »

saagarjha wrote: post #10
jkcorrea wrote: post #9

Fun fact: Apple's internal bug tracking tool, Radar, traces its origins to a pen-and-paper tracking system from the very early days. In a similar fashion to RAID from the article, it's use expanded way beyond the original use case and is now used by nearly every team at Apple, from hardware, to test, to marketing, retail, and everything in between. It's often the butt of a lot of jokes as most people hate its dated a…

As far as I can tell, most teams think Radar is the best bug tracking tool ever. Externally, it's extremely frustrating to interact with, even more so through Feedback Assistant.

> As far as I can tell, most teams think Radar is the best bug tracking tool ever.

To judge from the outside, one of its features is that it makes it super easy to ignore years-old and highly multiply submitted bugs.

Re: We called it RAID because it kills bugs dead

#39

Post by wlesieutre »

JadeNB wrote: post #38
saagarjha wrote: post #10

Earlier quoted context omitted.

As far as I can tell, most teams think Radar is the best bug tracking tool ever. Externally, it's extremely frustrating to interact with, even more so through Feedback Assistant.

> As far as I can tell, most teams think Radar is the best bug tracking tool ever. To judge from the outside, one of its features is that it makes it super easy to ignore years-old and highly multiply submitted bugs.

I've heard using it externally described as "throwing a Radar over the wall"

Re: We called it RAID because it kills bugs dead

#40

Post by fred256 »

m0zg wrote: post #12

Google's counterpart is called Buganizer. I've seen bugs in it dating back a decade or more. I don't know what, if anything, was in place before Buganizer. They might be exposing some version of it externally as well now: https://issuetracker.google.com/ , although the UI bears little resemblance with the internal version I used years ago, so it's probably a separate product. What Raymond's article does not mention (…

Buganizer was preceded by BugsDB if I recall correctly
Post reply on HN