
sheheryar retweeted
I do not send through “Jito”. I do not send through “Zeroslot”.
I send to the CURRENT LEADER’S TPU, and if it drops, I kill myself.
Albert Is Great
sheheryar retweeted
Asked @_snaerr where he & our intern went, should I be concerned??
sheheryar retweeted
N1's official job description for a rust engineer from our CTO. Ping me if you meet the criteria or know anyone.
Referral bonus for a successful hire included 🫡
sheheryar retweeted
Replying to @chrislakin
reading non-fiction is a completely different activity. with fiction you read and let the story unfold like a movie. with non-fiction my reading speed is like 1/10th. i'm re-reading, thinking of examples, creating rebuttals, looking up alternative interpretations, and so on
sheheryar retweeted
90% of coding is waiting for a fever dream where the entire code is revealed to you
sheheryar retweeted
they need to run the goth mommy benchmark on o3. until we have those results, the ARC-AGI score is meaningless
sheheryar retweeted
Introducing Zeroth-01 Bot: the world's smallest open-source end-to-end humanoid robot starting at $350!
Fully open-source, including hardware, SDK, sim environments & more. Zeroth-01 is the most hackable humanoid to-date!
Join⬇️to shape the future of accessible robotics w/ us
We designed, 3D printed, and built a <$270, 13-DOF mini humanoid robot, wirelessly controlled and capable of walking and boxing at the @kscalelabs hackathon in 24 hours
Open sourced: github.com/jingxiangmo/low_c…
sheheryar retweeted
we remembered the twitter password!!
in london, boston, waterloo, vancouver, montreal++ today — making retro game consoles, animations, material selection databases, stories, hacker fabs, and more
sheheryar retweeted
Builder aura in Montreal
I just launched a robotics hackerspace in Montreal!
We're building a highly technical robotics community for researchers and engineers to work on robotics projects, research, and startups
More info here: robotica.sh
Open house this Saturday: lu.ma/sy2rd1do
sheheryar retweeted
![/// Separates those instances which have attained Nirvana from those which /// remain bound to the cycle of rebirth. /// /// This struct encapsulates the logic to determine whether an instance is /// deemed eligible to reincarnate for both in-memory [`Instance`]s and for /// filtering database queries. This way, we define the logic in one place, /// making it easier for it to be kept in sync. #[derive(Clone, Debug)] pub struct ReincarnationFilter { /// The reincarnation cooldown period. An instance whose last reincarnation /// was within this interval from now must remain in _bardo_ --- the liminal /// state between death and rebirth --- before its next reincarnation. cooldown: chrono::TimeDelta, }](https://pbs.twimg.com/media/GXTylU9bgAIaiom.jpg?name=small&format=webp)
ALT /// Separates those instances which have attained Nirvana from those which /// remain bound to the cycle of rebirth. /// /// This struct encapsulates the logic to determine whether an instance is /// deemed eligible to reincarnate for both in-memory [`Instance`]s and for /// filtering database queries. This way, we define the logic in one place, /// making it easier for it to be kept in sync. #[derive(Clone, Debug)] pub struct ReincarnationFilter { /// The reincarnation cooldown period. An instance whose last reincarnation /// was within this interval from now must remain in _bardo_ --- the liminal /// state between death and rebirth --- before its next reincarnation. cooldown: chrono::TimeDelta, }
sheheryar retweeted
Replying to @crypt0lake
we're getting there. improved tooling for reproducible fuzzing. newer languages secure by design. infrastructure becoming simpler and more powerful. plenty of startups in the area, just gotta look in the right places :)
sheheryar retweeted
The decision to embrace VSR’s message passing for TigerBeetle was valuable and subtle:
“Use the simplest building blocks you can, and then push control flow (and guarantees) up.”
We learned this from networking, to follow the end-to-end principle.
en.m.wikipedia.org/wiki/End-…
Why would Message Passing be superior to RPC for implementing consensus protocols?!
Couldn’t we simply reason about remote procedure calls in terms of two messages being passed, a request and a response?!
System Model
We will think in terms of two layers, the application layer and the platform layer.
The application layer consists of the parts of the system that are aware of consensus
The platform layer consists of the parts of the system that are aware of sending and receiving messages
Message Passing
In case of message passing, the application layer is stateful, but the platform layer is stateless
After sending a message, the platform layer has no expectations
RPC
In case of rpc, both the application layer and the platform layer are stateful
After sending a request, the platform layer expects a response
The problem
The statefulness of the application layer contributes to finding consensus. However, the statefulness of the platform layer does not-at best, it is meaningless
In consensus protocols, message routing, timeouts, or retries require application-level semantics that the platform-level is incapable of providing
(E.g. increasing the value of a fencing token on retry)
Conclusion
Message passing is the lower level primitive on which remote procedure calls can be built.
However, consensus is a great example where the lower level primitive is the better choice-the higher level primitive increases complexity instead of simplicity
Message passing wins here
teapawt.net/DominikTornow/status/1…
sheheryar retweeted
Replying to @kindgracekind
With age you stop doing that this much and suddenly you have simulated annealing
sheheryar retweeted
We designed, 3D printed, and built a <$270, 13-DOF mini humanoid robot, wirelessly controlled and capable of walking and boxing at the @kscalelabs hackathon in 24 hours
Open sourced: github.com/jingxiangmo/low_c…
This quoted post is unavailable.
sheheryar retweeted
you know constructivist mathematics is gonna be good when an introduction to the field opens like this
sheheryar retweeted
Do you want formal verification for your actual system?
Deterministic Simulation Testing is "dangerously" close
teapawt.net/TigerBeetleDB/status/1…



































