Abhishek Singh
@0xlelouch_
Followers
1K
Following
3K
Media
87
Statuses
2K
Software Engineer. I talk about scalability challenges, infra, engineering productivity, web3, AI, trading and investing. Founder @0xffdevs
Holy Britannia Empire
Joined April 2021
My superpower as a remote software dev The real superpower of being a remote developer isn’t just freedom it’s the optionality it gives you. I have been working from landour for a week now and realised how blessed we are to have this kind of profession. You can work from
51
30
789
Strong types are power tools, not silver bullets. They can prevent whole classes of bugs, or they can grow a meta-language that’s harder to debug than the bug. My rule of thumb: use types to encode real domain invariants (make illegal states unrepresentable), but keep the happy
After programming in Haskell and Rust, the absence of silver bullets devastates me. Those languages provide neat features to prevent classes of errors at compile time via a powerful type system. Unfortunately, it's a double-edged sword. Many devs overengineer, and the
0
1
6
Senior SWE who writes Go and Rust by day, trekker on the weekends!
Senior SWE who writes C++ by day, Ogrepalooza Shrek Party dancer by night
3
0
63
There’s only one path to greatness - the grind. At some point, you’ll find yourself standing between two versions of you your old self, full of comfort and familiarity, and your new self, chasing something extraordinary. It’s tempting to go back. Back to the simple joys, the
1
5
12
Clickhouse 101 ---------------- Clickhouse is a columnar, OLAP-first database built to scan billions of rows in milliseconds. It wins by reading only the columns you ask for, compressing them hard, and executing vectorized/SIMD ops across CPU cores. Product analytics, logs,
Everyone including PlanetScale seems to use Clickhouse.
1
1
4
Legacy isn’t built from ambition, it’s built from mastery. Been reading a lot of @justinskycak posts lately, and it completely changed how I think about memory and recall. If you want to create something truly new, you have to become dangerously good at the fundamentals. We
3
3
83
New breakthrough quantum algorithm published in @Nature today: Our Willow chip has achieved the first-ever verifiable quantum advantage. Willow ran the algorithm - which we’ve named Quantum Echoes - 13,000x faster than the best classical algorithm on one of the world's fastest
2K
8K
47K
The detailed AWS incident report is out, and it’s worth a read - DNS records managed by 2 systems; a race condition led to regional record getting unset - EC2 lease establishment was borked as it depends on DynamoDB - fluctuating NLB health checks leading to EC2 DNS entry purges
57
429
3K
Rust vs C++ is a trade-off. Databento recently rewrote their feed handler back in C++23 after hitting real-world frustrations with Rust. Why? Easier code reuse from old C++ More control over memory + resources Familiarity → faster productivity Rust still shines for safety,
We process 14M messages/sec with sub-100μs latency. When rewriting our feed handler, Rust seemed like the obvious choice - we use it successfully across our stack... We chose C++ instead. Here's why the ownership model created friction for our specific use case:
8
0
71
A few add-ons that make APIs play even nicer with the borrow-checker: – prefer &self/&mut self methods that operate in place; avoid returning big owned structs if you can stream: fn rows(&self) -> impl Iterator<Item=&Row> – use AsRef/AsMut/Into on inputs to keep call sites
In Rust, how the borrow-checker shapes your API inputs and outputs .. The general design principle is to choose signatures that minimize ownership churn while keeping call sites clean and safe. Accepting input • Borrow when you only read: `fn parse(src: &str)` • Borrow
2
2
9
That’s why learning tougher, less crowded technologies early on pays off massively. When something just works out of the box, it eventually gets automated or abstracted away. But when you work in areas where things still break often like Rust systems programming, distributed
Worse technologies are better for employment. If things work smoothly, you don’t need so many people to do the job. In fact, we might not even need you. When things constantly break, it’s a guaranteed employment till retirement.
1
5
95
This feels so natural in Rust. No boilerplate, no ceremony just composable iterators with full type safety and zero-cost abstraction. Iterators just flow: (1..=n).map(|k| v.iter().skip(k-1).step_by(k).cloned().collect()).collect::<Vec<_>>() Rust makes elegance performant by
I haven't shared beautiful C++ code for a while. Here's some FP in C++ for a treat.
0
1
2
@AstraKernel @AdityaPlusp @rustlang @linuxfoundation @ubuntu @Embedded @tokio_rs @ThisWeekInRust Good news - Advanced Hands on Rust went into print a few days ago. eBook is available, print should follow shortly. Thanks for the shout-out!
1
4
8
Memory limit exceeded (While submitting on codeforces)
0
0
2
Lesson3: acclimatize, whether it's mountains, new skills, rust, go, devops, anything else physical or mental like gym, trading.. wait , breathe, take it in, enjoy the view then lock in and continue to march towards greatness!
0
0
4
Oh boy, keep going, can't stop, blood in my veins, i need to max out my mitochondrial function would request for @bryan_johnson help
0
0
4
Lesson2: everyone's journey is different, whether you wanna be a trader or a coder or a dancer or a cook, it doesn't matter where you stand or where others stand, keep moving at your own pace without comparison, with discipline and hard work you can get better with time
1
0
5
Lesson1: to be the best or to reach the top you must put in the hard work. It doesn't matter how slow you are as long as you keep moving!
0
0
5
Kedarnath yatra : LIVE I can't promise but will post frequently!! Har har mahadev!! Follow this thread 🧵
7
0
9
"Introduction to Applied Linear Algebra" This book from Stanford University is available FREE. To get your copy, comment below.
45
96
648
Unlike Java, Go doesn’t hide control flow behind exceptions. No checked/unchecked stack-unwinding that pops out three layers up. In Go you return error, handle it where it matters, and the happy path stays explicit. It’s verbose, but brutally honest. This pays off in prod:
5
13
131