Skip to content
DevMeme
6948 of 7590
Disgust Face at 0.000438 Seconds of Unnecessary Memory Allocation
Performance Post #7614 · source on Telegram

Disgust Face at 0.000438 Seconds of Unnecessary Memory Allocation

Description

A close-up black and white photograph of a man's face showing an expression of pure disgust, with annotated red markers pointing to specific facial features: '1. nose wrinkling' and '2. upper lip raised'. The right side has bold red italic text reading 'How I look at your code when it has 0.000438 seconds of unecessary memory allocation'. The clinical annotation style mimics scientific facial expression analysis (like Paul Ekman's FACS system), applied to the absurdly specific scenario of detecting sub-millisecond memory allocation waste, perfectly capturing the obsessive performance optimization mindset

Categories

Performance CodeQuality CodeReviews

Common Tags

MemoryManagement PerformanceOptimization CodeReview MemoryLeaks CodeOptimization CodeQualityMetrics PrematureOptimization

Comments

21
Anonymous ★ Top Pick This is the face of every Rust developer reviewing a Java codebase, except they make this expression approximately 0.000438 seconds into reading the first file
  1. Anonymous ★ Top Pick

    This is the face of every Rust developer reviewing a Java codebase, except they make this expression approximately 0.000438 seconds into reading the first file

  2. @blue_bonsai 7mo

    Linus Torvalds is a vibe coder

    1. @chupasaurus 7mo

      proof of any code he made in past 2 years?)

      1. @sysoevyarik 7mo

        Message stated he is a vibe coder, not the coder.

  3. @blue_bonsai 7mo

    No wonder they update the kernel like every second. They need to fix the trash. 😁

  4. @blue_bonsai 7mo

    Linus Torvalds is a viber

  5. @blue_bonsai 7mo

    A vibrator

    1. dev_meme 7mo

      a what

      1. @agonyship 7mo

        Yes

    2. @gongchanM1 7mo

      "there 34 rules Linus follows during development. google for 'Linus Torvalds r34' "

      1. @blue_bonsai 7mo

        Ok

  6. @blue_bonsai 7mo

    Ugh

  7. @blue_bonsai 7mo

    A vertebrate

  8. @blue_bonsai 7mo

    A variable

  9. @Agent1378 7mo

    Contempt

  10. @blue_bonsai 7mo

    Holy SHIT

  11. @SamsonovAnton 7mo

    How I look at your kernel installation script which looks up /etc/modules-${oldver} for enabled entries by invoking grep for each of several thousands of modules in the newly installed kernel, spending more than 30 seconds on what can be done in less than 0.5 seconds when implemented properly (but "who cares?" and "who needs that?"). 🤬

    1. @azizhakberdiev 7mo

      "premature optimization is the root of all evil"

      1. @SamsonovAnton 7mo

        "We will refactor after the first release". Ten years after the release: 🤡

        1. @azizhakberdiev 7mo

          they never said how long after

  12. @a_646_man 7mo

    average age of "for now" and "remove after" comments reaching 20+ years now 🌚

More like this

More like this in Performance →
Performance MemoryManagement PerformanceOptimization
Stuffing Kimi K3 2.8T Into a 3090

Stuffing Kimi K3 2.8T Into a 3090

AI ML
Rust vs HTML5 Memory Safety Comparison Table

Rust vs HTML5 Memory Safety Comparison Table

Languages
You Thought That Was a Uniform Address Space You Were Accessing?

You Thought That Was a Uniform Address Space You Were Accessing?

LowLevelProgramming
Use J and K for navigation