magic_lobster_party

Static lifetimes confused me when I started learning rust. The error message guides the developer to the wrong direction.

It took me a while to realize that just using Arc is sufficient in most of those cases.

I think the problem is that many introductory examples use unwrap, so many beginner programmers don’t get exposed to alternatives like unwrap_or and the likes.

I’m a OOP programmer.

I wrap everything within Arc<Mutex<>>.

I’m a happy dev.

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”.

The flaw also highlighted a social engineering exploit. It’s not the first time some vulnerability has entered open source software due to social pressure on the maintainer. Notably EventStream exploit.

This is difficult to account for. You can’t build automated tooling for social engineering exploits.

How do you prepare the USB stick without a secondary computer? Or do you have one lying around in case of emergencies?

&& git push --force

Maybe.

When using a random pivot, the worst case becomes exponentially more unlikely the larger the n. The O notation only cares about the complexity when n approaches infinity. So when n approaches infinity, the likelihood of O(n^2) performance approaches 0 (and the likelihood of O(n log n) approaches 1).

I think it’s fine to call it O(n log n).

The quadratic equation is the basis for most other math and physics. It’s used all the time.

The good thing about quicksort is that it’s a good demonstration of an O(n log n) algorithm, and that’s about it.

Full vibe development

”All features are xy problems”

”PM adds new features to the sprint faster than they’re solved”

”Each release require two weeks of testing”

”Each release introduces new bugs for customers despite the two weeks of testing”

They will resort to vibe debugging