Timeline for Is asking about "The most interesting bug in your career" a good interview question?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 15, 2017 at 7:10 | comment | added | FDM | I think you misunderstood my explanation as I was only talking about red values, but my example is only trying to show efficiency (checking 30 values in the UI might take 10 minutes, while in the database 2 minutes). As in: any value in this list turns the UI red (= the system, if it works for one it'll work for hundred) and I have to validate the list itself for correct values. | |
| Dec 14, 2017 at 20:24 | comment | added | Aaron | A minor disagreement: I would not consider testing 1 known good (non-red) value and the 30 known red values to be a good test. I would rather see tested, and would trust more, 10 and 10, or even 5 and 5, than just 1 and all-30. Otherwise good and +1 | |
| Dec 14, 2017 at 17:01 | comment | added | Cronax | Another option perhaps: what kind of defects do you most enjoy finding? | |
| Dec 14, 2017 at 15:21 | history | answered | FDM | CC BY-SA 3.0 |