>>105937422
It's more like: frustrated sales guy could sell more and thus make himself more money if somehow we could do X when Y. He takes longtime backend engineer out for a beer and tries to convince him. Backend engineer doesn't even really understand why it would be a big deal. Idea is then fed into Product Design/Management who don't understand the fundamental point of the idea and who then spin in circles with the Figma crowd to aggrandize everything into some "game changer" yet that misses the original point. Then sales engineering gets involved because they want to spin up a limited proof of concept eventually but can't see how $thing solves $problem and don't say anything but report back to sales that shit's fucked.

The sales guy loops back in with backend, who were completely unaware of the unfolding drama, who take a look at it, and say "hey, don't get too worked up about it, it can't happen without some new middleware layer that nobody is going to write or purchase". But that fails to satisfy sales, who then go nuclear.

Backend eventually whips up a view of the data that solves the original problem, then eventually the heated politics fizzle out, then middle management pajeet grind to consume the data and cut and paste together a broken frontend, which is then spit polished by the Figma faggots, barely documented, and rubber stamped by QA before being pushed to production Friday night so some pajeets can claim something about sprints. This all then happens 3.14 more times as scaling issues hit. The end.

>>510148460
>>510150058
keep me posted too brehs

Why is everything so bloated and clunky these days? Can't AI fix this?

this joke is literally too smart for /tv/
holy moly

edit: Nice, trips