idea regarding #code #review:
intentionally adding #bugs into #code to check if the #reviewer discovers them.
if the reviewer does not find them, then their #review is questionable.
of course the added bugs should be removed before merging ;-)

I am wondering if a concept like this already exists ...
#codequality #softwareengineering #quality #software #git #pullrequest #mergerequest

@jakobmiksch Likely, but always ask for consent beforehand. Realizing you've served as a guinea's pig to someone else social experiment always live a bad taste. Anyway the outcome is known: if you try hard enough, you'll succeed in introducing bugs not found during review. Review is not about preventing all bugs to be introduced but catching at least a few of them..

@EvenRouault @jakobmiksch didn't go too well when someone tried it on Linux kernel and the reasons Even cited were a big part.

https://news.ycombinator.com/item?id=26887670

“They introduce kernel bugs on purpose” | Hacker News

@ctoney @jakobmiksch Thanks Chris for finding back this occurence. I knew this was a déjà-vu