anyone else noticed that the <https://blog.jetbrai...
# getting-starteds
Stephan Schröder
06/01/2025, 10:25 AManyone else noticed that the New language features on the way - article on the Kotlin blog contains 2 error in its 6 points?
"Positional destructuring" isn't new, and "Must-use return values" is the same as "CheckReturnValue". So I assume (at least parts of) the article was written by AI and nobody (with enough technical knowledge) proofread it. Can someone fix this? It's not a good look that this is still wrong on the main Kotlin blog after a whole week.
😲 5
✅ 1
p
PoisonedYouth
06/01/2025, 2:46 PMGood catch. That is the problem trusting AI fully and saving time of checking the quality of the outcome.
l
loke
06/02/2025, 4:59 AMIf you can't trust it, what good is it? Actually writing down the words was never the hard part of writing.
👍 1
k
Klitos Kyriacou
06/02/2025, 7:52 AMGood point; I got confused when I first read that, as I thought it meant that positional destructuring was somehow going to be enhanced but couldn't find any information on it. I think this post might have been better on #C02B3PECK6E with a JetBrains staff member being notified.
👍 1
s
Stephan Schröder
06/02/2025, 8:54 AM@Klitos Kyriacou ah, thanks for the tip. I'll repost it there 👍
d
Daria Voronina [JB]
06/02/2025, 9:40 AMHi! Thank you for pointing that out — we really appreciate your attention to detail, and we’re sorry for the confusion caused by those inaccuracies. We will update the article to correct these points.
y
y
06/03/2025, 6:53 AM@Daria Voronina [JB] so were these "inaccuracies" caused because that article was generated by an LLM?
👍 1
d
Daria Voronina [JB]
06/03/2025, 7:09 AM@y No, the blog post wasn't generated by an LLM. I'm sorry if it gave that impression. The errors were due to my oversight, and I sincerely apologize for any confusion this may have caused.