51–60 of 128 posts
> 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.
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.
Actually you bring up a good point - the reactions are perhaps more bimodal than anything. If you're on one of the teams it was designed for, it is indeed near perfect. If not, it's far from it.
The one thing all long-lived systems have in common: nobody ever intended them to be long-lived systems.
I definitely never intend it to last that long.
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?
The one thing all long-lived systems have in common: nobody ever intended them to be long-lived systems.
The quick and dirty Perl deployment system I built at reddit lasted nine years. Five years after I left. I definitely never intend it to last that long.
I had a friend at a company I left tell me they were un-mothballing a cancelled platform (killed at the time by an unfortunate acquisition) and deployment system I built several years ago because it was needed again. The whole thing was pretty janky because it was barely past prototype but fairly functional.
I wished him good luck and told him to find a new job, because there be dragons. He took the advice eventually, but I did hear they got it up and running again, with some pain. Apparently it is out there chugging along doing its thing once again.
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…
Personally, I like to mention the ticket number(s) and a description of what changed and why. I wish git would reject commit messages like "fixed".
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…
Only to run across 2 years later, and find myself wondering "who was this 'future me' that I envisioned might be interested in an ethernet card that exhibits flaky behavior under high load when bonded?"