💻 My Experience of Developing My First Web Development Project: What I Have Learnt as a Beginner

in #programming3 days ago

pexels-markusspiske-1921326.jpg

Introduction

Building my first web development project was very different from simply watching programming tutorials.

When learning web development, it is easy to feel like you understand everything while watching someone else write code. But when you open your own code editor and try to build something from scratch, many new questions appear.

Where should I start?

How should the frontend communicate with the backend?

Where should the data be stored?

What happens when something goes wrong?

These questions became much clearer when I started building my own projects.

One of the projects I worked on was PickRide, a ride-sharing web application built using modern web development technologies.

🚗 Why I Started PickRide

The basic idea behind PickRide was to create a platform related to ride sharing.

Instead of building only a static webpage, I wanted to understand how a complete web application could work.

That meant learning about different parts of development, including:

Frontend
Backend
Database
APIs
Authentication
Deployment

This project gave me an opportunity to understand how these components work together.

⚛️ Frontend Development

The frontend is the part users interact with.

For PickRide, I worked with React and related frontend technologies.

React helped me understand concepts such as:

Components
Props
State
User interactions
API requests
Dynamic interfaces

One thing I learned is that creating a webpage and creating an interactive application are two different experiences.

A real application needs to respond to user actions and communicate with the backend.

🟢 Backend Development

The backend handles the logic behind the application.

I worked with Node.js and Express.js to create backend functionality and APIs.

This helped me understand how requests travel between the frontend and backend.

For example:

User action → API request → Backend processing → Database → Response → Frontend

Understanding this flow was one of the most useful lessons from the project.

🗄️ Working With MongoDB

The project also helped me understand how a database fits into a web application.

I worked with MongoDB for storing application data.

Before building the project, database concepts could sometimes feel theoretical.

But when an actual application needs to store and retrieve information, the purpose becomes much clearer.

I had to think about what data should be stored, how it should be accessed and how the backend should communicate with the database.

🔐 Authentication

Another important part of the project was authentication.

A real application needs to distinguish between users and protect certain functionality.

Working with authentication helped me understand concepts such as:

Login
User credentials
Tokens
Protected routes
Backend validation

This was more challenging than simply creating a login form because authentication involves both frontend and backend logic.

🐛 Problems and Debugging

The most valuable part of building PickRide wasn't when everything worked.

It was when things didn't work.

I encountered different types of development problems, including API issues, configuration problems, database connection issues and deployment-related errors.

Sometimes the problem was caused by something very small.

This taught me that debugging is a major part of software development.

My general debugging process became:

Read the error → Find where it occurs → Understand the cause → Try a solution → Test again

I also learned that randomly changing code isn't a good debugging strategy.

Understanding the actual error saves much more time.

☁️ Learning Deployment

Getting an application to work locally is one thing.

Deploying it so that other people can access it is another challenge.

Working with GitHub and deployment platforms helped me understand that a project also needs proper configuration outside the local development environment.

Environment variables, backend URLs and production settings can all affect whether an application works after deployment.

This was an important practical lesson that I wouldn't have understood as clearly from theory alone.

🤖 Using AI During Development

AI tools also became useful during development.

When I didn't understand an error, I could ask AI to explain the error in simple language.

I could also use it to:

Understand unfamiliar code
Brainstorm solutions
Explain concepts
Review possible approaches

But I learned not to blindly copy generated code.

If I don't understand why a solution works, I haven't really learned from it.

📚 What This Project Taught Me

The biggest lesson from PickRide was that building is different from watching tutorials.

When following a tutorial, someone has already solved the problems for you.

When building your own project, you have to make decisions yourself.

You have to search.

You have to experiment.

You have to debug.

And sometimes you have to start again.

That process can be frustrating, but it is also where a lot of practical learning happens.

🚀 What I Would Improve

If I build the project again, I would spend more time planning the application before writing code.

I would also:

Organize the code more carefully
Improve error handling
Improve UI consistency
Add stronger validation
Test features more thoroughly
Document the project better

A project doesn't have to be perfect to be useful.

The important thing is to understand what you built and learn from the experience.

Conclusion

Building PickRide was an important step in my web development journey.

It helped me connect concepts that I had previously learned separately.

React + Node.js + Express + MongoDB + APIs + Authentication + Deployment

Instead of seeing them as individual technologies, I started understanding how they can work together to create a complete application.

My first project wasn't perfect, and I still have a lot to learn.

But I learned something more valuable than simply writing code:

The best way to learn development is to build, break, debug and build again.

This is only one step in my journey, and I'm looking forward to improving my skills through more projects.

💬 Your Turn

What was the first programming or web development project you built?

What was the biggest problem you faced while building it?

Share your experience below. 👇

https://bit.ly/4AgpX3I

Sort:  

Me llamó la atención el flujo que describís: User action → API request → Backend processing → Database → Response → Frontend, la diferencia se nota cuando lo ves en acción. También el hecho de que usaste React + Node.js + MongoDB en un solo proyecto es práctico para quien arranca. Esto es genial, ¡a probarlo!