The first time I was editing documentation through GitHub, I was soooo scared to hit “Commit”! 😂
I wasn’t a developer, and I worried about messing something up. But the founders I worked with would tell me, “It’s not rocket science,” or, “Just try it”.
Sometimes, they trusted me more than I trusted myself.
Working in a startup gave me opportunities to try roles I hadn’t done before. There was no training or documentation to follow. I had to research, try something, make mistakes, and learn what to do next.
That encouragement helped me get comfortable starting before I felt fully ready. Eventually, I brought the same approach to building my own website.
A little personal project
It started as a little project. I wanted a space for my thoughts, things I’ve learned, and whatever I felt like sharing.
I didn’t want a monthly subscription for a website builder, so I bought my own domain, did some research, and started building with the help of AI. I used an Astro template so I didn’t have to build everything from scratch.
The domain cost me around $12 for the year, and hosting was free. For my business email, I chose iCloud+ because it also came with cloud storage, instead of paying $1 per month for email hosting alone.
That’s the startup mindset I brought with me: be resourceful, compare my options, figure out what I actually need, and spend only where it makes sense.
GitHub and VS Code were already familiar from work. I still didn’t know how to build a website, but I had somewhere to start.
Figuring things out with AI
I would explain what I wanted, sometimes make a mockup of how I wanted it to look, and ask AI to help me write the code. Then I would check the result.
Sometimes it worked immediately. Other times, I needed to explain the problem differently, ask more questions, or undo a change and try again.
AI helped me write the code, but I still had to decide what belonged on the website and whether the result made sense to someone using it.
For example, when I added blog categories, I noticed that my selected filter disappeared after I opened a post and returned to the list. I wanted visitors to continue browsing where they had left off, so I asked for help making that selection stay.
On mobile, I also noticed that moving from my demos to the Experience & Tools page meant scrolling back up to the navigation. I added a button at the bottom so visitors could continue to the next page without going back to the top.
There were plenty of small adjustments like these. Using the website myself helped me notice things I hadn’t thought to ask AI for in the first place.
Seeing my work differently
As the website came together, I realized I could also use it to showcase my work when applying for jobs.
I started adding projects and writing about how I approached them. That became one of my favorite parts. Looking back helped me recognize work I had gotten so used to doing that I hadn’t thought of it as something worth sharing.
Writing SOPs and documentation helped me explain each project to someone who had never worked with me. What was the problem? What did I do? How did it help?
Customer support helped me think about the visitor’s experience, from finding a project to reading its story and returning to the list. My operations experience helped me turn all those ideas into smaller tasks I could work through.
Building the website gave me a new way to use—and recognize—the skills I already had.
And then something breaks
One project’s “Read the story” link didn’t take me to the blog post. At first, I wondered whether the post’s slug was wrong.
Then I noticed that the address it opened included /portfolio/blog/, while the actual post lived under /blog/. The link was being treated as a path relative to the page I was already on. Adding a leading slash made it point from the site’s root instead.
One missing slash, one broken link, and something new learned.
There were deployment issues, too. At one point, my changes weren’t appearing on the live website. I checked Cloudflare and saw that the deployment had failed. Retrying it brought the changes live, although that alone didn’t explain why it had failed in the first place.
My technical support experience helped me approach these problems: compare what should happen with what actually happens, check the details, and gather information before deciding on the next step. It also helped me ask AI more useful questions instead of just saying, “It doesn’t work.”
Sometimes, I thought I was done, only to find something else that needed fixing. But getting a broken link or missing feature to work is so satisfying.
I liked investigating the problem, and I loved the moment it finally made sense.
What I’m taking from this
I’m still not a developer. There’s code I need help understanding, and plenty I’m learning as I go. But now I have a website I helped build, a space for my thoughts, and a way to share my work with potential employers or clients.
What started as a little personal project became useful in ways I hadn’t planned. It also gave me another reason to trust myself the next time I’m handed something I’ve never done before.
That’s what I want to bring to my next role: the enjoyment to work through problems, and the habit of documenting what I learn so the next person doesn’t have to start from zero.
The founders I worked with encouraged me to try before I felt ready. Building this website was a chance to give myself that same encouragement.
Takeaway: Trust yourself to figure it out.