Why YC went to DC

YC’s DC Trip and Stated Goals

• YC says it went to DC to advocate for “little tech”: open-source-ish AI, more competition vs “Big Tech”, app-store interoperability, banning noncompetes, fixing software R&D amortization (Section 174), easing compliance, and better health coverage for SMB employees.
• Some posters welcome more political engagement from non–big tech and see concentrated AI power as dangerous.
• Others view this as standard lobbying for YC’s portfolio interests, not for truly under-capitalized companies or “lifestyle” businesses.

YC as Representative of “Little Tech”

• Multiple commenters object to YC branding itself as “the voice of little tech,” given its role in producing unicorns and feeding Big Tech via acquisitions and IPOs.
• Critics point to earlier stances (e.g., lobbying around the SVB collapse) as inconsistent with a “small vs big” narrative.
• A minority argues YC still operates largely at early stage and thus is meaningfully distinct from Big Tech itself.

Open Source AI and Regulation

• Strong disagreement on what “open” means:
  • Some say releasing weights without training data, code, and full architecture/methodology isn’t real transparency or OSS.
  • Others counter that open weights have still enabled big communities (e.g., local inference, fine-tuning) and tangible innovation in applications.
• Licensing carveouts (commercial restrictions, custom terms) are criticized as “fake open source.”
• Concern that safety bills (e.g., ones making open model providers liable for downstream misuse) could chill major open releases.

Section 174 and Compliance Burdens

• Section 174’s requirement to amortize software R&D over 5+ years is described as:
  • For many startups, “phantom profit” taxation (e.g., revenue ≈ salaries but still owing large taxes).
  • A major brake on hiring and innovation, possibly contributing to layoffs/offshoring.
• Discussion shows confusion and conflicting professional guidance on what must be classified as R&D.
• SOC2 and similar frameworks are widely called security theater and de facto barriers for startups; some prefer ISO 27001 or “SOC2-lite,” others want many standards scrapped.

Noncompetes and Talent Poaching

• Many applaud the FTC’s move to ban employee noncompetes as pro-worker freedom and wage competition.
• A significant minority worry that without anti-raiding protections, large incumbents can simply poach entire teams instead of acquiring startups, potentially killing nascent competitors.
• Some note that California already bans noncompetes but has separate anti-raiding doctrines; opinions differ on whether that balance is desirable.

Healthcare and Startups

• Broad frustration with U.S. employer-tied insurance:
  • Startups struggle to offer decent plans; older founders and those with families feel pushed toward large employers.
  • Several advocate decoupling healthcare from employment entirely or moving to some form of universal or single-payer system.
• Others highlight transition complexity: existing insurers, providers, and varied public preferences make “Medicare for All by fiat” politically and fiscally contentious.

Tech, Lobbying, and Campaign Finance

• Some argue tech workers should organize politically like farmers, leveraging their numbers to push for housing reform, administrative modernization, and healthcare changes.
• Others insist the real root problem is money in politics: Citizens United, corporate personhood, and campaign finance structures that make all such lobbying a second-order issue.
• There’s debate over whether restricting corporate speech is compatible with the First Amendment and how to reconcile that with meaningful campaign finance reform.

AI and VC Hype Context

• YC notes that “almost all” funded companies are now AI-related; many interpret this as “you must be AI” to raise.
• Posters draw parallels to earlier waves (mobile, fintech, VR, web3), but several argue AI is more foundational and broadly useful than past fads.
• Some see YC’s current rhetoric (e.g., starting from tech then finding problems) as a reversal of its long-promoted “problem-first” advice, and label it hype-driven.