Hacker News Reader

I'm sorry but people who let an agent run on prod deserve what they get. Basically even saying you would do that should disqualify you from working in IT in the way saying "I like to drink when I'm working" should disqualify you from airtraffic control.

View on HN

I haven't been following too closely, but is there even a reason to do this? What are the benefits of allowing production access versus just asking for a simple build system which promotes git tags, writes database migration scripts, etc.? From my perspective, it should be easier than ever to use a "work" workflow for side projects, where code is being written to PR's, which could optionally be reviewed or even just auto approved as a historical record of changes, and use a trunk-based development workflow with simple CI/CD systems - all of which could even be a cookie cutter template/scaffolding to be reused on every project. Doesn't it make sense now more than ever to do something like that for every project?

> I'm sorry but people who let an agent run on prod deserve what they get.

The problem is that whatever consequences come of it won’t affect just them. You don’t really have any way of knowing if any service you use or depend on has developers running LLMs in production. One day not too far off in the future, people who don’t even like or use LLMs will be bitten hard by those who do.

Reply on news.ycombinator.com