When you're learning to code, your focus is entirely on the technical stuff. You worry about clean code, component reusability, state management, and picking the coolest looking UI libraries. You live in a perfect bubble where the user always inputs the right data and the requirements never change.
Then, you get your first real-world freelance client.
And suddenly, that perfect bubble bursts.
A while ago, I took on a project to build a travel agency and rental website for Srikandi Trans Purwokerto and Sandita Rent Car. Up until that point, I had been working on structured school applications like an LMS. But stepping into the SME (Small and Medium-sized Enterprises) sector taught me that in the real world, coding is only half the battle.
Here is what building production websites for real businesses taught me about what it actually means to be a software engineer.
1. Clients Don't Care About Your Tech Stack (And That's Okay)
When I started the project, I was incredibly excited to use React.js, Next.js, and Tailwind CSS. I wanted to show off fast rendering speeds, server-side capabilities, and optimized build sizes.
But during my first meeting with the owner, I realized something crucial: They didn't care. They didn't know what React was, and they didn't care about Tailwind. What they cared about was simple:
- "Will this help customers book our travel services easily?"
- "Will it load fast on a cheap smartphone with a weak internet connection?"
- "Will it rank on Google so people in Purwokerto can find us?"
This was a massive shift in mindset for me. As developers, we get obsessed with our tools. But for a business, technology is just a tool to solve a commercial problem. Your job isn't just to write code, it's to build a solution that drives business results.
2. The Power of UX Optimization over Over-Engineering
When building a commercial site, every second of loading time and every confusing button costs the business money. If a user gets confused trying to find the contact button or the fleet list, they will simply leave and go to a competitor.
Instead of over-engineering complex animations or features the client didn't ask for, I focused heavily on UI/UX optimization and site speed.
I spent hours ensuring the mobile responsiveness was flawless, because in the transport sector, almost 80% of your traffic comes from people browsing on their phones while on the move. I optimized images, removed heavy scripts, and streamlined the booking flow so a user could go from landing on the homepage to hitting the WhatsApp booking button in less than three clicks.
Seeing the conversion rates and user reach improve after the launch was infinitely more satisfying than just writing a clever piece of JavaScript.
3. Communication is a Hard Skill, Not a Soft Skill
People often call communication a "soft skill," as if it's optional. It's not. When working with freelance clients, clear communication is just as vital as writing bug-free code.
Local business owners know their industry inside out, but they might not know tech jargon. Part of my job as a developer was to play the role of a translator. Instead of saying, "We need to optimize asset delivery and configure DNS zone records for better propagation," I learned to say, "We are going to make the images load faster and make sure your domain name correctly points to our new server so customers can access it without issues."
Simplifying complex technical logic into clear, actionable business value saves time, prevents scope creep, and builds massive trust with your clients.
Final Thoughts
Freelancing while navigating my high school years at SMKN 1 Purbalingga and finishing up my internship has been a wild, exhausting ride. But nothing beats the experience of shipping real code that impacts a real business's bottom line.
If you're a junior developer looking to level up, stop just building fictional projects for your portfolio. Go out there and find a local business, a café, a laundry service, or a transport agency. Offer to fix their web presence. The technical challenges, the client meetings, and the pressure of pushing a commercial site live will teach you lessons no bootcamp or tutorial video ever could.
Have you ever built a project for a non-technical client? How did you handle the communication gap? Let's talk in the comments below!
If you want to check out the rest of my development work or collaborate on a project, feel free to visit my Portfolio or see what I'm breaking next on GitHub.
Cheers,
Ibra 🚀
Top comments (0)