Live data from Hacker News

I know you didn't write this

ammil.industries

21–30 of 145 posts

Re: I know you didn't write this

#21
post #2

> Suspicions aroused, I clicked on the “Document History” button in the top right and saw a clean history of empty document – and then wham – fully-formed plan, as if it had just spilled out of someone’s brain, straight onto the screen, ready to share. This isn't always a great indicator. I can't stand Google Docs as an interface to write with, so use VIM and the copy/paste the completed document into it.

I do something similar. I write markdown, then render it and copy-paste that in

Re: I know you didn't write this

#22
post #15
post #12

Why can't the plan be judged on its merits? Rigorous verification of the idea is a good thing that should happen anyways. The main potential problem I see is transmission of privileged information to a third party. I assume they are working at a business to make money, not a school or a writing competition.

The unstated elephant in the room is that you can't possibly know how much thought the originator has given to this. You can't know if it has been reviewed and checked for minimal sanity, or just chucked over the fence. So you have to fully vet it. And, if you have to fully vet it, then what value has the originator added? Might as well eliminate their position.

>Might as well eliminate their position.

It's where we're headed.

Re: I know you didn't write this

#23
post #15
post #12

Why can't the plan be judged on its merits? Rigorous verification of the idea is a good thing that should happen anyways. The main potential problem I see is transmission of privileged information to a third party. I assume they are working at a business to make money, not a school or a writing competition.

The unstated elephant in the room is that you can't possibly know how much thought the originator has given to this. You can't know if it has been reviewed and checked for minimal sanity, or just chucked over the fence. So you have to fully vet it. And, if you have to fully vet it, then what value has the originator added? Might as well eliminate their position.

> The unstated elephant in the room is that you can't possibly know how much thought the originator has given to this.

You can just ask them if they reviewed it in detail.

Re: I know you didn't write this

#24
post #4

I don’t really find it better when someone ads a disclaimer. What am I supposed to do then? There’s still an expected default behavior of reading it, and if I don’t I need to confront them and say “I don’t care what you got an LLM to say, why not give me your view”. It’s inappropriate under any circumstances imo

When I receive something that either I suspect an LLM wrote 90% of, or the author is up front about it, I always ask "Did you check all of this yourself to verify before I pick it up?" and maybe half of the times I get a no, and then they return a day later with a new document and some fixes. Other half the time people say yes, I start digging into it, start finding bunch of weird stuff and send it back to the person…

> I don't really care if it's a person or the LLM getting it wrong,

You're nicer than some of us.

If it's an LLM getting it wrong, and it's not caught before it gets to you, then what value is the intermediary adding to the process?

Re: I know you didn't write this

#25
post #2

> Suspicions aroused, I clicked on the “Document History” button in the top right and saw a clean history of empty document – and then wham – fully-formed plan, as if it had just spilled out of someone’s brain, straight onto the screen, ready to share. This isn't always a great indicator. I can't stand Google Docs as an interface to write with, so use VIM and the copy/paste the completed document into it.

Another copy/paste reason - I can't count the number of times I've written up something for work on my own google account by mistake, then paste it into a new doc on the work account so I can share it.

Re: I know you didn't write this

#26
>Regardless of their intent I realised something subtle had happened. Any time saved by (their) AI prompting gets consumed by verification overhead, the work just gets passed along to someone else – in this case me.

This is _exactly_ how I feel. Any time saved by precooking a "plan" (typically halfbaked ideas) with AI isn't really time saved, it is a transfer of work from the planner to whoever is going to implement the plan.

Re: I know you didn't write this

#28
post #24

Earlier quoted context omitted.

When I receive something that either I suspect an LLM wrote 90% of, or the author is up front about it, I always ask "Did you check all of this yourself to verify before I pick it up?" and maybe half of the times I get a no, and then they return a day later with a new document and some fixes. Other half the time people say yes, I start digging into it, start finding bunch of weird stuff and send it back to the person…

> I don't really care if it's a person or the LLM getting it wrong, You're nicer than some of us. If it's an LLM getting it wrong, and it's not caught before it gets to you, then what value is the intermediary adding to the process?

I meant it in a way that I'll blame the person regardless of who actually wrote the text. The LLM messed up and you failed to notice? I blame you. You messed up and failed to notice? I still blame you.

Re: I know you didn't write this

#29
> So it’s definitely AI. I felt betrayed and a little foolish. But why?

Because the prompter is basically gaslighting reviewers into doing work for them. They put their marks of authorship on the AI slop when they've barely looked at it at all which convinces the reviewer to look. When the comments come back, they pump the feedback into the LLM, more slop falls out and around we go again. The prompter isn't really doing work at all—the reviewers are.

Re: I know you didn't write this

#30
post #9
post #2

> Suspicions aroused, I clicked on the “Document History” button in the top right and saw a clean history of empty document – and then wham – fully-formed plan, as if it had just spilled out of someone’s brain, straight onto the screen, ready to share. This isn't always a great indicator. I can't stand Google Docs as an interface to write with, so use VIM and the copy/paste the completed document into it.

> This isn't always a great indicator. Right. Certainly not dispositive. > use VIM and the copy/paste the completed document into it. But he did mention tables. You'd think if they weren't just ASCII art, there'd be _some_ google docs history about fixing them up.

Different-sized headers too.
Post reply on HN