I built this in a weekend, entirely on my iPhone.
Why I built it this way
First, I want you to know me beyond my resume.
Every part of this site, the questions you can ask, the way it's organized, came out of conversations with Claude. I described what I wanted, asked it to interview me, reacted to what came back, and kept going until it looked and worked the way I wanted.
I didn't do this to prove I can code. I can't, and that's the point. I wanted to show a bit about who I am and how I work. Not only am I comfortable with technology as a tool, I am a creative innovator who gets things done.
I believe technology is a power tool. Not the outcome itself.
In this case, my power tool happened to be Claude and the output this website. The outcome is finding a place I can bring this innovative spirit and help do some amazing things with real human impact.
What it's made of
Nothing exotic. Four accounts, all free or close to it, doing four different jobs.
The order I actually did it in
- Told my story first. Before any design or code, I sat down with Claude for a series of conversations about my career, my leadership philosophy, and the harder calls I've had to make. That became the written source the chat box draws from.
- Designed it in conversation. I described the feeling I wanted the site to have, saw a few directions, and picked the one that felt like me.
- Built the chat function. This is the one piece with real code behind it, a small function that reads my story and answers questions in my voice. I never wrote a line of it. I set up the account, pasted in one API key, and Claude handled the rest.
- Put it on a real domain. Bought danoltersdorf.com, connected it to hosting, and uploaded the files, all from my phone through GoDaddy's app.
What this actually is
This is genuinely what it looked like. Short, direct instructions, typed on my phone between other things, refined over a series of exchanges until it matched what I had in my head.
If you're a non-technical person sitting on an idea, you don't need to learn to code first. You need to get specific about what you want, and be willing to go back and forth until it's right. That's the same skill that runs the rest of this site's story, whether it's people, culture, or a platform I built myself.