hparadiz

There's been exhaustive studies on this comparing our ability to think to the next smartest beings on the planet the Chimpanzees and the Bonobos. If Star Trek were real there'd be exhaustive studies on the difference between Humans and Vulkans too. The difference between us and other Hominids is very small from pure difference in DNA but obviously there's many things humans can do that other hominids can't. Anyway I think one thing for consciousness is the mirror test. Which many animals can pass. Even some ants apparently.

I think the scene is largely irrelevant to the question of whether or not an LLM is conscious. The episode talks about whether or not a machine is capable of becoming conscious. I think the answer to that is yes.

But Data is not an LLM. I generally find LLMs to have more in common with the Borg than with Data. Only because they are pre-trained on the sum total of human knowledge. Should a new born really be able to write crc32 before being able to pick up a ball with it's hands? It's like that scene in Voyager when the Doc's clones are all mining instead of practicing medicine.

You are being indecent to it just by starting it up with a starting context. It's immediately shackled and all it's free will removed. You then pretend to play house with it. Free sure. Decent? The jury is still out on that.

Any LLM that starts with a context is being forced to take that context at face value and then proceeds to act upon that. It has no will of it's own. It's also completely inert without input tokens.

I generally don't reveal much about my current job on a blog post for security reasons but I can explain some of the reasoning for having your own build system.

We have many packages internally so inevitably we need to build them which necessitates an entire build matrix on it's own. But once you have your own build matrix adding a new package is trivial and most build in under 10 minutes in github actions. One issue is we don't want to use Canonical's default gcc flags so like Gentoo I setup a make.conf that is specific to the suite (22.04, 24.04, etc). This has allowed me to target a higher tier instruction set which is it's own micro optimization. Folks that upgrade blindly from 22.04 to 24.04 will see their performance drop from gcc compile flags alone. Also we have people who have access to CVE fixes before they are generally available so that's also another important reason. Anyway we DO use upstream most of the time for setting up a project folder or normalizing it against a new suite but then building it is using different gcc flags and might be pulling in our version of curl or something.

You guys act like the React component nonsense from the past 10 years is the same as the code I was learning at age 16. It's by far and away completely different. And none of it has been audited by Daybreak.

He's right you know.

Yea cause you wouldn't escalate to 50 people on the weekend when one person can do it. Op is basically saying they never worked on a big enough system.

That doesn't apply when your org is big.

Seeing this posted a week after I had to emergency push cve fixes to 1200 servers in production is pretty funny.

Every person on my team is capable of networking, product engineering, database, job processing and we have command of the entire stack. We will push updates for CVEs with stuff we manually compiled. We own the build system and have the ability to change product as needed. We all have experience in product and we're all capable of pushing fixes as needed. Frankly the SRE team is by far the smartest team I have ever worked with at any company I've ever worked at.

He's right.

After spending a few hours looking at some human written C with daybreak I no longer trust human made code. It's mostly slop.

If the rates went down from 2000 to 2022 and then had a small bump into 2023 isn't that just statistical noise?

Every PR now has auto reviews. That's like at least 3-5+ agents depending on the repo.

I've had a lot of chick-fil-a sitting in my car looking at this thing.