joantune

> But, all we’ve achieved at this point is making a glorified token predicting machine trained on existing data (made by humans), not really being able to be creative outside of deriving things humans have already made before. Granted, they‘re really good at doing that, but not much else.

Remove token, and that's what we humans do.

Like, you need to realize that neural networks came to be because someone had the idea to mimic our brains' functionality, and see where that lead to.

Many skeptics at the beginning like you discredited the inventor, but he was proved wrong. LLMs shown how much more than your limited description they can achieve.

We mimicked birds with airplanes, and we can outdo them. It's actually in my view very short sighted to say we can't just mimic brains and outdo them. We're there. ChatGPT is the initial little planes that flew close to the ground and barely stayed up

Underrated comment

With motivation, repetition, and those depend on how plastic your brain is, thus the age, yes!

The intensity you did it though matters. You probably didn't spend that many years on a specific sport for instance.

And when we're talking about sports, genetics matter as well (depending on each one)

When we're talking brains, while genetics also matter, assuming normal (whatever that is) brain, the plasticity changes a lot how it operates.

So, the 10 years thing is definitely a big if not the biggest part. In my opinion. Would love to see studies if any exist out there on this

They're not boasting about their current productivity, they're boasting about the one they achieved at FoundationDB when they implemented the testing, which gave them the idea to build antithesis

Would a USB bluetooth adapter to connect to wireless keyboards and mouses work with this??

Perhaps just give descriptive names and then change it when the scope changes??

"Problem" solved!

Afraid of losing stars/dlds on the repo/etc? Make it clear in the Readme where the new project is. Have warnings et al for NPM projects.

Ask npm/GitHub to allow name changes with redirects.

This proposed "solution" is just bad for many reasons:

You need to delve into the Readme to find out what it does. Imagine you're seeing a package.json and for each line you have to Google what's the project about

SEO is best if name matches.

These are enough *good* reasons why this advice is a bad idea

Donated! Hope it helps

I use Google Cloud Tasks for at least some of the same purpose(s)

I wonder how this one stacks up given is centered for webhooks specifically

Oops, definitely

Hmm.. haven't coded in it for a while, but wouldn't typescript solve this?! Why are people still using vanilla JS?!

They definitely deserve to 'go under' because of the way they handled this. Anything less and it's going to be enabling these shannanigans

I think he would have gotten his point across much more easily with examples and alternatives like you did

See, I wish the author on the original article added the same reference and examples that you added here

I see zero examples and rational/practical arguments against the usage of REST.

The only thing here is: it wasn't intended to be used this way.

I see it being called an overload, but I see no alternatives..

This article adds little of value, or even doesn't highlight or enunciate the disadvantages of using REST for everything.

And on the other hand, the advantages are obvious