The Four Stages Of Debugging Grief

Content Write the tests before any of the code The tests all pass Run the tests, they should Fail The tests all pass

Content : Anonymous 011424(Sun)00:30:43 No.98435111 OK let's learn C make a new project in visual studio turns out thats not the correct way to do it because then it's not cross platform and i can't switch editors 280 KB JPG later start learning make, realize it's a clusterfuck of retardation but somehow copy paste something together that compiles turns out it's not the correct way to do it, the "modern" way is that you need to use premake to generate make files which then generate the visual studio solution :) ok let's write code.. wait, i have to write header files? you mean i have to have double the code for no reason other than the C build system being garbage? i want to parse a small json config file, it doesnt have to be performant. wait, how the fuck do i add libraries to my project? ok, so i have to add them and update them manually like a caveman or i have to do some git submoduling cancer, or i can use this package manager called conan that doesn't work half the time. run program - crashes that's fine it happens during development all the time let's read the helpful error message and fix what we did wrong "an error has occured" ProdrammerHumor.io

Started the day jamming to music while writing code that "totally works" – ended it staring at this electrical nightmare wondering which wire broke your production server. That poor technician is basically all of us at 4:30pm on a Friday when someone reports a "small bug" in the feature you pushed this morning. The only difference is his tangled mess is visible to everyone, while yours is safely hidden in a Git repository where only your therapist and future you will judge it.

Content We develop a program for our clients Our clients have no choice but to pay us extra to fix the bugs It is according to the requirements but has lots of bugs Our clients have no choice but to pay us extra to fix the bugs

That moment when you're mentally preparing for a complex algorithm to finish processing, only to realize you've been staring at a "Press any key to continue" prompt for the last 5 minutes. Your CPU is just sitting there at 0.1% utilization while your brain is at 100% wondering why nothing's happening. The rubber duck debugging method works great until the duck is silently judging your inability to read simple instructions.