Pete 🙆 retweeted
Holy shit, just found an article that completely agrees with all of my priors, I can't wait to share this
Pete 🙆 retweeted
It's really quite something when doing stuff with LLMs that you have to oscillate between deliberately built verification systems and just yelling at your little demon servant differently
Pete 🙆 retweeted
A16Z new media asked for a 30 min ramble vid about tech twitter
You can see it too:
Replying to @samkkaufman
31 minutes 14 seconds
i also sent you a bunch of other stuff in your twitter dms
Pete 🙆 retweeted
Goose: my latest programming language. Safer, faster and less memory than Rust/C++ for algorithms where tightly packed, flat data structures matter.
It can represent more kinds of data structures as flat, pointer-free bytes than any language I know.
github.com/aardappel/goose
1/
Pete 🙆 retweeted
a weird effect of
+seattle downtown retail in freefall
+Amazon return to office policy
+the ever-tightening ratchet of funko-pop millennial infantilization
is the preponderance of new "team outing morale event" storefronts in the vicinity — escape rooms, DIY pottery, etc
Pete 🙆 retweeted
a task that used to take me 1-3 days just took me 15 minutes with GLM-5.3 (extracting key material from a improperly implemented encrypted firmware upgrade and extracting/validating the firmware)
video tomorrow
Pete 🙆 retweeted
Nicholas Nethercote has been doing great work on speeding up the Rust compiler.
I'm proud that we at OpenAI will be funding his work, alongside others, as part of a Rust Project Goal to make rustc faster.
Pete 🙆 retweeted
If you're worried about not knowing Rust before embarking on a side quest to see whether it could fit in your stack, here's a tip: Include a line in your AGENTS.md file to optimize for readability and long term maintenance by devs well are inexperienced with Rust.
Pete 🙆 retweeted
I might be the only person in the world that likes looking at Rust code. I think it's super pretty.
Pete 🙆 retweeted
Introducing CUDA Rust!
CUDA Rust lets you write GPU kernels natively in Rust, not just launch them from it.
Two paths: cuda-oxide for SIMT kernels compiled to PTX, and cutile-rs for Tile-based programming on stable Rust. Both can catch aliasing errors at compile time.
Technical blog: nvda.ws/4hm1bHS































