OMG, the absolute HORROR of seeing a Python dev using print() statements instead of proper logging! 😱 It's like watching someone use a butter knife to fix an electrical outlet! Sure, importing that logging module takes a WHOLE EXTRA LINE of code and the UNBEARABLE AGONY of typing 'import logging' instead of just sprinkling print() statements everywhere like confetti at a debug party. But honey, when your production server is on fire at 2AM and you can't find which of your 500 print() statements is relevant, you'll be BEGGING for timestamp and log levels! The walk of shame depicted here is just *chef's kiss* PERFECTION.
To Be Fair Importing Logging Can Take Several Minutes
4 months ago
212,551 views
0 shares
python-memes, debugging-memes, logging-memes, print-memes, best-practices-memes | ProgrammerHumor.io
More Like This
Code Reuse Is The Holy Grail
5 months ago
239.0K views
0 shares
Learning YAML, I can't unsee this
2 years ago
89.0K views
0 shares
Absolutely devious question found on my Python Programming 101 Midterm uses the forbidden "=+" (also known as the "assignment operator for objects that support urnary '+'" operator)
1 year ago
108.7K views
0 shares
The Evolution Of Print Statements
8 months ago
238.8K views
0 shares
Love Python, Destroy Egos
8 months ago
316.3K views
0 shares
Pretty much me last night
3 years ago
101.8K views
0 shares
Loading more content...
AI
AWS
Agile
Algorithms
Android
Apple
Bash
C++
Csharp