Behind the Screens: Building DataSec Chronicles
- 14 hours ago
- 6 min read
The honest version of how one person runs a blog, a labs site, the certs, and a career — all at once, and never all at once.
The question I keep getting
Every so often, someone asks me a version of the same question:
How are you doing all of this?
The blog.DataSec Labs.Social media.Certifications.Projects.Workbooks.Learning cybersecurity while still working full-time.
Lately, I've also started getting messages from people who are beginning their own journeys and wondering where they should start.
So I thought it was time to pull back the curtain a little.
Because behind DataSec Chronicles, there isn't a content team, a developer, a social media manager, or some perfectly organized production schedule.
Right now, there's just me.
And a lot of open tabs.
01 — The reality
First, There's the Life Behind the Screens
DataSec Chronicles isn't my full-time job.
I'm a Senior Data Analyst. I've spent about a decade working with data, and now I'm building toward the next chapter of my career in cybersecurity.
I'm continuing my education through certifications, hands-on labs, and new tools. And I'm doing all of that while still having a full-time career.
I'm also a wife and a mom. I have a family, responsibilities, appointments, school schedules, weekends that don't go according to plan, and days when the thing I thought I was going to finish simply isn't getting finished.
DataSec Chronicles gets built around all of that.
Some mornings I have an idea before the rest of the house is moving. Some nights I build after everything else is done. Sometimes something I planned for Saturday becomes next Saturday.
Sometimes I get an idea for something like a seven-day cybersecurity crossword and apparently decide that I need to build that too.
That's the reality behind the screens.
02 — The through-line
So, What Is DataSec Chronicles?
At its core, DataSec Chronicles is where I document the intersection of where I've been and where I'm going.
I'm not entering cybersecurity with a blank slate.
I came here with years of experience asking questions of data, looking for patterns, investigating anomalies, building dashboards, explaining findings, and trying to understand what the numbers are actually telling me.
Long before that, I studied atmospheric science, where conditions matter, patterns matter, and individual signals become much more meaningful when you understand how they interact.
Now I'm finding those same instincts showing up again in cybersecurity.
The technology changes.
The context changes.
The question often doesn't.
What is happening here, and what doesn't belong?
That question is where this actually began.
Before there was a blog or a labs site, there was one conversation.
I sat down and asked an AI to help me map a path from data analytics into cybersecurity. The first answer was generic. So I kept asking — narrowing it, then finally asking the question that changed it: what am I missing?
That’s when the real plan appeared — the parts I didn’t know to ask for. That plan became my roadmap. Everything you’re looking at now grew out of it.
That's part of what DataSec Chronicles gives me a place to explore.
I write about what I'm learning while I'm learning it. That includes the things that click immediately and the things that absolutely do not.
The certification I passed.
The certification I had to retake first.
The lab that worked.
The tool that didn't make sense until suddenly it did.
The connections between data and cybersecurity that I didn't expect to find.
I don't want to document only the polished ending. The messy middle is usually where the interesting part is.
03 — Chronicles vs. Labs
Then There's DataSec Labs
Eventually, writing about what I was learning wasn't enough.
Sometimes I wanted to do something with the idea.
That's where DataSec Labs started taking shape.
The easiest way I can explain the difference is this:
DataSec Chronicles
Where I document the journey.
DataSec Labs
Where I turn some of what I'm learning into something you can do.
Sometimes that's an interactive tool. Sometimes it's a learning resource. Sometimes it's an experiment that started with me wondering, Wouldn't it be cool if…?
Not every idea becomes something. I have plenty sitting in my notes waiting for their turn.
Labs has given me a place to experiment with how cybersecurity and data concepts can be made more approachable, interactive, and maybe even a little fun.
04 — The system that isn't one
How Am I Actually Doing All of This?
This is probably the question I get most often, and I wish I had a secret productivity system to reveal here.
I don't.
What I do have is overlap.
A lot of what looks like separate work from the outside isn't actually separate work.
If I'm studying for a certification and something finally clicks, that might become a post. If I complete a hands-on lab and make a mistake that teaches me something, that might become a blog article. A concept I write about might eventually inspire an interactive resource. A question someone asks me might turn into something I realize other people probably need too.
The learning creates the raw material.
I'm not learning cybersecurity over here and then trying to invent content over there. Increasingly, they're part of the same process.
That has probably been one of the biggest lessons from building DataSec Chronicles.
Use what you're already doing.
05 — What you don't see
I'm Also Not Doing Everything at Once
This part matters.
When you see the finished blog post, graphic, lab, workbook, certification announcement, or project, you see the thing that made it across the finish line.
You don't see everything sitting behind it.
There are unfinished ideas in my notes.
There are projects I've moved down the list.
There are things I thought I'd launch earlier.
There are days when I can get a surprising amount done and others when DataSec Chronicles isn't the priority at all.
And that's okay.
I'm building this alongside a full life. I don't think the answer is squeezing productivity out of every available hour. Sometimes the answer is moving something to next week.
DataSec Chronicles has grown because I've kept coming back to it, not because I've managed to do everything perfectly.
06 — If you're just starting
Don't Copy My Current Starting Line
This might be the most important thing I can tell someone who asks me for advice.
Please don't look at everything I'm doing now and decide that you need to start a blog, build a website, create interactive labs, post on multiple platforms, study for certifications, make resources, and launch projects all at once.
You're seeing things that were added one at a time.
When someone asks me where they should start, my first question usually isn't the one they expect:
Not this. Which certification are you getting?
But this. Where are you trying to go?
Your next step depends on the answer.
Someone interested in becoming a SOC analyst may need a different starting point than someone interested in cloud security, governance, penetration testing, or security analytics, and someone coming from IT may already have skills that a career changer from another field needs to build.
Your existing experience matters too. One of the biggest things I've learned during my own transition is that changing directions doesn't necessarily mean throwing away everything you already know.
So start with what you're already doing and what you already bring with you.
If you're studying, document one thing you learned.
If you're doing a lab, write down what confused you and how you figured it out.
If you're building a project, finish a small version before worrying about making it impressive.
If you don't know exactly where your career is going yet, that's okay too. Pick the next useful step.
You don't need to build somebody else's journey.
You definitely don't need to build mine.
07 — Still in progress
I'm Still Figuring Out What This Becomes
That's probably my favorite part.
DataSec Chronicles has changed as I've changed. What started as a place to document my transition has gradually grown into writing, resources, experiments, and DataSec Labs.
I have ideas for where all of this could go.
More interactive learning.
More projects.
More resources.
More ways to connect data and cybersecurity.
Eventually, maybe not doing every single piece of it myself, and I'm not interested in pretending I have the entire roadmap figured out.
I'm still learning.
I'm still building.
I'm still working a full-time job and taking care of a family while figuring out where this cybersecurity journey leads.
I'm letting DataSec Chronicles grow alongside me.
If you're curious what that looks like in practice, DataSec Labs is where the latest experiments live — including a few things I've had entirely too much fun building.
For now, I'm just glad you're here to watch it get built.
the tool changes, the question doesn't🔎💜
Comments