I'm a product marketer. My job is words, positioning, creating content for campaigns.

Then one day I downloaded Claude desktop, loaded up VS Code, connected to GitHub, and started shipping.

This talk is about what happens when I stopped observing how engineers worked and started doing it, and the slow, uncomfortable transformation of the way work is shifting for many of us.

I didn't set out to become a developer. I set out to move faster and own more of my work. Once I started using the same tools (VS Code, GitHub, Claude as a collaborator rather than a ghostwriter) I couldn't unsee what I'd been doing wrong.

I had been treating creating things as a linear exercise: ship the campaign, move on. Engineers ship, break, iterate, ship again. I had to learn to work that way too.

You already know this feeling. Every developer has lived through it when picking up a new language or a new framework. You're slower than you should be. The tools expose what you don't understand. You make embarrassing mistakes. Then at some point, something clicks.

AI has lowered the floor enough that someone like me can step through the door. A new wave of people are using AI to write and deploy code without traditional engineering backgrounds. They're learning. They're building real things. They need what every junior developer has always needed: experienced people willing to explain the reasoning behind the thing, not just review the output.

Here's what I found and will share in this talk:

• Things get dramatically worse before they get better. Shipping code as a non-developer is humbling in ways no amount of AI assistance fully cushions.

• The tools don't flatten the learning curve. They just change the shape of it. AI let me move faster through the parts I understood and ran me straight into the walls I didn't.

• The mindset shift was harder than the technical one. Iterating on a deployed thing felt wrong. I had to unlearn "done."

• Human in the loop turned out to mean something specific: I had to stay the author. The moment I stopped understanding what I was shipping, the work collapsed.

This talk is part story, part ask. I'll tell you what crossing over looked like from my side. In return, I want to make a case for why welcoming people like me (vibe coders, accidental developers, curious non-engineers) will make the DevOps community stronger.