Post AOZnPekjTwCo3rKixs by binarycat@pleroma.envs.net
 (DIR) More posts by binarycat@pleroma.envs.net
 (DIR) Post #AOZnPekjTwCo3rKixs by binarycat@pleroma.envs.net
       2022-10-15T01:41:43.726360Z
       
       0 likes, 1 repeats
       
       * using watchpoints and other fancy debugger stuff to understand what your code is doing* using a debugger just to step through code and print stack traces* unit test everything and then some* look at the line number where the program crashed and scatter assert() around there until you find the problem* remove code until things work to find the problem* scientific method* insert print/log statements that output the value of variables* vauge print statements* print singular characters because you don't want to loop over a string in assembly* reimplement until it works* "it's a feature"* hope