I'm looking for a remote senior or principal backend engineering role. I’m based in GMT+5, with full working-hours overlap with CET.
I've spent the past 14 years building distributed systems with Go and Elixir/Erlang. You’re more likely to know me as the author of linux-insides.
I'm especially interested in infrastructure, databases, observability, and challenging systems-level problems.
If you're looking for an engineer who cares deeply about performance, scalability, reliability, and understanding how things work under the hood, let's connect.
My DMs are open, or feel free to reach me directly at [email protected]
Reposts are greatly appreciated.
This is Algebrica, a mathematical knowledge base I've been building since May 2023, primarily for university students.
306+ entries, carefully written and structured.
Over 4.2 million views since its launch (not much in absolute terms, perhaps, but meaningful to me).
No ads.
No courses to sell.
No gamification.
No distractions.
Built simply for the pleasure of sharing knowledge.
All content is licensed under Creative Commons (CC BY-NC 4.0). Every article, text, and illustration is freely available and downloadable in editable formats, including Markdown and SVG.
Free to access. Free to learn. Free to share.
If you believe mathematical knowledge should be freely accessible to everyone, explore Algebrica, use its resources, share them with others, and help this project reach more people.
https://t.co/B2muWVvO56
week 141, streaming OS dev (c++)
topic: preemption tests
one of my key principles is strong kernel test infrastructure
this week i explored integration tests for preempt multitasking
few hobby OSes do this. and I can see why! it's hard
here's my problem solving process:
week 141, streaming OS dev (c++)
topic: preemption tests
one of my key principles is strong kernel test infrastructure
this week i explored integration tests for preempt multitasking
few hobby OSes do this. and I can see why! it's hard
here's my problem solving process:
Here's part 3 of my video series on memory management. It has a fun and slightly cursed exercise of reimplementing the function call stack in user code, demonstrates frame allocators / arenas, and looks at a couple of freelist implementations.
https://t.co/flD6cxdpSt
How does that even work in your head?
"Oh, this language reads like pseudocode, I will use it"?
Put a little effort into reading the quoted tweet.
There are a lot of reasons why python is popular. Readability is one of them. Primary? So crucial to make python gone because we do not type code anymore? I doubt that.
Readability was a nice argument for people choosing between Perl and Python when that choice was still relevant. Today, the size of python's ecosystem is a far more convincing reason to choose it than readability
Somewhat sadly, I think we’re seeing the end of Python as a programming language. When agents write the code, the language designed to be the most readable just isn’t as useful.
You were fun, Python.