The Developer's Classic Time Sink Choice
Description
This is a classic 'Drake Hotline Bling' two-panel meme that humorously depicts a common developer behavior. In the top panel, the artist Drake is shown with a gesture of disapproval next to the text 'Reading documentation for 10 mins'. In the bottom panel, Drake is smiling and pointing in approval at the text 'Going down an unnecessary rabbit hole for 5 hours'. The meme satirizes the tendency for developers to avoid the straightforward, albeit sometimes tedious, task of reading documentation, which could solve a problem quickly. Instead, they often prefer to dive into a lengthy, complex, and often unnecessary investigation, fueled by a mix of curiosity, stubbornness, and the belief that they can figure it out on their own. It's a relatable commentary on developer productivity and problem-solving anti-patterns
Comments
14Comment deleted
Reading the docs is O(1), but debugging a rabbit hole is O(n!) where n is the number of undocumented features you discover and feel compelled to 'fix'
Docs: “set --sync=true.” Me with 20 years in: clone the repo, trace the commit from 2014, benchmark three kernels, whiteboard a CAP proof, write a post-mortem draft - then set --sync=true
The real rabbit hole starts when you decide to write your own documentation parser because the existing one doesn't support that one edge case you'll never actually encounter in production
Why spend 10 minutes reading the docs when you can independently reverse-engineer them with five hours and three abandoned mental models?
Every senior engineer knows the real architecture decision isn't choosing between microservices and monoliths - it's choosing between reading the three-paragraph API doc or spending your entire sprint reverse-engineering the library's source code, writing a custom wrapper, and ultimately discovering the exact solution was in the 'Quick Start' section you skipped. We call it 'exploratory development' in standup, but we all know it's just weaponized curiosity with a side of documentation allergy
RTFM takes 10 mins; RTFS confirms it after 5 hours of 'just checking'
20 YoE: instrument Envoy, tcpdump ALPN, bisect five releases to “validate assumptions” - then set the config flag the README mentioned on line 1
Architect brain: add distributed tracing, implement a bespoke backoff with jitter, skim two RFCs - then read line 1 of the README: set enable_legacy=false
Working as a IT dev in a nutshell Comment deleted
+ Comment deleted
absolutely fucking true Comment deleted
Docs are writing by a psyco on cocaine , without any context in it. Most of them I mean. All. Comment deleted
i've seen so few good docs in my life i actually somewhat struggle to see the joke Comment deleted
Indeed, real thing is usually under issue created and closed before christ, having nothing related to the problem in the title Comment deleted