Signal in the Static — Episode 1: Tuning In

I used to just drift.

Bouncing between ideas. Thinking about all the things I could do without ever really sticking to one long enough to make it happen. Endless noise.

That changes now.

I’m locking in on one signal: becoming a developer who can build apps and systems that help people like me…people who’ve been lost before, but want to improve themselves without having to change who they are to “fit in.”

I’ve never fully committed to anything before. This is me flipping that switch.

---

Why I’m Doing This

I’m moving from cybersecurity into development. I’ve seen a lot of beginner dev blogs, people starting from scratch, just documenting the grind and they’ve always caught my attention. So here’s mine.

This is my way to keep myself accountable, track the wins and losses, and maybe give someone else the push they need by showing the real side of starting over.

---

The Next Year

In the next 365 days, I want to:

• Build an AI path-finding script for the game PEAK that finds the best climbing route.

• Create an MVP workout tracker app | the first piece of a bigger vision I’ve got brewing.

---

Step One

First move? CS50.

I want a solid foundation in how systems work, even the low-level stuff most people skip. I’ve got some gaps to fill, and I’m trying not to cut corners this time around.

---

What I Hope You Get Out of This

I’m not here to just post code dumps. I want this blog to show progress from the ground up — someone going from “lost” to building things worth talking about.

If reading this makes you think “If he can start, so can I” — then it’s doing its job.

This is my signal. Cutting through the static.

---

Stay tuned. First CS50 post coming soon.