I started the Cloud Resume Challenge to learn how to become a cloud engineer. That was the whole reason. Not to build a product, not to start a brand, just to learn the stack and prove I could ship something real on AWS.
When I finished I had chamb.dev. My domain. An S3 bucket behind CloudFront with an ACM certificate. A Lambda function and a DynamoDB table counting visitors. A downloadable PDF resume. Links back to my GitHub repos. It worked. It was live. I was proud of it.
Then I started thinking about what else it could be.
A resume website doesn't give people a reason to come back. chamb.dev had a domain, infrastructure, a deployment pipeline, and an audience of zero.
I wanted to fix that. I wanted it to be a personal brand, a space where I could document what I was building in real time, publish my writing, and show my projects as they evolved. Not a snapshot of where I was. A living record of where I was going.
So I kept building.
The site now has a writing section for technical posts and academic work, and a projects section that documents what I built and what it produced, not a list of technologies but outcomes. The resume is still there because the purpose of the original challenge is still alive.
But the biggest change is what runs underneath it.
I built a Command Center, a private dashboard at chamb.dev/command, fully wired to GitHub. I write articles inside it, set a publish date and time, and the system handles the rest: generates the HTML, commits it to GitHub, updates the writing index, pushes to S3, invalidates the CDN cache, and sends me a confirmation email. I don't touch the terminal. I don't edit files manually. I write, I schedule, it publishes.
Watching it work for the first time was one of the best feelings I've had building anything.
A hiring manager told me something I think about a lot. He said he doesn't look at the surface of a repository. He looks at the change log. He wants to see how long it took to get from there to here. When he sees someone documenting their work consistently over months, adding things, evolving the project, he thinks: who told them that's how we do it? Because that's what gets you the phone call.
Not that you built a website that loads. Plenty of people build websites that load. He wants to see what you did after that.
He also said: always put your work out there. Don't wait until it's finished. It's never finished. If someone applies today and he checks the repository and the last commit was yesterday, he already knows what that means. But if he goes there and the repository is six months old and every month there is new work, new changes, visible growth, now he knows what kind of engineer he's looking at.
If you just finished the Cloud Resume Challenge and you're wondering what to do next, keep going. Think hard about what else the project could become. You have a domain. You have infrastructure. You have a deployment pipeline. You have a GitHub history that a hiring manager is going to look at.
What are you going to put in it?
The challenge is not the end of the project. It is the foundation.