Hacker News Reader

Comment by insin | Hacker News Reader

Every PR I have to review with an obviously LLM-generated title stuffed with adjectives, and a useless description containing an inaccurate summary of the code changes pushes me a little bit more into trying to make my side projects profitable in the hope that one takes off. It usually only gets worse from there.

Documentation needs to be by humans for humans, it's not a box that's there to be filled with slop.

View on HN

> The actual documentation needs to be by humans for humans.

This is true for producing the documentation but if there is an LLM that can take said documentation and answer questions about it is a great tool. I think I get the answer far quicker with LLM than sifting through documentation when looking for existence of a function in a library or a property on an object.

The documentation are for answering your questions, it’s not a puzzle to be solved. Using the reference docs assumes that you already have an understanding about the thing that is being documented and you’re looking for specificity or details. If not, the correct move is to go through a book, a tutorial, or the user guide. Aka the introductory materials.

There are UI kits that have lots and lots of elements and then each element has lots and lots of properties to tweak. I have to either guess the correct term or go through dozens of exmaples for the desired behavior. AI has saved me a lot of time in this regard. It is basically a "full text search" but far better than whatever the docs websites have built in.

seeing a lot of `const thing = doThing(); // add this line` showing up lately too.

Reply on news.ycombinator.com