Systems nerd. Hacking @zymtrace. Building an OS kernel in Rust and userspace in Zig currently.
Joined April 2026
- Tweets 65
- Following 25
- Followers 6
- Likes 26
7 Photos and videos
Jun 10
The funniest thing in the replies is AI-pilled people comparing the requirements of a robust, maintainable distributed system serving millions of users to their CRUD web app and saying AWS is wrong. Yeah boss, they should've hired you instead.
Jun 9
More AI-generated code doesn't make your team faster. It might actually slow you down.
1
17
Jun 8
I will proudly continue to not know what "looping" my agent means. As long as it does the monkey work that I definitely don't wanna do myself, I don't need anything else.
Jun 7
i hate how a few people will use a term and it will just become the "thing you should be doing."
99.9999% of you should in fact not being "looping" your agent
15
Jun 6
One of the best use of AI for me is to use it as a frontend for GDB. With some monitoring and guidance, it's much faster to find the root cause of the issues.
18
May 31
Watching the interview with Andrew impressed me so much that I started learning Zig yesterday. There is still much to do but my kernel now has it's first userspace program written in Zig.
For now, I'm planning to only implement the further userspace programs in Zig but I might write some parts of the kernel with it as well.
See:
github.com/aeryz/efiks-os/bl…
1
31
May 30
Agreed 100%. Use AI but don't give up on your brain.
May 28
I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem.
As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)!
I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work.
It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results?
88ms => 1.5ms
150K allocs => ~500 allocs
Incredible right? Nope.
My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path.
This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput.
The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity.
Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.
24
May 27
I've been building my OS in @rustlang from scratch for a while, and here are the updates from the last few weeks:
1. Implemented a VirtIO block driver to have persistent storage. It only supports synchronized reads/writes and no caching.
2. Implemented a simple VFS with only open, read, write and seek support.
3. Implemented the VSFS (very-simple file system) from the OSTEP book as the concrete filesystem implementation. Works well enough at this stage tbf.
4. Vibe-coded a tool to create a VSFS filesystem image based on a local file tree. (this is not a part of the learning experience, so im not gonna spend my limited time on it)
5. Implemented ELF-loading: Now I can load binaries directly from the filesystem. This way, I was able to split the userspace programs and the kernel binary entirely which is nice.
1
26
May 27
Next steps:
1. I again have a good amount of tech debt. Especially the task spawning logic now has a lot responsibilities. Need to fix that first.
2. Need to introduce a minimal task lifespan. Currently, we just spawn tasks and they run endlessly. But there is no exit, or parent/child stuff.
1
24
May 27
Very curious about the motivation of people vibe-coding non-trivial things and sharing it as if it's their work. I'm not against the use of AI or even vibe-coding. I'm just curious let's say you fooled everyone into thinking it's your code, and you got a cool job, how are you going to sustain that in a good team with decent engineers?
1
18
May 15
They are just making really sure that f->entries is unusable. Not seeing any issues here tbf.
My friend at dinner: AI bug hunters are ruining open-source projects 😭
Me: Well, an AI costing $20 a month would not write code like this
41
🔊 We’re thrilled to welcome Abdullah Eryuzlu (@KernelNomad_ ) to zymtrace.
Abdullah is a systems engineer with a deep passion for low-level programming, kernels, and performance optimization.
1
3
7
277
May 10
Lately I started this habit where instead of detailed planning and journaling, at the end of the day, I log what I did for my professional and personal work and the immediate next thing I'm gonna be working on tomorrow. It works very well so far. Will let my 4 followers know if it works after a month.
42
May 8
Nvidia just dropped a new thing to play with on the weekend. nice
May 8
Finally able to talk about what I've been heads-down on for 6 months at @nvidia 🦀⚡
We just open-sourced cuda-oxide — an experimental rustc backend that lets you write CUDA kernels in pure Rust.
No DSLs. No FFI. No source-to-source step. Single source.
Short🧵👇
ALT cuda-oxide is an experimental Rust-to-CUDA compiler that lets you write (SIMT) GPU kernels in safe(ish), idiomatic Rust.
1
62
May 7
The more I make progress in my kernel, the more I realize that the algorithms and making the hardware do stuff is not the hard part of writing an OS. But the hardest part is coming with a good abstraction and not doing hacky stuff all the time to support new things.
1
30
Apr 29
For the past few weeks I was looking for a @rustlang based, fully remote, non-crypto or non-backend job. I found one and here are my experiences:
1
1
71
Apr 29
1 other process was found on Linkedin (the only one on the worlds largest platform) and the last one is found on YCombinator's platform for the startups.
1
1
60
Apr 29
To sum up, X turned out to be the best platform for me who is looking for a very specific position. So I advise you to occosionally try searching for "rust", "hiring" etc. and just connect to the hirers even if you think you don't cover all the soft requirements.
2
64