I Thought Building AI Meant Learning Python. I Was Wrong.

For the longest time, I believed one thing:

If I wanted to build AI applications, I'd eventually have to leave my TypeScript stack behind and learn Python.

As a Full Stack Developer, every AI roadmap I came across looked something like this:

Python → NumPy → Pandas → PyTorch → TensorFlow → Deep Learning → Research Papers...

Honestly, it felt overwhelming.

A few weeks ago, I started digging into how companies actually build computer vision products. Things like:

• Driver monitoring systems in cars

• CCTV analytics

• Smart parking

• Retail theft detection

• Factory safety systems

• Attendance systems

I expected to find hundreds of pages of machine learning magic.

Instead, I found something much more interesting.

AI is just one small part of the system

One thing finally clicked for me.

Most real-world AI products aren't just "an AI model."

They're software systems.

A very simplified architecture looks something like this:

Camera
    ↓
Video Stream
    ↓
AI Model
    ↓
Business Rules
    ↓
Database
    ↓
Notifications
    ↓
Dashboard

The AI model is only one component.

Everything else is just software engineering.

That realization completely changed how I think about AI.

I also misunderstood what YOLO actually does

Before this, I thought models like YOLO somehow understood what was happening inside a video.

They don't.

YOLO doesn't know if someone is cheating in an exam.

It doesn't know if someone is stealing from a store.

It doesn't know if a driver is sleepy.

It simply says things like:

• Person

• Phone

• Bottle

• Car

• Laptop

That's it.

The interesting part comes afterwards.

Your application decides what those detections actually mean.

The business logic is where products become useful

Let's imagine an online exam.

YOLO detects:

• Person

• Phone

Your backend decides:

"If the exam has started and a phone is visible, create an alert."

Now imagine a retail store.

The exact same model detects:

• Person

• Bottle

Different product.

Different business rules.

Same AI model.

That was another big "aha!" moment for me.

You don't always need to train AI models

This was another misconception I had.

I assumed every company trained huge AI models from scratch.

Turns out, many products start with pretrained models.

The engineering effort goes into integrating them into a useful application.

Only after validating the product do teams usually think about collecting their own datasets and improving the model.

The best part?

I don't have to abandon the stack I already enjoy.

I can still build applications using:

• TypeScript

• Node.js

• Next.js

• PostgreSQL

while running pretrained AI models using technologies like ONNX Runtime.

That completely changed how approachable computer vision feels.

I'm still learning

I'm definitely not an expert in this space.

I'm just documenting what I'm learning because I know there are probably other JavaScript developers who think AI is only about ChatGPT or Python.

Over the next few weeks, I'm planning to explore topics like:

• How RTSP cameras actually work

• How AI models process video streams

• Why object tracking matters

• What ONNX Runtime actually does

• How production AI systems are designed

• Building small computer vision projects using TypeScript

If you're also exploring this space, I'd love to connect.

Learning in public has always been one of the best ways I've found to understand something deeply, and hopefully these notes help someone else who's just getting started.