I stopped learning Python because something felt missing. Here's what pulled me toward Linux Kernels instead.

Some journeys don't start with tutorials. Mine started with one random question at 11pm: "How did computers even begin?" That question pulled me into a two-month rabbit hole. The Jacquard loom. Babbage's machine. Ada Lovelace. Vacuum tubes. Transistors. Turing. Enigma. CPUs, clocks, GHz, memory — everything that makes computers breathe. It felt natural. It felt deep. It felt like home. Then I tried Python. Everyone said start here. So I did. But something felt wrong. Writing features felt like describing the surface of water — I kept wanting to know what was underneath . I didn't want to build on top of the system. I wanted to understand the system itself. Then I touched Linux. Kernels. Init systems. Boot sequences. Ring 0. Ring 3. The same excitement from that late-night rabbit hole came rushing back. That's when it clicked: I'm wired for systems. Since then: Daily commits to GitHub studying Linux kernel internals Built my first kernel module — character device driver Hit a kernel pan