alt Hacker NewsI also love the visualizations but I'm getting heavy LLM vibes from the prose:
> One setting drives this,...
> The cost is now about the rows you actually touch, not rounds times table size.
Etc.
I get the brain scramblies [1] from trying to parse this writing style at work so I hate to see it elsewhere. Apologies if I'm wrong. But if I'm not then OP don't use an LLM to write for you. It's hazardous to your reader's health [2].
[1]: https://www.youtube.com/watch?v=ipUJq-odt5Q
[2]: https://discourse.haskell.org/t/how-to-keep-enjoying-program...
Replies
I've lost count recently of how many times Claude has given me something in this style that I can't understand, and then I ask it to rework parts of it, and then it tells me that the original things it claimed weren't actually quite right anyway.
I'm starting to read it as a sign of low LLM effort not just low human effort. It seems most common when one few-sentence prompt leads it to generate 4+ paragraphs (and the longer the output, the worse the odds). Prompting to dig into each resulting paragraph one by one, to make them readable, makes it do higher-effort deep dives.
It really is unreadable. I guess you're supposed to skim an AI summary. Too bad you'd never see the visualizations that way.
I may be in the minority but I didn't get LLM vibes from this. Not enough to be bothered by it, at least
I have tried out the alpha releases of 2.0 and I got slopcoded vibes from it.
> It's hazardous to your reader's health [2].
Just because some guy on some forum said that doesn't make it true. That's not how you establish facts regarding health claims.
I get the brain scramblies [1] from trying to parse this writing style at work so I hate to see it elsewhere
More and more really important and useful information will arrive like this for us to consume. There's no way around. So this is a disservice for newcomers that could come and go unscathed but instead is crippled by these kinds of comments that brings nothing of substance to the table and has the potential to make them hate something they otherwise wouldn't even notice.
Also, from https://news.ycombinator.com/newsguidelines.html:
Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.
Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.My manager was previously whining about something similar when it comes to generated reports and I just pulled down all of his writing and made the LLM write in his style, he is really content now. Do the same using your own writing and you wont have to be offended
I noticed some AI tells, but found overall the article not too bad. It did seem to waffle at times though.
> Storing a lake as thousands of 1 MB Parquet files is a bad practice anyway, and 2.0 does not rescue it.
The "does not rescue it". No human would write like that.
> I'll explain what that means on a table you already know.
No I don't already know that table.
Also
> and claims 40x on graph reachability
Is really hard to parse.
The section on recursive CTEs wasn't well written and didn't explain how the optimisation was done. This article explains how the recursive CTEs were improved https://duckdb.org/2026/08/25/how-duckdb-runs-recursive-ctes...