Showing posts with label bugs. Show all posts
Showing posts with label bugs. Show all posts

Thursday, October 1, 2015

The quantum theory of bug resolution?

Snarky: I feel you can't know both the priority of the bug and simultaneously when the bug will be complete.

Snarky: I feel you can't know both the priority of the bug and simultaneously when the bug will be complete.
Title:  The quantum theory of bug resolution?

* As opposed to the Newtonian theory where the bug just falls out of the sky, hits you in the head, and leaves you dazed and confused.


Tuesday, September 29, 2015

Rats.

Snarky: I know you thought we were caught up on bugs.  But the cheese moves every day.

Snarky: I know you thought we were caught up on bugs.  But the cheese moves every day.
Title: Rats.

Wednesday, May 14, 2014

At what point do you decide we need a new roof?

Each of those bugs is a hole in our roof. No matter how big they are.  If we get enough of them then it's not a roof anymore.  We'll get wet.

I thought about titling this one something related to how many little holes fit in a great big hole, but I like this better.

Great Moments in Recent Metaphor History II
Snarky: Each of those bugs is a hole in our roof. No matter how big they are.  If we get enough of them then it's not a roof anymore.  We'll get wet.
Title: At what point do you decide we need a new roof?

Thursday, March 28, 2013

"Because that's stupid" is not a valid reason for closing out bugs.


Title: But what if that was the justification for building the feature in the first place? 
Snarky: "Because that's stupid" is not a valid reason for closing out bugs.


The product manager/developer relationship is inherently tense in my experience. I think it's because developers, ahead of the technological curve when it comes to building software products,  recommend features that go over like a lead balloon when pitched to the product team.   Not being the 'business' experts in the organization, they are then left to implement what in their minds are inferior or *gasp!* obsolete solutions.

Having then to go back and fix bugs in said features (arguably, their own fault),  it can be hard to resist adding a few snarky comments in the bug tracker.








Thursday, March 21, 2013

Only if you don't consider its purpose to be bug generation.




After all, software is eating the world...or so I'm told.

Title: Only if you don't consider its purpose to be bug generation.
Snarky: Creating software is not our core competency, or so I'm told.

Thursday, March 14, 2013

I see now why you choose not to comment your code.

Yes it looks like something I'd write, but it's not mine.  You'll just have to go ahead and fix that bug.
It is both a blessing and a curse when you find that your team writes code that is structured, both in organization and syntax, similarly.  On the one hand, you have consistency which if nothing else is pleasing from an architecture standpoint.  On the other you have consistency, which makes it easier for your teammates to claim ignorance of bugs and pawn the work off on you and simultaneously more difficult for one to deny authorship of said code.   At least we have source control for that....right?

Title: I see now why you choose not to comment your code.
Snarky: Yes it looks like something I'd write, but it's not mine.  You'll just have to go ahead and fix that bug.

Monday, August 20, 2012

If only we could say the same about ourselves.

No, it's not a bug.  That code only has to work from 9 to 5.

I want to put a survey/questionnaire right here: check real or fake.  I suspect you know the answer.  If a bug is never exercised, is it still a bug?  For the philosopher examining the tree question and pondering observation and the knowledge of reality, there's a lot to think about.  For a developer, the answer is a more clear cut "yes".  It's still a bug.  It still makes a noise.  Not only if it's outside 9 to 5 (that's why we have support and cell phones), but even when it's that hour twice a year during the daylight savings switch.  That's partially what test driven development is all about.  And it's certainly the impetus behind  making sure you catch all those edge cases, even if automating them means staring at your machine while it grinds through code contracts and Pex, speaking from a .NET perspective.  I think the Microsoft Research description of what Pex does is great, "Pex finds interesting input-output values of your methods."

Title: If only we could say the same about ourselves.
Snarky: No, it's not a bug.  That code only has to work from 9 to 5.

Monday, April 30, 2012

Maybe it's because we're always working on your 'Highs'?

Across the Table: I don't submit 'Lows' because you never fix them.
As a developer this has always been a pet peeve of mine -- never having a clue how important an issue is because "they're all important" while simultaneously implying that I'm not doing my job.

What's worse, making them all the same quickly leads to a categorizational arms race.  Showstopper?  Is that more or less important than High+?  What happened to all the Lows?  Oh they got moved up to Mediums? Are they more important than they were before?  No? Oh, you just eliminated the Low category? I see...