Hacker News new | ask | show | jobs
by simonw 467 days ago
I wonder if it would work to introduce a company policy that says you should never commit consensus aren't able to explain how it works?

I've been using that as my own personal policy for AI-assisted code and I am finding it works well for me, but would it work as a company company policy thing?

3 comments

I call this the "house scrabble rule" because I used to play regularly with a group who imposed a rule that said you couldn't play a word without being able to define it.
I assume that would be seen as creating unnecessary burden, provided that the script works and does what's required. Is it better than the code written by people who have departed, and now no one can explain how it works?

The developer in question has been later promoted to a team lead, and (among other things) this explains why it's "my previous place" :)

This should be (the major) part of the code review.