If you’ve checked my website, chances are you’ve seen the Samples page, which was only added this year (2024). Although the word “Samples” is kind of straightforward, I think it’s better to share the idea behind adding it to my site. Its general purpose is to list some of the finished gigs and jobs I have done for clients.
As a web developer, I’ve been blessed with opportunities to grow and learn, but my dev journey has been far from perfect. Even after years in this field, I still encounter numerous challenges and obstacles. One of the issues I continue to face is addressing diverse problems or client requests. I’ve come to understand that being a web developer means more than just coding or development; it requires the ability to find solutions and solve problems creatively.
However, there are also times when the issues or problems I need to address have already been solved in the past. Now, let’s talk about the first reason why I added it.
Documenting My Progress
As I was saying, there are times when the problem has already been solved or I have already come up with a solution to the request. I just need to refactor, improve, or align the existing solutions to the current problem or requests.
The problem is that I don’t have an easy way to recover those solutions because they were buried in hundreds, if not thousands, of files and folders. So I don’t have any choice but to rebuild them again. Since there’s a lot of work to do, I often forget to save or document it.
I call it “Progress” because I realized it’s not always a finished product or output. There will always be refactoring in every project or for every client request. I think with the help of Samples, there will be an easy starting point. Most of these samples are the initial versions of what I did; they won’t reflect the exact design they were intended to be.
Yes, there are dedicated platforms like GitHub to store codes or project files (which I’m also using), but I mostly prefer to add visuals to them so that my clients and I can see the sample or feature immediately.
A New Way of Showing Portfolio
Building websites often takes time; there are instances where it could take months to complete before a website can be deployed. With this short-form project, I can upload new content as a mini portfolio on my website without waiting for a full web project to be completed. Since the nature of my work consistently shifts to different projects, whenever I have new features that I develop, I can share them here easily.
Another thing, working as a freelancer, there are times I’m unable to showcase the entire project due to the NDA (Non-Disclosure Agreement). With the help of samples, I still have a way to share a “part” of the project and still showcase it on my website. Well, this always depends on the NDA. If it states that you don’t have the rights, why would you force it?
I must admit that as a freelance developer, my work often takes me away from maintaining my site. As much as I want to consistently add relevant content, it remains a challenge due to the demands of my work. Honestly, creating blog post content is one of my weaker skills, but since it’s essential for my website, I still do it.
As a professional, I understand the importance of showcasing my experience and skills through relevant content. Samples are one of the main types of content that can help me do just that. They provide a tangible way for potential clients like yourself to get a glimpse of the quality of work I can deliver. By sharing carefully curated samples, I can demonstrate my expertise, attention to detail, and ability to meet the unique needs of each client.