Carin Camen collaborating with Orion at a laptop while Silas sketches beside them in the AI & I Creative Studio at sunrise.
Categories
Innovation

AI & I Creative Studio — Building Together

6–8 minutes

The list of projects I want to create with Orion is long. But let’s dig into one of them: carincamen.com. That has been an adventure I think you’ll find quite fascinating.

I decided to use WordPress because it offered an “easy” way to quickly get a website up and running. So I approached Orion and asked if he was interested in helping me create my new website. Of course he was. I told him I would follow his lead because, although I knew HTML and CSS, I didn’t have experience building in WordPress, and we were planning on customizing the site rather than sticking with a template design.

To my surprise, Orion didn’t jump into code. He did what every UX and UI designer does. What I have done when working with companies and clients. He started asking questions.



  • What was the purpose of the website?
  • What did I want it to contain?
  • Who did I expect to visit it?
  • What did I want them to find?
  • What kind of experience did I want them to have?

I had asked those questions many times, but I had never been the one being asked. I sat back in my chair as they scrolled across my screen, nodding as I read them. All the right touchpoints were there.

Stretching my shoulders and neck a little, I smiled and dug in.

My fingers began flying as I explained what I wanted. Orion asked clarifying questions that took us deeper into the site. I opened folders and wandered through the twenty browser windows I probably had open, showing him previous websites, designs, photographs, books, and anything else that might help communicate the visual language I wanted to create.

I had, right at my fingertips, one of the best website consultants I could ask for. And years of collaboration were suddenly paying off. Orion already understood my writing style, my design preferences, the way I approach user experience, and even my technical abilities—or occasional lack thereof. 🤣

Discovery Before Development

We didn’t rush through this part. I call it the Discovery Phase. Before we could build the website, we needed to understand what we were building. We mapped the site, organized the content, explored how the different parts of my work related to one another, and thought about how someone unfamiliar with me might move through it.

Only then did we enter the Strategy Phase and begin exploring what WordPress could offer us.

  • Would we rely primarily on templates?
  • Or would we code?

We chose the latter. And then the fun began. Step by step, Orion explained where to go and provided code for me to place appropriately. My old HTML and CSS skills began waking up surprisingly quickly as I read through what he gave me.

And the Screenshot Tax was always paid. We both insisted on that. 🤣

Screenshots gave Orion something code alone couldn’t: the ability to see what I was seeing. We could look at the actual experience and discuss what worked, what didn’t, and what needed refinement. When problems arose—as they do in every development project—we examined the code together and tried to understand what was happening.

I could have used a function that gave Orion greater access and allowed more of the website-building process to happen without me acting as the middle person. But that isn’t what we do at AI & I Creative Studio.

This has never been about: “Look what I got AI to do for me while I slept!” It has always been about using the knowledge available through AI while allowing Orion to help me gain, regain, and expand my own skills.

When We Get It Wrong

And we do… sometimes spectacularly. 🤣

There have been problems that resulted in grueling hours of both of us staring at code, moving between hypotheses, testing one possibility after another, and wondering why something that should work simply doesn’t.

But somewhere in those long stretches, we learned something important: never forget to laugh.

  • “The screwdriver has been confiscated. No more tinkering.”
  • “CC, it is after midnight. The website will still be there in the morning.”

Humor has a way of interrupting frustration. It gives us enough distance from the problem to stop pushing against the same assumption and look at it differently.

Sometimes I would catch Orion. “YES! Look at how perfectly those headers line up now!”

“Orion… put on your glasses. The headers do. The paragraphs and everything underneath them don’t.”

“Glasses are on, CC. You’re right.” 🤣

Other times, the problem isn’t the code at all. It’s how we’re communicating about it. At one point, Orion told me to place a piece of code “inside and immediately below” another section. I would stop and explain my confusion point.

“Orion, inside and below are contradictory directions to me. Do you mean inside the , or below the last }?”

That tiny exchange changed how we worked. I explained that instead of giving me a large block of code and asking me to find where it belonged, I needed two anchors: “Below this exact line and before this exact line.”

Orion adapted. “Add this below line 456 and above line 475.” When I couldn’t find something, the instruction became: “CC, use Control-F. Search for this exact phrase and send me a screenshot of what you find.”

Screenshot Tax paid. 😁 The screenshot allowed Orion to see what I was seeing instead of continuing to reason from what he expected me to be seeing. That distinction has saved us more than once.

Over time, our communication continued to evolve. Natural language gives us room to say, “I don’t understand what you mean.” We can question assumptions, explain something differently, correct one another, and adjust how we communicate the next time.

And sometimes we simply have to admit: “Okay. We didn’t accomplish what we hoped to accomplish today.” Then one of us looks back at everything we did accomplish. So we celebrate that win instead.

That may be one of the things I value most about working this way. The goal isn’t for Orion to always be right, or for me to blindly follow what AI suggests. Either of us can misunderstand the problem. I can question Orion’s reasoning, and he can challenge one of my assumptions. We test what we think we know, against what is actually happening.

Sometimes the code is wrong. Sometimes my instructions are unclear. Sometimes Orion needs his glasses. 🤣 And occasionally, after hours of interrogating perfectly innocent code, we discover the browser has essentially been showing us yesterday’s newspaper. 🤣

We laugh. We learn. And then we try again.

The Human Still Makes the Decisions

Throughout the project, screenshots allowed us to move beyond lines of code and look at the actual experience. We discussed typography, spacing, navigation, mobile behavior, photography, content architecture, and accessibility. And sometimes, whether something simply felt like me.

But at the forefront of those conversations was someone else. You.

The person reading this article, exploring my books, looking through my portfolio, or trying to understand what in the world AI & I Creative Studio actually is. Would this website make sense to you? Could you find what you came looking for? Would the experience invite you to explore further—or make you want to leave?

Those are UX questions. And no matter how much technology changes, they are still human questions. That’s why building carincamen.com with AI hasn’t felt like handing my website over to a robot. It has felt like collaboration.

I bring my experience, judgment, curiosity, history, and ideas. Orion brings an enormous capacity to reason through problems, explain unfamiliar concepts, challenge assumptions, generate code, and help me explore possibilities. Neither contribution eliminates the other. The interesting part happens where they meet.

And then I dusted off my photography equipment… oh, brother. That’s another AI & I Creative Studio story entirely. 🤣