The race in California's 17th district has turned personal, and that should concern anyone who relies on data tools to do their work. Five-term incumbent Ro Khanna and tech founder Ethan Agarwal are clashing over AI policy, but the real stakes go far beyond campaign ads and billionaire endorsements. This is about whether the people building the technology you use every day will have a seat at the table when lawmakers decide how that technology is governed.
Khanna has publicly supported a proposed California ballot measure that would impose new regulations on AI development. Agarwal entered the race in March, backed by prominent tech billionaires, largely in response to that position. The fight is already nasty, and the primary isn't until June. For users of AI-native tools, this is not a distant political squabble. It is a preview of the tension that will define your experience for the next several years. The central question is straightforward: Should the people writing the rules understand the technology they are regulating, or should they remain at arm's length from the industry they oversee?
We believe the answer is not as simple as either side wants it to be. Khanna has a record of thoughtful engagement with tech policy, and his willingness to take a stand on regulation is not inherently wrong. But Agarwal's entry into the race signals something important: the people building these systems feel that their voices are being excluded from the conversation. That feeling is valid. A regulation written by people who have never built a spreadsheet, let alone an AI model, risks being brittle, impractical, or worse. At the same time, an industry that resists all oversight invites the kind of backlash that leads to poorly designed rules.
What this means for you, as someone exploring or using AI-powered tools, is that the political environment around your software is shifting. The next version of your spreadsheet assistant, your data pipeline, or your analytics platform could be shaped as much by a ballot measure as by a product roadmap. Pay attention to candidates who understand the difference between a prompt and a policy. Your productivity depends on it.
