Search…

Computer Vision Roadmap: From Basics to Real Projects

In this series (30 parts)
  1. Computer Vision Roadmap: From Basics to Real Projects
  2. What is Computer Vision? From Pixels to Decisions
  3. A Short History of Computer Vision: 1545 to Now
  4. Math for CV Beginners: Vectors, Matrices, Convolutions
  5. Image Fundamentals: Color, Histograms, Noise, Filtering
  6. How Images and Video Are Stored: Colour, JPEG, Frames
  7. OpenCV Setup + First 10 Tasks in Python
  8. Vision Metrics: Accuracy, Precision, Recall, mAP, IoU
  9. CV Project Workflow: Dataset, Baseline, Error Iteration
  10. Intensity Transforms and Frequency-Domain Filtering
  11. Edge Detection and Thresholding That Actually Work
  12. Morphology, Contours, and Shape Analysis for Real Images
  13. Feature Matching (SIFT/ORB) and Image Stitching
  14. Camera Calibration and Perspective Correction
  15. Epipolar Geometry, Stereo Vision, and Depth Estimation
  16. Optical Flow and Motion Tracking in Video
  17. HOG, HOF and MBH: Descriptors Before Deep Learning
  18. Your First Image Classifier (PyTorch + Transfer Learning)
  19. Data Pipelines and Augmentation for Vision Models
  20. CNN Architectures Explained: From LeNet to ResNet
  21. YOLO Detection Pipeline: Data to Inference
  22. Semantic and Instance Segmentation: U-Net to Mask R-CNN
  23. Vision Transformers (ViT) and When to Use Them
  24. CV Explainability: Grad-CAM, Failures, Bias Checks
  25. 3D Vision Basics: SfM, Point Clouds, and Pose Estimation
  26. Multimodal Vision: CLIP, Embeddings, and Retrieval Systems
  27. Video Understanding: Flow Networks, Interpolation, Stabilisation
  28. Real-Time CV Systems: Tracking, Latency, Streaming
  29. Deploying CV Models: ONNX, TensorRT, Edge, and APIs
  30. Responsible CV: Privacy, Fairness, Security, Governance

This is a 29-post path through computer vision, written so that someone who has never opened an image in Python and someone who trains models for a living both find something they can use. Every post has hand-worked examples, runnable code, and a practice task.

What you will be able to build

By the end of the series you should be able to do all of these without looking anything up:

  • Load, inspect, and clean images, and know from a histogram whether an image is even usable.
  • Tell from a file whether it has already been through a lossy step that will hurt your model.
  • Build a working inspection or counting system using thresholds, contours, and shape measurements, with no training data at all.
  • Calibrate a camera, correct perspective, and convert pixel measurements into real-world millimetres.
  • Stitch photos into a panorama and estimate depth from a stereo pair.
  • Fine-tune an image classifier, train an object detector, and train a segmentation model.
  • Process video efficiently instead of running an image model 30 times a second.
  • Explain why a model made a prediction, and find the bias in it before someone else does.
  • Deploy a model to run in real time on a CPU, a GPU, or an edge device.
  • Evaluate all of the above honestly and know which metric is lying to you.

The four parts

Part 1: FoundationsPart 2: Classical CVPart 3: Deep learningPart 4: Production
Posts1-910-1617-2223-29
Main toolsNumPy, OpenCVOpenCVPyTorchONNX, TensorRT, monitoring
HardwareAny laptopAny laptopGPU strongly preferredVaries
Training data neededNoneNoneHundreds to thousandsDepends
Time to work through~20 hours~20 hours~24 hours~22 hours
You end up able toRead and clean imagesBuild rule-based systemsTrain models for real tasksShip and keep them working
What each part covers and what it costs you

Choose your route

You do not have to read all 29 posts in order. Pick the route that matches where you are.

# If you are... Start with Then Skip for now
1 New to images entirely 1 → 2 → 3 → 4 5, 6, 7, 8, then part 2 in order Nothing, go in order
2 A developer who wants something working this week 1 → 6 → 10 → 11 7, 8, then 17 The heavy math in 3, and post 9
3 An ML practitioner adding vision 1 → 7 → 17 → 18 19, 20, 21, 22 Parts of 2 and 4 you already know
4 An engineer shipping an existing model 7 → 8 → 26 → 27 28, 23, 29 Parts 1 and 2 mostly
5 A student preparing for interviews 3 → 19 → 22 → 20 2, 7, 16, 23 Part 4 until later

Five routes through the same 29 posts

Posts 7 and 8 sit in the middle of every route on purpose. Measuring honestly and knowing what to fix next are the two skills that decide whether a project finishes, and they apply equally to a threshold rule and to a transformer.

Part 1: Foundations (posts 1–9)

# # Post What you build or work out by hand
1 1 What is computer vision? A cap-detection rule from a raw 8×8 pixel grid, counted by hand
2 2 History of computer vision Why every era's method failed, traced through one running problem
3 3 Math for CV beginners A 3×3 convolution computed cell by cell; layer output sizes
4 4 Image fundamentals An RGB→HSV conversion by hand showing why hue survives lighting changes
5 5 How images and video are stored A DCT block, a bit-depth reduction, and the I/P/B latency argument
6 6 OpenCV setup + first 10 tasks Ten runnable tasks, ending in a batch processor with a CSV report
7 7 Vision metrics IoU, precision, recall, F1 and Average Precision all computed by hand
8 8 CV project workflow An error-bucket analysis that shows which fix returns the most per day
9 9 Intensity transforms and frequency filtering A log transform with the constant derived, and a Butterworth response table

Part 1 — nothing here needs a GPU or any training data

Part 2: Classical CV and geometry (posts 10–16)

Classical methods still run most working vision systems in factories, on production lines, and inside larger pipelines. They need no training data, they run on any CPU, and you can explain exactly why they made a decision.

Part 3: Deep learning for vision (posts 17–22)

# # Post Task it solves Typical training time
1 17 First image classifier (PyTorch) Classification 20 min on a GPU
2 18 Data pipelines and augmentation Every task n/a
3 19 CNN architectures: LeNet to ResNet Understanding n/a
4 20 YOLO object detection pipeline Detection 2-8 hours
5 21 Semantic and instance segmentation Segmentation 4-12 hours
6 22 Vision transformers (ViT) Classification and beyond Hours to days

Part 3 — a GPU makes a real difference here, though everything runs on CPU if you are patient

Part 4: Modern CV, video, deployment, and responsible use (posts 23–29)

Check whether you are ready

Answer these four. If you can, start at post 1 and move quickly. If you cannot, start at post 1 and move slowly. Either way, post 1 is the right place.

  1. In Python, what does a[2:5] give you if a = [10, 20, 30, 40, 50]?
  2. If a NumPy array has shape (480, 640, 3), how many numbers does it contain in total?
  3. What is 1818+7\frac{18}{18 + 7} as a decimal?
  4. If you multiply every number in a list by 0.5, what happens to the average?

Answers: (1) [30, 40, 50]. (2) 480×640×3=921,600480 \times 640 \times 3 = 921{,}600. (3) 0.720.72. (4) It halves.

That is genuinely the entry bar for parts 1 and 2. Part 3 additionally assumes you have seen a training loop before; if not, the machine learning series covers that ground first, and neural networks from scratch covers backpropagation.

What you will install

# Part Install Hardware
1 1 and 2 python, numpy, opencv-python, matplotlib Any laptop
2 3 + torch, torchvision, albumentations GPU strongly preferred
3 3 (detection) + ultralytics or detectron2 GPU
4 4 + onnxruntime, optionally tensorrt Depends on target

Nothing needs installing until the post that uses it

If you have no GPU, Google Colab and Kaggle Notebooks both give free GPU time that is enough for every training task in part 3.

How to actually get through it

Checkpoints

Five points where you should be able to build something on your own, with nothing open but a terminal.

# After post You should be able to If you cannot, revisit
1 6 Load a folder of images, resize them correctly, and produce a CSV of measurements Posts 1, 4 and 6
2 11 Count and measure objects on a plain background, and say when it will fail Posts 4, 10 and 11
3 18 Fine-tune a classifier on your own photos and report precision and recall Posts 7, 8 and 17
4 22 Choose between a CNN and a ViT for a given dataset size and justify it Posts 19 and 22
5 28 Export a model, measure its latency, and state its throughput on real hardware Posts 27 and 28

Five checkpoints. Each one is a small project, not a quiz.

Roughly 86 hours end to end with the practice tasks. At five hours a week that is about four months, which is a realistic pace for something you are learning alongside other work.

Summary

Twenty-nine posts, four parts, five routes. Parts 1 and 2 need nothing but a laptop and give you systems that work without any training data. Part 3 adds learned models for classification, detection, and segmentation. Part 4 covers video, explaining, shipping, and keeping models working once real conditions hit them.

Whichever route you take, posts 7 and 8 are the ones to read early. Everything else is a technique; those two are the judgement that decides which technique you need.

Start here

What is computer vision? opens with a real factory problem and solves it completely using nothing but a grid of numbers and a threshold. It is the shortest path to understanding what every method in the rest of the series is actually doing.

Frequently asked questions

Do I need a GPU to follow this series?
Not for parts 1 and 2, which cover 16 of the 29 posts and run comfortably on any laptop. Part 3 trains neural networks, and while everything runs on CPU it will be slow. Google Colab and Kaggle both offer free GPU sessions that are enough for every training task here.
Do I need to know machine learning before starting?
No. Parts 1 and 2 involve no learning at all, only image processing and geometry. By the time you reach part 3 you will want a working idea of training loops, loss functions, and overfitting, and the machine learning series on this site covers that if you need it.
Is classical computer vision still worth learning?
Yes, and more than most people expect. Threshold and contour methods run a large share of working industrial inspection systems because they need no training data, run on cheap hardware, and can be explained to an auditor. They also form the baseline that tells you whether a learned model is actually earning its cost.
How long does the whole series take?
Roughly 75 to 95 hours including the practice tasks, which is about four months at five hours a week. If you only need one part, budget 20 to 24 hours for it. The practice tasks are where most of the learning happens, so cutting them to save time mostly saves you from learning.
Can I skip to the post I need right now?
Yes. Each post lists its prerequisites at the top and links back to them, so you can follow the chain backwards when something is unfamiliar. The only real recommendation is to read posts 7 and 8 early no matter what, because they are what let you tell whether anything else is working.
Start typing to search across all content
navigate Enter open Esc close