BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.devopsdays.org//devopsdays-portland-2026//speaker
 //9XSMLU
BEGIN:VTIMEZONE
TZID:US/Pacific
BEGIN:DAYLIGHT
DTSTART:20250910T000000
TZNAME:PDT
TZOFFSETFROM:-0700
TZOFFSETTO:-0700
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20251102T020000
RDATE:20261101T020000
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260308T030000
RDATE:20270314T030000
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:I Guess I Deploy Code Now? A Product Marketer's Accidental DevOps 
 Story - Anna Daugherty
DTSTART;TZID=US/Pacific:20260910T134500
DTEND;TZID=US/Pacific:20260910T135000
DTSTAMP:20260824T030032Z
UID:pretalx-devopsdays-portland-2026-VQWBZG@talks.devopsdays.org
DESCRIPTION:I'm a product marketer. My job is words\, positioning\, creati
 ng content for campaigns. \n\nThen one day I downloaded Claude desktop\, l
 oaded up VS Code\, connected to GitHub\, and started shipping.\n\nThis tal
 k 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.\n\nI didn't set out to become a developer
 . I set out to move faster and own more of my work. Once I started using t
 he same tools (VS Code\, GitHub\, Claude as a collaborator rather than a g
 hostwriter) I couldn't unsee what I'd been doing wrong. \n\nI had been tre
 ating creating things as a linear exercise: ship the campaign\, move on. E
 ngineers ship\, break\, iterate\, ship again. I had to learn to work that 
 way too.\n\nYou already know this feeling. Every developer has lived throu
 gh it when picking up a new language or a new framework. You're slower tha
 n you should be. The tools expose what you don't understand. You make emba
 rrassing mistakes. Then at some point\, something clicks.\n\nAI has lowere
 d the floor enough that someone like me can step through the door. A new w
 ave of people are using AI to write and deploy code without traditional en
 gineering backgrounds. They're learning. They're building real things. The
 y need what every junior developer has always needed: experienced people w
 illing to explain the reasoning behind the thing\, not just review the out
 put.\n\nHere's what I found and will share in this talk:\n\n- Things get d
 ramatically worse before they get better. Shipping code as a non-developer
  is humbling in ways no amount of AI assistance fully cushions.\n\n- The t
 ools don't flatten the learning curve. They just change the shape of it. A
 I let me move faster through the parts I understood and ran me straight in
 to the walls I didn't.\n\n- The mindset shift was harder than the technica
 l one. Iterating on a deployed thing felt wrong. I had to unlearn "done."\
 n\n- Human in the loop turned out to mean something specific: I had to sta
 y the author. The moment I stopped understanding what I was shipping\, the
  work collapsed.\n\nThis 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\, c
 urious non-engineers) will make the DevOps community stronger.
LOCATION:Ballroom
URL:https://talks.devopsdays.org/devopsdays-portland-2026/talk/VQWBZG/
END:VEVENT
END:VCALENDAR