Timeline for Should I send an errata after technical interview?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2013 at 16:38 | comment | added | emory | @MichaelMrozek I agree that my wording was poor. I still think discussing the bug is more important than fixing it. If you just make a one line fix, I don't care. Tell me why your one line fix is important, what bad things will happen without it, etc. Why should I care about your fix? | |
| Aug 7, 2013 at 14:38 | history | edited | emory | CC BY-SA 3.0 |
deleted 143 characters in body
|
| Aug 7, 2013 at 7:37 | comment | added | le-doude | In my case it is an important one liner, breaks the function though, but is fixed very obviously. But I like this answer because sometime you might need to overhaul the code you gave and it is true that the more lines you write the more bugs you might introduce again. I will definitely bear this in mind if I am in a situation where the mistake is on a broader stroke kind of question. | |
| Aug 6, 2013 at 20:57 | comment | added | Michael Mrozek | This is worded a little weird. You meant "don't take too long sending the followup", but you said "don't fix the bug". He said it's a minor bug he noticed as he was walking out, so he probably already has the fix | |
| Aug 6, 2013 at 14:18 | history | answered | emory | CC BY-SA 3.0 |