About

pkglog is a technical blog that 0xmote writes and maintains alone. Most of it is about C++ systems and network programming, with some posts on web development, databases, and DevOps as well. The point isn't traffic; it's keeping notes that are still useful when I come back to them months later.

The site started in early 2026, and publishing hasn't been steady. There have been quiet stretches when new projects, translation, or cleanup work took over. Rather than promise a schedule, I'd rather keep what's already here accurate.

About the author

I write C++ for a living. Recently most of that work has been on autonomous mobile robot (AMR) software, camera video streaming, and the tooling that lets a team build and ship the same code base. The robotics posts (ROS 2, Gazebo simulation, path planning), the media posts (RTSP, WebRTC, HLS, codecs, DRM), and the build and collaboration posts (CMake, GitLab, Jira) mostly started as problems I got stuck on along the way.

The C++ posts try to explain why something is written a certain way and where it breaks in practice, rather than walking through syntax. Company names, project names, and internal code never appear here; every example is rewritten from scratch so it can be published, and checked on its own.

What's covered

The biggest topic by far is C++: compiler basics, the memory model, smart pointers, lock-free data structures, and network programming with sockets, epoll, and io_uring. There are also posts on other languages (Python, Go, Rust, TypeScript), databases (PostgreSQL, MySQL, Redis, and others), and infrastructure tools such as Docker and Kubernetes.

Posts vary in depth. Some are short, code-first references I keep for myself; others spend most of their length on background, trade-offs, and the mistakes that led to them.

How this is written

I use an AI assistant (Claude Code) to help with drafts and with polishing sentences. Code examples are run and checked by me rather than taken on faith, and mistakes get fixed when I find them. None of this is perfect, so if you spot an error, the contact details below reach me directly.

Every post shows when it was first published and when it was last updated. Older posts aren't left to rot: when something turns out to be wrong or out of date, I rewrite it, merge it into a better post, or take it down.

Contact

Corrections, questions, and ideas for working together are all welcome.

See the Privacy Policy and Terms of Service for how this site handles data and content. The site shows ads through Google AdSense.