snvzz

>How a $500k/Year AI Engineer Lost Everything

Apparently they saved no money and went homeless in a matter of months (?!).

People who work in mcdonalds putting the fries in the bag do not earn 500k/yr and somehow manage to avoid homelessness.

It is quite telling that they blame the AI rather than themselves.

Crazy idea: Putting them in Prison, so that the rest of us can live in peace.

It would have prevented it. e.g.

>Of course, you’d want to try ../… Yes, it does let you escape the temporary folder...

This is absolute bull on seL4 by construction. "sandboxes" that prevent access that the OS otherwise grants. In seL4, this component would not need a sandbox in the first place, because it would never have a capability to some VFS path it doesn't need to access.

This sort of escape relies on ambient security, which is the security model of UNIX and Windows NT. Access is granted by default and then restricted, rather than simply not granted. A broken security model.

And, unlike a demonstrated shitty browser sandbox, seL4 formally guarantees isolation. Capabilities cannot be forged.

Who voted Claude in?

seL4 can guarantee* time domain isolation between processes.

*on some CPUs. There's a WIP time fence specification in RISC-V to try and improve this.

The Amiga drama never ends.

RISC-V is inevitable.

AIUI TensTorrent has some sort of contract with Rapidus.

You won't have to wait long.

It is only possible to draw the rest of the safe owl if you have a safe crayon.

seL4 is the choice that allows for a safe system to be built. Any other choice of kernel currently available does lack the mechanisms and guarantees.

That's way too many PDF implementations affected by this category of stupidity.

It makes me wonder: Coincidence, really? There's enough there to think that there might be some invisible hand behind it.

Not using AI is a choice they can make.

They'll be left behind, but it clearly doesn't matter to them.

Knowledge is knowledge. "Illegally obtained" is obsolete thinking.

>You can point an LLM at any large codebase and it will find vulnerabilities, so "patch the planet" isn't very scalable.

So the solutions need to be structural.

e.g. relative to a monolith kernel, seL4 is small, has no known bugs (AI can try, but so far crickets) and is the only piece that needs to run privileged.

Everything running under seL4 benefits from the guarantees seL4 provides.