Software developer. Obsessed with Linux and and understanding how things work underneath. Author of linux-insides. Open to work.
Kazakhstan / Astana
Joined October 2012
- Tweets8.7K
- Following188
- Followers12.5K
- Likes942
Pinned Tweet
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.
I will never tire of recommending these streams
Optimizing a Lock-Free Ring Buffer david.alvarezrosa.com/posts/…
Trying to make linux-insides not just useful to read, but pleasant.
It is surprisingly satisfying to go back to something you wrote years ago and ask: can I improve the explanation and make it clearer?
One of the obvious answers is diagrams.
So, I have been spending some time improving the diagrams in linux-insides. Hope they make some of the harder parts a little easier and more pleasant to follow.
And yes, new chapters are coming soon!
The sources as usual you can find on github: github.com/0xAX/linux-inside…
Web version: 0xax.dev/books/linux-inside/
And if you want to support me and my work on linux-insides, you can do it via patreon patreon.com/cw/0xAX
I think it is still fun and to a certain degree is even more fun than before.
No any manual boilerplate anymore.
Want a prove (or not) your next idea - here it is.
The flow state hasn't gone anywhere. Why would it?
There is still plenty of room to be proud of what you build.
If you are into golang, this is one of those authors that is really worth following
New interactive mini-book: Go concurrency distilled
It gives a brief overview of many concurrency topics in Go, along with examples you can run in the browser. There's also a PDF version.
The book is AI-free.
antonz.org/go-concurrency-di…
Stop relying on technologies. Learn the fundamentals.
So @dhh just told 1000 rails programmers “accept that it’s over”
Last words of the opening #railsworld keynote were “don’t be a f*cking loser” and then he walks off
Glad I’ve been through the existential dread phase already, cos I’m ready to run through a damn wall right now!!
On HN front page now!
Boot sectors are not only for loading operating systems.
They can be much more fun than that.
Over the weekend I built BootLife - Conway's Game of Life running directly from a 512-byte x86 boot sector, using VGA memory as the simulation grid.
Just BIOS, VGA memory, and a little bit of assembly.
Not everything we build has to be useful. Sometimes programming should just be fun 🪁
And my githib profile I also updated so it doesn't look like from the same 2014)
github.com/0xAX
I have spent a bit of time prettifying the linux-insides readme.
Small change, but at least the readme no longer looks like it came straight from 2014, where it all started 😅
github.com/0xAX/linux-inside…
Very nice reading - Transformers explained visually
poloclub.github.io/transform…
I have spent a bit of time prettifying the linux-insides readme.
Small change, but at least the readme no longer looks like it came straight from 2014, where it all started 😅
github.com/0xAX/linux-inside…
Fight, do not give up!
I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.