⣿⣿⣿⣿⣿⣿⣿⣿⣿⠿⠿⣿⣿⣿⣿⣿⣿
⣿⣿⣿⣿⣿⣿⣿⠿⠁⠀⠀⠙⣿⣿⣿⣿⣿⠇
⣿⣿⣿⣿⡏⠩⠂⠀⠀⠀⠀⢀⣿⣿⣿⣿⣿⣿
⣿⣿⣿⡇⠠⠂⠂⡐⠄⠀⠀⢶⣿⣿⣿⣿⣿⠇
⣿⣿⣿⠇⠀⠄⠜⡄⢠⠀⠀⠈⣿⣿⣿⣿⣿⠇
⣿⣿⣏⠀⠠⠔⠐⠓⠀⠄⠀⡀⠈⢿⣿⣿⣿⣿
⣿⣿⡇⢀⠀⠀⠀⠀⠀⠀⠀⢀⠀⠀⠹⢿⣿⣿⠇
⣿⣿⠇⠀⠂⠀⠀⠀⠀⠀⠂⢰⣿⣦⠄⠈⣿⣿
⣿⣿⣦⠄⠁⠀⠀⠀⠀⠀⠀⢸⣿⣿⣶⣆⣿⣿
⣿⣿⡟⠀⠀⠀⠀⠀⠀⠀⠀⠈⣿⣿⣿⣿⣿⣿⠇
⣿⣿⣷⣤⠀⠀⠀⡀⡀⠀⠀⢰⣿⣿⣿⣿⣿⣿
⣿⣿⣿⢟⠀⠀⢡⡇⠀⠀⠀⢼⣿⣿⣿⣿⣿⣿
⣿⣿⣏⠠⠀⠀⣼⠠⠀⠀⢐⣿⣿⣿⣿⣿⣿⣿
⣿⣿⣿⠰⠀⣸⣿⡫⠀⠀⢸⣿-⣿⣿⣿⣿⣿
⣿⣿⣯⠀⠀⢸⣿⠆⠀⠀⢿⢿⣿⣿⣿⣿⣿⣿
⣿⣿⣿⣶⣶⣿⣿⡅⠀⠀⠀⢉⣹⣿⣿⣿⣿⣿
⣿⣿⣿⣿⣿⣿⣿⣿⣷⣶⣿⣿⣿⣿⣿⣿⣿

Trying to make code simpler while creating a program is a path to failure such as those. First, make sure it works, and only then try to make it more elegant, optimized and simpler. One step at a time.

As a rule, when in doubt, just make it so your variables only serve one purpose, not more, and always give them a unique name, and don't be afraid of duplicates. If you don't, those kinda things are bound to happen when you're too tired to remember how everything works and interacts with itself. If you do, you will just lose a small bit of processing power but save yourself a lot of trouble. The later is always preferable to being ♥♥♥♥♥♥♥♥♥♥ when you're trying to understand what went wrong in dozens of files interacting with each other, and you can always optimize later on when everything is working correctly.

Ah, yes, the all-time classic of spaghetti code. Reusing the same variable names whilst failing to correctly see the scope you're working in. This is peak level programming failure that can lead to serious bugs, and at the same time it's not always easy to avoid accidentally overwriting variables unless all of your code is 100% object-oriented.

L + ratio + maidenless + tarnished + touch grace

Never trust the french - Dan Brownies The Da Vinci Codex