When Thanksgiving turns into an impromptu A/B testing peer review
Description
A casual selfie-style video call frame shows an older relative in a bathrobe, soft daylight from a window behind them. Caption text at the bottom reads, “You know like A/B testing”. The blurred-out face suggests the caller is earnestly trying to use tech jargon while chatting. Visually, the muted indoor colors and robe scream comfort, contrasting with the surprisingly specific product-analytics term. For seasoned engineers, the scene evokes every holiday conversation where explaining controlled experiments to non-tech family members becomes an unscheduled stakeholder briefing - highlighting the perpetual communication gap between builders and end users
Comments
22Comment deleted
Nothing says "rigorous experimentation" like Grandma asking if variant B still comes with cranberry sauce
After 20 years in the industry, you'd think we'd have solved string escaping, but here we are still explaining to junior devs why their API returns '{"data": "{\\\'valid\\\': false}"}' and watching the light leave their eyes as they discover the seventh circle of escape character hell
Ah yes, the classic JSON string - where every quote becomes a philosophical debate between your code and the parser, and you find yourself in an infinite recursion of backslashes trying to escape the escape characters. It's like Inception, but instead of dreams within dreams, it's strings within strings, and the only way out is to question whether you should have just used Protocol Buffers in the first place. Bonus points if you've ever had to JSON.stringify() a string that's already JSON, creating a matryoshka doll of serialization that makes you wonder if this is what Dante meant by the ninth circle of hell
Every time someone says, “You know, like account settings,” an architect spawns RBAC roles, GDPR consent flows, audit logs, and a migration plan - then gets told it should be a single checkbox
Translation of "you know, like a… setting": please turn my indecision into a tenant‑aware feature flag with per‑user overrides, a 5x QA matrix, and its own entry in the on‑call runbook
Stakeholder specs: 'You know, like a JSON string.' Cue the schema drift and six-month Protobuf migration
https://www.computerenhance.com/p/clean-code-horrible-performance Comment deleted
Pages like this is absolutely wrong. Comparing simple loops is pointless. In 99% slowdown was because of shit architecture, that dont use normal data structures to speedup access or computations. Comment deleted
that is literally what data-oriented development is, and is literally what he is talking about https://medium.com/@aminedirhoussi1/clean-code-horrible-performance-rust-edition-abf794a30e95 Comment deleted
Horrible performance — Rust style. 👌 Comment deleted
Oh my so much bullshit. Comment deleted
Explain plz, I feel stupid … Comment deleted
Plus one. I've got no idea what the meme here is referring to. I get it's in the context of Clean Code and this is probably the guy who wrote it, but what's the text referring to? Comment deleted
This is author of too popular Clean Code And recently he got famous for his angry rants about different "dev" things Should I make like compilation/a bunch of those videos and post them together in a single post? Comment deleted
Ah, did he do some rant about json strings? Comment deleted
Would be great 👍 Comment deleted
The line could be blurry but if performance is key, do what performance requires. For everything else, write good readable code. Comment deleted
Anything was net negative for everything Comment deleted
On a long enough timeline survival rate leads to zero. Comment deleted
Unless quantum immortality is a thing😊 Comment deleted
Oh boy then you havent seen 7zip source code Comment deleted
No not the uncle Bob slander :( Comment deleted