The eternal struggle of every developer who knows better but chooses chaos anyway. Sure, debuggers exist with their fancy breakpoints and variable inspection, but there's something primitively satisfying about littering your code with print("HERE")
, print("WHY GOD WHY")
, and the classic print("AAAAAAAAAAA")
. It's like using a stone axe when you have a chainsaw in your garage. We all know we should use proper debugging tools, but smashing that red button and turning our console into a Jackson Pollock painting of random values just hits different. Proper debugging techniques? In this economy?
All The Print Statements
1 month ago
142,205 views
1 shares

debugging-memes, print-statements-memes, console-output-memes, lazy-debugging-memes, developer-habits-memes | ProgrammerHumor.io
More Like This
the bug becomes a feature
3 years ago
15.8K views
0 shares

Are interruptions really worse for programmers than for other knowledge workers?
3 years ago
21.8K views
0 shares

Not today junior.. not today...
2 years ago
6.9K views
0 shares

Kill The Feature, Not The Customer
3 days ago
81.1K views
0 shares

Loading more content...