I'm Tayyab Sabir.

College and C++

College was where programming first became part of my education. Because I had selected Computer Science as my major subject, I was introduced to programming concepts more seriously than I would have been through a single elective course. One of the languages I started learning was C++.

Instead of relying entirely on classroom material, I started studying through documentation and practical examples. LearnCpp became one of the resources I used to learn C++ and understand programming fundamentals.

I built small programs in C++ while learning. They weren't impressive applications, but they were important because they forced me to think about how programs actually work — variables, conditions, loops, functions, data structures, and breaking a problem into smaller pieces. Looking back, learning C++ before web development gave me something that became much more valuable later: problem-solving ability and stronger programming fundamentals.

Web development

After getting comfortable with programming fundamentals, I became interested in web development. I wanted to understand how websites actually worked, so I started learning the technologies behind them step by step.

One resource I relied on heavily was W3Schools. I learned HTML, CSS, JavaScript, PHP, and MySQL through a gradual process rather than trying to learn everything at once. I also developed a preference for documentation and reference material. I don't want to depend completely on tutorials to build something — tutorials can be useful, and I still use them when I need them, but I prefer learning the underlying concepts well enough that I can eventually figure things out myself.

Eventually, I reached the point where I could build basic websites and connect them to databases using PHP and MySQL. That was when web development stopped being something I was simply studying and became something I could actually build with.

Learning by building

Once I understood the basics, I started building projects. I created small applications and websites to turn what I was learning into something practical. Among them were PHP and MySQL projects, including an e-commerce website, several portfolio websites, and other small web applications. I also built a website for my school.

These projects were important because they exposed the gap between understanding a programming concept and actually using it in a working application. A tutorial can show you how a form works. A real project makes you think about what happens when the user submits invalid data, how information should be stored, how different pages communicate, what happens when something goes wrong, and how all of those pieces should fit together.

First professional role

At the end of December 2024, I received a paid internship opportunity as a PHP Developer at CAT Marketing Systems. This was an important transition because I was no longer learning web development only through personal projects. I was working on software in a professional environment and dealing with requirements that existed outside my own ideas.

During my internship, I worked on a real estate CMS project. Working on a real project introduced me to problems that tutorials rarely prepare you for — understanding existing code, working within an existing structure, dealing with database-driven features, debugging issues, and making changes without breaking things that were already working.

PHPTravels

My next role was at PHPTravels, where I worked as a Junior PHP Developer on their booking engine and on a SaaS project.

This introduced me to a different side of web development. Travel software isn't simply about displaying pages and saving records in a database. Booking systems involve business rules, users, availability, customer information, integrations, workflows, and many different pieces that have to work together correctly. Working on those systems helped me understand how software is built when it has to support actual business processes.

It also pushed me beyond simply knowing PHP syntax. I started thinking more about application structure, database design, APIs, authentication, business logic, integrations, and how different parts of a larger application communicate with each other. That experience became an important bridge between the PHP developer I had become and the developer I wanted to become next.

Why Laravel

My path to Laravel was a natural result of everything I had learned before it. After working with PHP applications and seeing increasingly complex software systems, I wanted to understand better ways of structuring and building modern PHP applications. That's when I started seriously learning Laravel.

Laravel introduced me to tools and patterns that helped me think differently about application development — MVC architecture, routing, middleware, authentication, validation, database relationships, APIs, and application structure.

But learning Laravel for me isn't just about learning syntax. I'm interested in understanding why an application should be structured a certain way. Why should middleware handle a particular responsibility? Why should business logic live in one place rather than another? How should an API be designed? Those questions are a big part of what I'm working through now.

My main focus is PHP and Laravel web development. My work and learning have covered areas such as:

• PHP web applications
• Laravel applications
• MySQL and relational databases
• REST API development
• Authentication and authorization
• CMS and admin systems
• Database-driven business applications
• API integrations
• SaaS modules
• Customer and user management systems
• Backend development
• Application deployment and production environments

I've worked on projects involving real estate, travel software, booking systems, content management, expense tracking, authentication, and SaaS applications. My experience has also taken me beyond writing application code — I've worked with Linux servers, Apache, DNS, SSL, Git-based deployment, production configuration, and troubleshooting applications in live environments.

• Understand, don't just copy

  If I use a solution, I want to understand what it is doing and why it works.

• Build before assuming

  Some concepts don't really make sense until you use them in an actual project.

• Keep things practical

  I care about clean and maintainable code, but I also care about solving the actual problem rather than overengineering everything.

• Learn from mistakes

  Some of my most useful lessons have come from things breaking — deployment problems, unexpected PHP errors, database issues, API mistakes, and code that seemed fine until it met a real use case.

I'm working toward becoming a stronger backend-focused PHP and Laravel developer. I want to deepen my understanding of application architecture, APIs, databases, authentication, integrations, SaaS systems, and production software.

I'm particularly interested in software where there are real business rules behind the application — systems with users, permissions, workflows, data, integrations, and problems that need thoughtful solutions. I don't want my development journey to stop at knowing a framework. I want to understand the engineering decisions behind the applications I build.

Right now, I'm building Sakinah, an Islamic web application focused on Azkar, Hadith, and Quran content. I'm developing it as a personal project with the intention of it being a Sadaqah Jariyah, and I'm using it as the main place to practice the Laravel and application architecture concepts I'm learning.

I'm also open to backend and Laravel roles, as well as contract work on PHP projects.

This website is part portfolio, part developer journal, and part record of my journey. I built it to showcase the projects I've worked on, explain what I can do, and document things I'm learning along the way.

I also want it to show the progression behind the code, not just the finished result. Becoming a developer isn't a straight line. It's a collection of things you learned, things you built, things you broke, problems you solved, and questions you haven't answered yet. This website is where I'm documenting that process.