logoalt Hacker News

jmccafyesterday at 2:48 PM2 repliesview on HN

If you push a change, or you approve, you're responsible for the change and its effects later. Regardless of size. If change is too big, tell your teammates its too big to review and to refactor to bite-size with their great coding agents. Use AI models also for review of large changes, consider a checklist . Setup CI and integration tests (also can be AI assisted)


Replies

JTbaneyesterday at 7:49 PM

Agreed, and something will go wrong (as every junior has experienced). You cannot lay blame on the AI when git blame shows your name.

MSFT_Edgingyesterday at 6:24 PM

Oh there's plenty of CI, linting, etc. Half of which is not properly plumbed in.

show 1 reply