client websites
building websites for other people teaches you things personal projects never will. you learn that what makes sense to you as a developer rarely makes sense to someone who just wants their business online.
the projects
one of the first substantial ones was a website for a mobile repair service. they needed online booking, service listings, and a way for customers to check repair status. i built it with a node.js backend and a clean frontend that their non-technical staff could actually update. the booking system had to handle time slots, service types, and confirmation emails. nothing groundbreaking, but it had to work reliably every single day.
the job portal was more complex. search and filtering across multiple categories, user accounts for both employers and job seekers, and an admin dashboard for content moderation. react on the frontend, node.js on the backend. the hardest part wasn't the code itself but designing the information architecture so that both sides of the marketplace could find what they needed quickly.
i also built several custom landing pages for local businesses. these were simpler in scope but just as important to get right. a restaurant that needed their menu online. a tutor who wanted a professional presence. each one was an exercise in translating someone's vision of their business into something that works on a screen.
working with clients
the technical stack matters less than the conversation. most of my clients had no technical background, which meant i had to learn how to listen for what they actually needed rather than what they said they wanted. someone asks for "a modern website" and what they mean is they want something that doesn't look like it was built in 2005. that's a design conversation, not a technology conversation.
iteration was everything. i'd build a first version, walk them through it, and then rebuild based on their reactions. the feedback loop is where the real work happens.
deployment and maintenance
shipping the site is only half the job. i handle hosting, domain setup, ssl certificates, and ongoing maintenance for most of my clients. some of these sites have been running for years now with minimal intervention, which is exactly how it should be. the best infrastructure is the kind nobody has to think about.
freelance work taught me that software is ultimately about solving someone else's problem. the technology is just the tool you use to get there.