You solve a LeetCode problem, feel like a genius, and two weeks later it is gone. Here you save the link and a short note on the trick. It comes back after 3, 7 and 30 days, right before you would forget it.
Each review is a quick re-solve, not a re-learn. A few minutes a day and the patterns actually stick for the interview.
Ever wanted to just see what the kernel is doing? Which process keeps opening that file, where the latency hides, why packets drop. Tell me what you need.
I review every request, build the tool with eBPF and publish it for free at jrzayev/BPFs. You get a working tool, I get real problems to learn on. Good ideas are the hardest part, so you are helping me too.
Write a real XDP program, run it on packets right in your browser and watch every register, byte and map change. Drop a ping, block SSH, count packets per protocol, see the C next to the bytecode. A small verifier tells you what the kernel would reject. No account needed.