[docs]: update closing ceremony speech #57
Conversation
Nliver
requested review from
CarlJi and
Copilot
and removed request for
Copilot
Summary of ChangesHello @Nliver, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! 本次拉取请求主要新增了一篇关于AI时代软件工程重塑的深度文章，该文章由许式伟先生撰写，详细阐述了AI技术如何改变软件开发范式。同时，对现有文档进行了重命名和结构调整，以保持内容组织的一致性，并对 Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the closing ceremony speech and reorders some documents. The newly added article, 'Reshaping Software Engineering in the AI Era,' is insightful and well-structured.
My review focuses on the new Markdown file, providing suggestions to improve its formatting and maintain consistency with standard practices. The feedback includes:
- Adjusting heading levels for better document structure.
- Using standard Markdown syntax for paragraph breaks.
- Converting a plain URL into a clickable link for better usability.
- Ensuring the file ends with a newline, which is a common convention.
These minor changes will help improve the overall quality and readability of the document. Please see the specific comments for details.
|
|
||
| 在第四期1024实训营结营仪式上，实训营发起人许式伟先生以《AI 时代重塑软件工程》为题，为全体学员和在线观众带来了一场深度分享。他从软件工程的基础理论出发，深入剖析了AI技术对软件工程领域的深刻影响与重塑。以下是演讲全文： | ||
|
|
||
| # 正文： |
There was a problem hiding this comment.
It's recommended to adjust the heading level for better document structure. The main title of the article is already a level 1 heading (#). This line, 正文： (which means "Body text:"), should probably be a level 2 heading (##) to maintain a proper hierarchy. Alternatively, since it acts as an introduction, you could remove it entirely for a more compact presentation.
| # 正文： | |
| ## 正文： |
|
|
||
| 这意味着，“许式定律”中的极限理论不再只是思想实验，而成为每个团队必须面对的现实： | ||
|
|
||
| >如果你的产品需求清晰、架构拆解合理，AI能在几小时内交付过去需要数周的代码；<br/>但如果你的需求模糊、模块边界混乱，AI只会以百倍速度放大你的错误。 |
There was a problem hiding this comment.
It's better to use standard Markdown for paragraph breaks within a blockquote. Using <br/> might not render consistently across all platforms. I suggest splitting the content into two separate blockquotes for better clarity and standard compliance.
| >如果你的产品需求清晰、架构拆解合理，AI能在几小时内交付过去需要数周的代码；<br/>但如果你的需求模糊、模块边界混乱，AI只会以百倍速度放大你的错误。 | |
| >如果你的产品需求清晰、架构拆解合理，AI能在几小时内交付过去需要数周的代码； | |
| >但如果你的需求模糊、模块边界混乱，AI只会以百倍速度放大你的错误。 |
|
|
||
| 如果一个公司的软件开发过程没有因为AI而实现效率倍增，那么它必将成为落后者。效率翻倍只是底线，实际上有潜力实现更高的提升。 | ||
|
|
||
| 在 XGo 语言的开发中，我们已经全面使用 AI Coding，并且以完全公开透明的方式展示整个过程——包括如何给 AI 提任务、如何指挥 AI 工作。欢迎大家到 XGo 仓库（github.com/goplus/xgo）观摩交流。 |
There was a problem hiding this comment.
For better readability and accessibility, it's recommended to format this plain URL as a clickable Markdown link.
| 在 XGo 语言的开发中，我们已经全面使用 AI Coding，并且以完全公开透明的方式展示整个过程——包括如何给 AI 提任务、如何指挥 AI 工作。欢迎大家到 XGo 仓库（github.com/goplus/xgo）观摩交流。 | |
| 在 XGo 语言的开发中，我们已经全面使用 AI Coding，并且以完全公开透明的方式展示整个过程——包括如何给 AI 提任务、如何指挥 AI 工作。欢迎大家到 XGo 仓库（[github.com/goplus/xgo](https://github.com/goplus/xgo)）观摩交流。 |
|
|
||
| 软件工程正在被重塑，而我们有幸成为这场变革的见证者和参与者。与其恐惧，不如拥抱；与其被动，不如主动学习驾驭这个强大的新工具。 | ||
|
|
||
| 未来的软件工程，属于那些能够将人类智慧与机器智能完美结合的组织和个人。 No newline at end of file |
There was a problem hiding this comment.
It's a common convention to have a single newline at the end of a file. This prevents issues with some command-line tools like cat and can avoid noisy diffs in version control.
| 未来的软件工程，属于那些能够将人类智慧与机器智能完美结合的组织和个人。 | |
| 未来的软件工程，属于那些能够将人类智慧与机器智能完美结合的组织和个人。 | |
![xgopilot[bot]](https://avatars.githubusercontent.com/in/1924301?s=60&v=4){kind=small}
| | 14 | Code Review 不是什么——盘点5个常见误区 | [📖 阅读](2025/14.%20Code%20Review%20不是什么/what-code-review-is-not.md) | | ||
| | 15 | 架构设计从何入手？ | [📖 阅读](2025/15.%20架构设计从何入手/content.md) | | ||
|
|
||
| ### 🎓 第 4 期训练营 |
There was a problem hiding this comment.
Critical: Missing entries for articles #16-22 in table of contents. The new article (#22) and 6 other existing articles are not discoverable via README. Please add:
| 16 | 关于架构设计的几点认知体会 | [📖 阅读](2025/16.%20关于架构设计的几点认知体会/content.md) |
| 17 | SPX-Algorithm：构建多模态搜索服务的一些心得 | [📖 阅读](2025/17.%20SPX-Algorithm：构建多模态搜索服务的一些心得/share.md) |
| 18 | 代码不是核心：从 XLink 项目看产品开发的决策层次 | [📖 阅读](2025/18.%20代码不是核心：从%20XLink%20项目看产品开发的决策层次/content.md) |
| 19 | llpyg: LLGo 快速集成 Python 生态的桥梁 | [📖 阅读](2025/19.%20llpyg:%20LLGo%20快速集成%20Python%20生态的桥梁/content.md) |
| 20 | X绘图-我们是如何让AI更好的融入我们的产品的 | [📖 阅读](2025/20.X绘图-我们是如何让AI更好的融入我们的产品的/实训感悟.md) |
| 21 | 实训营分享：LLGo 中 Python 编译与运行时集成 | [📖 阅读](2025/21.%20实训营分享：LLGo%20中%20Python%20编译与运行时集成/content.md) |
| 22 | 许式伟：AI时代重塑软件工程 | [📖 阅读](2025/22.许式伟：AI时代重塑软件工程/reinventing_software_engineering_in_the_AI_Era.md) |
|
|
||
| 在第四期1024实训营结营仪式上，实训营发起人许式伟先生以《AI 时代重塑软件工程》为题，为全体学员和在线观众带来了一场深度分享。他从软件工程的基础理论出发，深入剖析了AI技术对软件工程领域的深刻影响与重塑。以下是演讲全文： | ||
|
|
||
| # 正文： |
There was a problem hiding this comment.
Critical: Double H1 heading violates markdown structure. Either remove "# 正文：" or change to ## 正文：. Recommend removing entirely as it adds no semantic value.
|
|
||
| 软件工程正在被重塑，而我们有幸成为这场变革的见证者和参与者。与其恐惧，不如拥抱；与其被动，不如主动学习驾驭这个强大的新工具。 | ||
|
|
||
| 未来的软件工程，属于那些能够将人类智慧与机器智能完美结合的组织和个人。 No newline at end of file |
There was a problem hiding this comment.
Critical: Missing newline at end of file (violates POSIX and repository's own article #6 standard "一行之差：为什么你的文件末尾应该留一个空行？"). Please add trailing newline.
|
|
||
| 如果一个公司的软件开发过程没有因为AI而实现效率倍增，那么它必将成为落后者。效率翻倍只是底线，实际上有潜力实现更高的提升。 | ||
|
|
||
| 在 XGo 语言的开发中，我们已经全面使用 AI Coding，并且以完全公开透明的方式展示整个过程——包括如何给 AI 提任务、如何指挥 AI 工作。欢迎大家到 XGo 仓库（github.com/goplus/xgo）观摩交流。 |
There was a problem hiding this comment.
Consider converting to proper markdown link for better UX:
欢迎大家到 [XGo 仓库](https://github.com/goplus/xgo) 观摩交流。
| 架构设计之所以比产品设计更难，是因为它极度“逆直觉”。当我看到团队 Leader 简单地按照页面分配任务（页面A交给张三，页面B交给李四......）时，就知道这样的架构设计通常是错误的。**真正好的架构设计是在做“乘法”**，它要求每个模块都应被当作一个“子业务”来设计——**有独立需求边界、高复用性、低耦合。就像搭乐高，积木种类越少、拼装步骤越简、外部依赖越成熟，系统就越健壮**。 | ||
|
|
||
|
|
||
| ## AI时代：“人月神话” 的终结 |
There was a problem hiding this comment.
Inconsistent spacing: two blank lines before heading. Use single blank line for consistency.
|
|
||
| 这意味着，“许式定律”中的极限理论不再只是思想实验，而成为每个团队必须面对的现实： | ||
|
|
||
| >如果你的产品需求清晰、架构拆解合理，AI能在几小时内交付过去需要数周的代码；<br/>但如果你的需求模糊、模块边界混乱，AI只会以百倍速度放大你的错误。 |
There was a problem hiding this comment.
Consider using markdown line breaks instead of HTML <br/> for better portability:
> 如果你的产品需求清晰、架构拆解合理,AI能在几小时内交付过去需要数周的代码；
>
> 但如果你的需求模糊、模块边界混乱,AI只会以百倍速度放大你的错误。1 participant
Update article "Reshaping Software Engineering in the AI Era"