Skip to content

构建 Application Development 模块:6 个核心概念 + 方法论#13

Open
AlexAnys wants to merge 3 commits intomasterfrom
feat/app-dev-module
Open

构建 Application Development 模块:6 个核心概念 + 方法论#13
AlexAnys wants to merge 3 commits intomasterfrom
feat/app-dev-module

Conversation

@AlexAnys
Copy link
Owner

Summary

基于 Chicago Booth BUSN 36110 课程 transcript(9 天)和 lesson 材料(121 个 HTML)的深度研究,构建第二个完整模块。

定位:与 Coding Agent 协作开发的心智模型前置课。不教语法,教理解——理解了这些概念,给 AI 的指令才能准确,AI 生成的代码才敢改。

新建 7 个页面

章节 核心心智模型
01 互联网是怎么工作的 HTTP 请求/响应 = 餐厅点餐流程
02 数据建模 名词→表,纸质表格测试,关系判断黄金问题
03 请求的生命周期 RCAV(Route→Controller→Action→View)
04 数据库与 CRUD 数据库 = 电子表格,所有功能 = 增删改查
05 API "一切都是 HTTP 请求",AI 调用去神秘化
06 认证与安全 Authentication ≠ Authorization,Session/Cookie
方法论 螺旋学习、砍范围、读错误信息、AI 是乘数

更新 2 个文件

  • 模块 README:新增"为什么 Coding Agent 用户需要这个模块"+ "教学理念"
  • 根 README:模块 2 展开为 7 行概念表

Test plan

  • 7 个概念页全部可从模块首页和根 README 跳转
  • 每个概念页包含:一句话概括、心智模型、常见误区、Agentic Coding 关联
  • 导航链 01→02→03→04→05→06→方法论 完整
  • 模块 README 包含教学理念和与 Agentic Coding 关系说明

基于 Chicago Booth BUSN 36110 课程研究,构建面向 AI 协作开发者的心智模型课:

- 01 互联网是怎么工作的:HTTP 请求/响应、URL 结构
- 02 数据建模:名词→表、关系类型、纸质表格测试
- 03 请求的生命周期:RCAV 模式(Route→Controller→Action→View)
- 04 数据库与 CRUD:增删改查、数据库=电子表格
- 05 API:"一切都是 HTTP 请求",JSON,AI 调用去神秘化
- 06 认证与安全:Authentication vs Authorization、Session/Cookie
- 方法论:螺旋学习、先做后解释、砍范围、读错误信息、AI 是乘数

模块 README 新增"为什么 Coding Agent 用户需要这个模块"和"教学理念"
根 README 同步更新模块 2 的 Level 2 展开
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1339846a05

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".


#### 一对一(One-to-One)

一个用户有一份个人档案。相对少见,但偶尔会用到。处理方式和一对多类似,只是在"一"的那一方加外键。

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Correct one-to-one schema guidance

This sentence says one-to-one relations are handled by adding a foreign key on the “one” side, but that alone does not enforce one-to-one and can easily become one-to-many unless a uniqueness constraint (or shared primary key) is specified. Learners applying this literally may design invalid schemas (e.g., multiple profiles linked to one user), so the guidance should explicitly describe how to enforce cardinality.

Useful? React with 👍 / 👎.

每个概念页新增免费、无需注册的在线练习:
- 01 HTTP:浏览器 DevTools Network 面板 + httpbin.org
- 02 数据建模:SQLiteOnline 建表、外键、JOIN 查询
- 03 RCAV:在 GitHub 上追踪请求路径 + JSONPlaceholder
- 04 CRUD:SQLiteOnline 完整增删改查操作
- 05 API:浏览器直接调 API + Hoppscotch 发 POST 请求
- 06 认证:查看浏览器 Cookie + HTTP vs HTTPS 对比
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant