It would be easy depending on your company’s git practices. Complicated git workflows can leave room for you to slip stuff in unnoticed or misattributed. I mean, it still has to pass a review, but a lot of the devs I work with don’t review that closely. Could just assign a lazy dev to the review and increase your odds of getting it through.

It’s not the same, and you kinda answered your own question with that quote. Consider what happens when an object defines both dunder bool and dunder len. It’s possible for dunder len to return 0 while dunder bool returns True, in which case the falsy-ness of the instance would not depend at all on the value of len