i went to cascadiajs 2026. here's what developers are telling us~

Published Thursday, 11 June 2026

i spent two days at cascadiajs 2026 in seattle as deepgram's community engineer — notebook in hand a lot of questions and one very good conversation opener~

A 5 min read.

june 1-2 2026 | seattle wa | ~200 attendees

i spent two days at cascadiajs 2026 in seattle as deepgram's community engineer — notebook in hand a lot of questions and one very good conversation opener~

this is what i found~

the setup

cascadiajs is a javascript conference that has been running since 2012 drawing around 200 developers to seattle for a single-track programme focused on web development and the javascript ecosystem. the crowd skews younger — a lot of folks breaking into the industry a lot of people at their first or second dev conference. that demographic tells you something important up front and i'll come back to it~

i was there to listen. to have conversations. to understand what developers building with voice ai are running into what they're excited about and where the friction is~

the conversations that mattered

the best opener i found was this: "what if your customers used their voice instead of typing?"

that question landed differently every time. some people lit up immediately — they'd been thinking about it and had opinions. others paused genuinely hadn't considered it and then started working through the implications out loud. either way it opened something real~

what came up again and again: developers are excited about voice ai but they're running into the same friction points. integration complexity. latency. not knowing where to start. the enthusiasm is there. the on-ramp needs work — and that's a content and documentation opportunity worth paying attention to~

some of the best developer face time happened organically in the conference hallways and around the exhibitor area. voice ai conversations surfaced naturally: people talking about what they were building how different models fit together what they were trying to make work. casual genuine and far more useful than any scripted pitch~

the mentorship angle

a significant chunk of the cascadiajs crowd is newer to the industry — people figuring out how to break in what to build who to learn from. i spent a fair amount of time with that group — not pitching anything just helping where i could~

that paid off in ways that are hard to quantify but easy to feel. "the community engineer at deepgram spent her own time helping me" is the kind of impression that travels. it's a long game but a real one~

i also had a genuinely good conversation with dylan from atomic object about their accelerator programme — a two-year initiative for developing junior developer teams. that surfaced an interesting thesis worth following up on: get developers excited and comfortable with voice ai tools early in their careers and they carry that familiarity with them when they land at larger organizations. hard to attribute pipeline to but worth thinking through carefully~

the thing i didn't expect

seattle's tech community has opinions about ai. strong ones~

nearly every lamp post newspaper box and street fixture i walked past had a "no ai" sticker on it. at the same time the developers inside the conference were genuinely engaged with ai tools — building with them curious about where they're going talking about them with real enthusiasm~

that's a real tension and it's worth watching. it's not a dealbreaker — developers building with ai aren't the same crowd as the people stickering the lamp posts — but it's a signal about the local discourse worth keeping in mind. awareness is better than ignorance here~

who i connected with

a few specific connections worth flagging:

what this means for next time

a traditional deepgram booth at cascadiajs isn't the right fit — not yet. the audience skews junior and a static exhibit doesn't match how this crowd learns best~

what does make sense: a workshop. the appetite for hands-on practical voice ai content was real. a session where developers actually build something — in a room full of people who are genuinely excited about it — is a far better fit for this crowd than a static booth~

the longer play is building a consistent presence in the pacific northwest developer community. not hard sells just showing up reliably and being useful. the channel with the conference organiser is the right thread to pull on. a recurring seattle touchpoint — once we have the infrastructure to make it repeatable and handoff-able — is worth building toward~

the bottom line

cascadiajs 2026 was worth going to. not because it delivered immediate pipeline but because it delivered signal — about where developers are struggling about what the pacific northwest tech community thinks about ai about which relationships are worth investing in~

the voice ai conversation is happening. developers are building with it thinking about it running into friction with it. being present in those conversations — as a genuinely helpful knowledgeable person rather than a brand doing marketing — is what community building looks like at this stage~

more to come as we follow up on the ground we covered~

Love this post? Think Naomi is completely wrong? Have other thoughts you would like to share? Come tell us on Discord~!

← Back to homeSee version history