Alex Kuleshov

8K posts

Alex Kuleshov banner
Alex Kuleshov

Alex Kuleshov

@0xAX

Software developer. Passionate about Linux, Kubernetes, databases and things around. Author of linux-insides.

Katılım Ekim 2012
182 Takip Edilen11.2K Takipçiler
Sabitlenmiş Tweet
Alex Kuleshov
Alex Kuleshov@0xAX·
Took me almost a month, but it’s finally done. I completely rewrote the first chapter of linux-insides about the Linux kernel initialization process. Now it should be aligned with modern kernels (up to master). github.com/0xAX/linux-ins…
English
11
222
1.3K
52.5K
Alex Kuleshov
Alex Kuleshov@0xAX·
Replaced Discord.SortedSet NIF for IP pool allocation in our Elixir app. Initially, I learned about the library from Discord from this great post: Using Rust to Scale Elixir for 11 Million Concurrent Users - discord.com/blog/using-rus… Now swapped to: bucketed Vec> -> two flat u32 arrays and sparse set on top. No malloc, no memmove, no memcpy. Allocate once and reuse. First benchmarks look promising:
Alex Kuleshov tweet media
English
0
0
5
328
Alex Kuleshov
Alex Kuleshov@0xAX·
GitHub is still not ready to accept that bun moved from zig to rust
Alex Kuleshov tweet media
English
0
0
6
1.1K
Vikram
Vikram@vchennai2·
We're position 4 on the front page of HN :)
Vikram tweet media
English
6
1
64
5K
Arpit Bhayani
Arpit Bhayani@arpit_bhayani·
ape turned 35. ape happy.
Arpit Bhayani tweet media
English
183
5
2.4K
54.8K
Maksim Terekhin 🇺🇦
@0xAX Hope you get a great opportunity soon 🙏 Market is flipped, it seems, especially for remote positions. Good luck 👍
English
1
0
1
70
Alex Kuleshov
Alex Kuleshov@0xAX·
I’m considering my next career step and would be happy to hear about interesting remote backend/infra roles. My background is mostly in Elixir/Erlang/OTP, distributed backend systems, Kubernetes, observability, and telecom/AAA platforms. I’m especially interested in technically strong teams working on infrastructure, observability, databases, Kubernetes, or distributed systems. I’m based in GMT+5 and open to working with teams across compatible time zones. If your team is hiring for something similar, feel free to DM me or point me to the right person.
English
1
3
11
1.6K
Alex Kuleshov retweetledi
mark_l_watson
mark_l_watson@mark_l_watson·
Two new chapters in my Common Lisp book and a lot of fun! New chapters: "Building an AI Coding Assistant for Common Lisp" "Hacking the SBCL REPL" that is a work in progress, with two examples (for now): - Using `#!` to execute shell commands. - Adding an AI coding agent that is always available in the REPL and instantiated with `#?`. Read free online (last two chapters): leanpub.com/read/lovinglisp
English
0
2
18
1.1K
Dmitrii Kovanikov
Dmitrii Kovanikov@ChShersh·
Pray for me today. I have one of the most important things to do in my life. And I need it to succeed.
English
51
0
387
20.7K
Alex Kuleshov retweetledi
Phil Eaton
Phil Eaton@eatonphil·
Whatever your transactional database is, help me understand your use of it. This survey is run by @theconsensusdev, independent of any database or vendor. RT or pass along to industry peers for broader representation forms.gle/fqjQsezWsztxvY…
Phil Eaton tweet media
English
1
11
15
4.7K
Alex Kuleshov
Alex Kuleshov@0xAX·
I would have completely agreed if I had read this in the pre-ai era. Right now, I honestly don't know. I think about it from time to time, but I still haven't come up with an answer. The problem is that with this approach, all eight of your working hours can be spent on review. The situation is especially exacerbated if you have colleagues who can generate PRs in, say, 40 minutes, and you need to thoroughly check it
Arpit Bhayani@arpit_bhayani

If someone is waiting on you for a code review, that has to be your P0 task. Look, waiting on a code review is one of the most frustrating things because the person is literally blocked on you. It gets even worse when there is a time zone difference to deal with. I get it. You do not have malicious intent and are genuinely busy with something important. But still, I would say it is a prioritization problem. Most people treat code review as something they get to when they have a quiet moment, and that quiet moment rarely comes. Coming from my personal pain point, I would say treat code review as a high-priority task, not a background one. If your teammate has raised a PR and you are the reviewer, that is important work in progress sitting idle. Every hour it waits is an hour of 'blocked momentum' (yeah, fancy term). Also, it is okay to preempt your non-urgent work for it. This matters even more across time zones because a delayed review does not cost an hour; it costs an entire working day for the other person (ohhh, this used to be such a pain). So the next time you see a PR sitting there, wrap up the review, because it is not "someone else's work"; it is yours. Hope this helps.

English
0
1
9
1.9K
🫡︎
🫡︎@gizmobly·
Pls recommend a very good technical book that can be finished within 10 hours 🫡
English
17
1
62
9.3K
Alex Kuleshov
Alex Kuleshov@0xAX·
According to my X feed today it seems everything is faster than postgres on nvme
English
1
0
5
1.1K
Alex Kuleshov retweetledi
trish
trish@TrisH0x2A·
the linux kernel's min() macro is one of the most carefully engineered macros ever written standard C's #define min(a,b) ((a)<(b)?(a):(b)) evaluates a or b TWICE and if you pass min(x++, y) you get a double increment the kernel uses a GCC extension: statement expressions.
trish tweet media
English
17
48
491
30.9K