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

A Taxonomy of Bugs

ruby0x1.github.io

Post reply on HN
Print view View original

1–10 of 26 posts

Re: A Taxonomy of Bugs

#2

Post by mannykannot »

Here's a step 0 for your debugging strategy: spend a few minutes thinking about what could account for the bug. Prior to its occurrence, you are thinking about what could go wrong, but now you are thinking about what did go wrong, which is a much less open-ended question.

Re: A Taxonomy of Bugs

#3

Post by readthenotes1 »

I was such a bad developer that I realized I had to automate the re-running of parts of the system to find the bugs.

Of course, the code I wrote to exercise the code I wrote had bugs, but usually I wouldn't make offsetting errors.

It didn't fix all the problems I made, but it helped. And it helped to have the humility when trying to fix code to realize I wouldn't get it the first time, so should automate replication

Re: A Taxonomy of Bugs

#4

Post by bheadmaster »

readthenotes1 wrote: post #3

I was such a bad developer that I realized I had to automate the re-running of parts of the system to find the bugs. Of course, the code I wrote to exercise the code I wrote had bugs, but usually I wouldn't make offsetting errors. It didn't fix all the problems I made, but it helped. And it helped to have the humility when trying to fix code to realize I wouldn't get it the first time, so should automate replication

> I had to automate the re-running of parts of the system to find the bugs

Congratz, you've independently invented integration tests.

Re: A Taxonomy of Bugs

#5

Post by tough »

bheadmaster wrote: post #4
readthenotes1 wrote: post #3

I was such a bad developer that I realized I had to automate the re-running of parts of the system to find the bugs. Of course, the code I wrote to exercise the code I wrote had bugs, but usually I wouldn't make offsetting errors. It didn't fix all the problems I made, but it helped. And it helped to have the humility when trying to fix code to realize I wouldn't get it the first time, so should automate replication

> I had to automate the re-running of parts of the system to find the bugs Congratz, you've independently invented integration tests.

I don't always test but adding a lil test after finding and fixing a bug so you don't end up there again a second time is a great practice

Re: A Taxonomy of Bugs

#8

Post by quantadev »

bheadmaster wrote: post #4
readthenotes1 wrote: post #3

I was such a bad developer that I realized I had to automate the re-running of parts of the system to find the bugs. Of course, the code I wrote to exercise the code I wrote had bugs, but usually I wouldn't make offsetting errors. It didn't fix all the problems I made, but it helped. And it helped to have the humility when trying to fix code to realize I wouldn't get it the first time, so should automate replication

> I had to automate the re-running of parts of the system to find the bugs Congratz, you've independently invented integration tests.

Congrats, you've found someone who failed to invoke a buzzword that you know.

EDIT: But Acktshally `the code I wrote to exercise the code I wrote` is a description of "Unit Testing", not integration testing.

Post reply on HN