Hi HN!<p>My name's Robert Escriva. I got my PhD from Cornell's Computer Science department back in 2017. And three years ago I had a psychotic episode that irreversibly shook up my world.<p>Since then I've been applying a skill I learned in grad school---namely, debugging distributed and complex systems---to my own mind.<p>What I've found I've put into a [book (pdf)](<a href="https://rescrv.net/engineering-schizophrenia.pdf" rel="nofollow">https://rescrv.net/engineering-schizophrenia.pdf</a>) on engineering, my particular schizophrenic delusions, and how people who suffer as I once did can find a way through the fog to the other side.<p>This is not a healing memoir; it is a guide and a warning for all those who never stopped to ask,
"What happens if my brain begins to fail me?"<p>I am writing because what I've found is not a destination, but a process. It is an ongoing process for me and for people like me. I also believe it is automate-able using the same techniques we apply to machine-based systems.<p>I am looking for others who recognize the stakes of the human mind to engage in discussion on the
topic.<p>Happy hacking,
Robert
返回首页
最新
Simply paste a product URL, answer a few personalized questions about your needs and preferences, and our AI analyzes your responses to provide a calm, reasoned recommendation.
You can paste links to products from any e-commerce site including Amazon, eBay, Best Buy, and most online retailers. Our AI analyzes the product to generate tailored questions.
Previously it has been using Akamai
Most consensus libraries (Raft, Paxos) treat the state machine as a pure black box. This is fine until your state machine needs to actually do something, like charge a credit card, fire a webhook, or send an email.<p>If a leader crashes after the side effect but before committing it, you get duplicates. This is my attempt at fixing this problem from first principles ish: build chr2 to make crash-safe side effects first-class citizens.<p>mechanism:<p>Replicated Outbox: Side effects are stored as "pending" in replicated state. Only the leader executes them under a fencing token.<p>Durable Fencing: A manifest persists the highest view using atomic tmp+fsync+rename. This ensures a "zombie" leader can't wake up and double-execute stale effects.<p>Deterministic Context: Application code receives a deterministic RNG seed and block_time from the log, ensuring 1:1 state transitions during replay.<p>Strict WAL: Entries are CRC’d and hash chained. it is designed to prefer halting on mid-log corruption over guessing.<p>The Trade-offs: Side effects are intentionally at-least-once; "exactly-once" requires stable effect IDs for sink-side deduplication. It’s a CP system safety over availability.<p>Repo: <a href="https://github.com/abokhalill/chr2" rel="nofollow">https://github.com/abokhalill/chr2</a><p>if you’ve ever had “exactly once” collapse the first time a leader died mid flight, you know exactly why I built this.