At least this is what I'm telling myself to stay sane

Content Your code gives errors when u run it Your code runs but there is no output

Content CLEAN CODE SUSELESSIF T DOESN'TWORK 34 34 WRITING CLEAN CODE SIMPORTANT MESSY CODE THAT WORKS, BUT ISN'T MAINTAINABLE, IS JUST TECHNICAL DEBT 14 14 0.1 2 10 score 55 70 85 100 115 130 2 0.1 145

Content When you don't know what the code does but you put it in anyways to see if it fixes the error

Content Coding Best Practices: code must be self-documenting, so that even a brief look at it may tell you what it does. 2 3 4 5 6 7 8 9 10 11 12 13 Me: Uhm... Like this? p 1 a 1 ? ) (f 0 a? n (n, 2 ) f (p) p ) ) f ( (! n a1 a 1e2) console. log (...p) DEBUG CONSOLE usrlocalbinnode .prime.js 2 3 5 7 11 13 17 19 23 29 31 37 41 43 47 53 59 61 67 71 73 79 83 89 97

Content SENIOR DEV PUT IT IN BACKLOG JUNIOR DEV SO WE CAN FIX IT LATER, RIGHT? SO WE CAN FIX IT LATER, RIGHT?

Content I just saw a man 5:33 AM Share his screen 5:33 AM And do the below git add - A git commit -m "Bug fix" precommit warning git commit -m "Bug fix" --no-verify git push your branch is behind git push --force 5:35 AM ProdrammerHumor.io