Bugs
Post #6949 · source on Telegram
Staring into the abyss of unreadable code
Description
A screenshot of code written in a Go-like syntax is displayed against a dark purple background. The code is filled with syntax errors, typos, and logical flaws, such as 'elapsed = do-DoSomething()', 'default_intervaral', and a function returning an undefined variable. Overlaid on the right side of the code is a jumble of corrupted text and glitched characters, creating a chaotic effect. Peeking through this visual noise are two large, white, pixelated cartoon eyes, staring intently at the flawed code. The meme visually represents the surreal and painful experience of trying to debug or comprehend poorly written, buggy, or 'cursed' code, where the code itself seems to be falling apart while being watched
More like this
More like this in Bugs →
Use J and K for navigation
Comments
22Comment deleted
This isn't just legacy code; it's a cognitohazard that causes compiler errors just by looking at it. The bug isn't in the code, the bug is the code
Somewhere between the ASCII eyes and “time.Sleep(3s)”, go vet filed for burnout and go fmt just pretended the file never existed
After 15 years of debugging race conditions and mysterious timing bugs, you finally understand why Go's time.Sleep() takes a Duration instead of milliseconds - it's measuring how long until your sanity completely unravels and the code starts staring back at you
When your performance monitoring is so aggressive it literally watches your every function call. This Go code's timing instrumentation has achieved sentience and is now judging your 3-second sleep() calls with the disappointed gaze of a senior architect reviewing a junior's first PR. The eyes say 'I see you measuring elapsed time... but have you considered using context.WithTimeout instead?'
Protip: if your Go “benchmark” sets time.Second = 5 and measures with Sleep, the only throughput you improved is how fast the code reviewers’ ASCII eyes roll - wrap time behind an interface or enjoy flaky tests forever
To measure elapsed time, just Sleep(5) - because in prod, stakeholders love 'responsive' UIs that ponder existence
Nothing says rigorous benchmarking like resetting the clock in PrintElaped, calling time.Sleep(time.Duration), then wondering why pprof reports 100% of your time in logging
bro invented new unicode (and words (and syntax)) Comment deleted
tittime.Now() Comment deleted
Elaped? 🤓 Comment deleted
El Aped Comment deleted
was this the only problem you noticed? Comment deleted
The only problem that is related to public API. The internals are not relevant, as long as it works (I didn't tested). Comment deleted
I am certainly sure this is just AI slop again Comment deleted
why did you have to say "certainly sure" as if there is any doubt in the first place Comment deleted
Lmao Comment deleted
how about instead of variations of "elapsed" we instead talk about Comment deleted
tit time 😏 Comment deleted
NOW Comment deleted
:3 Comment deleted
me when i take estrogen: Comment deleted
Does it compile? Comment deleted