Agreed. That's why the documentation is important. If the issue ticket says "I saw this but once. It took 2 days of reproducing and it could only be done if the moon was in a waning phase while 3 dogs bathed simultaneously" and "this is the log dump. You can see on line 3453 that we segfault" etc, it shows what you've been doing.
The way I felt the article should be interpreted is that yes, if after 2 weeks you have a 1 line change, that's going to get you fired. And debatably it should, given that it'll likely take somebody else another 2 weeks to fix a similar problem. Why would a manager want to pay 2 weeks salary for (what we call, unsure if commonly used) "tribal knowledge"? At least do a post-mortem/lessons-learnt
The way I felt the article should be interpreted is that yes, if after 2 weeks you have a 1 line change, that's going to get you fired. And debatably it should, given that it'll likely take somebody else another 2 weeks to fix a similar problem. Why would a manager want to pay 2 weeks salary for (what we call, unsure if commonly used) "tribal knowledge"? At least do a post-mortem/lessons-learnt