Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

It's insulting to read AI-generated blog posts

blog.pabloecortez.com

Post reply on HN
Print view View original

491–500 of 565 posts

Re: It's insulting to read AI-generated blog posts

#491

Post by Frieren »

ummonk wrote: post #433
collingreen wrote: post #294

Earlier quoted context omitted.

I tell my team that the diff already perfectly describes what changed. The commits and PR are to convey WHY and in what context and what we learned (or should look out for). Putting the "what" in the thing meant for the "why" is using the tools incorrectly.

Does the PR description not end up in the commit history after merge? A description of what changed is very useful when browsing through git logs.

> A description of what changed is very useful when browsing through git logs.

Doing a blame on a file, or just looking at the diff of the pull request gives you that. The why is lost very fast. After a few months it is possible that the people that did the change is not anymore in the company, so nobody to ask why something was done.

"Oh, they changed the algorithm to generate random numbers". I can see that in the code. "Why was it changed?". I have not clue if there is no extra information somewhere else like a change log, pull request description, or in the commit comments.

But all this depends on the company and size of the project. In your situation may be different.

Re: It's insulting to read AI-generated blog posts

#492

Post by nobodywillobsrv »

jihadjihad wrote: post #23

It's similarly insulting to read your AI-generated pull request. If I see another "dart-on-target" emoji... You're telling me I need to use 100% of my brain, reasoning power, and time to go over your code, but you didn't feel the need to hold yourself to the same standard?

How to do simple change on complex projects at the same ROI with LLM?

Re: It's insulting to read AI-generated blog posts

#493

Post by nobodywillobsrv »

collingreen wrote: post #294
ab_io wrote: post #206

Earlier quoted context omitted.

100%. My team started using graphite.dev, which provides AI generated PR descriptions that are so bloated with useless content that I've learned to just ignore them. The issue is they are doing a kind of reverse inference from the code changes to a human-readable description, which doesn't actually capture the intent behind the changes.

I tell my team that the diff already perfectly describes what changed. The commits and PR are to convey WHY and in what context and what we learned (or should look out for). Putting the "what" in the thing meant for the "why" is using the tools incorrectly.

The PR spec for some open source projects are quite onerous.

What is unspoken here is that some open projects are using cost of submission AND cost of change / contrib as a kind of means of keeping review work down.

Nobody is correct here really. It's just that the bottlenecks have changed and we need to rethink everything.

Changing something small on a very large project is a good test. A user might simply want a new optional argument or something. Now they can do it and PR. But the process is geared towards people who know the project better even if the contributor can run all the tests it is still not trivial to fill in the PR request for a trivial change.

We need to rethink this regime shift a bit.

Re: It's insulting to read AI-generated blog posts

#494

Post by somethingsome »

ManuelKiessling wrote: post #312
jihadjihad wrote: post #23

It's similarly insulting to read your AI-generated pull request. If I see another "dart-on-target" emoji... You're telling me I need to use 100% of my brain, reasoning power, and time to go over your code, but you didn't feel the need to hold yourself to the same standard?

Why have the LLMs „learned“ to write PRs (and other stuff) this way? This style was definitely not mainstream on Github (or Reddit) pre-LLMs, was it? It’s strange how AI style is so easy to spot. If LLMs just follow the style that they encountered most frequently during training, wouldn’t that mean that their style would be especially hard to spot?

My impression is that this style started with apple products. I remember distinctly opening a terminal and many command lines (mostly Javascript frameworks) applications were showing emoji in the terminal way before LLMs.

But maybe it originated somewhere else.. In Javascript libraries..?

Re: It's insulting to read AI-generated blog posts

#495

Post by somethingsome »

alyxya wrote: post #54

I personally don’t think I care if a blog post is AI generated or not. The only thing that matters to me is the content. I use ChatGPT to learn about a variety of different things, so if someone came up with an interesting set of prompts and follow ups and shared a summary of the research ChatGPT did, it could be meaningful content to me. > No, don't use it to fix your grammar, or for translations, or for whatever el…

I don't mind either, I have way too few time to write blogposts, but I have some things that I want to share. So I focus on the content extensively, and use the llm to help with the style and the phrasing and grammar..

But I often correct the result and change some wording.

Maybe at the beginning, when I was less experienced with llms, I used more llm style, but now I find it a good compromise to convey what I think without hindering the message behind my awful writing :)

Re: It's insulting to read AI-generated blog posts

#497

Post by jibal »

palmotea wrote: post #441
alyxya wrote: post #54

I personally don’t think I care if a blog post is AI generated or not. The only thing that matters to me is the content. I use ChatGPT to learn about a variety of different things, so if someone came up with an interesting set of prompts and follow ups and shared a summary of the research ChatGPT did, it could be meaningful content to me. > No, don't use it to fix your grammar, or for translations, or for whatever el…

> I personally don’t think I care if a blog post is AI generated or not. The only thing that matters to me is the content. An LLM generated blog post is by definition derivative and bland. > I use ChatGPT to learn about a variety of different things, so if someone came up with an interesting set of prompts and follow ups and shared a summary of the research ChatGPT did, it could be meaningful content to me. Then say…

People say "by definition" when they have no idea what the phrase actually means, and their use of it is intellectually dishonest.

Re: It's insulting to read AI-generated blog posts

#498

Post by jibal »

aakkaakk wrote: post #247
alyxya wrote: post #54

I personally don’t think I care if a blog post is AI generated or not. The only thing that matters to me is the content. I use ChatGPT to learn about a variety of different things, so if someone came up with an interesting set of prompts and follow ups and shared a summary of the research ChatGPT did, it could be meaningful content to me. > No, don't use it to fix your grammar, or for translations, or for whatever el…

As long as you’re not using an autopen, because that is definitely not you! https://archive.ph/20250317072117/https://www.bloomberg.com/...

Trump uses it more than anyone.

Re: It's insulting to read AI-generated blog posts

#499

Post by jibal »

runj__ wrote: post #451
jacquesm wrote: post #248

Earlier quoted context omitted.

If I want to know about the law, I'll ask a lawyer (ok, not any lawyer, but it's a useful first pass filter). If I want to know about plumbing I'll ask a plumber. If I want to ask questions or learn about writing I will ask one or more writers. And so on. Experts in the field are way better at their field than 95% of the population, which you can ask but probably shouldn't. There are many 100's of professions, and mo…

Surely you don't always call up and pay for a lawyer any time you have an interest or question about law, you google it? In what world do you have the time, money and interest to ask people about every single thing you want some more information about. I've done small plumbing jobs after asking AI if it was safe, I've written legal formalia nonsense that the government wanted with the help of AI. It was faster, cheap…

Indeed. The level of intellectual dishonesty on this page is staggering.

Re: It's insulting to read AI-generated blog posts

#500

Post by FinnKuhn »

ManuelKiessling wrote: post #312
jihadjihad wrote: post #23

It's similarly insulting to read your AI-generated pull request. If I see another "dart-on-target" emoji... You're telling me I need to use 100% of my brain, reasoning power, and time to go over your code, but you didn't feel the need to hold yourself to the same standard?

Why have the LLMs „learned“ to write PRs (and other stuff) this way? This style was definitely not mainstream on Github (or Reddit) pre-LLMs, was it? It’s strange how AI style is so easy to spot. If LLMs just follow the style that they encountered most frequently during training, wouldn’t that mean that their style would be especially hard to spot?

It reminds me of this, but without the logic and structure: https://gitmoji.dev/
Post reply on HN