You'll find a bunch of tech recruiters asking you about Big O notation for the algorithm you propose. They want to look smart. Most of the times you'll smell sh

You'll find a bunch of tech recruiters asking you about Big O notation for the algorithm you propose. They want to look smart. Most of the times you'll smell shitty code, inefficient loops, slow I/O, waste of memory without formal methods. An old example from the beginning of the century: if you did matrix algebra you could have understood how to rotate an object position in 3D for a game using math but find it very hard to code. Or you could take Michael Abrash's Graphics Programming Black Book [1] and learn it anyway. You'll do fine. [1] https://www.jagregory.com/abrash-black-book/#a-simple-3-d-example https://www.jagregory.com/abrash-black-book/#a-simple-3-d-ex...