Jeff Preshing

Canadian game developer

[Jeff Preshing @preshing]

@AnthropicAI That's nothing. Satya's been doing it since 2024! 🤪 https://t.co/i4ghzweUgu

[Tsarathustra @tsarnick]

Microsoft CEO Satya Nadella says AI development is being optimized by OpenAI's o1 model and has entered a recursive phase: "we are using AI to build AI tools to build better AI"

[Jeff Preshing @preshing]

@simonw @xSiladitya @antirez Access to advanced exploit automation is going to become widespread no matter what. That means hardening existing software with these tools is now part of the job. I'm glad everyone is taking their jobs seriously, but the media blitz around it was a bit much.

[Jeff Preshing @preshing]

@simonw @xSiladitya @antirez "Too powerful for public release" was the stunt part.

[Jeff Preshing @preshing]

@kevinroose @Noahpinion If messaging changes, it means leadership changed their minds (obviously). And the ability to change one's mind in light of new information is good.

[Jeff Preshing @preshing]

I believe it was Von Neumann who originally said this

[Andrew Ambrosino @ajambrosino]

it's important, i think, to resist the temptation to ship garbage

[Jeff Preshing @preshing]

@__tinygrad__ I'm drooling at the red v2 🤑

[Jeff Preshing @preshing]

@antirez I'm digging the terseness.

[Jeff Preshing @preshing]

@noguchis @antirez That brought it up to ~22 t/s (nice!) but I also had to switch to the perf/clean branch. I had previously tested in main.

[Jeff Preshing @preshing]

@__tinygrad__ People need controversy to avoid confronting their own personal issues. Not even educated people are immune to this.

[Jeff Preshing @preshing]

These are all great use cases for LLMs, but I don't see why it should cost more than a few hundred bucks a month!

[Peter Steinberger 🦞 @steipete]

People freaking out over my AI spend. What nobody sees: Part of what excites me so much about working on OpenClaw is that I'm trying to answer the question:

How would we build software in the future if tokens don't matter?

We constant run ~100 codex in the cloud, reviewing every PR, every issue. If a fix on main lands, @clawsweeper will eventually find that 6 month old issue and close it with an exact reference.

We run codex on every commit to review for security issues (as it's far too easy to miss).

We run codex to de-duplicate issues and find clusters and send reports for the most pressing issues.

We have agents that can recreate complex setups, spin up ephemeral https://t.co/Q1NRXLemEy machines, log into e.g. Telegram, make a video and post before/after fix on the PR.

There's codex that watch new issues and - if it fits our documented vision well, automatically create a PR of it. (that then another codex reviews)

We have codex running that scans comments for spam and blocks people.

We have codex instances running that verify performance benchmarks and report regressions into Discord.

We have agents that listen on our meetings and proactively start work, e.g. create PRs when we discuss new features while we discuss them.

We build https://t.co/bmA1XnoB7P to split all our projects into functional units to review and find bugs and regresssions.

We do the same split for security with Vercel's deepsec and Codex Security to find regressions and vulnerabilities.

All that automation allows us to run this project extremely lean.

[Jeff Preshing @preshing]

@mitsuhiko Agreed. Also plays completely into LLM strengths and reveals the mindset behind his earlier "no human contributions allowed in future OSS" tweet. I'd rather hear about his approach to automation instead of another Anthropic-style sound bite.

[Jeff Preshing @preshing]

@antirez JavaScript taught me that there are no limits to the way an ecosystem can be extended. I never foresaw three.js, wasm, etc. but once the web became huge, the collective willpower of developers made it all happen. It shattered my preconception that things should be planned ahead.

[Jeff Preshing @preshing]

@supahvee1234 @pmddomingos Yeah. It also runs on DGX Spark. Too slow to be a daily driver (~14 t/s) and flails a little compared to the real model, but capable!

[Jeff Preshing @preshing]

@antirez What you have done with Codex is some real kung fu. Where do I sign up for your course?!

[Jeff Preshing @preshing]

@antirez Just got it running on the Spark! Thanks again for showing what's possible. Wish I had more time to study what you did.

[Jeff Preshing @preshing]

@__tinygrad__ @curl_justin That would have been great if the US viewed AI more like China. I wouldn't have had to read so much garbage in my feed for the last few years. It's getting better at least.

[Jeff Preshing @preshing]

@mattpocockuk Automatic Inference

[Jeff Preshing @preshing]

It's not true that nobody reviews compiler output. In game development and other fields, the ability to read and understand compiler output is pretty common. The popularity of https://t.co/wDSat9anBo is evidence of this.

Sometimes there's an issue to fix and symbols are missing, the debugger isn't displaying something correctly, or all you have is a crash dump with limited information. At those moments, reading disassembly is a big advantage.

I'm open to arguments about the viability of vibe coding, but not arguments based on falsehoods.

[solst/ICE of Astarte @IceSolst]

Interesting article on treating agent output like compiler output (and why)

https://t.co/UHV1V1PzN1