My first interaction with the internet was in the early 2000s, back when dial-up was still a thing and websites looked like digital brochures. I remember being fascinated by how content appeared on the screen — text, images, buttons — all organized within a browser window. I didn’t know it then, but that fascination would spark the flame of curiosity that led me here.
I started dabbling with basic HTML during high school. It wasn’t part of the curriculum, but I found myself exploring "View Page Source" on websites and trying to understand how things were structured. I created a simple webpage just for fun using Notepad and opened it in Internet Explorer — and that first moment seeing something I created on the web was unforgettable.
From Hobby to Skill: Learning the Tools of the Trade
Once I realized that websites were essentially code and design fused together, I wanted to know more. At that point, I wasn’t thinking about a career in web design — it was just a hobby. I began learning more advanced HTML, CSS, and then JavaScript. These languages felt like magic spells that transformed ideas into functioning websites.
Back then, platforms like W3Schools and CodeAcademy were my best friends. I followed tutorials, experimented with layouts, and even broke things (a lot). But with every broken layout came a better understanding of how web pages worked.
Then came Adobe Photoshop. Design, I learned, was just as important as code. I started exploring the visual side of web development — colors, typography, layout grids, and user experience. That’s when I started to shift from being a coder to becoming a designer.
The First Real Project: Baptism by Fire
My first “real” project was designing a website for a local bakery. It wasn’t a paid job — more like a favor. But the experience taught me more than any tutorial ever could.
I had to communicate with a client, understand their brand, and convert their vision into a functional and beautiful site. I designed mockups in Photoshop, converted them to HTML/CSS, and made sure the site worked on different browsers (hello, Internet Explorer again).
There were mistakes, of course — I didn’t understand SEO, the mobile layout was a mess, and my color choices weren’t great. But that project gave me the confidence that I could do this for real.
Formal Education vs. Self-Taught Learning
I often get asked: “Did you go to school for web design?”
The answer is no. I’m a self-taught designer. But that doesn't mean I didn’t educate myself. I just did it outside of a traditional classroom. I took online courses, read books on design principles, and followed top web design blogs.
That being said, formal education isn’t a bad route. It can give you structure, community, and credibility. But in web design, what truly matters is your portfolio and problem-solving ability. Whether you learn from YouTube, Udemy, or university, the goal is the same: create websites that work well and look great.
Building a Portfolio and Landing My First Paid Gig
Once I had a few projects under my belt, I created an online portfolio. It didn’t need to be flashy — it just had to show my work, my style, and my capabilities. I used platforms like Behance and Dribbble to showcase projects and wrote about my process.
My first paid gig came through a friend of a friend. A small business needed a new site, and I jumped in. That one project led to another, and soon I had enough experience to start freelancing more seriously.
I joined freelancing platforms, pitched clients directly, and started growing a network. I realized that being a web designer was not just about design — it was about understanding clients, managing time, pricing projects, and delivering value.
Learning Never Stops
The web is constantly evolving. New technologies, trends, and best practices pop up all the time. That’s why I made learning part of my routine.
I learned responsive design, accessibility, performance optimization, and CMS platforms like WordPress. I dabbled in frameworks like Bootstrap and Tailwind CSS. Eventually, I even started exploring UI/UX design and tools like Figma and Adobe XD.
This continuous learning helped me stay relevant and offer better solutions to clients. I didn’t want to be “just” a web designer — I wanted to be a problem solver.
Turning Passion into Profession
With consistent work, referrals, and an ever-growing portfolio, web design transitioned from side hustle to full-time career. I registered my freelance business, built a brand around my services, and started working with larger clients.
I also began collaborating with developers, marketers, and other designers. Working in teams opened new opportunities and helped me grow in areas I hadn’t thought about before — like project management and digital strategy.
Advice for Aspiring Web Designers
If you’re reading this wondering how you can become a web designer, here’s what I’d say:
Start small: Build something — anything. A portfolio site, a blog, a landing page.
Focus on fundamentals: Learn HTML, CSS, basic JavaScript, and design principles.
Build a portfolio: Even if it’s just practice projects, show what you can do.
Stay updated: Follow design trends, learn new tools, and adapt to changes.
Practice empathy: Design is about users, not just visuals.
Be persistent: There will be self-doubt and setbacks, but consistency wins.
Final Thoughts: Looking Back, Moving Forward
Looking back, the path I took wasn’t straightforward — but it was mine. Every late-night coding session, every failed design, every client conversation added up to where I am today.
Web design is an incredible field — part art, part logic, part psychology. It lets you build things that live on the internet, solve problems for people, and express creativity.
If you’re on the fence about becoming a web designer, take the leap. The tools are accessible, the community is supportive, and the opportunities are endless.