When you're on call and see one of those *really* bad alerts pop up, so you pray, and a few minutes later it just resolves itself
I've finally accepted it... Type safety simply isn't real and doesn't exist.
It assumes your code runs in a happy little dreamland where memory doesn't corrupt, power doesn't turn off, and metal is just a word.
Was asking a question to a colleague about a system he knows and he jokingly said "why are you asking me, ask the clanker!"
Bit of a shock because we both know I can, but I didn't because I actually wanted to build more of a bond with them. Kinda worried we're getting more antisocial with the clankers around.
When my grandma got her first smartphone at 91, I was blown away by how completely foreign touch gestures were to her.
“Pinch to zoom” and “double tap” might as well have been alien instructions. She had no reference frame for how these devices worked.
But after watching my brother and I use our phones, within a ~day she became just proficient enough to be dangerous.
It’s a good reminder that what's intuitive is local. What "feels" obvious to one person can be utterly opaque to another. Yet universally even a 30 second demonstration can accomplish multitudes more than just letting users "figure it out"
Everything that needs to be said has already been said, but no one was listening, so it all must be said again.
I used to feel a bit of shame pushing a purely vibe coded PR (and still do to some degree). But the abilities of the models to one shot maintenance fixes, misconfigurations, code owner updates, among other mundane tasks. Zero shame, just pure utility
Grateful to have finally solved one of the janestreet HF puzzles 🙇♂️
https://huggingface .co/spaces/jane-street/droppedaneuralnet
TIL if you turn on rust's `#![feature(generic_const_exprs)]` feature you can enforce compile time "inequality checking" with const generics and do stuff like a type safe suffix.
Alex Comerford retweeted
here's Hack Night in a nutshell, in case you were wondering. thank you @GeminiApp @NanoBanana for the help! 😊
Big thanks to @AlexKontorovich for making his Intro to Real Analysis course open and lean based!
As someone who never had the chance to formally study it, it's amazing to now be able to take it and know my proofs are verified!
I've started using `cargo-show-asm` more but I've found it annoying switching `#[inline(always)]` to `#[inline(never)]` to see specific functions outputs, so I made small proc macro to fix this!
Now you can just do `#[inline_conditioned(always)]` then add the feature `never-inline` on your `cargo asm` so you don't have to think about un-inlining again.
```
cargo asm --features never-inline --lib ...
```









