magic_lobster_party

Job description: we’re looking for someone with experience in deploying cutting edge machine learning systems, preferably PhD.

Actual job: Excel spreadsheet

And after all that it is discovered that it was the wrong solution all along because the requirements were poorly specified, so the process must be started all over again

Product Manager: Make a step by step guide of how they think the lightbulb is going to be fixed without explicitly mentioning the broken lightbulb.

jQuery got popular because Internet Explorer, Firefox, Chrome and other browsers weren’t exactly cross compatible. Writing vanilla JS was risky business in that sense.

It also supported AJAX across all major browsers, which meant the website could make API requests without reloading the entire page. It was super revolutionary to press a button and it only changed a part of the page.

Then Angular and React took it a step forward and that’s where we are now.

JavaScript frameworks are invented because pure HTML and CSS suck for dynamically loaded pages, and vanilla JavaScript suck in general.

What’s not shown is that the car doesn’t have an engine. Management was really eager to release it to the customer. Don’t worry, it’s planned to get fixed later (spoiler: it’s never going to get fixed).

Rust and Cargo were built to be in a symbiosis with each other.

NPM is an afterthought of a rushed language.

Then you haven’t seen bad documentation (or had that sex you regret).

There’s also ”we do machine learning”, which usually translates to ”someone trained an SVM model 10 years ago”.

Google seem to be particularly bad at this. They did the same with Tensorflow. It was kind of the de facto deep learning framework until Google decided to deprecate everything. Everyone responded by switching to Torch instead.