I Wrote a Docker Book — Here's Why
I never got through most technical books. Too much theory. Too many words. Not enough action. So I wrote the book I wished existed — practical, concise, and straight to the point. Just enough explanation to get things done. Why This Book? Over the past 5 years, I've worked with Docker in training rooms, client environments, and real production deployments in Singapore — teaching engineers, advising on architecture, and rolling it out on actual infrastructure. Docker comes up everywhere, and so does the same question: where do I start? The problem isn't capability. It's always the same thing: people get lost in the theory before they ever run a single container. They read about namespaces and cgroups and layer caches, and by the time they get to an actual command, they've lost the thread. So I started keeping notes — just the practical bits. The commands that actually matter. The patterns that show up again and again in real deployments. During Chinese New ...