Live data from Hacker News

We called it RAID because it kills bugs dead

devblogs.microsoft.com

81–90 of 128 posts

Re: We called it RAID because it kills bugs dead

#81
post #75

Earlier quoted context omitted.

Such a great show. I wish more people knew about it.

Never heard of it, but as a tech nerd from the 80's it sounds awesome. Will definitely check it out.

1st season is very good. Rest are crap.

Re: We called it RAID because it kills bugs dead

#82

The bug puns were everywhere! When I started working at Industrial Light and Magic in 1998, there was no bug tracker in regular use. I ended up building a bug tracker in Python called "Roundup" (inspired by a program by Alan Trombla, who came up with the name). To create the thinnest veneer of plausible deniability in case the bug spray lawyers came after us, the icon was a little spinning GIF animation of a cowboy o…

I think I used that. Was it open source? There was a short time when there were almost no open source bug trackers

Re: We called it RAID because it kills bugs dead

#83
post #75

Earlier quoted context omitted.

Never heard of it, but as a tech nerd from the 80's it sounds awesome. Will definitely check it out.

1st season is very good. Rest are crap.

A bit unfair, first season is amazing, the rest are merely very good - it’s a brilliant show overall though.

Re: We called it RAID because it kills bugs dead

#84

>>> they might have been too scared to write it. When looking back on the origin of RAID, one of the original developers confessed, “It really wasn’t made to last that long. Sorry!” This speaks to me - too many times we think we need clever architecture and well thought out methodologies and ... the most useful tools are a mix of inspiration and timing and luck. Had the developers stopped to plan they would have buil…

On the other hand, temporary fixes are often the most permanent kind.

Re: We called it RAID because it kills bugs dead

#85

The bug puns were everywhere! When I started working at Industrial Light and Magic in 1998, there was no bug tracker in regular use. I ended up building a bug tracker in Python called "Roundup" (inspired by a program by Alan Trombla, who came up with the name). To create the thinnest veneer of plausible deniability in case the bug spray lawyers came after us, the icon was a little spinning GIF animation of a cowboy o…

That sounds like an interesting historical error, because Roundup is a herbicide, not insecticide.

Don't say it too loud, but I hear it also kills humans.

Re: We called it RAID because it kills bugs dead

#86
post #2

I left MSFT and went to Viair (with folks from the MSN Mobile and Outlook Express team), and we didn't have a bug tracking system... so we had someone send us a few screenshots of RAID and built a VisualJ clone one weekend. Fun side project, didn't really want to be in the business of bug tracking, was slightly before the web app era... We called our bug tracking system "BlackFlag" because it was a competing brand of…

Fun fact, one of Sweden’s most influential music- and culture journalists was being interviewed on national television about a weird documentary wearing a pink “Pink Flag” t-shirt with a modified Black Flag logo. Beyond meta.

Is that a clever way of referring to Black Flag at the same time as Wire's Pink Flag?

Re: We called it RAID because it kills bugs dead

#87

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…

Fossil ( https://www.fossil-scm.org ) has an interesting approach to this problem - integrate bug and work item tracking, project wikis, and source control, but make them all distributed, so that there is not a single master copy of the bug database or the docs wiki. It attempts to solve both the cultural challenge (bugbase written by a different company/team from the source control, imposing 2 different styles on yo…

If only Fossil weren't so opinionated... I love the idea of bundling everything in the repo, and not averse to SQLite database as the storage format. But there's no way to edit history, even for commits that don't exist anywhere other than your own local repo - because the author considers rebase an anti-pattern.

Re: We called it RAID because it kills bugs dead

#88

> Unfortunately, the archive project renumbers the work items. Fortunately, the original work item is remembered in the title, so you can do a search for originalid:3141 to find the old work item known as number 3141. I wonder what happened if a bug was carried over for 2 or more databases.

I assume it'd be a chain e.g.

db 1 - issue 3141

db 2 - issue 12 (originalid:3141)

db 3 - issue 4 (originalid:12)

etc.

Re: We called it RAID because it kills bugs dead

#89

Earlier quoted context omitted.

1st season is very good. Rest are crap.

A bit unfair, first season is amazing, the rest are merely very good - it’s a brilliant show overall though.

Really depends on what you want in a show. If you came in expecting a show about people designing computer and solving hard and interesting technical problems along the way you will be become more and more disappointed as the show goes on and focuses more on the characters personal problems and whether or not they get married/divorced/sleep with each other.

Re: We called it RAID because it kills bugs dead

#90

Earlier quoted context omitted.

Fun fact, one of Sweden’s most influential music- and culture journalists was being interviewed on national television about a weird documentary wearing a pink “Pink Flag” t-shirt with a modified Black Flag logo. Beyond meta.

Is that a clever way of referring to Black Flag at the same time as Wire's Pink Flag?

That’s how I interpret it. I actually asked him on Twitter an hour ago - I’ll keep you posted :)
Post reply on HN