Whose idea was to name FaaS "serverless"? It's just a terribly misleading name which can confuse newcomers.

Anyone else have the ritual of searching for curse words in code prior to committing & pushing your changes?

Stop using the term "AI" for everything. That's it.

Oh PHP, such a wonderful t̶e̶m̶p̶l̶a̶t̶i̶n̶g̶ ̶e̶n̶g̶i̶n̶e̶ language to n̶o̶t̶ program in.

NPM and the whole dependency tree for JS packages should burn in the pits of hell.
Let's pretend that uninstalling a single (albeit larger) module didn't take 8 minutes and that it didn't spit out 20 warnings from a total of 277 (HOLY FUCK) related packages.

How can you guys (JS-only devs) handle this ?!

Someone just left a small turd in front of the toilet bowl and stepped on it so now there's smeared shit on the floor tiles in a toilet stall.

Must be all the caffeine I guess.
Oh, and don't stand up too fast after taking a shit apparently, since I can't fathom how that happened.

Pro tip: Don't cheap out on dongles for newer macbook models.. Bought a (somewhat) working Chinese dongle with 4 ports. Fire hazard and I think my 13" mbp just farted a fireball

For the love of GOD, if you're an architect or someone in the position where you can make drastic changes to the overarching design of a software system, if you're so keen on enforcing something "cool" just because you've read about it in a blog post/seen it on a youtube video, READ ABOUT IT THOROUGHLY, as in, pick up a fucking book or do actual research. An architect overseas just informed us that a whole legacy PHP application (a fucking monolith with a dysfunctional database, yes, I think someone demented designed it) should be rewritten to a microservice architecture (without a messaging broker, just plain API interaction through HTTP) AND WE'RE KEEPING THE DATABASE WHICH BEGS TO BE PUT DOWN FOR GOOD. So now we're gonna have a clusterfuck of tons of PHP microservices (Q_Q) which interact through plain HTTP APIs (swagger's gonna be put to a test) and all have a single broken database in the center. Talk about a microlithic design. Jesus Christ.

The company that I work for just opted for PHP in favor of Elixir, Node and Scala(Akka really) for building a high-concurrency system, because we have more people who work with PHP (mediocre skill really). How do we convince our team leads and higher-order beings by the hierarchy to try newer (or at least better suited) technologies? Good luck popening and pthreading stuff on this project I guess.