To whoever does that, I hope that there is a special place in hell where they force you to do type safe API bindings for a JSON API, and every time you use the wrong type for a value, they cave your skull in.
Floats are only great if you deal with numbers that have no needs for precision and accuracy. Want to calculate the F cost of an a* node? Floats are good enough.
But every time I need to get any kind of accuracy, I go straight for actual decimal numbers. Unless you are in extreme scenarios, you can afford the extra 64 to 256 bits in your memory
From someone in computer networking classes:
"I don't use GitHub. This is too complicated"
Like bruh. The instructions are right there in the readme.
There's also the time where we were asked to read temperature from a sensor, and everyone went straight to chatgpt. Meanwhile, first search result, full repo with full noob instructions.
Writing prompt right here