High grades. Average portfolios.

That was the reality check I got a few weeks ago. We had to submit our final projects for the Web Development Portfolio subject at Holy Angel University. It was a massive deployment day for our entire year level. I was excited to see what everyone built. I assumed the classmates who always aced the written exams would have the most impressive websites.

I was completely wrong.

When I looked at their deployed links and checked the tech stack they listed, the pattern was obvious. Most of them just stuck to exactly what was taught in school. They did not learn new languages or frameworks at all. They used safe templates, basic layouts, and standard text blocks. They checked all the boxes on the grading rubric, but the websites lacked any real technical depth. It hit me that being good at academics is a completely different skill than being good at software engineering. Getting a high grade just means you know how to follow instructions.

The Logic Trap

I started looking at the submissions from the Computer Science sections to see how they handled the exact same assignment. The contrast was huge.

Since CS students focus heavily on algorithms and database structures, their backend logic was usually amazing. The data routing was efficient and secure. But the frontend was a complete disaster. The user interface felt clunky, and the user experience was totally ignored. It proved that you can write perfect backend code, but if the frontend is terrible, the whole project feels cheap.

Breaking the Syllabus

Then there were the outliers. Once I saw the portfolios of others, there were SOME that were really good. But honestly, they could be counted on one hand. Since there were only a FEW, they stood out immediately.

These specific students were not just using standard HTML and CSS. They were actively using tools like React Bits to build interactive UI components. They implemented GSAP to handle complex, high-performance animations. Their projects felt premium and polished. It was obvious they spent their free time learning modern libraries instead of just sticking to the school syllabus. They were building for the real world, not just for the professor.

The Realization

Seeing all of this changed my perspective entirely. It is easy to feel pressured or experience impostor syndrome when you see other students getting perfect grades or bragging on LinkedIn. I am definitely not the best developer in the room, and I still struggle with my own bugs every single day. But this experience made me realize that the tech industry does not care about your test scores. It cares about what you can actually build and deploy.

You need a strict balance. You need the solid logic of a backend developer, but you also need the frontend skills to make the application usable. From now on, my goal is not just to pass the school requirements. My goal is to completely ignore the baseline rubric and build things that actually stand out.