I get the impression that Nvidia employees don't care too much - I started seeing fully AI-written "documentation" on some of their smaller projects more than a year ago (i.e., before it was even slightly a good idea).
Yeah lol it’s basically the only reliable way to know how things work. Pre-AI, I read documentation for libraries that I used almost every day.
And now with AI I’m using it to fact check Claude. And still reading it for myself to understand why other peoples code is written a certain way. It’s basically the most important thing to reference when coding.
Sure today Claude can just read the library code and tell you what a function does or how to do something. But it still won’t tell you why something is a certain way or won’t figure out specifically-designed usage patterns as reliably as the author telling you “this is an example of doing x”
claiir · · focus · HN ↗
Damn even Nvidia is putting out fully Claude-written articles.
daemonologist · · focus · HN ↗
DonsDiscountGas · · focus · HN ↗
WD-42 · · focus · HN ↗
The heck you talking about? How do you think we wrote software for the last 50 years?
californical · · focus · HN ↗
And now with AI I’m using it to fact check Claude. And still reading it for myself to understand why other peoples code is written a certain way. It’s basically the most important thing to reference when coding.
Sure today Claude can just read the library code and tell you what a function does or how to do something. But it still won’t tell you why something is a certain way or won’t figure out specifically-designed usage patterns as reliably as the author telling you “this is an example of doing x”
stevemk14ebr · · focus · HN ↗
californical · · focus · HN ↗
You need the documentation to know why certain things work a particular way, or to know why some relationships or methods are the way they are