| ▲ | anematode 3 hours ago | |
The author claimed that it was an honest mistake, but looking closer at the original PR removing it, his explanation doesn't make sense. Maybe what's happened is that their bots reward hacked their way into special-casing the benchmarks without a proper audit from the humans involved, and now they're doing vibed damage control.... | ||
| ▲ | hitekker 17 minutes ago | parent | next [-] | |
This comes up a lot in People Management. An employee takes a bad shortcut or does something that most reasonable people would call "cheating". Their manager benefits from that shortcut and pretends not to see it. When that bad shortcut comes up, the manager takes the employee's excuses ("technically...") and shops it around. No one "lies" per se; it's just deception. | ||
| ▲ | verdverm 2 hours ago | parent | prev [-] | |
This is almost certainly what happened. The first commit has 400k+ files, there is no way one person audited that. The project has tell tale signs of eyes free coding and ralph-like loops. | ||