Data Science Teacher Brandyn

24/07/2026

We talk a lot about "observability" in software, using tools to get deep insights into application performance and network health. But what about workflow observability?
In my experience building agentic architectures, wherever there is a massive technical bottleneck, there is almost always an underlying human communication bottleneck hiding right behind it.
This is Conway's Law in action: organizations inevitably design systems that mirror their own internal communication structures. If your human marketing, dev, and finance teams operate in isolated silos and refuse to establish shared data definitions (what we call Ontology Mapping), your digital assembly line will snap.
If we want to truly build scalable AI workflows, we have to start by making our human workflows just as visible as our code. Break down the silos, establish a shared vocabulary, and the technical flow will naturally follow.
Code is easy. It's the human systems that require true architectural thinking.

21/07/2026

You can buy the best enterprise AI tooling in the world, but if your engineering culture lacks psychological safety, your digital transformation will catastrophically stall.
I was thinking recently about the concept of a "generative culture" in tech, especially as we transition into managing "mixed teams"—hybrid battalions of human judgment and autonomous machine ex*****on.
True agility isn't just about spinning up a swarm of agents to reduce batch sizes.
It’s about building an environment where teams feel safe experimenting, and where failures are treated as systemic learning opportunities.
When we focus solely on the technology and ignore the human friction, we miss the point.
If you demand that your team members manage complex, automated workflows while still grading them on industrial-era volume metrics (like hours-in-seat or tickets closed), you will break them.
We need the "Human-in-the-Loop" for their high-stakes judgment, not their mechanical output.
DevOps and AI orchestration, at their core, are cultural imperatives.
How does your team foster psychological safety during complex digital transformations?

14/07/2026

Canadian businesses are at a critical crossroads with the AI revolution, and we cannot afford to sit this one out.
Today, I am incredibly proud to announce the launch of my new book, Skill Shift: From Ex*****on to Orchestration.
I wrote this playbook with a specific mission: to help students and fellow Canadians navigate the AI Era, and to encourage our local businesses to proactively implement this technology to realize unprecedented efficiency gains.
We are facing a brutal reality. The era of building a career solely on your ability to act as a "Biological API", manually pulling digital levers and writing boilerplate code, is officially over. Ex*****on is being commoditized to zero.
But this isn't a threat; it's an overdue promotion. The true "Skill Shift" is the ability to unlearn legacy ex*****on and step into the role of the Orchestrator. The leaders who survive and thrive in this transition aren't the ones who type the fastest. They are the "Empathy Brokers", professionals who combine autonomous machine ex*****on with extreme relational intelligence, psychological safety, and high-stakes judgment.
It is time for us to step off the digital assembly line and into the control room.
I’d love to hear your thoughts on how Canadian tech is adapting to this shift. Are we moving fast enough?
Skill Shift: From Ex*****on to Orchestration is officially live today. To celebrate the release, the digital edition is available at a special promotional rate for the next 24 hours. Secure your copy here:
https://www.amazon.ca/Skill-Shift-Ex*****on-Orchestration-Playbook-ebook/dp/B0H8Q9WCFS/

01/05/2026

Congratulations to the Winning Team Yabba Dabba Data! At last nights AWS Jam.

That was an awesome experience and I was so fortunate to have an amazing team that together we used fixed AWS Bedrock Ai Agentic systems and we ended up winning by a mile :).

Thanks Hussain, Priya and Shivam. You guys were an awesome and really helped us win by a large margin. :)

Thanks Team :)

Its too bad we were working so hard that we forget to get pizza! lol

28/04/2026

We joke about AI taking over the world, but while we were laughing, 5 AI agents quietly unpacked their bags and moved into your daily routine.
It feels exactly like that meme where you're standing alone in an empty bathroom, and a guy walks in just to pick the urinal right next to yours.
AI has gotten uncomfortably close to our personal lives, and most of us didn't even notice.
I’ve been studying for the AWS Generative AI Developer exam lately, and let me tell you, this stuff is hard, and it’s okay if it doesn’t click yet.
But as aspiring data scientists, it is our job to peek behind the curtain and spot the invisible code running our day.
Here are 5 areas where AI agents have quietly taken over, and the hidden data science making it happen:
1. The Inbox Bouncer
Your email isn't just a static spam filter anymore; it's an active NLP agent.
(NLP stands for Natural Language Processing, which is simply a way we teach computers to read, understand, and categorize human words).
This agent reads the context of your emails and silently decides what is important enough for your primary inbox based on your habits.
2. The Fraud Detective
When you buy a coffee, an agent runs an Anomaly Detection model in milliseconds to make sure it's actually you.
(Anomaly Detection is just a math system trained to ring an alarm when data looks out of character for your normal daily routine).
3. The Rideshare Negotiator
Ever notice Uber or Lyft prices jump while you're just staring at the screen?
That’s an agent using Reinforcement Learning.
(Reinforcement Learning trains an AI kind of like a puppy, giving it a digital "treat" or reward every time it makes a highly profitable choice based on live city demand).
4. The Social Media DJ
TikTok and Instagram don't just show you a list of popular videos; they use a Multi-Armed Bandit algorithm.
(This is a casino-inspired math trick where the app constantly tests new, unseen content on you while safely showing what you already like, just to figure out exactly what keeps you hooked).
5. The Texting Mind-Reader
Autocorrect is dead; your phone now uses lightweight LLMs to predict your next thought.
(LLMs, or Large Language Models, are massive prediction engines trained on the whole internet to logically guess the very next word in a sentence).
I remember the first time I tried to code a basic text-prediction model, and my "AI" just repeatedly spit out the word "banana" over and over again.
I felt so defeated, and I questioned if I was cut out for this field.
So if you are reading about Generative AI today and feeling a little overwhelmed, please be kind to yourself.
Take your time with this.
Let’s look at it one more time, break it down, and remember that every expert was once a beginner staring confused at a broken script.
You have the immense potential to not just use these invisible agents, but to build the ones that shape the future.

25/04/2026

Stop trying to build the perfect AI application on your first try. Do this weirdly simple step instead.
I remember my early days trying to build machine learning models, thinking I had to write the most complex code ever on day one.

It was a complete disaster, and I spent hours staring at a broken screen with no idea where I went wrong.

(This stuff is hard, and it’s okay if it doesn’t click yet!)

Here is the weirdly simple step: start with an "ugly baseline."

A baseline is just a simple, basic version of your project that you use as a starting score to compare all your future, complex versions against.

I always tell my data science students this exact same rule whether they are cleaning data, doing an analysis, or building a neural network.

A neural network is a type of machine learning model inspired by the human brain that learns to recognize complex patterns.

I recently had to swallow my own medicine while building "AI Teacher Brandyn," my new educational AI.

I am building a Multi-Agent System for it.

A Multi-Agent System is just a fancy way of saying a team of specialized AI bots working together, instead of one giant bot trying to do everything.

Right now, my architecture is intentionally basic with just two main bots: a "Learn Agent" to guide students through the curriculum, and a "Test Agent" to give practice quizzes.

Overseeing them is a "Routing Supervisor Agent," which acts like a traffic cop, reading the student's prompt and sending it to the right bot.

It is so tempting to add ten more agents to do a million cool things, but here is the rewarding secret: you have to establish that rock-solid baseline first.

I am taking my time experimenting with and fine-tuning these two simple agents.

Then, I validate their performance using a testing technique called "LLM-as-a-judge."

LLM-as-a-judge is when you use a very smart AI model to grade the homework of your AI system, scoring how accurate and helpful the responses actually are.

Because I have a baseline score for a simple setup, whenever I tweak the architecture or add a new agent later, I have something to compare it to.

This guarantees I am creating a real-world improvement in the output, rather than just adding complexity that breaks the system.
Take your time with this. Let’s look at this one more time: build simple, test, validate, and then add complexity.

You have the potential to build incredibly powerful and advanced tools, but remember that every great data project starts by mastering the simple steps first!

PS: I once spent an entire weekend trying to fix a deep learning model, only to realize I forgot to normalize my data... a painfully simple step I skipped because I was rushing to do the complex stuff!

21/04/2026

The difference between an AI Agent and Agentic AI is the difference between a microwave and a personal chef.
Most people are still treating AI like a fancy Google search.
They think an AI Agent and Agentic AI are the same thing.
I used to think so too, until I tried to automate a data pipeline and realized my "agent" was just sitting there waiting for me to hit "Enter" like a lazy intern.
This stuff is hard, and it’s totally okay if it doesn’t click yet—most of the industry is still arguing over the definitions!
Let’s look at this one more time using the image I attached.
An AI Agent is like a smart thermostat.
AI Agent (Task-Focused): A software entity that can observe its environment and take a specific action to reach a single goal.
You tell it "Set the temperature to 21°C," and it does it.
It’s great at ex*****on, but it has a narrow "blindfold" on.
It won’t care if the window is open or if electricity prices just tripled—it just does the one job you gave it.
Agentic AI (Outcome-Focused): A system of multiple agents and tools working together to own a "big picture" result without you holding its hand.
Think of the right side of the image.
The system doesn't just "set the temp."
It checks the weather forecast (Data Retrieval).
It looks at your calendar to see when you're home (User Context).
It monitors energy prices to save you money (Optimization).
It even talks to your appliances to balance the load (Orchestration).
Agentic AI doesn't just do the task; it handles the workflow.
I remember the first time I tried to build a "Simple" scraper... I built an agent to get the data, but I had to manually clean it, manually save it, and manually email the report.
I was the "orchestrator" doing all the hard work!
A truly Agentic System would have seen the dirty data, spun up a "cleaning agent," and realized the report needed to go out every Friday without me saying a word.
Here is the hidden gem for your next interview:
The "secret sauce" of Agentic AI isn't just the LLM—it’s Reasoning and Tool Use.
In 2026, the best Data Scientists aren't just writing Python; they are designing Orchestration Layers.
This is the "brain" that decides which tool to call and when to "loop" back if the first result wasn't good enough.
Take your time with this.
Moving from "Prompting" to "Designing Systems" is a big jump.
But once you start thinking in outcomes instead of tasks, your value as a developer skyrockets.
You’ve got the brain for this—keep building.

18/04/2026

The hardest skill in data science today isn't writing Python anymore—it's reading it.
Everyone thinks large language models, or LLMs, replaced the need to learn the basics.
(An LLM is just the fancy text-predicting AI powering tools like ChatGPT and Gemini).
But from continually doing projects with my students, I'm seeing the exact opposite.
Yes, co-writing code with Gemini in Google Colab gets us to the finish line much faster.
It handles the boring, common parts of a project like a champion.
But I remember the first time I let an AI write a complex data cleaning script for me without checking it closely.
It completely dropped half my dataset because it misunderstood my logic!
This stuff is hard, and it’s okay if navigating AI code doesn’t quite click yet.
Here is the hidden trap most beginners fall into.
As soon as you inject your own ideas and your project becomes a unique research concept, the AI loses its high-level accuracy.
It starts making assumptions.
What ends up happening is you have to read 15 to 20 lines of AI-generated code just to spot the 2 or 3 sneaky mistakes.
Or you have to catch exactly where it started branching in a completely wrong direction for what you planned next.
So even though we physically type way less code these days, the demand on understanding what each line actually does has skyrocketed.
You have to be an editor now, not just a writer.
Let’s look at this one more time with a quick, rewarding tip you can use today to fix this AI hallucination issue.
When prompting your AI for a data transformation (which just means mathematically altering your data, like shrinking extreme outliers so they don't skew your results)...
Don't just ask it to "clean the data."
Instead, explicitly list out the exact columns you want to transform and the specific method you want for each.
If you tell it exactly which columns need a log transformation and which need outlier capping, it understands your intent perfectly.
It will rapidly generate the slightly varied, customized code you need for each individual column without guessing.
Take your time learning these fundamentals.
It's not about memorizing syntax anymore; it's about knowing enough to steer the ship.
If you want to learn the basics in a simple way to accelerate your whole learning process, check out our free path at DataSimple.
https://www.datasimple.education/datasimple-data-learning/python-data-basics-free-learning
You have incredible potential to build amazing things once you master these foundations, so stick with it!
PS: I still look up how to drop a column in Pandas sometimes, so don't ever sweat the small stuff or feel like you need to memorize everything!

15/04/2026

I finished a full-time university degree, many AWS Certications all while working a 40-hour week and kept my marriage happy—without "grinding."
Check out the full conversation on Mike Vardy's Podcast a productive conversation: https://www.youtube.com/watch?v=0Lg0nOpVSjg.
Most people think productivity is about squeezing more juice out of a lemon.
But if you’re a "Forager" like me—someone with a restless, high-energy mind—traditional focus techniques feel like holding your breath underwater.
I remember sitting on my apartment floor years ago, stuffing 500 envelopes a week for a financial job I hated.
My hands were moving at 5 mph, but my brain was spinning at 100 mph, and that friction made me want to crawl out of my skin.
I wasn't "broken" or "distracted." I was under-utilized.
I realized that if I gave the "wandering" 15% of my brain a simple task—like a narrative movie—the other 85% could actually do the rote work in a "Mechanical Trance".
This is what I call Parallel Processing: layering a low-load task (like laundry or commuting) with a high-load one (like learning a new language).
The secret "hidden gem"? It’s called Cross-Modal Stacking.
Your brain has separate "pools" for different senses. You can’t write an email and listen to a podcast at the same time because they both fight for your Language Center.
But you can listen to a lecture while walking or cooking because those tasks use different neural "lanes".
I used these exact methods to knock out AWS certifications and a degree while working full-time, all without missing dinner with my wife.
You don't need more willpower; you need a better internal "operating manual" for the 21st century.
Take your time with this—it's okay if it doesn't click immediately, but know that your restless mind is a high-performance engine, not a flaw.
You have the power to be an architect of your own focus, not just a reactive participant in a loud world.

PS: Here is a quick win: Next time you have a "dead" 5-minute gap, don't doom-scroll. Use a "Strategic Switch" to knock out one tiny, pre-planned task from your list. It’s the dopamine hit your brain actually craves.

Much of the modern productivity conversation revolves around a single ideal: deep work. The ability to focus intensely on one task at a time is often present...

14/04/2026

My friend tried to break my AI, and it taught me a $15,000 lesson in "cheap" tech.
My friend tried to break my AI today.
https://www.datasimple.education/ai-tutor-brandyn
He went full "troll mode" on Teacher Brandyn at DataSimple.education.
He wasn't looking for Python tips or Seaborn tutorials.
He was stress-testing the soul of the machine.
And it was the best thing that could have happened for my product.
I’ve been debating a technical choice lately:
Should I use Claude Haiku or Claude Sonnet for my "orchestration agent"?
An orchestration agent is basically the "brainy receptionist" that decides which specialist AI should handle your specific question.
Haiku is fast and dirt cheap.
Sonnet is the premium, heavy-lifting model with deeper reasoning.
I thought, "Hey, for just routing a message, Haiku is plenty smart, right?"
Wrong.
Watching my friend’s "troll" prompts, I realized something critical.
The first contact isn’t just about classification—it’s about character.
Haiku might have just tagged the message as "noise."
But Sonnet? It handled the trolling like a champ, stayed in character, and gently nudged the "student" back to data science.
It maintained the "Humble Guide" vibe I worked so hard to build.
In data science—and in business—we often try to optimize for cost too early.
But if your "first contact" layer feels like a rigid robot, you lose the user before they even see your best work.
This stuff is hard, and building these systems is even harder.
It's okay to spend a little more on the "brain" if it means your users feel heard, even when they’re just messing around.
Don’t cheap out on the bridge between your tech and your humans.
You’ve got the potential to build something amazing—just make sure it has the "wisdom" to handle the bumps along the way.