Hacker News new | ask | show | jobs
by al_borland 2 days ago
If it’s for work, I always review the output. Usually, I find it to not be up to par and still end up writing it myself, maybe borrowing an idea here and there.

I need to be able to answer questions about what was built and maintain it. I’m ultimately responsible for it.

For something for myself, that won’t be deployed, it depends. If it’s an area I know, I’ll give it a quick look over to make sure some prompt injection didn’t stick something in the code that’s going to do something malicious. If it’s an area I don’t know and I want to learn, I will use the LLM as a jumping off point for how things connect, then make my own so I can actually learn it. The review might make sense, but it isn’t until I actually do it myself that I understand how it actually works… that’s when I realize what I thought made sense in the review was wrong, or at least not the full picture.