A practical guide for new web developers: what to learn first and how to get your first client

Every week someone asks me, "Where do I start if I want to be a web developer?" The good news: you don't need a computer science degree, an expensive laptop or a bootcamp. The bad news: there is so much to learn that many beginners spend months jumping between tutorials and never build anything.

This guide gives you a simple path. It's the advice I wish I had when I started.

1. Learn in the right order

Don't start with the newest framework. Start with the basics that every website is built on, in this order:

1. HTML: the structure of a page (headings, paragraphs, links, forms). One to two weeks.

2. CSS: how it looks. Learn the box model, Flexbox, Grid and how to make a page work on phones. Two to four weeks.

3. JavaScript: how it behaves. Variables, functions, arrays, the DOM, events and fetch(). This takes the longest. Be patient.

4. A back-end language and a database: PHP with MySQL is still a great, job-friendly choice in the Philippines, and so are JavaScript (Node.js) or Python. Pick one.

5. A framework: only after the basics. Laravel for PHP, or React/Vue for the front end.

Frameworks change. HTML, CSS, JavaScript, SQL and HTTP don't change much. Time spent on the basics pays you back for years.

2. Set up your development environment

You only need a few free tools:

• A code editor: Visual Studio Code is free and works on Windows, Mac and Linux.

• A modern browser with developer tools (Chrome, Firefox or Edge). Learn to open the inspector and the console early. It's how you find out why something broke.

• A local server for PHP: Laravel Herd (Mac and Windows), XAMPP or Laragon let you run PHP and MySQL on your own computer.

• Node.js, if you'll work with JavaScript tooling.

• Git, which deserves its own section.

An old laptop is fine. A stable internet connection and a second monitor help more than a fast processor.

3. Learn Git from week one

Git saves the history of your code, so you can undo mistakes and work with others. Every company uses it, and clients will ask for it. Learn these first:

git init
git add .
git commit -m "Add contact form"
git push

Create a free GitHub account and push every project there. Write clear commit messages that say what changed. Your GitHub profile becomes a living portfolio that employers really do look at.

4. Build real projects, not just tutorials

Tutorials feel productive, but you only really learn when you build something on your own and get stuck. A good rule: for every hour of tutorial, spend two hours building.

Project ideas that use real skills and make good portfolio pieces:

• A landing page for a family business, like a carinderia, a sari-sari store or a tutoring service.

• A to-do or budget tracker that saves data in a database.

• A booking form for a barbershop or clinic, with email confirmation.

• A small tool that solves a real problem, like a bill splitter or a quote calculator.

Put each one online. Free hosting on GitHub Pages or Netlify works for static sites, and cheap shared hosting works for PHP. A live link beats a screenshot every time.

5. Get comfortable being stuck

Professional developers are stuck all the time. The skill is getting unstuck:

• Read the error message, slowly, all of it. It usually tells you the file and line.

• Search the exact error in quotes.

• Read the official docs before random blog posts.

• Use AI assistants wisely. Ask them to explain code and errors, not just write it for you. If you paste code you don't understand, you'll have a bug you can't fix.

• Ask good questions: what you tried, what you expected and what happened instead.

6. Learn the basics of security early

Even beginner projects go online, and bots find them within hours. Learn to use prepared statements for SQL, escape output, hash passwords with password_hash(), and never commit passwords or API keys to Git. Our article on securing PHP sites has a full checklist.

7. Getting your first job or client

For a job

• Have three to five finished, live projects on GitHub with a short README for each.

• Make a simple portfolio site with your projects, a photo and a contact link.

• Apply to junior roles, internships and OJT programs, and don't skip smaller local companies and BPOs with in-house dev teams.

• Join local communities like PHP and Laravel user groups, Facebook developer groups and meetups. Many jobs are filled through referrals.

For freelance clients

• Start close to home. Family businesses, your church, your barangay or a friend's small shop often need a simple website or Facebook-linked landing page.

• Offer a clear package: for example, a five-page website with a contact form, mobile-friendly, done in two weeks.

• Use a simple written agreement that lists the scope, price, timeline and how many revisions are included. Ask for a downpayment (50% is common).

• Send a proper invoice. Our free Invoice Generator makes one in a minute.

• Ask for a testimonial and permission to show the work in your portfolio.

8. Common traps to avoid

• Tutorial hell: watching course after course without building anything.

• Framework hopping: switching from React to Vue to Svelte every month. Pick one and finish a project.

• Comparing yourself to others online. People post their wins, not their 2 a.m. bugs.

• Underpricing forever. Cheap is fine for your first one or two clients. After that, charge for the value you deliver.

• No backups and no Git. You will lose work once. Make it the only time.

• Burning out. One focused hour a day for a year beats 12-hour weekends for a month.

Where to go next

Pick one learning path and stick with it for three months. Our list of learning resources for developers covers the best free and paid options, and our web development best practices will help you build habits that clients and employers notice.