• System / infrastructure oriented C++ developer
• Focus on IPC, shared memory, ring buffer, low-latency communication
• Prefer simple, explicit, debuggable designs over over-engineering
• Building reusable low-level libraries, not one-off applications
• Linux / Windows cross-platform development

• Cross-process ring buffer based on shared memory
• MPSC / SPSC friendly design
• Explicit memory layout, no hidden allocation
• Cross-platform (Linux / Windows)

• High-performance event loop
• epoll + C++20 coroutine
• Minimal abstraction, no framework-style magic
• Designed for system-level services

• Avoid implicit behavior
• Avoid global state
• Avoid framework lock-in
• Prefer mechanical sympathy over abstraction purity
• If it cannot be reasoned about, it is probably wrong

Software engineering is not about stacking abstractions,
but about understanding constraints and making trade-offs explicit.