Yoda conditions

All linters and C compilers emit a warning when an assignment is made in a condition. There are zero reasons to use that ugly and unnatural Yoda notation in 2019.

One of the best bugs I've ever seen was in the game Dungeon Crawl Stone Soup. It's a roguelike, and a venerable old one at that, so the codebase is quite tangled and convoluted, with logic for everything in every corner. One of the worshippable gods in the game is Xom, god of chaos, whose effects are just as likely to kill their worshipers as to help them (frustrating for those who might actually want to win, but always good…

I use Xcode for development and it already warns against assignment within conditions[0]. gcc also warns against it[1]. Python just errors out all together[2]. I don't have my Windows instance up with Visual Studio but I'm fairly certain that it too notifies you of assignments within conditions. So the question is, why would you sacrifice readability to help solve a non-issue? [0]https://www.dropbox.com/s/sjtefd55mwigq3y/Screenshot%202014-... [1]https://www.dropbox.com/s/yx01tdeykpkespv/Screenshot%202014-…

There is a fantastic list of similar jargon: https://blog.codinghorror.com/new-programming-jargon/ At work, we reference these all the time, especially the Ninja comments and the Heisenbugs.