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.

This is why I rarely use AI for coding. How to put my thoughts into code is not my main concern. My main concern is that another person should understand my thoughts when reading the code.

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

Creator of curl just made a rant about users submitting AI slop vulnerability reports. It has gotten so bad they will reject any report they deem AI slop.

So there’s some data.

There’s also the argument whether games really need that high of a budget. It feels like there’s little correlation between the budget of a game, and its success (or quality).

Sony could’ve invested in five or ten more Helldivers 2 scaled games, instead of wasting it all on the Concord flop.

What’s more frustrating is when the password creation page is silently cutting off too long passwords and don’t inform you about it.

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

It wasn’t just this though; the tool itself lacks the intent, context, and limitations of what we’re doing. It doesn’t have other aspects of the project, influences, references, or personal experiences in the back of its mind, because it doesn’t have a mind.

This describes the fundamental problem with AI. The chatbot will forever be like that new recruit to the team. Sure, they have the skills to make some contributions, but they lack the surrounding context to fully work autonomously. They need some guidance to get to the right path.

The difference between the chatbot and the new recruit is that the chatbot won’t remember all the guidances it got. The chatbot won’t remember all the design decisions that were made. The chatbot won’t remember that time prod went down. The chatbot will forever be like the new recruit with no experience.