Performance
Post #6219 · source on Telegram
Meta's $500k fix: pop-up warns that the next page is slow
Description
The meme has a black background with three white text lines at the top: “* Meta paying $500k/y for senior dev *”, then “PM: page load is slow”, followed by “Senior Dev fix”. Below, a cropped screenshot of Meta’s App Dashboard shows a modal dialog titled “Submit?” with the message: “After clicking Submit, the next page may take several seconds to load.” Two buttons read “Cancel” and a blue “Submit”. The joke is that instead of improving performance, the highly-paid senior engineer simply inserts a latency disclaimer. Seasoned engineers will recognize this as the classic ‘perceived-performance’ hack that shifts expectations rather than refactoring heavy React bundles, optimizing SQL queries, or adding CDN caching
More like this
More like this in Performance →
Use J and K for navigation
Comments
13Comment deleted
Why chase TTFB when you can meet the SLA by redefining ‘B’ as ‘Button click acknowledged’?
At $500k/year, you're not paying for someone to fix performance issues - you're paying for someone experienced enough to know that managing user expectations is cheaper than refactoring the entire data pipeline that marketing insisted needed 47 tracking pixels and real-time analytics for their A/B/C/D/E/F testing framework
When your $500k/year senior engineer's performance optimization strategy is essentially implementing a loading screen with extra steps - because why fix O(n²) when you can just set user expectations to O(∞)? It's not a bug, it's a feature... with a disclaimer
Optimizing for TC over TTFB: the true senior dev dark art at FAANG scale
Couldn't move p95, so we shipped DDD - Disclaimer-Driven Development - and met the PM's SLA for expectations
Nothing fixes p95 latency like moving it from the backend to the copywriter
Junior dev: #456842 fix page loading too slowly Senior dev: loudly takes a sip of coffee APPROVE, SQUASH AND MERGE, ah, what a tough workday Comment deleted
I've literally done the same lately. I should try applying to Meta Comment deleted
Me too. I used progress bar in client code showing the random complete percentage lol. Client find that app much faster with the change. Actually no Backend code change at all lol Comment deleted
You would need to explain O complexity of this solution on the interview and the chosen algorithm Comment deleted
it's a complex task due to a variance in user environments with instability in user behavior while guaranteeing user experience we need to use O(log(10^(x*(1/x)^e^(x-(x^(x*1/x))))) equation where x is a number of lavander rafs I drank today Comment deleted
I did the same tbh. I was too lazy (it it may have been impossible anyway) to make a progress bar, so I just wrote "may take several minutes". No one complained. Comment deleted
Is it real salary in meta? Comment deleted