engineering Memes

Or Maybe Both Are One

5 hours ago 71.6K views 0 shares

The beautiful union nobody asked for but everyone's living through. You've got engineers who can build a rocket ship but couldn't sell water in a desert, and marketers who could sell sand in the Sahara but can't tell HTML from a sandwich. Separately, they're useless. Together? Still questionable, but at least now you've got a "vibe startup" where the product barely works and the pitch deck is immaculate. The real genius move is when one person tries to do both jobs—coding at night, "disrupting industries" during the day, slowly losing their sanity in between. That's the true startup spirit: maximum delusion, minimum resources, infinite coffee.

Yet Another CEO Pretending AI Takes Our Jobs

AI Programming Backend

4 days ago 255.2K views 0 shares

Yet Another CEO Pretending AI Takes Our Jobs

So the Salesforce CEO just casually announced they don't need to hire engineers anymore because AI is doing all the work, while simultaneously their company is "making billions." Cool, cool. Nothing dystopian about that at all. Here's the thing though: if AI is so productive that you don't need engineers, who exactly is building, maintaining, debugging, and updating these AI agents? Are they self-healing? Self-deploying? Writing their own unit tests and doing code reviews for each other? Because last time I checked, AI still hallucinates package names and suggests importing libraries that don't exist. The irony is that companies like Salesforce probably have entire teams of engineers working overtime to keep these "autonomous" AI agents from going off the rails. But sure, engineers are "no longer required" – just like how we were all supposed to be replaced by low-code platforms five years ago. Spoiler alert: we're still here, fixing the mess those created.

Mock Engineer

Programming

20 days ago 168.4K views 0 shares

Oh honey, someone just discovered the existential crisis that keeps traditional engineers up at night! One astronaut is about to commit space violence after realizing software developers have been casually calling themselves "engineers" without touching a single differential equation or wearing a hard hat. The drama is REAL because while mechanical engineers spent four years calculating stress loads and memorizing material properties, software devs just learned some JavaScript and suddenly they're "Senior Software Engineers" making bank. The audacity! The betrayal! The sheer disrespect to people who actually have to worry about things collapsing or exploding! But let's be honest—both groups spend most of their time Googling things and pretending they knew the answer all along, so maybe we're not that different after all. 💀

Brother From Another Mother

Programming Webdev

1 month ago 182.2K views 0 shares

The ultimate startup power couple: one person who can build anything but couldn't sell water in a desert, and another who could sell ice to penguins but can't tell HTML from a sandwich. Separately, they're walking disasters. Together? They form a vibe startup that'll either revolutionize an industry or burn through VC money in 18 months. No in-between. It's like watching two people with exactly opposite skill trees finally realize they need each other to survive. The engineer's been building "the perfect product" for 3 years with zero users, while the marketer's been promising features that don't exist to investors. Match made in startup heaven.

Overcome

Hardware Debugging

1 month ago 209.7K views 0 shares

When you order the wrong audio cable but you've already spent your entire tech budget on energy drinks and mechanical keyboards, so you enter full MacGyver mode. That beautiful abomination of adapters stacked on adapters is the physical manifestation of every developer's "it works on my machine" energy. Sure, it looks like a fire hazard designed by someone who's never heard of signal degradation, but who cares? You're basically an engineer now. Bear Grylls would be proud of this survival instinct—turning a $5 mistake into a $50 Frankenstein's monster of connectors because admitting defeat and ordering the right cable would take 2-3 business days and you need that audio working RIGHT NOW.

When You Reject The Fix

AI Programming Debugging Testing

1 month ago 277.0K views 0 shares

AI tools confidently rolling up with their "perfect" solution to your bug, and you—battle-scarred from years of production incidents—just staring them down like "not today, Satan." That icon is probably ChatGPT, Copilot, or some other AI assistant thinking it's about to save the day with its auto-generated fix. But you know better. You've seen what happens when you blindly trust the machine. Last time you accepted an AI suggestion without reading it, you accidentally deleted half the database and spent the weekend explaining to your manager why the company lost $50k in revenue. So yeah, the engineering team says "NOT YET" because we're still debugging the debugger.

Twitter Algorithm Github Issue

AI Python StackOverflow Linux Debugging

2 months ago 269.7K views 0 shares

Simple Cube vs. Sci-Fi Concept Art

Programming Webdev Agile Gamedev Frontend

4 months ago 411.7K views 0 shares

The perfect visualization of how product managers describe features vs. how engineers implement them. Left: "Just a simple cube, how hard could it be?" Right: The same damn cube with one unnecessary line that took 8 meetings, 3 design revisions, and somehow doubled the development timeline. The sci-fi concept art is just corporate speak for "we added a groove that serves no purpose but looks techy." This is why I drink coffee by the gallon.

No Jira No Slack

Agile Devops Programming

4 months ago 372.2K views 0 shares

Turns out 4,500 years of engineering brilliance didn't require a single Jira ticket or Slack channel. The ancient Egyptians just... did the work? No daily standups about "blockers" or 47-message threads debating the optimal stone-dragging methodology. No PM asking "can we squeeze one more obelisk into this sprint?" Just thousands of people moving massive rocks with nothing but determination, physics, and probably a terrifying project manager with actual whips instead of digital notifications. Makes you wonder if we've actually evolved or just created digital bureaucracy to avoid the real work.

Code Works, Business Doesn't

Webdev Agile Programming

4 months ago 273.7K views 0 shares

The classic startup death spiral visualized in three painful steps. You've got 250 domain names because "what if we need them someday?" Then somehow you managed to ship 17 actual apps—impressive engineering, terrible focus. But the grand finale? Zero paying users. That beautiful moment when you realize your brilliant technical solutions are solving problems nobody wants to pay for. It's the perfect illustration of the engineer's fallacy: thinking that elegant code automatically translates to business success. Spoiler alert: users don't care about your perfect microservice architecture—they care about their problems being solved. And apparently, none of your 17 apps across 250 domains managed that particular trick.

When AI Writes Your Production Code

AI Devops AWS Programming Debugging

5 months ago 357.0K views 0 shares

So AWS proudly announces that AI writes 75% of their production code, and then their engineers wonder why everything's on fire? Classic. When "Claude" (their AI) responds with enthusiastic agreement to fix production issues, it's basically Elmo cheerfully presiding over the flames of digital hell. Welcome to the future of cloud computing, where your critical infrastructure is maintained by the digital equivalent of a pyromaniac puppet who's just happy to be included in the conversation. Next time your AWS-hosted site goes down, remember: it's not a bug, it's an AI-generated feature!

Tricking Rocks Into Thinking

Hardware Programming Debugging

5 months ago 378.8K views 2 shares

Your hacky code works because we're all just manipulating fancy rocks. CPUs are literally silicon (sand) that we've meticulously flattened, etched, and zapped with electricity until they somehow process logic. So next time your questionable regex or bizarre workaround functions perfectly, remember: you've successfully communicated with an electrified rock. The universe is absurd and your code is just one more layer of this cosmic joke.

Browse