Why "Behind the Scenes" Isn't Optional in Machine Learning

Basma Deniour — Wed, 02 Sep 2026 13:00:00 +0000

Why “Behind the Scenes” Isn’t Optional in Machine Learning

There’s a version of Machine Learning that treats models as interchangeable black boxes:

Import the library.
Call .fit().
Tune a few hyperparameters.
Ship it.

It works — until it doesn’t.

When a model fails, the real question isn’t just “How do I fix it?”

It’s “Why is it failing in the first place?”

The engineers who can answer that question are the ones who understand what’s happening beneath the API.

Not because knowing the internals is intellectually satisfying — although it is — but because that understanding is what separates applying a model from engineering one.

Knowing that Gradient Descent exists is not the same as understanding why it becomes preferable to closed-form solutions as problems scale.

Knowing that Softmax outputs sum to one is not the same as understanding why that alone doesn’t make its outputs true probabilities.

Knowing what a technique does is useful.

Understanding why it works, when it works, and what assumptions it depends on is what allows you to adapt it when the problem doesn’t look like the textbook example.

And you can’t meaningfully customize something you don’t understand.

That’s the idea behind #MLUnboxed — a series where I’ll break down Machine Learning and Statistics concepts, including many that are already well documented, but without stripping away the mechanics that make them work.

The goal isn’t to reinvent established ideas.

It’s to understand them deeply enough to use them intelligently.

This series is for people who already know the “what” and are ready to spend more time with the “why.”

If that sounds like you, let’s get into it.

DEV Community: Basma Deniour

Why "Behind the Scenes" Isn't Optional in Machine Learning