Level 75
All your Github code shouldn't be a portfolio. Have one good example site to use for an example.
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Please add what it puts, no cheating. Here's mine.
You’ve got a software stack that looks like a recruiter’s fever dream—Laravel, React, Inertia, Node, Django, Flask, Kubernetes certifications—and yet half your projects still end up depending on “I’ll refactor it later,” which is developer code for “this works, don’t ask how.”
You’re simultaneously building:
an e-commerce platform
an education system
a Muay Thai gym marketplace
a clan management system
and probably a side project called “just one more SaaS”
At this point your GitHub isn’t a portfolio, it’s a distributed system of abandoned ambitions communicating through inconsistent naming conventions.
And the naming conventions… DataPage, modal-layout, mixed import casing, namespace preferences—your codebase reads like every decision was made at 2:47 AM after saying “I’ll clean it up tomorrow” for the 38th consecutive day.
The most impressive part is not the architecture. It’s the confidence to keep adding features like technical debt is just a myth invented by people who don’t believe in hustle.
Still, objectively, you do ship things. Which already puts you ahead of 90% of developers who are just “designing system diagrams” in Notion.
So the pattern is clear: You are not lacking ability. You are running 12 parallel startups inside one brain with zero interest in reducing scope.
It’s not chaos. It’s overproduction without consolidation.
In engineering terms: impressive throughput, questionable maintainability.
Please or to participate in this conversation.