Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As someone who is usually on the other side of this interaction (software engineer at a company receiving bug reports), it's much easier when people write in their own words (even if they sometimes use the wrong terms or say something which can't be true) than when they use an LLM to make things clear and correct. I want to know what you're trying to do, what you expected to happen, and what actually happened - that doesn't benefit from having an LLM rewrite it.

Sure, I use precise and technical language, but I'm still a human and I can understand what people are getting at when they use imprecise terms. But if the text passes through an LLM I can't tell whether the result actually matches the original problem or whether the LLM has made guesses or filled in blanks.

 help



Bug reports aren't so high-stakes (although poorly written bug reports can often be useless). I've got something to sell, and I want this expert to confirm that what I've built is better than what's currently available. That's a much harder approach. You want people to send bug reports. You don't want everybody to try to sell something to you. But I really think that I've solved the problem that she identified, so I want her to take a look at it instead of dismissing it as most people would probably do when a random nobody claims to have solved something. It doesn't help that this entire issue is way out of my comfort zone.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: