Front Matter
F3 · Who Should Read This Book

Who Should Read This Book

This book is written for people who build software and want to build vision systems: thoroughly, from the pixel up, without first acquiring a graduate degree in the subject. If you can write Python and remember what a matrix multiplication does, you have everything you need to start at Chapter 0 and finish at the capstone.

You Are in the Right Place If...

What You Need Before Page One

Two prerequisites, both modest. First, working Python: functions, classes, virtual environments, installing packages. You do not need to be an expert; the code favors clarity over cleverness. Second, basic linear algebra: vectors, matrices, dot products, and a comfort with the idea that a transformation can be written as a matrix. A nodding acquaintance with derivatives and probability helps in Parts III and IV, and Appendix A refreshes every piece of mathematics the chapters rely on, exactly when honesty requires more than intuition.

Hardware is not a barrier. Parts I and II run comfortably on any laptop CPU. Part III and Part IV benefit from a GPU, but the chapters are written so that a modest consumer card or a free cloud notebook is enough to run every example; nothing in the book requires a data-center budget.

What You Do Not Need

You do not need prior computer vision experience: the book assumes none and defines every term it uses. You do not need a mathematics degree: formal results appear where they earn their keep, always alongside code and pictures. And you do not need allegiance to a particular framework: the book teaches concepts first and uses the best mainstream tool for each job, OpenCV and scikit-image early, PyTorch and the Hugging Face ecosystem later.

What This Book Is Not

It is not a theory monograph; proofs are sketched only when they change how you build. It is not an exhaustive survey of the research literature; each chapter curates a short annotated bibliography instead of citing everything. And it is not a cookbook of recipes for one library version; APIs appear throughout, but the goal is the understanding that survives the next major release.

If that matches your situation, continue to the next page for a guided preview of what the chapters look like inside, or jump straight to How to Use This Book to pick your reading path.