Skip to content
DevMeme
2910 of 7590
The Grand Creativity of Over-Engineered Code
CodeQuality Post #3216 · source on Telegram

The Grand Creativity of Over-Engineered Code

Description

The image is a two-part meme that satirizes the creative self-perception of programmers. The first part, with black text on a white background, states, 'programmers: We are creative people just as artists and writers'. The second part, labeled 'also programmers:', presents the punchline: a screenshot of a single line of code against a dark background. The code reads, 'Events.EventBus.sendEvent(Events.Events.events.defaultEvent);'. There is a small, faint watermark for 't.me/dev_meme' in the bottom corner of the code block. The humor lies in the stark contrast between the claim of creativity and the reality of writing absurdly verbose and repetitive code. The example line shows terrible naming conventions and excessive nesting, with the word 'Event' appearing five times. For senior developers, this is a painfully familiar sight from legacy systems or over-engineered enterprise frameworks (often seen in languages like Java), where poor API design and namespacing lead to such unreadable and unwieldy code

Categories

CodeQuality Enterprise DesignPatterns Architecture DeveloperExperience DX Languages

Common Tags

NamingThings DeveloperHumor NamingConventions CodeQuality CodingHumor CleanCodePrinciples CodeSmells RelatableDevExperience DeveloperSelfDeprecation InsideJokes

Comments

25
Anonymous ★ Top Pick I see the architect was a fan of the AbstractSingletonProxyFactoryBean school of naming conventions. You don't write code like that; it's procedurally generated by the tears of the maintenance team
  1. Anonymous ★ Top Pick

    I see the architect was a fan of the AbstractSingletonProxyFactoryBean school of naming conventions. You don't write code like that; it's procedurally generated by the tears of the maintenance team

  2. Anonymous

    grep -R "Event" | wc -l returned 11,342 - turns out our “ubiquitous language” is just EventBus.EventService.EventHandler in the Events module… truly domain-driven, if the domain is existential dread

  3. Anonymous

    After 15 years of arguing about microservice boundaries and event sourcing patterns, you realize the real distributed system was the Events.Events.events we named along the way

  4. Anonymous

    Ah yes, the classic 'Events.EventBus.sendEvent(Events.Events.events.defaultEvent)' - when your event-driven architecture becomes so meta it achieves self-awareness through sheer namespace recursion. This is what happens when your abstraction layers have abstraction layers, and your team's 'creative solution' to event handling looks like it was designed by the Department of Redundancy Department. At least when the inevitable refactoring ticket comes, you can defensively argue it follows the Single Responsibility Principle - it's singularly responsible for making code reviewers question their career choices

  5. Anonymous

    When every bounded context is named “Events”, you’ve built an event‑driven monolith: perfect autocomplete, zero semantics, and a code review that lasts two sprints

  6. Anonymous

    We’re creative - then ship Events.EventBus.sendEvent(Events.Events.events.defaultEvent). DDD by tautology: our ubiquitous language is just “event.”

  7. Anonymous

    Claiming artistic creativity while turning a simple event into a 50-level recursion tower - because who needs a for-loop when you have eventBus.sendEvent(eventBus.sendEvent(...))?

  8. @alhimik45 5y

    Replaces with spaces the braces in cases where braces in places cause stasis

  9. Deleted Account 5y

    Isn't it a poetry?

  10. @dsmagikswsa 5y

    Naming is always the hardest thing...

  11. Deleted Account 5y

    i hate oop

    1. @RiedleroD 5y

      I hate functional programming all my homies use Object-oriented programming

  12. @lirys 5y

    Sometimes creativity is stupidity

  13. @lirys 5y

    thy art is murder - their name fits the best here

  14. @azizhakberdiev 5y

    Event event = new Event(default_event);

    1. @RiedleroD 5y

      wrong DocumentActionListenerEvent documentActionListenerEvent = new DocumentActionListenerEvent(DocumentActionListenerEvent.DEFAULT_DOCUMENT_ACTION_LISTENER_EVENT);

      1. @sylfn 5y

        DEFAULTDOCUMENTACTIONLISTENEREVENT ---> DEFAULT_DOCUMENT_ACTION_LISTENER_EVENT

        1. @RiedleroD 5y

          FIXED

          1. @RiedleroD 5y

            fuck forgot to turn capslock off lol

  15. @azizhakberdiev 5y

    Heard you hate fp function callbackCaller(...callbacks) { let callbacksCount = 0 if(!callbacks.length) return return callbacks[n](callbacks[++n]) } function callback1(nextCallback) { if (!nextCallback) return return nextCallback } callbackCaller( callback1, callback1(function callback2() { return antoherCallback } )

    1. @RiedleroD 5y

      I have no idea what that does, but I don't like it

  16. @adhdnigga 5y

    imtelligemt

  17. @Agent1378 5y

    Sorry

  18. @Dobreposhka 5y

    !report

  19. @Agent1378 5y

    Okok

More like this

More like this in CodeQuality →
CodeQuality NamingThings DeveloperHumor
The Thinker Statue Contemplating What to Write in Git Commit Message

The Thinker Statue Contemplating What to Write in Git Commit Message

VersionControl
Self-Documenting Code Taken to Absurd Extremes with Function Name as Comment

Self-Documenting Code Taken to Absurd Extremes with Function Name as Comment

CodeQuality
Devil Promises Readable Variable Names - Child Writes ASCII Art in Code

Devil Promises Readable Variable Names - Child Writes ASCII Art in Code

CodeQuality
Use J and K for navigation