Coding4Food LogoCoding4Food
HomeCategoriesArcadeBookmarks
vi
HomeCategoriesArcadeBookmarks
Coding4Food LogoCoding4Food
HomeCategoriesArcadeBookmarks
Privacy|Terms

© 2026 Coding4Food. Written by devs, for devs.

All news
IT DramaDev Life

75MB Payload Drama: Are Developers 'Incompetent' or is Marketing at it Again?

March 5, 20263 min read

A LinkedIn warrior blasts a website for a 75MB payload and using jQuery, calling the devs 'incompetent'. Here's how the Reddit hivemind roasted his toxic ego.

Share this post:
programming, html, css, javascript, php, website development, code, html code, computer code, coding, digital, computer programming, pc, www, cyberspace, programmer, web development, computer, technology, developer, computer programmer, internet, ide, lines of code, hacker, hacking, gray computer, gray technology, gray laptop, gray website, gray internet, gray digital, gray web, gray code, gray coding, gray programming, programming, programming, programming, javascript, code, code, code, coding, coding, coding, coding, coding, digital, web development, computer, computer, computer, technology, technology, technology, developer, internet, hacker, hacker, hacker, hacking
Nguồn gốc: https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-fault. Nội dung thuộc bản quyền Coding4Food. Original source: https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-fault. Content is property of Coding4Food. This content was scraped without permission from https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-faultNguồn gốc: https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-fault. Nội dung thuộc bản quyền Coding4Food. Original source: https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-fault. Content is property of Coding4Food. This content was scraped without permission from https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-fault
Nguồn gốc: https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-fault. Nội dung thuộc bản quyền Coding4Food. Original source: https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-fault. Content is property of Coding4Food. This content was scraped without permission from https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-faultNguồn gốc: https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-fault. Nội dung thuộc bản quyền Coding4Food. Original source: https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-fault. Content is property of Coding4Food. This content was scraped without permission from https://coding4food.com/post/75mb-payload-drama-incompetent-devs-or-marketing-fault
drama devweb performancejquerytối ưu websitefrontend dev
Share this post:

Bình luận

Related posts

ai generated, data centre, computer, server, rack, technology, digital, processor, server, server, server, server, server
IT DramaAI & Automation

r/LocalLLaMA Drama: Wrapper Dev Gets Roasted for Calling Local AI Users 'Broke'

A popular tech YouTuber caught massive heat from the AI community after claiming local LLM enthusiasts are just too broke to pay for API keys.

Mar 112 min read
Read more →
scam, alert, cybersecurity, phishing, fraud, hacker, crime, attack, warning, cut out, scam, scam, scam, scam, scam
IT DramaTechnology

Wikipedia Goes Read-Only: The Old-School XSS Worm That Nuked Admin Accounts

Wikipedia was forced into read-only mode after a classic XSS worm compromised admin accounts. Let's unpack this dumpster fire of jQuery and PHP memes.

Mar 63 min read
Read more →

Was casually scrolling through LinkedIn looking for some toxic tech bro inspiration when I stumbled upon a juicy rant. Some guy decided to blast a corporate site (allegedly Subway) for loading a whopping 75MB of assets on page load, while casually roasting them for using jQuery in the year of our lord 2026, dropping the ultimate bomb: "such incompetent developers."

The 75MB bandwidth-guzzling dumpster fire

So here's the tea. A LinkedIn warrior opened up his DevTools, saw 75MB of raw data being downloaded, and noticed the ancient relic known as jQuery sitting in the network tab. Instead of just pointing out the bloatware, he decided to publicly execute the dev team with a lovely concluding remark: "such incompetent developers." Classic ego-tripping.

This spicy take immediately got dragged over to Reddit, and of course, the dev community went absolutely wild.

What the Reddit hivemind had to say

Take 1: Blame the Marketing team! A ton of veterans immediately called BS on blaming the devs. 99% of the time, this is a CMS issue where some marketing intern uploaded a massive, uncompressed 50MB hero image. Automating dynamic image compression on a CMS is a massive headache. Even a marketing guy chimed in to self-report: "Yeah, I doubt the dev is sourcing that file. This probably came from marketing."

Take 2: The toxic Tech Bro ego The community dragged the OP for their lack of social skills. Finding a legitimate performance issue is cool, but ending your post with "incompetent developers" just screams unhoused ego. "Imagine finding a legit issue and finishing your post with 'such incompetent developers'. I love my community, keep with those social skills guys," one user sarcastically noted.

Take 3: Leave jQuery alone! People are tired of the "jQuery is bad" meme. Is it strictly necessary nowadays since vanilla JS caught up? No. Does it mean the site is garbage? Also no. Big corporate websites are just slop factories by nature, regardless of the framework.

Take 4: 5G covers a multitude of sins One guy casually mentioned his company has a 129MB video on their homepage. With modern pocket supercomputers and 5G networks, a lot of this heavy bloatware just slips past QA unnoticed because it loads surprisingly fast anyway.

The C4F Takeaway

Look, guys. What did we learn from this mess?

First, before you go full keyboard warrior on your fellow devs, remember that large systems are chaotic. That 75MB disaster you're looking at is probably completely out of the frontend dev's hands.

Second, keep your ego in check. Being a smug jerk on LinkedIn doesn't make you a 10x developer. It just highlights your terrible soft skills.

And finally, stop framework shaming. If jQuery is paying the bills and keeping the servers running, it's doing its job. Good code is code that makes money.

Source: Reddit - Saw this on Linkedin. How should this be intreperted?