been doing this since March and can confirm it’s the best approach.
i use AI when i need to (literally used up $60 of OpenAI tokens yesterday)
and my VS code & Zed has no AI so i can build more stuffs.
built a mini search engine, a shell, a file compressor, a cpu emulator and a ton of cool stuff by handwriting code 🤞.
my brain is sharp and i can think more clearly and even design better than before…
We’re excited to announce Ayodeji Akinola (@ayodeji0x0) as a speaker at SysConf 2026!
His talk is titled “Correctness Over Availability: Running an FX Market on One Writer.”
At Daya_HQ, where stablecoins trade against the Nigerian Naira, correctness is far more important than availability. So instead of a distributed cluster, where a split-brain scenario means losing money, the team runs a single writer: one process owns each market's order book.
This talk walks through the mechanics of their production system. Ayodeji breaks down the layout of Daya’s in-memory B-tree order book, how the engine deterministically recovers after a crash, their fencing implementation, and how the API scales out safely without touching the order book directly.
#SysConf #SysConf26
@peculiarerhis it depends actually, if you want high throughput then you go for eventual consistency, because it does not wait for all nodes to be updated before acknowledging.
You should go for strong when you want data accuracy. All replicas returns the same data at every point.
We’re excited to announce Rubbie Kelvin (@KelvinRubbie) as a speaker at SysConf 2026!
His talk is titled “The Autopsy of an Asynchronous Deadlock.”
Async Rust promises fearless concurrency, but the runtime can still lock up, and when it does, no stack trace exists to point you to the culprit. This talk walks through a deadlock Rubbie hit in a production Tokio-based service, using it as a case study for a general forensic method.
How do we recognize a deadlock vs a slowdown? How do we use tokio-console to see relevant task state? How do we reason about lock ordering, .await points and task starvation? Come find out at this talk!
#SysConf #SysConf26