Replying to @LewisCTech
Not sure about the TUI, this is the desktop app.
Replying to @shrirambalaji
Yep, the models are just flat out better too. Opus 5.5 is the first time I've actually been happy with a model in a long time, particularly in the way that it talks.
Replying to @thesammykins
OH right, I thought that was your phones autocorrect for a sec.
I've been the official No. 1 Anthropic hater since the initial Fable release and its hidden guardrails, but I have to admit they've been crushing it lately.
Replying to @abdimoalim_
Well they said they were going to, so you'd be forgiven for thinking that.
I still like Communities but I don't want to continue using mine if it's just going to get pulled out from under me any day now.
It's so stupid that X made this big deal out of removing the Communities feature, doubled down after the backlash and then proceeded to... leave the feature as is. They haven't even explained whether they're still planning to remove it at a later date or not.
So many things about X are completely amateurish in this way. The X Chat app still isn't available in the Australian app store for some reason, etc.
I remember when a recruiter introduced himself to me as a “Talent Pipeline Engineer” (yes, this actually happened).
autumnkyoko@akcushmanOct 22United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
idk who needs to hear this but it’s ok to not put ‘engineer’ after every job title
Get rekt Tanenbaum.
Replying to @tetsuo_cpp
So real and true, but instead of cuda kernels we should combine OS kernels fuck microkernels we need to start the era of megakernels. Make the Mach creators tremble in fear, our kernel will do userland heap management and nested virtulzation all at once !
Replying to @jashan702
If you’re not building gigakernels, you’re ngmi.
tetsuo.mlir retweeted
This is my last week at @NVIDIA.
It's been an honor and a pleasure to be a part of this incredible team.
I couldn't have asked for a better job these last 9 years.
🫡
I joined @nvidia nine years ago today, against the advice of a colleague who said their comp was below market.
But I really believed in the mission and the people, so I went.
I met @__simt__, Michael Garland, and Jared Hoberock on the C++ committee. I thought they were the smartest people there.
I worked at @BerkeleyLab on concurrent and parallel programming paradigms, mostly for SIMD.
@__simt__ convinced me that SIMT was a superior model for parallelism.
He sold me on a revolutionary new GPU architecture where threads would independently scheduled: Volta, the basis of all modern GPUs.
I asked him three times to find me a place at @nvidia. The first two times, he wasn't sure where to place me or if I'd like it.
The third time, he had me come in to talk to Chris Lamb (now VP of CUDA). We chatted for two hours and he outlined the role he believed modern C++ would play in CUDA.
I came back for an 8 round interview panel. All of the questions were answered with std::atomic. No one was sure what I would be working on.
I, a modern C++ person, was placed in the CUDA driver org, which was written almost entirely in C.
On my first day, my manager told me I'd be responsible for Thrust and CUB, @nvidia's first two open source libraries. No one had worked on them for a while and there was no product manager. I'd have to do it all.
I put together a roadmap and got the libraries back on GitHub. I started sending status updates from CCCL, the CUDA Core Compute Libraries team, which did not exist. Eventually, they let me hire three people to fill out the team.
We built libcu++ and abstractions for all the quirky new features being added to our chips to support these AI workloads that seemed to be growing in importance rapidly.
After a few years I was asked switch orgs and guide the roadmap for our HPC C++ compiler. Programming languages and models quickly became my role, from stdpar to CUDA-Q to CUDA Python to CUDA Tile to autoresearch.
What a ride it's been!









