Skip to main content

The First Notebook

Somewhere between where I was and where I am going!


Welcome to One Notebook at a Time.


Every data project starts the same way.

A blank notebook. A first cell. No idea yet what the data is going to say, or whether the model is going to work, or whether the whole approach is wrong and you'll scrap it by Tuesday.

You just start.

This blog is that first cell.


Why "One Notebook at a Time"

I picked this name because it's literally true on two levels.

If you're a data person, you already know what a notebook is — Jupyter, Colab, whatever your tool of choice. It's where the real thinking happens. Not the polished dashboard, not the final slide deck — the notebook. Messy cells, half-finished thoughts, a graph that didn't work followed by one that finally did.

But it's also true in the older sense of the word. A notebook is just where you write things down before you know what they're going to become.

That's what this space is for. One notebook — one post, one idea, one small piece of the bigger picture — at a time.


What This Blog Is

I'm currently mid-pivot — moving from a background in IT and systems work into Data Science and Analytics. I'm not writing from the other side of that transition, looking back at it cleanly. I'm writing from inside it, right now, while it's still happening.

So this won't be a highlight reel. It'll be closer to a working notebook than a finished paper.

Here's what you can expect:

  • Concepts, explained simply — the kind of explanations I wish I'd had when I was first learning them
  • Real projects, real mess — the actual process behind the work, not just the clean final output
  • AI tools, tested honestly — what's actually useful day to day versus what's just noise
  • The pivot itself — documented as it happens, including the parts that don't make for a good highlight reel

Why I'm Doing This in Public

It would be easier to learn quietly and only show up once I had a polished, finished version of myself to present. A lot of people do it that way, and there's nothing wrong with that approach.

But I think there's more value — for me and maybe for you — in showing the actual process. The questions I'm still working through. The things that click on the third attempt instead of the first. The honest version of what it looks like to rebuild a career path mid-stream rather than at the very beginning.

If you're somewhere in a similar middle — pivoting industries, learning a new skill set, rebuilding something — I think you'll recognize a lot of what shows up here.


Where to Start

This is post one. There's no archive yet, no "best of" to point you toward. Just this notebook, and the ones that will come after it.

If that sounds like something you want to follow along with, stick around. I'll be adding new entries regularly — some technical, some reflective, all genuinely worked through rather than polished for show.

See you in the next notebook.

Comments

Popular posts from this blog

The Line of Best Fit Isn't "Best" — It's a Decision What I wish someone had told me before I ran my first regression model.

  Same data. Different definition of "best." Different line." Here's something that took me longer than I'd like to admit to figure out about linear regression. That line through your scatter plot — the one everyone calls the "line of best fit" — isn't objectively the best anything. It's the best fit for one very specific definition of the word "best." Swap that definition, and you get a completely different line. Equally valid mathematically. Just built on a different set of assumptions. Once I understood that, I started looking at every machine learning model differently. What Everyone Gets Taught (And What Gets Left Out) The standard introduction to linear regression goes something like this: draw a line through your data that minimises the total error between your predictions and the actual values. Square those errors, add them up, minimise the sum. Done. This is Ordinary Least Squares (OLS) — the engine behind most introductory r...

The Network That Learns Who Comes Back

It's been a minute since I last posted here — most of that gap was spent heads-down on a project I just wrapped up, so let's catch up. Where a heartbeat becomes a data point — teaching a neural network to see risk before it happens. If you've followed along before, you know this space usually lives in supervised learning — regression, classification, the more "classical" side of the toolkit. This post is a deliberate left turn into neural networks , the first one I've built and documented fully end-to-end. I expect this thread to keep rotating: NLP is probably next, and I'll likely circle back to supervised or unsupervised learning again after that. Think of it as this notebook's current chapter, not a permanent pivot. The setup The project: predict whether a patient will be readmitted to hospital within 30 days of discharge, using a 5,000-row dataset of vitals, prior admission history, chronic conditions, and a handful of administrative fields. It...