Hahaha. I love seeing someone get a heap corruption for the first time and try and track it down with prints or stepping through debug only to find the magic floaty point where the system detects the corruption. Their face when I tell them that the system detecting the corruption and the actually corruption happening aren't the same place is absolutely priceless. Using a mem checking tool like valgrind has been amazing for me. Especially with WSL, because valgrind is waaaay better than Dr. memory and WSL is super easy to setup and use with CLion.