What CS50's Web Programming Taught Me Before I Even Started

I started watching CS50's Web Programming with Python and JavaScript (CS50W) today. I only watched the short Introduction video so far — just over 2 minutes — but it already changed how I think about my own project.

Why I watched this

I love programming, and I want to get better at building real web apps with Django and Next.js — the same stack CS50W teaches. I wanted to see how Harvard teaches these ideas, and compare it to what I'm already doing on Code With John.

The one idea that stuck

The course description says something simple but important: by the end, students should be able to "design and deploy applications on the Internet" — not just follow tutorials, but actually ship real, working software. That's the whole point. Not watching. Not copying code. Shipping.

That hit me, because this week I did exactly that — without even realizing it was "the CS50 way."

How I used it in my own project

Before watching any CS50W lecture, I already:

• Built a Django backend with real user accounts (register, login, email verification)
• Connected it to a Next.js frontend
• Found and fixed a real bug (an email sending it failed for new users)
• Added a small blog feature, with Django serving data and Next.js showing the pages
• Pushed all of it to GitHub as real pull requests

I didn't plan it around a course. I was just building. But it turns out that is the lesson CS50W opens with: build real things, deploy them, and learn from what breaks.

What's next

I'm going to keep watching CS50W lecture by lecture — starting with Lecture 0 (HTML and CSS) — and connect each one back to Code With John, the same way I did here. My goal isn't to finish the course fast. My goal is to learn something from every lecture that makes my own project better.