I get asked this a lot, usually by other students trying to figure out where to start: "Why web development? Why not something more advanced-sounding?" The honest answer is boring at first glance — I chose it because it was the fastest way to see something real. But the longer I've sat with that decision, the more I've realized it was the right one for reasons I didn't fully understand at seventeen.
The problem with invisible progress
When you're new to IT, almost everything feels abstract. Networking diagrams, OSI layers, database schemas — they're all genuinely important, but they don't give you anything to show anyone. You can study for weeks and still not have a single thing to point at and say "I built this."
Web development doesn't have that problem. I wrote my first HTML file, opened it in a browser, and there it was — text on a screen, made entirely out of something I typed myself. It sounds small. It wasn't. That immediate feedback loop — write code, refresh, see the result — is what kept me coming back on the nights I didn't feel like learning anything.
"You can study networking for a month and still not be sure what you know. You can learn CSS for an afternoon and watch a broken layout become a real page."
It rewards curiosity, not just discipline
A lot of learning advice assumes you already have discipline figured out. I didn't, not at first. What actually worked for me was curiosity — wanting to know why a button looked a certain way, why my layout broke on mobile, why one line of JavaScript could change everything on the page. Web development is full of small, answerable "why" questions, and chasing them taught me more than any structured course did.
That's not to say it's easy. I spent an embarrassing number of hours fighting Flexbox before it clicked, and my first attempt at a responsive layout looked correct on my laptop and completely broken on my phone. But every one of those failures had a visible, debuggable cause — which made them frustrating in a productive way, not a demoralizing one.
A gateway, not a destination
The other reason I started here is less about the web itself and more about what it opens up. Once you understand how a browser requests a page, you start asking how that request travels — which pulls you toward networking. Once you build something with a form, you start wondering where that data goes — which pulls you toward databases and backend logic. Once your own site is live, you start caring about who could mess with it — which pulls you toward security.
Web development didn't narrow my interests in IT. It gave me a doorway into almost all of them, one honest question at a time.
If you're choosing where to start in IT and you learn best by building visible things, don't overthink it. Pick a small page. Break it. Fix it. Ship it somewhere, even if it's ugly. The confidence you get from finishing something real is worth more early on than getting the "correct" starting point.
Where it's taken me so far
This site is the clearest example I have. Every page of it — the layout, the animations, the gallery, the contact form — is something I built while still figuring the fundamentals out. It's not perfect, and I still find things to rebuild every few months, but that's kind of the point. Web development gave me a project that grows exactly as fast as I do.
I'm about to start a formal IT degree, and I expect a lot of what I learn there — networking, systems design, databases — to feel less immediately visible than building a webpage does. But I'm glad I have this as my foundation. It's the thing that proved to me, early and repeatedly, that I could actually learn this stuff.
