[{"content":"I\u0026rsquo;ve kept scattered notes for years — in text files, code comments, and the backs of pull requests. This blog is an attempt to tidy a few of them into something worth reading, for me later and maybe for you now.\nWhy write it down Writing forces clarity. A bug I think I understand often turns out to have a sharper explanation once I try to put it in words. The act of explaining is where the real understanding happens.\nWhat to expect Mostly engineering, close to the ground:\nSystems \u0026amp; performance — where the time and memory actually go Debugging stories — the ones with a lesson attached Tooling \u0026amp; craft — small things that make a codebase nicer to live in Posts will be short when short is enough, and long only when the topic earns it. No filler.\nStaying in touch New posts go out on the RSS feed. If something here is useful, wrong, or interesting, I\u0026rsquo;d genuinely like to hear about it — email me.\nThanks for reading.\n","permalink":"https://blog.kernel.li/posts/hello/","summary":"A short note on why this blog exists and what I plan to write here.","title":"Hello, and What This Blog Is"},{"content":"Hi, I\u0026rsquo;m Yuejun Sun I\u0026rsquo;m a software engineer who enjoys working close to the metal — systems programming, performance, and understanding how things really work underneath the abstractions.\nThis blog is where I keep notes on what I\u0026rsquo;m learning and building: debugging stories, design decisions, and the occasional deep dive into something that caught my curiosity.\nWhat I write about Systems \u0026amp; performance — profiling, memory, concurrency, the Linux stack Engineering craft — tooling, testing, and keeping codebases healthy Lessons from real bugs — the ones worth writing down Elsewhere The fastest way to reach me is by email. You can also subscribe via RSS to follow new posts.\n","permalink":"https://blog.kernel.li/about/","summary":"About me","title":"About"}]