3 ms·
I consider a shame to read some of you, literally trashing and blaming the whole team after the article. One thing is to healthly discuss how dangerous can be
by luismedel 2y ago
I consider a shame to read some of you, literally trashing and blaming the whole team after the article.
One thing is to healthly discuss how dangerous can be assuming a GPT-generated code is safe or not. Or how unit tests could identify this (could really in this specific case?). Or why you need oncall shifts and good alerts. But, come on.
I spotted the issue in the code at first sight, but that doesn't make me morally superior, nor smart enough to blame someone to publicly talk about their mistake. It only means I'm currently reading that kind of code a lot, and I know where to look at. Pass me some clever ARM code and I'll be unable to spot even the most superfluous mistake.
It seems HN is crowded by the most smart guys on the planet, who never had dumb mistakes and are SO "quality inclined" they need to blame someone for theirs.
edit: of course, the decision to make it public is questionable, but that's topic for another thread, IMHO.