也有
（请不要不读正文就‘高谈阔论’，多谢！） 新进入一个项目组，组里氛围很好，大家都朝气蓬勃的，但是好像没有 landing 过程，说起来也加入组里 2 月了，做了一些功能改造、错误率优化，但现在如果问我其中两个主要功能的实现逻辑，我只能说个 50 字的大概抽象，对于时序图、系统拆分、API 和 MQ 分别负责什么，我回答不上来 但我们是希望能够提高工程化，建立起统一的响应结构、错误码、代码库结构、系统分拆、可观测性的。 但在这样盲人摸象的情况下，不仅谈不上清晰的需求迭代，而且规范代码编写、可观测性改造也无从下手 所以想问一下社区里的大家，现在是怎么 AI 编程的 --- 自我思考：vibe coding 被提出也有 1-2 年了，新小组 100%代码都是 AI 生成的，成员对代码库心智地图有些模糊，业界有 ADR
This explanation quotes or summarizes the cited source record. Saving creates a bookmark on this device, with no automatic account sync.
- First observed in our collection
- Nov 12, 2026, 6:30 AM UTC
- Earliest cited publication
- Nov 12, 2026, 4:39 AM UTC
- Last observed
- Nov 12, 2026, 6:30 AM UTC
Evidence in the last complete seven days
- Source mentions
- 1 Previous seven days 0
- Distinct sources
- 1 Previous 0
- Comparable growth
- Not comparable
- Ranking appearances
- 0
Collection observations and undated records are separate from dated publication counts. Observed in 7d：1 · Undated records：0
Collection coverage · Comparable windowsCurrent / previous observed days 7 / 7
Counts use complete UTC days. First observed means first seen by this collection, not when a term was coined.
Current window：2026-11-06 → 2026-11-13 (end excluded) · History 25 days
| Source | Current days | Previous days | Last success |
|---|---|---|---|
| arXiv | 7 | 6 | Nov 12, 2026, 11:22 AM UTC |
| arXiv | 7 | 7 | Nov 13, 2026, 2:52 PM UTC |
| Ask HN | 7 | 7 | Nov 13, 2026, 8:38 AM UTC |
| Ask HN | 7 | 7 | Nov 13, 2026, 2:53 PM UTC |
| Ask HN | 7 | 7 | Nov 13, 2026, 1:17 AM UTC |
| Ask HN | 7 | 7 | Nov 13, 2026, 8:38 AM UTC |
| GitHub | 7 | 7 | Nov 13, 2026, 2:52 PM UTC |
| GitHub Issues | 7 | 7 | Nov 13, 2026, 2:52 PM UTC |
| GitHub Releases | 7 | 7 | Nov 13, 2026, 1:16 AM UTC |
| GitHub | 7 | 7 | Nov 13, 2026, 2:52 PM UTC |
| GitHub Issues | 7 | 7 | Nov 13, 2026, 2:52 PM UTC |
| GitHub Releases | 7 | 7 | Nov 13, 2026, 2:53 PM UTC |
| GitHub | 7 | 7 | Nov 13, 2026, 2:53 PM UTC |
| GitHub Issues | 7 | 7 | Nov 13, 2026, 2:52 PM UTC |
| GitHub Releases | 7 | 7 | Nov 13, 2026, 2:53 PM UTC |
| GitHub Discovery | 7 | 1 | Nov 13, 2026, 2:52 PM UTC |
| GitHub Trending | 7 | 7 | Nov 13, 2026, 2:53 PM UTC |
| 7 | 7 | Nov 13, 2026, 8:38 AM UTC | |
| Hugging Face | 7 | 7 | Nov 12, 2026, 9:30 AM UTC |
| Hugging Face Spaces | 7 | 1 | Nov 13, 2026, 1:17 AM UTC |
| Hacker News | 7 | 7 | Nov 13, 2026, 8:38 AM UTC |
| Hacker News | 7 | 7 | Nov 13, 2026, 8:38 AM UTC |
| Hacker News | 7 | 7 | Nov 13, 2026, 8:38 AM UTC |
| Hacker News | 7 | 1 | Nov 13, 2026, 8:38 AM UTC |
| Show HN | 7 | 1 | Nov 13, 2026, 8:38 AM UTC |
| MIT News | 6 | 7 | Nov 13, 2026, 1:16 AM UTC |
| OpenAI | 7 | 7 | Nov 13, 2026, 8:38 AM UTC |
| Product Hunt | 7 | 7 | Nov 13, 2026, 2:53 PM UTC |
| 量子位 | 6 | 6 | Nov 13, 2026, 8:38 AM UTC |
| OpenRouter | 7 | 1 | Nov 13, 2026, 2:53 PM UTC |
| GitHub Trending | 7 | 7 | Nov 12, 2026, 4:00 AM UTC |
| Hugging Face Models | 7 | 1 | Nov 13, 2026, 1:17 AM UTC |
| HF Daily Papers | 6 | 1 | Nov 13, 2026, 1:17 AM UTC |
| OpenRouter | 7 | 1 | Nov 13, 2026, 2:53 PM UTC |
| Product Hunt | 7 | 7 | Nov 12, 2026, 4:00 AM UTC |
| SEC EDGAR | 7 | 7 | Nov 13, 2026, 2:52 PM UTC |
| Sequoia Capital | 7 | 7 | Nov 13, 2026, 8:38 AM UTC |
| Simon Willison | 7 | 1 | Nov 13, 2026, 8:38 AM UTC |
| TechCrunch | 7 | 7 | Nov 13, 2026, 2:52 PM UTC |
| Contracts Finder | 7 | 7 | Nov 13, 2026, 1:16 AM UTC |
| V2EX | 7 | 7 | Nov 13, 2026, 1:00 AM UTC |
- Counts describe monitored public sources, not the whole web or search demand.
Daily history · up to 90 days
Bars show dated source mentions. The latest UTC day may be incomplete. Zero mentions and missing collection coverage are different conditions.
View accessible daily data
| UTC date | Mentions | Sources | Observations | Ranking appearances |
|---|---|---|---|---|
| 2026-10-30 | 0 | 0 | 0 | 0 |
| 2026-10-31 | 0 | 0 | 0 | 0 |
| 2026-11-01 | 0 | 0 | 0 | 0 |
| 2026-11-02 | 0 | 0 | 0 | 0 |
| 2026-11-03 | 0 | 0 | 0 | 0 |
| 2026-11-04 | 0 | 0 | 0 | 0 |
| 2026-11-05 | 0 | 0 | 0 | 0 |
| 2026-11-06 | 0 | 0 | 0 | 0 |
| 2026-11-07 | 0 | 0 | 0 | 0 |
| 2026-11-08 | 0 | 0 | 0 | 0 |
| 2026-11-09 | 0 | 0 | 0 | 0 |
| 2026-11-10 | 0 | 0 | 0 | 0 |
| 2026-11-11 | 0 | 0 | 0 | 0 |
| 2026-11-12 | 1 | 1 | 1 | 0 |
| 2026-11-13 | 0 | 0 | 0 | 0 |
![Source page screenshot: [问与答] 还是想问一下大家是怎么 AI 编程的](/media/b27399a4939d95ce46e3b70f?v=2026-11-12T08%3A15%3A17.407Z)
Source evidence
Sources in the evidence shown：V2EX 1
V2EX · Published Nov 12, 2026
[问与答] 还是想问一下大家是怎么 AI 编程的
（请不要不读正文就‘高谈阔论’，多谢！） 新进入一个项目组，组里氛围很好，大家都朝气蓬勃的，但是好像没有 landing 过程，说起来也加入组里 2 月了，做了一些功能改造、错误率优化，但现在如果问我其中两个主要功能的实现逻辑，我只能说个 50 字的大概抽象，对于时序图、系统拆分、API 和 MQ 分别负责什么，我回答不上来 但我们是希望能够提高工程化，建立起统一的响应结构、错误码、代码库结构、系统分拆、可观测性的。 但在这样盲人摸象的情况下，不仅谈不上清晰的需求迭代，而且规范代码编写、可观测性改造也无从下手 所以想问一下社区里的大家，现在是怎么 AI 编程的 --- 自我思考：vibe coding 被提出也有 1-2 年了，新小组 100%代码都是 AI 生成的，成员对代码库心智地图有些模糊，业界有 ADR
View source record →
Review priority 38 / 100
This score orders research candidates. It is not search volume, a forecast or verified commercial demand.
Evidence
8 / 30Distinct dated articles or first observations; repeat crawling adds nothing.
Publisher diversity
8 / 25Conservative owner grouping; syndicated copies count once.
Comparable change
0 / 20Comparable complete weeks only; no percentage from a zero baseline.
Recent evidence
13.6 / 15Latest publication or first observation, not repeated fetch time.
Name specificity
8 / 10Explicit entities and technical concepts outrank ambiguous acronyms.
Limitations and interpretation
- First observation is a collection milestone, not proof that a word or product is new to the world.
- Counts describe monitored public sources, not the whole web or search demand.
- First observed here is not the invention date of a name or idea.
- Candidates come from public titles, summaries and entity URLs, not verified full-text analysis.
- Owner grouping is conservative; undisclosed syndication may remain.
- The previous week is too small for a reliable percentage change.
- Current evidence comes from one publisher or owner.