backend engineer · cairo, egypt
.net c sql linux
|
i write code for a living and study systems because i genuinely can't stop. backend engineer from cairo. my days are .NET and C#, sql schemas and api design. the kind of work where reliability matters more than being clever, and people depend on what you build. |
the real learning starts after midnight. that is when i drop past the framework, past the runtime, through the syscall gate, into the kernel. the allocator. the bare handshake between software and hardware. not because it looks cool on a resume. because understanding how things work all the way down makes everything above it easier. |
|
🏗️ building a kernel a unix-like OS from the bootloader up. paging, context switching, vfs, a preemptive scheduler, ide drivers, signals, pipes. the messy art of making a shell work. not because the world needs another kernel. because building one teaches you things no book can. |
📖 reading postgres internals going through the source cover to cover. the buffer pool clock sweep. mvcc. the lock manager. wal and aries recovery. tracing every concept from the paper through the C code. theory without code is incomplete. code without theory is blind. |
🔨 writing small systems a malloc. a kv store over io_uring. a sql parser. a b-tree. nothing production grade. everything educational. each one teaches something the last one did not. also reading linux from 0.95 to 6.x because the history of systems software is written in C. |
backend systems for government platforms, educational software, business applications. the kind of projects where a crash means a phone call and downtime has real consequences. good architecture is survival, not preference.
i pick up languages when the problem needs them. the fundamentals (data structures, systems thinking, architecture) stick with me everywhere i go.
the stack between your keyboard and the disk is hundreds of layers deep. most people stay near the top. the engineers i respect most keep climbing down.
understanding the allocator makes you a better C programmer. understanding the scheduler makes you a better systems designer. understanding the buffer pool makes you better in any language. every layer you learn makes the ones above it clearer.
there is no shortcut. no course, no bootcamp, no prompt will give you what staring at kernel/sched/core.c until the pattern clicks gives you. you sit with it until it makes sense.
that is not a punishment. that is the whole deal. the work teaches you if you let it.
i am not in a hurry. the stack is deep. i have years ahead of me.