Nicholas Wilt retweeted
“Tell him to enter the password he knows is correct. Inform him it is incorrect. Invite him to reset it. Watch as he enters the password he believed it to be all along. Then tell him he cannot use it… because it is his current password.”
Nicholas Wilt retweeted
That’s neat, but I think we can make this design more efficient. What if we gave it a bigger shovel so it could take in more at once, and reduced the design complexity by fixing at street level with slight adjustments and we removed the arms? We could call it a snow plow
Reflex Robotics is testing a robot designed to handle real-world manual labor, such as snow shoveling ☃️@NYCMayor
Nicholas Wilt retweeted
Yeah, forget my praises about amdgpu drivers in Linux, it’s been crashing in every other Dota 2 session since kernel 6.17 and there are tons of reports everywhere. Phoronix even haven’t been able to run many benchmarks on RDNA3/4 for a while. AMD software is cursed — they simply don’t have the talent or knowledge to properly do drivers or any minimally relevant software, which will always keep them significantly behind NVIDIA in DC, too. #SiliconGang
Nicholas Wilt retweeted

Jack Andrade@RealJackAndradeFeb 9
🇺🇸
United StatesConnected via United States Android AppAccount-level information, not a live location or per-post device.
The @Seahawks defense had more sacks (9) and takeaways (4) in 2 games at Levi's Stadium this season than the 49ers did in their 8 home games combined (7 sacks, 3 takeaways)
Kenneth Walker III also had more runs of 20+ yards (3) than the whole SF team (2) in that stadium
Nicholas Wilt retweeted
Replying to @CDonnick1
Impossible? No, it gets even better iff they beat the Patriots in the Super Bowl.
Nicholas Wilt retweeted
From our Discord server.
No, *you folks* are amazing! ♥
Join our community: discord.com/invite/KNpgGbTc3…
Nicholas Wilt retweeted
A visit to this booth is like time travel to the future.
Most people come to Booth #6552 for a free Scaley plushie.
Some come to see the same, untouched CUDA code running on both AMD and NVIDIA GPUs.
We don't judge your priorities. Just come say hi.
#SC25 #HPC #HardwareFreedom #CUDA #AMD #NVIDIA @Supercomputing
Nicholas Wilt retweeted
Spectral Compute Brings Vendor-Agnostic CUDA to HPC and AI with New Funding
@SpectralCom #HPC #CUDA
ow.ly/Ft9Q50XpB0W
Nicholas Wilt retweeted
Hehehe... very nice integer literals to use in C (and ASM):
"Ate bad food" (0x8BADF00D), "Ace of base" (0xACE0FBA5E), the classic "Big Boobs" (0xB16B005), "Cool off" (0xC0010FF), "Dead Code" (0xDEADC0DE), "zero disease" (0x0D15EA5E), "Feel Dead" (0xFEE1DEAD), "Leet Code" (0x1EE7C0DE), "Bad Ass" (0xBADA55), "Defecate" (0xDEFECA7E).
There is also the classics 0xDEADBEEF, 0xBADBABE and 0xCAFEBABE... But I found another interesting one: 0xDEADCELL (a long long int literal).
Nicholas Wilt retweeted
There are *zero* successful software engineers who have only used one language in their careers.
Zero.
Most have used a dozen languages or more.
Programming languages don't matter. They have no bearing on how valuable you are.
And more importantly, people who pay don't care.
Nicholas Wilt retweeted
Krzanich... Swan...Gelsinger...
Why aren't we talking more about Frank Yeary and Intel's board? Yeary is longest serving board member & the constant over the long decline
youtube.com/watch?v=rc6BlaNS…
Nicholas Wilt retweeted
I’m not an equities analyst, but I told you so…. This one was so easy to predict. Board ghosts the CEO without an explanation or replacement and the stuck plummets. Investor’s only thoughts are what bad happened? Who can fill Pat’s shows? I talk to all of Intel’s largest customer’s executives. No one is cheering.
$INTC
As I said on @CNBCOvertime yesterday when they asked me about $INTC stock increasing then going negative and now negative today:
- makes no sense the stock rose early
- makes sense it went negative yesterday
- Pat’s departure inserts risk; something changed
The reality is setting in. Pat leaving is risky and we don’t know what we don’t know about the motivation. Whatever it is, could it be positive?
If this move doesn’t work, then the Intel BoD will be the next to go. I’m not an equity analyst, but I wouldn’t be surprised if the slide continues.
Nicholas Wilt retweeted
Agree with a lot of this from @sallywf
Pat was the right guy, there is zero doubt. The board very likely made a costly tactical error.
My hot take: @intel will never find another Gelsinger. The 30-year Intel veteran, former Intel CTO and former VMWare CEO is irreplaceable.
eetimes.com/intel-will-never…
Nicholas Wilt retweeted
Nicholas Wilt retweeted
My hot take: @intel will never find another Gelsinger. The 30-year Intel veteran, former Intel CTO and former VMWare CEO is irreplaceable.
eetimes.com/intel-will-never…
Nicholas Wilt retweeted
IMO, it will be difficult for @Intel to get someone of the caliber of @PGelsinger as the new CEO
Nicholas Wilt retweeted
I don't have any inside information to add here, but from the outside, I think a fair bit of the Gelsinger dissing is presumptuous. By the time he came on board, Intel's fab tech was already in a hard-failure state, and vanishingly few CEOs could have turned that around in four years.
In other words: not being privy to what happened inside Intel, I don't know how good a job Gelsinger did or didn't do. Maybe he did, in fact, do a terrible job. But without question, he inherited a complete disaster. So without more, the only real conclusion I can draw from the external observables is that he wasn't a miracle worker.
Which, to be fair, some select few CEOs are - but I don't know who Intel could have gotten who would've executed at that level. You can't just call up Gwynne Shotwell and convince her to come rehabilitate your failed engineering culture for you. The select few who can lead at that level of competence are already running their own major corporations, and it's hard to find new rare leadership talent like that.
Nicholas Wilt retweeted
1. Changes in execution timing (or locking), hiding race condition
2. Changes in code layout hiding memory corruption/uninitialized, or hiding cache bugs
3. Changes in codegen hides compiler or HW bug
I don't know which one's scarier
This Post is from an account that no longer exists. Learn more

































