Vibe Coding 时代：为何身份认证不应由 AI 生成
Vibe coding and shipping fast means an insane amount of code is hitting prod. Yo…
Vibe coding and shipping fast means an insane amount of code is hitting prod. You’ve gotta be smart about the foundational tools you build on.
快速进行 Vibe Coding 并上线意味着大量代码被推送到生产环境。你必须对构建所依赖的基础工具保持明智的选择。
Identity is a good example.
身份认证就是一个很好的例子。
You can ask the agent to "add auth" and get a working login flow quickly. Then the product starts accumulating requirements: MFA, user data, enterprise SSO, organization boundaries, compliance, eventually SCIM. Suddenly, auth isn’t just another generated feature. It’s something you’re going to have to test, secure, and maintain for years.
你可以要求 AI 助手“添加认证功能”，从而快速获得一个可用的登录流程。随后，产品开始积累各种需求：多因素认证 (MFA)、用户数据、企业单点登录 (SSO)、组织边界、合规性，最终还包括 SCIM。突然间，认证不再只是另一个生成的功能模块，而是你需要测试、保障安全并长期维护的核心组件。
This is where using @auth0 from day 1 makes more sense to me than treating authentication as another piece of generated application code.
正因如此，我认为从第一天起就使用 @auth0，比将认证视为另一段生成的应用程序代码更有意义。
That’s where I’d rather use something purpose-built like Auth0 from day one than keep adding identity logic to the application itself.Auth0 gives you a way to start with what you need today and scale identity as the product grows.
因此，我更倾向于从一开始就使用 Auth0 这样专为身份管理打造的服务，而不是不断向应用程序本身添加身份逻辑。Auth0 让你能够以当前所需的功能起步，并随着产品的增长扩展身份管理能力。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力