15. Do Personal Projects
School assignments rarely impress me; personal projects do. They're the perfect playground to grow as a developer — and they can give your career a massive head start.
As a Frontend Lead, I often receive applications from junior developers or students looking for internships. Most of the time, they only show school assignments in their portfolio. And to be honest? That's usually not enough to convince me.
Why? Because I want to work with people who are motivated, curious, and ambitious. People who push themselves to reach their full potential. And that rarely shines through in school projects — but it does in personal projects.
Why personal projects are so valuable
If you really want to become a great developer, you need to go beyond the basics. Personal projects are the perfect playground. No clients, no deadlines, no requirements — just you, building whatever you want, however you want, at your own pace.
You get to choose what to learn, explore the tools you're interested in, and dive deep into the topics that excite you. That not only leads to tons of experience and knowledge, but often results in a cool project you can proudly add to your portfolio.
And the best part? You barely need anything. A laptop, some time, and a bit of motivation. Hosting, tools, domains — often free or super cheap. So what's stopping you?
My first project
Back when I was still in school, we had to build a basic website to track our study progress. But a few classmates and I took it way further — not because we had to, but because we loved it.
We added a chat, a photo upload system, a noodle rating feature (essential student food!), and even a script that decided who had to fetch coffee. None of it was required. We just did it for fun.
That project eventually evolved into a social platform for party lovers. Think: party calendars, chat rooms, photo galleries, and a real sense of community. This was back in 2002 — before Facebook. I built everything from scratch. There were hardly any libraries, so I had to figure it all out myself. That's how I learned some lessons the hard way — like when a classmate taught me about SQL injection by visiting user.php?id=1;DROP TABLE users. Let's just say… I wasn't amused. Especially since I didn't have backups.
What it gave me
During the day, I worked as a junior developer. At night and on weekends, I built my site. It didn't earn me any money — it actually cost me money. But it taught me a lot, helped me meet amazing people, got me into parties for free, and — most importantly — landed me paid jobs. Showing that one project during interviews was often enough to get hired.
Eventually, the project died quietly when my hosting provider upgraded from PHP4 to PHP5. The site broke, and I didn't have the time (or energy) to rebuild it. By then, I had a busier job and more responsibilities, so I let it go. But looking back, that project gave my career a massive head start.
So: Do Personal Projects!
To every (aspiring) developer out there — go build something for yourself. It doesn't have to be big. It doesn't have to be finished. It doesn't even have to be good. As long as you learn. And enjoy the process.
