Fuck you c++...!!!
TL;DR:
float a = 1.0/10.0;
float b = a*10.0;
a == b returns false
😐

Story:
A beginner of c++ here
Wrote about a 1000 lines code (spread across multiple files, m not dumb)
Passed 90% of cases
Took one and a half days to figure out what's wrong

Turns out c++ doesn't give accurate (as perceived by a human who thinks in decimal) results when comparing equality of 2 floats with ==

Shouldn't that be the first thing to be taught in schools?

This happened last November. I was on my merry way, not using Windows on my laptop. When suddenly a friend asks me to do some heavy video editing work.
And none of the softwares on Linux are as good as Premiere Pro, After Effects etc
Davinci Resolve on Linux has codec issues and is a pain to deal with

Anyway, I boot up windows and somehow it updates itself (I distinctly remember disabling the update service permanently).
So now, it bugs me every fucking minute to reboot.
Luckily I decide to finish my project before rebooting.
Coz as soon as I reboot, it throws me an error saying something like my license key couldn't be verified. One key recovery doesn't help
I have a OEM licensed Windows 10 Home that came with the laptop.

The solutions are to either recover windows, which needs a fucking 11GB download or reinstall Windows (but hey... Lenovo didn't give me a Windows License key. And I have a lot of pre setup folders on the windows drive linked to my Linux, making it a bad choice to wipe that drive). To put the cherry on the top, I have to download a software that Lenovo provides (Windows only) to download that 11GB iso.
Every sane person around me uses Linux (I only used Windows for Video Editing)
Also, living in India, 11GB is a fucking big size to download.... And the software doesn't support interrupted downloads
One more pain in the ass....
So, fuck you Windows. Fuck you Lenovo.

Living happily with elementary OS since then
Never bothered to download the Windows iso

So, this has happened to me quite a few times
I write about 100 untested lines of code (I know, bad practice) and then go ahead to test it
As expected, the program crashes
Spend hours debugging, to no avail
And then I add a print statement to check where the code stopped, and hey presto! The code completes execution
I remove the print statement, the code gets stuck

Also, the codes don't use any low level functions that might be interfered by print statements anyhow

Till today, never understood how a print statement helps codes execute properly