Many excellent comments and viewpoints about this Charlie Foxtrot, but it took until page 9 to get the best one.This is one of those perfect demonstrations of how AI does not save time. In this case:
1. It did not save time summarizing the article because the first tool failed to work at all.
2. It did not save time because the second tool generated a summary filled with quotes that never existed.
3. It did not save time because the person the article was about had to come and fact check the article himself in the comments.
4. It did not save time because multiple members of the Ars staff had to look into the situation on a weekend.
5. It did not save time because Kyle had to post about his innocence.
6. It did not save time because Benj had to post his explanation and apology.
Contingent on employment law and contractual details, it would be absolutely appropriate for Ars Technica to announce "We have fired our senior AI reporter for an egregious violation of policy and professional ethics in misusing an AI tool to generate false reporting".You want what, a public execution?
One aspect of sympathy I'll extend to Ars is that you really do need to be able to expect that your employees are, on the whole, acting in generally good faith. You should have measures in place to catch somebody stealing from the corporate coffers, stuff like that, but it's hard to imagine a system operating with any kind of efficiency when you have to assume everyone is acting in bad faith, all the time. This is even a who-watches-the-watchers situation--Mr. Edwards was not junior staff. He ostensibly runs (hopefully ran) this beat.No they don't. But at the same time, this was a systemic failure. Benj Edwards very clearly violated existing policy, something that a senior writer (covering the AI beat no less) should never, ever do.
But he's not alone, apparently whatever review articles are put through before they're published is woefully insufficient.
a.k.a., "I only stole from the company once"if it is verified as an isolated occurrence about which everyone is honest within a short, but non-zero, amount of time
A journalist fabricating quotes from a real person (or fabricating evidence more broadly) is nearly the worst non-malicious professional act I can imagine within their field, just as accidentally running over a bunch of children is nearly the worst non-malicious professional act a bus driver could perform. The implied equivalence was completely intentional and I stand by it confidently and resolutely.While I get the point you're trying to make, comparing this to vehicular manslaughter (of children no less) is way off base.
It would be much sadder if 20 (?) Ars Technica journalists lost their jobs because nobody had a whisker of faith in the journalistic standards of the organization and the whole thing went under. Or the other writers at any other organization that foolishly hired him into a like role after this.But as a human being, I also hate the idea that a screw-up while sick, which was likely a quick "this will only take a minute and nobody will know," has thoroughly fucked Edwards's job and reputation. He should have known better - he's clearly spent a lot of time around these abominations, as his job, and should be well aware of their pitfalls. But I feel sorry for him, and yeah, I hope he has a chance at professional redemption, either here or elsewhere.
If it's interesting context or if anybody cares regarding "active comments section", that comment section ran for about two pages (definitely sure) in maybe ninety minutes (less sure).5. Shit hit the fan, etc. As I understand it, there was an active comments section following Shambaugh's engagement.
The comments were locked somewhere around 3:30 Central (quoting from my own memory here), and the article remained up for, eh, a few tens of minutes thereafter. But the duration was short enough that it could well have been the time it takes between clicking one button and clicking another.I don't think 5a happened before 6. Listing it first implies Ars tried to shut down the conversation while leaving the article up, and I don't know that it actually happened that way. Of course once the original article was pulled, it makes sense that the comments would also be hidden, that has happened before.
1) I think enforceability is a bit of a canard. We have all kinds of policies that would be difficult or impossible to enforce in a rigorous manner. Hell, the fast food joint down the street does not have a camera in the bathroom ensuring that employees wash their hands after relieving themselves. Nevertheless, if we have a policy that says "You shall not do ABC and this is the reason why", a lot of conscientious employees will follow that policy regardless of whether they think they'll get caught. Which matters becauseI'm on the fence about zero tolerance for using AI in this line of work. First, it's completely unenforceable for remote work. Second, we don't know what the future holds for this tech and its perception. Third, I think the best policy is to have those that submit work be accountable for what they submit, regardless of how it is produced.
It's a drug, and the first one's free.This is part of why I flatly refuse to use LLM slopcoding machines in my work.
I will fail to check something well enough at some point. I don't want to deal with the consequences of a slopcoded test I failed to properly vet letting a bug through and potentially fucking up processing a card transaction or thousand.
I think Jim's point is that Mr. Edwards does not face the question of "resign or be downsized", where there is an open question of what post-employment resources may be available. He perhaps faces the question of "resign or be fired for cause", where there is no question anyway--zero versus zero.Unemployment benefits generally are not available for an employee resigning voluntarily.
Of course, that presumes you're in a semi-anonymous position where hiding is even remotely possible.Where the gamesmanship comes in is trying to figure out whether you'll get let go or fired, because if it's the former, you don't want to resign and lose your benefits--but if it's the latter, you REALLY want to resign first, so you don't have to put a termination for cause on your resume (or lie about it).
No, but he had a LLM pluck a couple of select quotes* out of it.Did you read the article you linked, cause I've read the first dozen or so paragraphs and it doesn't support the point you're making.
The article was redirected to /dev/null within about two hours of publication on a Friday afternoon. We are still only about 50 hours out from that event. There have been basically zero conventional working hours since the failstorm erupted.That's why Ars buried it as hard as they could, then when they lost containment they recreated the article (rather than un-unpublishing it) or deleted all comments on it, don't state who did the thing, what the thing they did was, and otherwise assign no actual accountability.
...
Ars got caught aiming that firehose at their audience, lost containment of the attempt to hide it, and are still hiding what the firehose contained. This is not kudos-worthy.
Giles Corey, screaming in his death throes: MORE NINESLeaving aside whether it’s doable at all, getting 99.9% reliable LLM output is the holy grail of the field and anyone doing it would be screaming it from the rooftops.
When someone steals from the company account, in a sense, the whole company failed. But one guy was the thief.This is a collective failure, and no one person is fully responsible.
This is hilarious and sad. Mr. Edwards' continued employment would prove beyond a shadow of a doubt that Ars Technica is absolutely willing to tolerate this misconduct.Of all people to make this same mistake again, it is less likely to be this author. His reporting will be viewed with a critical eye for years, and he knows it. He'll be on his best behavior because Ars has proven it won't tolerate the black eye, evidence by the retraction and acknowledgement.
You say "non-subscribers". I say "former subscribers". For a reason.While you are absolutely entitled to your opinions I find it particularly bold for non-subscribers like yourselves to disparage paying readers' opinions on this. You have no skin in this game.
For those commentators who are denouncing what they see as torches and pitchforks, it's important to understand that the he-must-be-fired brigade do not necessarily see this as a question of punishment. Rather, it is: is Benj Edwards fit for purpose? Is he able to fulfill the duties and responsibilities of an Ars Technica journalist on February 17, 2026 and beyond?I understand the calls to not be bloodthirsty but that's not really what's going on here in the first place and frankly bad faith to keep calling out people for that. Rather it's What are the grounds for dismissal? And specifically, for a journalist.
Contrary to the usual semi-conspiratorial viewpoint on paid actors or bots, creating an account and leaving your first comment is actually rather high-friction. If somebody has never gone through the effort to create a user account and leave a comment but they specifically chose to do so for this story, the baseline expectation is that they actually felt very strongly about this, far above and beyond their reaction to any normal story they read on Ars Technica. Discounting their first comment viewpoint, purely on the basis of it being their first comment, is probably the opposite of what you should be doing.Sorry how dare I try to provide a reasoned perspective instead of screaming into the void like all the people who created accounts just to complain about this.![]()
This combination of factors was also not lost on me. The magnitude of that potential contradiction gives me an additional degree of confidence that the final resolution of this saga will be a rather severe one.Hopefully Benj Edwards gets "ejected" from writing AI articles for a bit. It would be absurd to hold us commentators (not least of which the legendary Jim Salter) to a higher standard than paid writers.
Momentarily leaving aside allllll of the other problems here, this is not how the word "everything" works!Everything in the article was written by humans, except the quotes
Some form of "we will have more to say on this topic once we have completed our investigation, but that will take some time" should have been the last line of Ken Fisher's statement, and I don't think there was a good reason to omit it.That was actually part of my point: it's important to be seen to be doing the right thing. As you point out, currently the idea that there will be a full and open investigation is left to be taken on faith.
Saving his colleagues the profound mess and headaches that he has caused them, when the final outcome probably is not in doubt, is one of the reasons I think Mr. Edwards should immediately resign his position (perhaps, at management's discretion, after participating in a process failure analysis that is clearly sorely needed). If he ever wants to work again in this or a related field, it would be a tiny first step towards building back up his professional reputation.The long story short is that there's a whole shit-ton of stuff to unpack before decisions can be made.
This is an excellent comment, and it really underscores just how badly Mr. Edwards fucked over his colleagues.It's a bit deeper than that, and as much as I enjoy a good prank, consider this fair warning a bucket of cold water may be coming:
Amusingly, this is not how soccer works. A major transgression absolutely will result in immediate ejection. In fact, a not-insignificant aspect of arguing with your buds while watching a soccer game is whether a player's first transgression merits immediate ejection or merely a caution.Agreed. The soccer rule of two yellow cards (warnings) then a red one (out!) ought to apply.
You're describing how you mentor an intern, not how you discipline a senior staffer.They don't need to be terminated, and potentially canceled in the industry, to learn. They can be counseled and educated. They can be made to understand that this can't happen again.
Maybe someone else said Mr. Edwards should be barred from the industry--I don't think I did. What I did more or less say that if he ever hopes to convince any particular journalism outlet to hire him, he has some enormous work ahead of him. No individual outlet is obligated to hire him. He doesn't have a perpetual right to a job in this field, certainly not if he is a known fraudster.Well, Soccer players given an ejection are usually ejected for the match. The system would be somewhat more controversial if ejection meant being fired and barred from taking a position at another team, per your earlier suggestion.
This one merits pondering. I might be able to live with something like that. Specifically, no articles about anything serious.Now, should Benj be fired? I think he should be dismissed from the AI beat, but not dismissed from reviewing video games or classic computers or other non-AI subjects.
A promise to not use AI in direct and specific violation of policy again, plus two bucks, will get me a nice coffee at Starbucks.These three things are known, and I believe they are enough to make a decision on Benj's fate. The question becomes: What does "not permit" actually mean? I'd be happy with a promise not to use AI again and a breakdown of how things will change at Ars Technica as a result.
If you incorrectly think that I am the one who introduced the soccer yellow/red card metaphor to describe Mr. Edwards' apparent misconduct and how Ars Technica might seek to discipline him, perhaps you unwisely used an AI tool to summarize the comment section up to that point.A red card does not mean booting the player from the team permanently - unless it was the result of deliberate malice.
No team - and you damn well know that - would boot a player permanently for getting a red card in a match.
There's an old saying in Tennessee--I know it's in Texas, probably in Tennessee--that says, fool me once, shame on--shame on you. Fool me--you can't get fooled again.well now that they got caught they'll make extra-certain they don't get caught again
I think "reckless disregard for the truth" is the applicable standard here. Putative AI expert asks the slopbox to pull quotes from a single blog post, an act which would take that expert maybe five minutes of human time, and he just rolls with it and publishes it to the world.I don't believe it's likely that Mr. Edwards intended to quote the subject of his article incorrectly, therefore I don't think those adjectives accurately convey the situation.
So back to intent - does it matter? My initial reaction is that it should matter, but I'm open to other thoughts on the matter.
If it eases that twitch you're feeling in the back of your eye, this comment is absolutely a level of detail I regularly get into with prospective new employees during an interview. And if the tables were turned, I would be uncomfortably shifting in my seat if the hiring manager wouldn't tell me even that much.We're getting pretty close to the edge of inside baseball that I'm not sure I want to cross, even as a former (not current) staffer. But in the interests of transparency, I'll tell you a little about how this worked four or five years ago.
We know this comment section is being watched, as it should be. If someone has not yet told senior staff that they are burning their accumulated trust and political capital by each passing hour--not necessarily in issuing a final report but in saying "we really are working on it"--then they are doing management (who should know better anyway) a grave disservice.I have to urge more patience. Until we hear otherwise I'm prepared to give a week, but I would desperately want at least an update that something is being done.
lol.An interview is:
- under cover of commercial confidentiality
Alas, probably never existed very long before, either. The age of yellow journalism was not something to celebrate.Which is a long way of saying: those of us who grew up reading newspapers or watching nationally edited TV news prior to 2000 experienced a thoroughness and level of precision in reporting and writing that no longer exists and will probably never exist again.