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

id.expect COEs to be coming up with AI code action items though, not to have more thorough human checks


There's an explicit tension: SWEs would love that as a "get out of jail free" card, but their management chain is being evaluated by ajassy on AI/ML adoption. Admitting AI code as the root cause of a CoE is gonna look really bad unless/until your peers are also copping to it.


I think its a question 2 or 3 in a why chain, but 4 and 5 need to be why the agent screwed up, and there needs to be action items that are around giving the ai better guardrails, context, or tooling.

"get a person to look at it" is a cop-out action item, and best intentions only. nothing that you could actually apply to make development better across the whole company




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: