EP48 AI 来了,代码该这么写才能从从容容游刃有余 episode artwork

EPISODE · Oct 20, 2025 · 26 MIN

EP48 AI 来了,代码该这么写才能从从容容游刃有余

from AsyncTalk

如何才能在 AI 时代写代码写得从从容容,游刃有余?本期 AsyncTalk 讨论了这个问题。给出了一些想法:- 程序员的可拓展逻辑没有变,还是难以替代- 后端就选 node,别 bb- 写代码首先支持可读性,老板的要求都要退居其后有任何意见建议可以在评论区留言,或者邮件联系 [email protected] 也可以在 X(Twitter) 上与我们互动 https://x.com/AsyncTalk主播AnnatarHe: https://annatarhe.comTimeline00:20 AI 仍然是被低估的01:10 程序员不会消失 - 它具有极大的可拓展性02:45 程序员不会消失 - 这个群体人才比例高03:31 程序员的要求会越来越高04:20 程序员要求从老到新都要懂 - XML, CLI 等05:55 AI 时代怎么写项目06:00 Next.js 是你的首选08:52 后端选 Node 或 Python11:27 UI 就选 tailwindcss + shadcn12:44 UI 也可以自己写14:58 业务开发怎么结合 AI15:10 可访问性优先16:30 llm.txt17:00 UA 检查 AI 应该返回纯文本18:23 XML 优于 JSON19:35 支持标准 IO20:38 AI 时代的开发原则21:08 可读性高于一切。高于性能,高于效率,高于短期收益23:58 抛弃非语义化。比如 uuid24:58 写测试25:47 欢迎留下自己的想法相关链接SEO 搜索引擎优化: https://en.wikipedia.org/wiki/Search_engine_optimizationCritical npm supply chain attack response - September 8, 2025: https://vercel.com/blog/critical-npm-supply-chain-attack-response-september-8-2025OpenAI Agents SDK: https://openai.github.io/openai-agents-js/tailwindcss: https://tailwindcss.com/Adam Wathan https://x.com/adamwathan/status/1953510802159219096shadcn: https://ui.shadcn.com/llm.txt: https://llmstxt.org/bun 支持输出 markdown: https://x.com/bunjavascript/status/1971934734940098971?s=46stripe 支持复制为 markdown: https://docs.stripe.com/building-with-llms扩展阅读EP46 如何正确开喷 Next.js: https://asynctalk.com/posts/ep46

Episode metadata supplied by the publisher feed · Published Oct 20, 2025

Embed this episode

Ready to play

EP48 AI 来了,代码该这么写才能从从容容游刃有余

0:00 26:15

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

No similar episodes found.

No similar podcasts found.

Frequently Asked Questions

How long is this episode of AsyncTalk?

This episode is 26 minutes long.

When was this AsyncTalk episode published?

This episode was published on October 20, 2025.

Can I download this AsyncTalk episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.
URL copied to clipboard!