me when i present on "why use the Rust programming language in automotive systems" when wearing the @pants "RATS" shirt

Have we considered solving the RAM shortage by rewriting everything in Rust?

Why DHH is going in on Rust even though he hates it (yes, maybe you should too)

I might be the only person in the world that likes looking at Rust code. I think it's super pretty.

２３年前に描いた壁砕きアニメ。そもそも見れなくなってたっぽいので再掲

「お年寄りにキュンとした出来事」その18

いややかましいわwwwwwwwwwwwwwwwwwwww

「Pを間違って上下逆に付けてるやん！」 と思ったら、おでん屋さんやった！

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

this is why i simply do not reply to my emails

I wasn't sure yet if he was just some random employee and didn't want to blow his name up as like, "the horny pumpkin guy"

The contagion of fear bcantrill.dtrace.org/2026/09…

I merged a change that should reduce the size of your Rust `target` directory by ~20% during development. It turns out the compiler was retaining an extra completed snapshot for every crate that was incrementally recompiled.

AI loops 101 in two tweets: When CI fails with on a flaky test, send this to your agent: "a test failed in a flaky fashion, please figure out why and propose a pragmatic path forward: <CI link>"

all foreigners looking for multi-year visas should be required to pass the JLPT N1 being able to speak the language of your host nation is a basic courtesy that wait a matte the JLPT doesn't even test speaking

there *is* undefined behavior: all of what you are describing is behavior determined by the implementation and the hardware platform, and not by the C standard. but the thing is, when the implementation is known, undefined behavior is often benign!

Both are autonomous driving systems of some kind btw

I know this is garbage engagement bait, but I think it's worth calling out this mindset for the young kids that get hooked on hustle culture, or think of abusively hard work as something virtuous. A few things I have learned to be true: 1. One day you will be dead and shortly after nobody will remember you. They certainly won't give a shit about your work. The ones that do will be the people you loved and who loved you. Not your stakeholders, colleagues or business associates. Shit, most people forget about you the day you change jobs. Even the CEO. Once you leave, you just kind of...fade away. Your work mostly doesn't matter. Also, as you get older you start to watch people die...way way earlier than they should. You genuinely don't know how much time you have. Do you really want to spend it all hustling...or even worse...pumping out engagement slop celebrating hustle culture? 2. More people are like Walter White than they care to believe. At the end of Breaking Bad, Walt finally confronts the truth. He wasn't doing it for the family. "I did it for me. I liked it. I was good at it. And, I was really... I was alive.” Most people find value in their work, which is great. But my old man gave me incredible advice when I was younger, "Beyond a certain point, a successful career is a selfish act." The people who really get themselves into trouble are the ones who convince themselves they are doing it for someone else. 3. You don't know the cost until too late I've watched friends wreck their health and their relationships chasing the next promotion, the next round, the higher salary. Justifying each step along the way as the right thing to do. Mostly they were just addicted to the work. Or they felt trapped. I don't think any of them would have made the trade if they could go back and know the cost from the start.

For this code to have bugs you must first define the pre- and post-conditions of the function and then show how the function fails to honor the post conditions when the pre-conditions are honored. UB on violated pre-conditions is part of working software.