2025-04-04-top
- 精選方式: TOP
- 時間範圍: DAY
討論重點
以下是29篇文章的摘要與重點條列整理,並附上對應的錨點連結:
#1 hot take: Vibe Coding will be dead before most people understand
- AI在軟體開發中的局限性
- AI(如LLM)創造的價值有限,技術能力仍是關鍵。
- 軟體工程師的不可替代性
- 工程師在核心問題上仍具經濟可靠性,AI生成代碼無法取代主導地位。
- 編程的本質是解決問題
- 重點在解決問題能力,而非單純代碼生成。
#2 slurp-ai: Tool for scraping and consolidating documentation websites into a single MD file.
- 工具功能
- 將文檔網站轉為Markdown,提升LLM回應質量。
- 與Cursor Pro比較
- 探討是否為更優的開源替代方案。
- 實際應用測試
- 詢問兼容性(如ArcGIS Pro文檔)。
#3 RA.Aid Update: Claude 3.7, Gemini 2.5 Pro, Custom Tools, Ollama & More!
- 功能擴展
- 支援Claude 3.7、Gemini 2.5 Pro等模型,整合Ollama。
- 開發者體驗
- 新增API文件、成本監控工具。
- 開源精神
- 鼓勵社群貢獻(Apache 2.0授權)。
#4 Gemini 2.5 Pro saving me from duplication hell
- 簡短口號:傳達「英雄精神不朽」的激勵性概念。
#5 Like fr
- 自然語言提示的局限
- 結構化符號化(symboling)更高效。
- 諷刺技術演進
- 未來可能將既有技巧當作新發現。
#6 Best AI tools to analyze full codebase
- 需求背景:尋求優化NodeJS/Express遊戲專案的AI工具推薦(如GitHub Copilot)。
#7 Vibe coding creates a mess, but it can be solved faster
- AI編程痛點
- 無限除錯循環耗時。
- 解決方案
- 開源工具「Composer Web」自動收集日誌、截圖。
- 社群協作
- 計劃擴展支援iOS模擬器、AWS日誌。
#8 Vibe Coding vs Vibe Engineering
- 批判流行術語:嘲諷「氛圍工程」定義模糊且缺乏實質內容。
#9 Hot take
- AI趨勢不可逆
- 呼籲開發者學習AI工具,避免被淘汰。
- 歷史教訓
- 引用黑莓抗拒觸控技術的失敗案例。
#10 M/L Science applied to prompt engineering for coding assistan
- 元認知架構
- 結合流程圖與記憶銀行提升AI決策能力。
- 開源理念
- Apache 2.0授權,強調技術民主化。
#11 Oops, at least it works...
- 溝通問題:非技術人員(如PM)因缺乏背景知識無法理解代碼。
#12 Has anyone tried Exponent?
- 工具初體驗:詢問社群對新工具的使用反饋。
#13 Any idea to work around claude ai free plan limitations?
- 免費方案限制:尋求超額後繼續使用的方法。
#14 Screw Coding Assessmen
- 工具功能
- 自動破解HackerRank等平台題目。
- 免責聲明
- 不承擔使用者風險。
#15 Kerricks Wager: on the Future of Manual Programming
- AI風險賭注
- 主張預防AI潛在威脅(即使機率低)。
- 反駁質疑
- 對比
文章核心重點
以下是各篇文章標題的一句話摘要(條列式輸出):
- Vibe Coding將在大多數人理解前消亡:AI代碼生成無法取代軟體工程師解決複雜問題的核心價值。
- slurp-ai工具:將文檔網站轉換為單一Markdown文件以提升LLM回應質量的開源工具。
- RA.Aid更新:開源AI編程助手新增多模型支援、本地整合與自訂工具功能。
- Gemini 2.5 Pro拯救重複地獄:簡短口號傳達「英雄精神不朽」的象徵意義。
- Like fr:諷刺從自然語言提示到結構化「符號化」的技術演進被當作新發現。
- 分析完整代碼庫的最佳AI工具:尋求優化NodeJS/Express遊戲專案的AI工具推薦。
- Vibe coding製造混亂但能更快解決:開發者自製工具「Composer Web」簡化AI生成代碼的除錯流程。
- Vibe Coding vs Vibe Engineering:嘲諷技術領域中缺乏實質內容的流行術語。
- Hot take:呼籲開發者接受AI編程趨勢,避免重蹈黑莓抗拒觸控技術的覆轍。
- 提示工程的M/L科學應用:提出結合認知科學與強化學習的元認知提示框架。
- 至少它能運作...:幽默反映非技術人員參與程式碼審查的溝通障礙。
- 有人試過Exponent嗎?:分享新工具使用體驗並徵求社群反饋。
- 繞過Claude免費方案限制的方法?:探討免費額度耗盡後的替代使用策略。
- 面試程式測驗破解工具:作者釋出免費Python工具自動解題,聲明不承擔風險責任。
- Kerrick的賭注:借鑑帕斯卡賭注論證防範AI存在級風險的必要性。
- 面試中被問過除錯問題嗎?:需提供影片內容才能摘要。
- 有人試過SourceGraph Cody嗎?:詢問企業級低調技術的實際使用體驗。
- AI現狀:新手能用AI編寫主題醫院嗎?:探討不同技能層級結合AI開發遊戲的極限。
- 完全新手——目標現實嗎?:非技術者評估自建危機熱線排班系統的可行性。
- 用Flask/Python和ChatGPT擴充功能:尋求AI輔助Python開發的資源與社群。
- 尋找某款應用程式:求助社群回憶一款專注生成程式碼提示的桌面工具。
- 為Vibe coders打造的安全工具:提供人工代碼審查與自動刪除的隱私保護服務。
- 終端中用AI除錯瀏覽器應用:Plandex v2新增自動轉發瀏覽器日誌至終端功能。
- 幾個問題:開發者質疑AI生成代碼的實用性與手動編程價值。
- 當前最常用模型?:探討依任務難度切換模型以平衡成本、能力與速度的策略。
- Augment Agent上線:用戶批評該月費30美元服務性價比低且功能不足。
- 用手機Vibe coding?:尋求手機遠端監控伺服器日誌的簡便方案。
- 代理式編程工具是浪費:批判AI代理工具成本高、效率低,手動精簡上下文更優。
- 千元出售:社群質疑產品Manos Pro價值,認為不如ChatGPT Plus。
(註:第16篇因缺乏內容未生成摘要)
目錄
- [1.
hot take: Vibe Coding will be dead before most people understand](#1-``` hot-take-vibe-coding-will-be-dead-before-mos) - [2.
slurp-ai: Tool for scraping and consolidating documentation websites into a single MD file.](#2-``` slurp-ai-tool-for-scraping-and-consolidating) - [3.
RA.Aid Update: Claude 3.7, Gemini 2.5 Pro, Custom Tools, Ollama & More!](#3-``` ra-aid-update-claude-3-7-gemini-2-5-pro-cust) - [4.
Gemini 2.5 Pro saving me from duplication hell](#4-``` gemini-2-5-pro-saving-me-from-duplication-he) - [5.
Like fr](#5-``` like-fr-
- [6. ```
Best AI tools to analyze full codebase
```](#6-```
best-ai-tools-to-analyze-full-codebase
```)
- [7. ```
Vibe coding creates a mess, but it can be solved faster
```](#7-```
vibe-coding-creates-a-mess-but-it-can-be-sol)
- [8. ```
Vibe Coding vs Vibe Engineering
```](#8-```
vibe-coding-vs-vibe-engineering
```)
- [9. ```
Hot take
```](#9-```
hot-take
```)
- [10. M/L Science applied to prompt engineering for coding assistan```](#10-m-l-science-applied-to-prompt-engineering-for-c)
- [11. ```
Oops, at least it works...
```](#11-```
oops-at-least-it-works-
```)
- [12. ```
Has anyone tried Exponent?
```](#12-```
has-anyone-tried-exponent-
```)
- [13. ```
Any idea to work around claude ai free plan limitations?
```](#13-```
any-idea-to-work-around-claude-ai-free-plan)
- [14. ```
Screw Coding Assessmen``` - Follow up: I wrote a free program that will solve code assessment challenges for job interviews
```](#14-```
screw-coding-assessmen```-follow-up-i-wrote)
- [15. ```
Kerricks Wager: on the Future of Manual Programming
```](#15-```
kerricks-wager-on-the-future-of-manual-prog)
- [16. ```
Have you ever been asked about debugging or troubleshooting in a coding interview?
```](#16-```
have-you-ever-been-asked-about-debugging-or)
- [17. ```
Anyone try SourceGraph Cody?
```](#17-```
anyone-try-sourcegraph-cody-
```)
- [18. ```
Where is AI at now: could you code Theme Hospital with beginner knowledge?
```](#18-```
where-is-ai-at-now-could-you-code-theme-hos)
- [19. ```
complete noob - realistic goal?
```](#19-```
complete-noob-realistic-goal-
```)
- [20. ```
Using flask/python and ChatGPT to ammend functionality
```](#20-```
using-flask-python-and-chatgpt-to-ammend-fu)
- [21. ```
Trying to re-find this application
```](#21-```
trying-to-re-find-this-application
```)
- [22. ```
Built a tool that secures the code for vibe coders
```](#22-```
built-a-tool-that-secures-the-code-for-vibe)
- [23. ```
Debugging browser apps in the terminal with AI
```](#23-```
debugging-browser-apps-in-the-terminal-with)
- [24. ```
A few questions
```](#24-```
a-few-questions
```)
- [25. ```
Which models are you using most right now? Which models do you find are the best overall and which do you find to strike the best balance of cost, ability, and speed?
```](#25-```
which-models-are-you-using-most-right-now-w)
- [26. ```
Augment Agent is live today. Unlimited usage?
```](#26-```
augment-agent-is-live-today-unlimited-usage)
- [27. ```
Vibe coding from my phone?
```](#27-```
vibe-coding-from-my-phone-
```)
- [28. ```
Agentic coding with tools like Aider, Cline, Claude Code, etc. is a waste
```](#28-```
agentic-coding-with-tools-like-aider-cline-)
- [29. ```
I'll sell it for 1,000 bucks.
```](#29-```
i-ll-sell-it-for-1-000-bucks-
```)
---
## 1. ```
hot take: Vibe Coding will be dead before most people understand
``` {#1-```
hot-take-vibe-coding-will-be-dead-before-mos}
這篇文章的核心討論主題可以總結為以下幾點:
1. **AI在軟體開發中的局限性**:
- 作者認為AI(如LLM)的應用範圍有限,且在整體軟體開發中創造的價值不高。
- 技術能力(如解決問題的能力)仍是充分發揮AI潛力的關鍵,而非單純依賴AI生成代碼。
2. **軟體工程師(SWEs)的不可替代性**:
- 對於與收入相關的核心問題,軟體工程師仍然是經濟上更可靠的選擇。
- 即使AI代碼生成能力提升(如已達99%),也不會從根本上改變工程師的主導地位。
3. **編程的本質是解決問題**:
- 編程的重點不在於「打字」(即寫代碼),而在於解決問題的能力。
- 只有具備解決問題的能力,才能真正創造價值,而非依賴AI生成代碼。
**核心結論**:
AI工具(如LLM)雖能輔助代碼生成,但無法取代軟體工程師的核心價值——解決複雜問題的能力。技術技能和問題導向的思維仍是軟體開發的關鍵。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqjn4r/hot_take_vibe_coding_will_be_dead_before_most/](https://reddit.com/r/ChatGPTCoding/comments/1jqjn4r/hot_take_vibe_coding_will_be_dead_before_most/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqjn4r/hot_take_vibe_coding_will_be_dead_before_most/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqjn4r/hot_take_vibe_coding_will_be_dead_before_most/)
- **發布時間**: 2025-04-03 22:17:52
### 內容
Dead -> wide understanding that 1) it has limited applicability and generates little value in the grand scheme of software development and 2) technical skills are fundamental to using AI to i``` full potential;
Notes:
- For revenue relevant problems SWEs are and will remain the economically relevant choice
- LLM capabilities will not fundamentally change that regardless what Anthropic and OpenAI CEOs say. Engineers are already at 99% AI code generation.
- Coding was never about typing. Learn to solve problems, if you want to generate value.
---
## 2. ```
slurp-ai: Tool for scraping and consolidating documentation websites into a single MD file.
``` {#2-```
slurp-ai-tool-for-scraping-and-consolidating}
這段對話的核心討論主題是關於一個能夠將整個文檔網站轉換為Markdown格式(MD)並將其納入上下文(context)以提高大型語言模型(LLM)回應質量的工具。具體要點包括:
1. **工具的功能與優勢**:
- 該工具能節省時間並提升LLM的回應質量,尤其適用於將文檔網站內容轉換為Markdown並整合到上下文中的場景。
- 未來計劃是將其開發為MCP(可能是某種伺服器)服務。
2. **與現有工具(如Cursor Pro)的比較**:
- 討論該工具是否與Cursor Pro的「添加文檔」功能類似,或是更優的開源替代方案(可能免費提供)。
3. **實際應用測試**:
- 詢問該工具是否適用於特定網頁(如ArcGIS Pro的官方幫助文檔),探討其兼容性與實用性。
總結:對話聚焦於一款文檔處理工具的效率、功能比較(商業vs.開源)以及實際應用場景的驗證。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqceld/slurpai_tool_for_scraping_and_consolidating/](https://reddit.com/r/ChatGPTCoding/comments/1jqceld/slurpai_tool_for_scraping_and_consolidating/)
- **外部連結**: [https://github.com/ratacat/slurp-ai](https://github.com/ratacat/slurp-ai)
- **發布時間**: 2025-04-03 15:44:39
### 內容
I just finished working on this tonight, it's been super helpful, and saves me a lot of time. And can really up the quality of your LLM responses when you can slurp a whole doc site to MD and drop it in context. Next steps are to get it working as an MCP server. But this is a really good start.
Thanks! I've been looking for something like this.
what am i missing ?
"The question is only from people who use cursor pro"
so cursor offers add docs feature in the setting, is slurp same but better or just same but for open source community and i``` free ?
Just wondering if you think it would work on this?
https://pro.arcgis.com/en/pro-app/latest/help/main/welcome-to-the-arcgis-pro-app-help.htm
---
## 3. ```
RA.Aid Update: Claude 3.7, Gemini 2.5 Pro, Custom Tools, Ollama & More!
``` {#3-```
ra-aid-update-claude-3-7-gemini-2-5-pro-cust}
這篇文章的核心討論主題是 **RA.Aid 開源 AI 編程助手的最新功能更新與版本發布**,具體聚焦於以下重點:
1. **功能擴展**
- 新增多種 LLM 模型支援(如 Claude 3.7、Gemini 2.5 Pro、Fireworks AI 等)
- 強化本地模型整合(Ollama 支援)
- 自訂工具擴展性(透過 MCP 協議和 `--custom-tools` 標籤)
2. **開發者體驗優化**
- 透明度提升(`<think>` 標籤支援思考過程可視化)
- 新增 API 文件與 OpenAPI 規範
- 實用工具改進(如從文件載入提示、追蹤 token 使用量、成本監控等)
3. **社群協作與開源精神**
- 感謝貢獻者名單
- 鼓勵用戶回饋與參與開發
4. **產品定位**
- 強調免費、開源(Apache 2.0 授權)
- 專注於命令列原生工作流程的高效能 AI 助手
總結:文章旨在向開發者社群推廣 RA.Aid 的最新版本,突出其技術升級、靈活性和社群驅動的特性,並邀請用戶試用與參與貢獻。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jpxtvw/raaid_update_claude_37_gemini_25_pro_custom_tools/](https://reddit.com/r/ChatGPTCoding/comments/1jpxtvw/raaid_update_claude_37_gemini_25_pro_custom_tools/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jpxtvw/raaid_update_claude_37_gemini_25_pro_custom_tools/](https://www.reddit.com/r/ChatGPTCoding/comments/1jpxtvw/raaid_update_claude_37_gemini_25_pro_custom_tools/)
- **發布時間**: 2025-04-03 03:44:02
### 內容
Hey all
For those unfamiliar, RA.Aid is a completely free and open-source (Apache 2.0) AI coding assistant designed for intensive, command-line native agent workflows. We've been busy over the past few releases (v0.17.0 - v0.22.0) adding some powerful new features and improvemen```!
New LLM Provider Support
We've expanded our model compatibility significantly! RA.Aid now suppor```:
-
Anthropic Claude 3.7 Sonnet (
claude-3.7-sonnet) -
Google Gemini 2.5 Pro (
gemini-2.5-pro-exp-03-25) -
Fireworks AI models (
fireworks/firefunction-v2,fireworks/dbrx-instruct) -
Groq provider for blazing fast inference of open models like
qwq-32b -
Deepseek v3 0324 models
Local Model Power
Run powerful models locally with our new & improved Ollama integration. Gain privacy and control over your development process.
Extensibility with Custom Tools
Integrate your own scrip``` and external tools directly into RA.Aid's workflow using the Model-Completion-Protocol (MCP) and the --custom-tools flag. Tailor the agent to your specific needs!
Transparency & Control
Understand the agent's reasoning better with \<think\> tag support (`--show-though````), now with implicit detection for broader compatibility. See the thought process behind the actions.
</> Developer Focus
We've added comprehensive API Documentation, including an OpenAPI specification and a dedicated documentation site built with Docusaurus, making it easier to integrate with and understand RA.Aid's backend.
⚙️ Usability Enhancemen```
-
Load promp``` or messages directly from files using
--msg-file. -
Track token usage across sessions with
ra-aid usage latestandra-aid usage all. -
Monitor cos``` with the
--show-costflag. -
Specify a custom project data directory using
--project-state-dir.
Community Contributions
A massive thank you to our amazing community contributors who made these releases possible! Special shout-ou``` to:
-
Ariel Frischer
-
Arshan Dabirsiaghi
-
Benedikt Terhechte
-
Guillermo Creus Botella
-
Ikko Eltociear Ashimine
-
Jose Leon
-
Mark Varkevisser
-
Shree Varsaan
-
Will Bonde
-
Yehia Serag
-
arthrod
-
dancompton
-
patrick
Try it Out!
Ready to give the latest version a spin?
pip install -U ra-aid
We'd love to hear your feedback! Please report any bugs or suggest features on our GitHub Issues. Contributions are always welcome!
Happy coding!
---
## 4. ```
Gemini 2.5 Pro saving me from duplication hell
``` {#4-```
gemini-2-5-pro-saving-me-from-duplication-he}
這句簡短的口號「Heroes never die!」的核心討論主題可以總結為:
**「英雄精神的不朽與永恆性」**
它傳達了英雄(無論是現實或虛構人物)的影響力、犧牲或價值不會因時間或死亡而消逝,可能隱含對勇氣、奉獻或理想化形象的頌揚。此概念常見於激勵性話語、流行文化(如遊戲《鬥陣特攻》中的角色臺詞)或紀念性場合,強調精神層面的延續性。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jq4jef/gemini_25_pro_saving_me_from_function_duplication/](https://reddit.com/r/ChatGPTCoding/comments/1jq4jef/gemini_25_pro_saving_me_from_function_duplication/)
- **外部連結**: [https://i.redd.it/16pns1uklise1.gif](https://i.redd.it/16pns1uklise1.gif)
- **發布時間**: 2025-04-03 08:31:28
### 內容
Heroes never die!
---
## 5. ```
Like fr
``` {#5-```
like-fr-
```}
這段文字的核心討論主題是:**從自然語言提示(prompting)到更結構化、精確的「符號化」(symboling)的演變趨勢**,並以幽默的方式諷刺未來「氛圍編程者」(vibe coders)可能將這種進化視為新發現的現象。
具體要點包括:
1. **自然語言提示的局限性**:指出單純依賴自然語言與大型語言模型(LLM)互動可能效率不足。
2. **結構化提示的優勢**:強調改用特定語法、符號或精確描述(即「符號化」)能提升結果品質。
3. **對技術演進的諷刺**:調侃未來使用者可能將這種早已存在的技巧當作「新發明」來追捧,反映技術社群中常見的「重新發明輪子」現象。
整體透過反諷語氣,探討人類與AI互動方式的優化及技術認知上的落差。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqn5xm/like_fr/](https://reddit.com/r/ChatGPTCoding/comments/1jqn5xm/like_fr/)
- **外部連結**: [https://i.redd.it/6vwcs3onqmse1.jpeg](https://i.redd.it/6vwcs3onqmse1.jpeg)
- **發布時間**: 2025-04-04 00:35:17
### 內容
Ironically, by the time they're done, they'll be actual coders.
Vibe coders a year from now:
"HEY GUYZZZ, did you know if you stop using 'natural language' and instead write promp using specific prose and syntax to represent the functionality want, that you get way better resul?! I've come up with a new name for this wild style of interacting with LLMs: symboling!"
---
## 6. ```
Best AI tools to analyze full codebase
``` {#6-```
best-ai-tools-to-analyze-full-codebase
```}
這篇文章的核心討論主題是:
**「詢問推薦適合協助改進NodeJS與Express網頁遊戲專案的AI工具(如GitHub Copilot或RooCode等),並尋求相關建議。」**
具體重點包括:
1. **需求背景**:重新優化幾年前開發的NodeJS+Express網頁遊戲程式碼並新增功能。
2. **工具類型**:尋求AI輔助工具(如程式生成、自動補全)或特定模型的推薦。
3. **開放性提問**:希望獲得任何相關的使用建議或技巧。
關鍵字:AI工具推薦、NodeJS/Express專案優化、程式碼改進。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jpxewk/best_ai_tools_to_analyze_full_codebase/](https://reddit.com/r/ChatGPTCoding/comments/1jpxewk/best_ai_tools_to_analyze_full_codebase/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jpxewk/best_ai_tools_to_analyze_full_codebase/](https://www.reddit.com/r/ChatGPTCoding/comments/1jpxewk/best_ai_tools_to_analyze_full_codebase/)
- **發布時間**: 2025-04-03 03:27:00
### 內容
Hello,
I have a game I coded a few years ago which I want to revisit. I plan to improve the code and add some features. It's a relatively simple web app using NodeJS and Express.
Which AI tools would you recommend to help me with this? It could be a tool like CoPilot/RooCode or a specific model. Any tips will be appreciated.
Thank you.
---
## 7. ```
Vibe coding creates a mess, but it can be solved faster
``` {#7-```
vibe-coding-creates-a-mess-but-it-can-be-sol}
這篇文章的核心討論主題是:
**「開發者如何透過自製工具『Composer Web』解決AI編程(如Cursor、Copilot等)在快速生成應用時遇到的除錯效率問題,並尋求開源社群的協作與反饋以擴展功能。」**
具體要點包括:
1. **AI編程的現狀與痛點**:作者描述使用AI工具(如Cursor、ChatGPT)快速生成應用時,常陷入「無限除錯循環」,需手動介入耗時排查。
2. **解決方案的開發**:為提升效率,作者開發了開源工具「Composer Web」,能一鍵自動收集網頁日誌、網絡請求、截圖等資訊,直接傳送至AI聊天界面(如Cursor),大幅簡化除錯流程。
3. **開源協作與未來規劃**:工具爆紅後,作者邀請社群參與維護,並計劃擴展支援iOS模擬器、AWS日誌等場景,同時兼容其他開源IDE。
4. **社群互動**:強調開放接受反饋,鼓勵使用者透過GitHub或Discord提供建議。
整體聚焦於「透過工具橋接AI編程與實際開發流程的落差」,並推動社群共同優化。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqec4q/vibe_coding_creates_a_mess_but_it_can_be_solved/](https://reddit.com/r/ChatGPTCoding/comments/1jqec4q/vibe_coding_creates_a_mess_but_it_can_be_solved/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqec4q/vibe_coding_creates_a_mess_but_it_can_be_solved/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqec4q/vibe_coding_creates_a_mess_but_it_can_be_solved/)
- **發布時間**: 2025-04-03 17:54:48
### 內容
I've been using Cursor, Co-Pilot, ChatGPT, Claude and what not since quite some time now, and we are at a stage where we can just "vibe code" whole apps from idea to execution in a few promp```.
I tried this personally to create some side projec that solved little problems for me. But I always got stuck at a point where it just goes into an infinite loop of issues and can't solve the issue by ielf.
Well, I'm a developer, so it's easier for me to dive into the code and solve the problem myself, but that would take a hell lot of time to understand all the code AI wrote for me. If I keep wanna "vibing", I would just give it the screenshot of my current webpage view along with the console logs, and even network reques if i connected to some APIs.
But even this took quite some manual effort and time, so I decided to solve this problem for myself when I created Composer Web
It solves that problem seamlessly by sending all your logs, reqs, and screenshot of your webpage altogether directly to your cursor chat, in just one-click and LESS THAN A SECOND.
I made this open source and it kinda blew up. So I'm looking for people to help me maintain this and build it further for more use cases like iOS Simulator logs, AWS Cloud Console logs and even extend the support to other open source IDEs like Cline, Aider, etc.
I'm also open to any feedback and suggestions you have for me. So feel free to comment here, or ping me on the discord given on the github repo
Hope it makes your vibe coding flow even easier and hassle-free :D
---
## 8. ```
Vibe Coding vs Vibe Engineering
``` {#8-```
vibe-coding-vs-vibe-engineering
```}
這篇短文的討論主題可以總結為:
1. **對「氛圍工程/編程」(vibe engineering/coding)的調侃與批判**
作者以諷刺語氣表達對這種概念(可能指過度強調主觀感受而非實質技術的開發方式)的不以為然,認為其荒謬性「沒有最糟只有更糟」。
2. **概念界定的模糊性**
後續回應「算是...但也不完全是」(Sort of... But not really.)暗示「氛圍工程」的定義難以明確釐清,可能涉及主觀解讀或爭議性,強化了前文對其不嚴謹性的質疑。
整體而言,核心在於**嘲諷技術領域中過於抽象或缺乏實質內容的流行術語**,並反映對專業術語被濫用的不滿。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqpu4x/vibe_coding_vs_vibe_engineering/](https://reddit.com/r/ChatGPTCoding/comments/1jqpu4x/vibe_coding_vs_vibe_engineering/)
- **外部連結**: [https://i.redd.it/vw0d41sbvnse1.png](https://i.redd.it/vw0d41sbvnse1.png)
- **發布時間**: 2025-04-04 02:16:45
### 內容
vibe engineering
just like when i thought vibe coding couldnt get any worse
Sort of... But not really.
---
## 9. ```
Hot take
``` {#9-```
hot-take
```}
這篇文章的核心討論主題是:**對AI編程工具(如LLMs)的抵制與適應的必要性**。
作者指出,當前許多人對依賴AI輔助編碼的開發者(如「vibe coders」)抱有敵意,但強調AI技術進步迅速,未來將大幅改變編程生態。他呼籲專業開發者應接受趨勢、學習使用AI工具,而非抗拒變革(以黑莓拒絕觸控螢幕為反面教材),否則可能被淘汰。
關鍵論點包括:
1. **技術進步的必然性**:AI編程能力將在3-4年內顯著提升,現有問題會逐漸消失。
2. **適應而非抵制**:傳統學習路徑(如四年學位)雖有價值,但拒絕AI輔助可能導致競爭力下降。
3. **歷史教訓**:引用黑莓因抗拒觸控技術而沒落的案例,強調擁抱變革的重要性。
整體而言,文章聚焦於「AI時代下開發者心態轉變的迫切性」。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqk4c3/hot_take/](https://reddit.com/r/ChatGPTCoding/comments/1jqk4c3/hot_take/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqk4c3/hot_take/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqk4c3/hot_take/)
- **發布時間**: 2025-04-03 22:36:53
### 內容
I love development and am a developer myself but. The amount of hate for vibe coders , people who use LLMs to code is crazy.
Yeah its not there yet. 3-4 years from now AI is going to be in a completely different ballgame the issues that exist now wont later.
Yes you went to school for 4 years and spent years learning a skill and now AI can do it better than you, the sooner you accept it and learn to use it the better it will be.
Dont be like blackberry who refused to adopt to the touch screen.. move forward.
---
## 10. M/L Science applied to prompt engineering for coding assistan``` \{#10-m-l-science-applied-to-prompt-engineering-for-c}
這篇文章的核心討論主題是作者提出的一種創新的「元認知工作流程架構」(Engineered Meta-Cognitive Workflow Architecture),旨在透過結構化的提示工程(prompt engineering)技術,提升人工智慧模型的決策與問題解決能力。以下是主要重點:
1. **技術突破**:
- 作者聲稱開發出一種革命性的提示框架,結合「美人魚流程圖」(mermaid flowgraph)和「克萊恩記憶銀行」(Cline Memory Bank)等概念,強化AI的推理與記憶機制。
- 方法論融合了蒙特卡羅樹搜索(Monte Carlo Tree Search)、馬可夫決策過程(Markov Decision Processes)和強化學習(Reinforcement Learning)等理論。
2. **框架機制**:
- 提出7項核心技術,包括:顯式樹搜索模擬、嵌套評估循環、記憶引用系統、漸進式複雜化、元認知提示、量化反饋循環,以及時間約束探索。
- 目標是讓AI模擬人類的決策過程,通過多輪評估與修正來優化輸出。
3. **開源與理念**:
- 作者以Apache 2.0許可釋出框架,強調技術民主化,認為AI工具的普及比商業利益更重要。
- 呼籲尊重知識產權,要求使用者標註來源,並開放合作諮詢。
4. **個人動機**:
- 自述非學術背景出身,但透過自學突破,希望幫助類似處境的人利用AI改變生活。
- 文中帶有挑釁語氣,預期會引發質疑,但鼓勵批評者將精力投入建設性工作。
總結:文章核心在於介紹一種結合認知科學與強化學習的AI提示框架,並透過開源分享推動技術平等化,同時反映作者對學術門檻與知識壟斷的批判。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqia0f/ml_science_applied_to_prompt_engineering_for/](https://reddit.com/r/ChatGPTCoding/comments/1jqia0f/ml_science_applied_to_prompt_engineering_for/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqia0f/ml_science_applied_to_prompt_engineering_for/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqia0f/ml_science_applied_to_prompt_engineering_for/)
- **發布時間**: 2025-04-03 21:20:56
### 內容
I wanted to take a moment this morning and really soak your brain with the details.
https://entrepeneur4lyf.github.io/engineered-meta-cognitive-workflow-architecture/
Recently, I made an amazing breakthrough that I feel revolutionizes prompt engineering. I have used every search and research method that I could find and have not encountered anything similar. If you are aware of it's existence, I would love to see it.
Nick Baumann @ Cline deserves much credit after he discovered that the models could be prompted to follow a mermaid flowgraph diagram. He used that discovery to create the "Cline Memory Bank" prompt that set me on this path.
Previously, I had developed a set of 6 prompt frameworks that were part of what I refer to as Structured Decision Optimization and I developed them to for a tool I am developing called Prompt Daemon and would be used by a council of diverse agen``` - say 3 differently trained models - to develop an environment where the models could outperform their training.
There has been a lot of research applied to this type of concept. In fact, much of these ideas stem from Monte Carlo Tree Search which uses Upper Context Bounds to refine decisions by using a Reward/Penalty evaluation and "pruning" to remove invalid decision trees. [see the poster]. This method was used in AlphaZero to teach it how to win games.
In the case of my prompt framework, this concept is applied with what is referred to as Markov Decision Processes - which are the basis for Reinforcement Learning. This is the absolute dumb beauty of combining Nick's memory system BECAUSE it provides a project level microcosm for the coding model to exploit these concep perfectly and has the added benefit of applying a few more of these amazing concep like Temporal Difference Learning or continual learning to solve a complex coding problem.
Here is a synopsis of it's mechanisms -
-
Explicit Tree Search Simulation: Have the AI explicitly map out decision trees within the response, showing branches it explores and prunes.
-
Nested Evaluation Cycles: Create a prompt structure where the AI must propose, evaluate, refine, and re-evaluate solutions in multiple passes.
-
Memory Mechanism: Include a system where previous problem-solving attemp``` are referenced to build experience over multiple interactions.
-
Progressive Complexity: Start with simpler problems and gradually increase complexity, allowing the framework to demonstrate improved performance.
-
Meta-Cognition Prompting: Require the AI to explain i
reasoning about ireasoning, creating a higher-order evaluation process. -
Quantified Feedback Loop: Use numerical scoring consistently to create a clear reward signal the model can optimize toward.
-
Time-Boxed Exploration: Allocate specific compute budget for exploration vs. exploitation phases.
Yes, I should probably write a paper and submit it to Arxiv for peer review. I may have been able to hold it close and developed a tool to make the rest of these tools catch up.
Deepseek probably could have stayed closed source... but they didn't. Why? Isn't profit everything?
No, says I... Furtherance of the effectiveness of the tools in general to democratize the power of what artificial intelligence means for us all is of more value to me. I'll make money with this, I am certain. (my wife said it better be sooner than later). However, I have no formal education. I am the epitome of the type of person in rural farmland or a someone who's family had no means to send to university that could benefit from a tool that could help them change their life. The value of that is more important because the universe pays it's deb``` like a Lannister and I have been the beneficiary before and will be again.
There are many like me who were born with natural intelligence, eidetic memory or neuro-atypical understanding of the world around them since a young age. I see you and this is my gift to you.
My framework is released under an Apache 2.0 license because there are cowards who steal the ideas of others. I am not the one. Don't do it. Give me accreditation. What did it cost you?
I am available for consultation or assistance. Send me a DM and I will reply. Have the day you deserve! :)
***
Since this is Reddit and I have been a Redditor for more than 15 years, I fully expect that some will read this and be offended that I am making claims... any claim... claims offend those who can't make claims. So, go on... flame on, sir or madame. Maybe, just maybe, that energy could be used for an endeavor such as this rather than wasting your life as a non-claiming hater. Get at me. lol.
---
## 11. ```
Oops, at least it works...
``` {#11-```
oops-at-least-it-works-
```}
這則簡短對話的核心討論主題是「程式碼審查(code review)中的溝通問題」。
具體而言,它反映了以下幾點:
1. **非技術人員(如專案經理 PM)參與技術討論的困難**:PM 在檢視程式碼時因缺乏相關背景知識而無法理解內容,導致溝通斷層。
2. **技術與非技術角色間的隔閡**:開發者與非技術人員(如管理者)在協作時可能因專業術語或複雜邏輯而產生理解落差。
3. **幽默或諷刺的表達方式**:透過簡短對話凸顯現實中常見的職場情境,並以幽默形式引發共鳴。
整體而言,內容聚焦於「跨職能協作中的溝通挑戰」,尤其是技術與非技術角色之間的互動障礙。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqi87s/oops_at_least_it_works/](https://reddit.com/r/ChatGPTCoding/comments/1jqi87s/oops_at_least_it_works/)
- **外部連結**: [https://i.redd.it/tl6zpq37emse1.png](https://i.redd.it/tl6zpq37emse1.png)
- **發布時間**: 2025-04-03 21:18:44
### 內容
>PM looking at my code
You lost me there
---
## 12. ```
Has anyone tried Exponent?
``` {#12-```
has-anyone-tried-exponent-
```}
這段文字的核心討論主題是:
**「作者分享對某款新工具的初步使用體驗,並詢問其他人是否有類似經驗」**
具體要點包括:
1. **工具初體驗**:作者提及剛接觸這款新工具,適應其用戶界面(UX)後順利完成任務(為股票交易專案添加功能)。
2. **徵求社群反饋**:詢問其他人是否也用過該工具,暗示希望交流使用心得或建議。
3. **未來應用意向**:表達後續計劃嘗試用該工具處理其他任務。
整體圍繞「個人使用經驗分享」與「社群互動討論」展開。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jq3z88/has_anyone_tried_exponent/](https://reddit.com/r/ChatGPTCoding/comments/1jq3z88/has_anyone_tried_exponent/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jq3z88/has_anyone_tried_exponent/](https://www.reddit.com/r/ChatGPTCoding/comments/1jq3z88/has_anyone_tried_exponent/)
- **發布時間**: 2025-04-03 08:04:38
### 內容
I saw this tool launched today and Ive been trying it out, wondering if anyone else has.
The UX was a bit new at first but I got used to it and ended up adding a new feature to a stock trading side project of mine pretty smoothly. Im going to try using it for a few other things later. Has anyone else used it?
---
## 13. ```
Any idea to work around claude ai free plan limitations?
``` {#13-```
any-idea-to-work-around-claude-ai-free-plan}
這段文字的核心討論主題是:
**「如何在免費方案達到使用限制後,繼續有效發送訊息或提高免費方案的使用效率」**
具體要點包括:
1. **免費方案限制的困擾**:用戶因超出免費額度需等待(如4小時),影響使用。
2. **尋求解決方案**:
- 是否有「替代方法」(workaround)在超限後繼續發送訊息。
- 如何更高效地利用免費方案(如優化使用方式)。
3. **請求經驗分享**:希望他人提供實際應對類似情況的建議。
整體聚焦於「資源有限下的成本節省與功能延續」策略。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqbci3/any_idea_to_work_around_claude_ai_free_plan/](https://reddit.com/r/ChatGPTCoding/comments/1jqbci3/any_idea_to_work_around_claude_ai_free_plan/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqbci3/any_idea_to_work_around_claude_ai_free_plan/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqbci3/any_idea_to_work_around_claude_ai_free_plan/)
- **發布時間**: 2025-04-03 14:33:43
### 內容
I like to use it but still can not afford to upgrade, so is there any idea or a work around to be able to post a new message after the free plan exceeded the limi```? or any idea how to handle using free plan efficiently? it end very soon and i have to wait about 4 hours to be able to post. so please, if any ideas that would be much appreciated from your experience with these situation.
---
## 14. ```
Screw Coding Assessmen``` - Follow up: I wrote a free program that will solve code assessment challenges for job interviews
``` {#14-```
screw-coding-assessmen```-follow-up-i-wrote}
這篇文章的核心討論主題是:
**作者開發了一個基於Python的免費工具(透過OpenAI API),旨在「隱蔽地」自動解決程式測驗平台(如HackerRank、LeetCode)的題目,並公開釋出程式碼,同時聲明不承擔使用者因此可能面臨的風險責任。**
重點摘要:
1. **工具功能**:自動化破解技術面試中的線上程式測驗,強調「不被瀏覽器偵測」的隱蔽性。
2. **技術基礎**:使用Python與OpenAI API,需使用者自行提供API金鑰。
3. **免責聲明**:明確指出使用者若因工具被發現而受罰,作者不負責任。
4. **動機與爭議**:挑戰程式測驗的篩選機制,可能涉及學術或招聘倫理問題。
(附註:原文連結因格式問題無法完整呈現,但主要資訊已涵蓋。)
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jq7wc4/screw_coding_assessments_follow_up_i_wrote_a_free/](https://reddit.com/r/ChatGPTCoding/comments/1jq7wc4/screw_coding_assessments_follow_up_i_wrote_a_free/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jq7wc4/screw_coding_assessments_follow_up_i_wrote_a_free/](https://www.reddit.com/r/ChatGPTCoding/comments/1jq7wc4/screw_coding_assessments_follow_up_i_wrote_a_free/)
- **發布時間**: 2025-04-03 11:14:40
### 內容
So a few days ago I made a post on here (https://www.reddit.com/r/ChatGPTCoding/commen```/1jonjwg/im_writing_a_free_program_that_will_silently/utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)
about a program I was going to write to solve code assessment challenges in a stealthy can't-be-seen-by-the-browser way. I have done so and have released the first version of this code for free. It's written in python and will solve code assessment (hacker rank, leetcode) assessment questions for you. You just need an openAI API key.
Link to the github: [https://github.com/programmingTomato/ScrewCodingAssessmen](`https`://github.com/programmingTomato/ScrewCodingAssessmen)
Also, just to be clear, if you use this program and get caught I am not responsible for any punishmen``` you incur. Have fun and code responsibly!
---
## 15. ```
Kerricks Wager: on the Future of Manual Programming
``` {#15-```
kerricks-wager-on-the-future-of-manual-prog}
Kerrick's Wager 的核心討論主題是對「人工智慧風險」的理性評估與應對策略的哲學性探討,尤其是針對「存在級風險」(existential risk, x-risk)的爭議。文章借鑒「帕斯卡的賭注」(Pascal's Wager)的邏輯框架,提出以下關鍵論點:
1. **AI風險的賭注性質**:
作者認為,即使對AI毀滅人類的可能性(如1%)存在分歧,忽略這種風險的代價(人類滅絕)遠高於防範成本,因此理性選擇應傾向於積極預防(類似帕斯卡賭注中「信神」的邏輯)。
2. **反駁常見質疑**:
- 針對「AI風險論是科幻臆測」,作者指出歷史上新技術(如核武)的威脅也曾被低估,且AI的潛在能力(如自主決策)可能超越人類控制。
- 針對「防範措施阻礙進步」,主張可兼顧安全與發展(如「減緩研發」不等於停止創新)。
3. **行動建議**:
呼籲支持AI安全研究、政策監管與技術減緩(如延後超級AI的開發),並強調現階段投入預防的「成本效益比」極高。
4. **哲學延伸**:
討論「不確定性下的決策理論」,認為在無法精確量化風險時,保守策略(precautionary principle)更具合理性。
總結:文章核心是通過風險評估的邏輯論證,主張社會應嚴肅看待AI的潛在威脅,並採取預防性行動,即使其發生概率存在爭議。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jq4qor/kerricks_wager_on_the_future_of_manual_programming/](https://reddit.com/r/ChatGPTCoding/comments/1jq4qor/kerricks_wager_on_the_future_of_manual_programming/)
- **外部連結**: [https://kerrick.blog/articles/2025/kerricks-wager/](https://kerrick.blog/articles/2025/kerricks-wager/)
- **發布時間**: 2025-04-03 08:41:04
### 內容
連結: [https://kerrick.blog/articles/2025/kerricks-wager/](https://kerrick.blog/articles/2025/kerricks-wager/)
---
## 16. ```
Have you ever been asked about debugging or troubleshooting in a coding interview?
``` {#16-```
have-you-ever-been-asked-about-debugging-or}
由於我無法直接訪問 YouTube 影片內容,因此無法總結該影片的核心討論主題。不過,您可以提供影片的標題、描述或關鍵內容點,我可以根據這些信息幫助您分析並總結其核心主題。
如果您能分享影片的標題或簡要描述,我可以協助您歸納重點!
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jq0b0p/have_you_ever_been_asked_about_debugging_or/](https://reddit.com/r/ChatGPTCoding/comments/1jq0b0p/have_you_ever_been_asked_about_debugging_or/)
- **外部連結**: [https://www.youtube.com/watch?v=A_fOHpBqj50&t=923s](https://www.youtube.com/watch?v=A_fOHpBqj50&t=923s)
- **發布時間**: 2025-04-03 05:25:04
### 內容
連結: [https://www.youtube.com/watch?v=A_fOHpBqj50&t=923s](https://www.youtube.com/watch?v=A_fOHpBqj50&t=923s)
---
## 17. ```
Anyone try SourceGraph Cody?
``` {#17-```
anyone-try-sourcegraph-cody-
```}
這段文字的核心討論主題是:
**「某個在企業領域中具有重要地位('big player')但社交媒體上討論度較低的技術或產品,以及使用者對其實際體驗的詢問,同時提及該技術/產品具備與 Microsoft Certified Professional (MCP) 的整合功能。」**
具體可歸納為以下三點:
1. **企業級技術的低調性**:該技術/產品在企業環境中影響力大,但缺乏社交媒體的公開討論。
2. **使用者經驗分享**:發文者希望了解其他人的實際使用體驗或評價。
3. **技術整合特性**:特別提到與 MCP(可能指微軟認證或相關技術)的兼容性或功能整合。
可能的討論方向包括:該技術的市場定位、為何社交媒體聲量低、MCP整合的實際應用價值等。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqmk37/anyone_try_sourcegraph_cody/](https://reddit.com/r/ChatGPTCoding/comments/1jqmk37/anyone_try_sourcegraph_cody/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqmk37/anyone_try_sourcegraph_cody/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqmk37/anyone_try_sourcegraph_cody/)
- **發布時間**: 2025-04-04 00:11:51
### 內容
This appears to be a "big player" in enterprise but hardly hear anything about it on social media. any experiences?
Has MCP integration too
---
## 18. ```
Where is AI at now: could you code Theme Hospital with beginner knowledge?
``` {#18-```
where-is-ai-at-now-could-you-code-theme-hos}
這篇文章的核心討論主題是:**探討在不同能力層級(新手、中階開發者)和時間限制(一週)下,結合AI工具(如ChatGPT)的輔助,能夠開發出多麼複雜的遊戲**。具體分為三個方向:
1. **AI模型的極限**:當前頂尖AI模型(如GPT)能否「一次性」獨立生成完整遊戲?
2. **新手的潛力**:僅具備基礎AI操作能力的新手,能否在一週內利用AI工具開發出類似《主題公園》《主題醫院》的經典遊戲?
3. **中階開發者的加成**:若具備程式基礎(如軟體工程師),搭配AI輔助,一週內能完成多複雜的專案?
隱含議題包括:
- AI如何降低開發門檻(如教學、生成代碼、除錯)
- 傳統遊戲開發的複雜性(如代碼量、系統設計)與AI當前能力的落差
- 「提示詞技巧」(prompting)對產出品質的影響
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqlj6f/where_is_ai_at_now_could_you_code_theme_hospital/](https://reddit.com/r/ChatGPTCoding/comments/1jqlj6f/where_is_ai_at_now_could_you_code_theme_hospital/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqlj6f/where_is_ai_at_now_could_you_code_theme_hospital/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqlj6f/where_is_ai_at_now_could_you_code_theme_hospital/)
- **發布時間**: 2025-04-03 23:32:05
### 內容
I'm trying to get a sense of how much AI can do without having massive amoun``` of expertise. Considering that with effective prompting, AI can teach the necessary expertise or guide you through how to use it effectively, it seems like a competent, computer and AI literate person can already create some cool stuff.
I have no idea how big the code base is of games I grew up loving. Theme Park and Theme Hospital were two favourites.
Could a game like that be built by a novice with AI competence and a week with chatgpt and whatever add-ons would help?
What in your opinion is the biggest /ost complex game that could be created:
A) in one shot by the leading models today
B) by a novice with a week and resources
C) by an intermediate coder (eg software developer or computer science grad) with a week and resources
Thanks!
---
## 19. ```
complete noob - realistic goal?
``` {#19-```
complete-noob-realistic-goal-
```}
这篇文章的核心讨论主題是:**一位沒有程式設計經驗的非技術背景人士,詢問開發一個危機熱線排班應用程式的可行性與現實性**。
具體重點包括:
1. **開發動機**:希望為團隊建立一個排班系統,以追蹤危機熱線的人員調度。
2. **功能需求**:
- 員工資料庫(角色、技能、可用性)
- 輪班模板(24/7 重複排班)
- 最低人力需求設定
- 休假請求與衝突檢測
- 儀表板與人力不足警示
3. **核心疑問**:
- 以初學者的能力,這樣的專案是否現實?
- 是否過於雄心勃勃而難以實現基本可用的成果?
4. **求助方向**:尋求技術建議,評估自學開發的可行性或替代方案。
整體聚焦於「非技術者能否獨立完成此專案」的可行性探討,並列出初步功能架構供評估。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqkyfp/complete_noob_realistic_goal/](https://reddit.com/r/ChatGPTCoding/comments/1jqkyfp/complete_noob_realistic_goal/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqkyfp/complete_noob_realistic_goal/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqkyfp/complete_noob_realistic_goal/)
- **發布時間**: 2025-04-03 23:09:44
### 內容
Hi all, i have no coding experience and am not particularly tech savy. i really want to build an app to help our team track schedules for a crisis hotline. here's a basic outline i was happy with below. Im willing to dedicate some time trying to learn this, but i want to understand first if whether i'm asking is even realistic or too ambitious to end up with anything remotely competent? Appreciate any help you can offer **Core Features:**
* **Key Componen```:**
* Staff database with roles, skills, and availability
* Shift templates for recurring 24/7 coverage
* Minimum staffing requiremen``` by shift/role
* PTO request system with conflict detection
* Dashboard with staffing aler```
---
## 20. ```
Using flask/python and ChatGPT to ammend functionality
``` {#20-```
using-flask-python-and-chatgpt-to-ammend-fu}
这篇文章的核心討論主題是:
**「如何利用AI輔助開發Python腳本(特別是結合Flask框架)來優化LLM任務,並尋找相關的線上資源或社群以支持此類個人專案。」**
具體要點包括:
1. **個人技術轉變**:從消耗時間在社交媒體/新聞,轉向用Python開發AI輔助的腳本(尤其是過往有Python基礎)。
2. **工具與方法**:
- 使用ChatGPT等LLM執行任務,並透過Python(如Flask框架)提升專案的便攜性。
3. **尋求資源與社群**:
- 詢問是否有現成的線上社群或資源(如教程、開源專案)能協助這類開發需求。
- 不確定當前平台(如發文處)是否為最適合的起點。
整體聚焦於「AI輔助編程」的實踐與社群協作可能性。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqjlty/using_flaskpython_and_chatgpt_to_ammend/](https://reddit.com/r/ChatGPTCoding/comments/1jqjlty/using_flaskpython_and_chatgpt_to_ammend/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqjlty/using_flaskpython_and_chatgpt_to_ammend/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqjlty/using_flaskpython_and_chatgpt_to_ammend/)
- **發布時間**: 2025-04-03 22:16:24
### 內容
I am currently finding myself with time I used to spend on news or social media allocated instead to developing simple python scrip with AI assistance (I used to make basic apps with python myself so I dont purely vibe code) to ammend the LLM tasks I run on ChatGPT and have found Flask is a nice way to make my projec portable. Is there a community effort or set of online resources which might compliment my effor```? Is this the best place to start?
---
## 21. ```
Trying to re-find this application
``` {#21-```
trying-to-re-find-this-application
```}
這段文字的核心討論主題是:
**「尋找一款用於生成程式碼提示(prompt)的桌面應用程式」**
具體重點包括:
1. 作者在尋找一款曾使用過、但忘記名稱的桌面應用程式。
2. 該工具的主要功能是協助生成「程式碼相關的提示」(vibe coding prompts),尤其適用於在 ChatGPT 等環境中輸入提示詞(prompting)。
3. 作者嘗試過使用 Perplexity 等工具搜尋,但未能找到該應用程式的名稱或網站連結。
4. 與類似 Cursor(另一款程式碼工具)的用途不同,這款工具更專注於「提示生成」而非直接編寫程式碼。
問題本質是希望透過社群協助回憶或推薦這款工具的名稱或來源。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqig2j/trying_to_refind_this_application/](https://reddit.com/r/ChatGPTCoding/comments/1jqig2j/trying_to_refind_this_application/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqig2j/trying_to_refind_this_application/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqig2j/trying_to_refind_this_application/)
- **發布時間**: 2025-04-03 21:28:10
### 內容
Trying to re-find this application, I have tried using perplexity and all sor. Basically it was a good desktop application someone made that helped to generate promp for vibe coding. But I cant remember the name of the site or anything. It helped especially for say using prompting inside ChatGPT rather than something like cursor. Does anyone know the app I am talking about? I just cant find the link to it.
---
## 22. ```
Built a tool that secures the code for vibe coders
``` {#22-```
built-a-tool-that-secures-the-code-for-vibe}
这篇文章的核心討論主題是介紹一個專為開發者設計的工具,旨在幫助他們在代碼上線前確保安全性。主要特點包括:
1. **安全性審查**:提供由安全專家進行的人工代碼審查,以識別漏洞並確保代碼安全。
2. **隱私保護**:採用零存儲政策,審計後自動刪除代碼,保障用戶隱私。
3. **解決痛點**:針對開發者因急於上線而可能忽略安全問題的情況,提供預防性解決方案。
總結:工具的核心價值在於「提升代碼安全性」與「保護隱私」,並強調其在開發流程中的實用性。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqi64a/built_a_tool_that_secures_the_code_for_vibe_coders/](https://reddit.com/r/ChatGPTCoding/comments/1jqi64a/built_a_tool_that_secures_the_code_for_vibe_coders/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqi64a/built_a_tool_that_secures_the_code_for_vibe_coders/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqi64a/built_a_tool_that_secures_the_code_for_vibe_coders/)
- **發布時間**: 2025-04-03 21:16:13
### 內容
We recently built atooldesigned to help developers secure their code before it goes live. We know that rushing to launch can lead to security oversigh```.
It offers manual code reviews by security exper``` that spot vulnerabilities and ensuring your code is safe. Plus, with our zero-storage policy, your code is auto-deleted after the audit for complete privacy.
Hopefully you guys will find it useful
---
## 23. ```
Debugging browser apps in the terminal with AI
``` {#23-```
debugging-browser-apps-in-the-terminal-with}
這篇文章的核心討論主題是:
**「Plandex v2 開源 AI 編程工具的更新與新功能介紹」**,具體內容包括:
1. **版本修復與穩定性提升**:解決初期發布後的錯誤(如模型問題),並呼籲用戶重新嘗試。
2. **新增功能亮點**:
- **自動調試瀏覽器應用**:透過 Chrome 直接將控制台日誌和錯誤轉發至終端,簡化調試流程(無需配置)。
3. **其他更新**:新增內建模型(model packs)與功能改進。
4. **社群互動**:邀請用戶反饋意見或提問。
整體聚焦於工具迭代後的改進與實用性增強,尤其強調對開發者效率的提升。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqh5r5/debugging_browser_apps_in_the_terminal_with_ai/](https://reddit.com/r/ChatGPTCoding/comments/1jqh5r5/debugging_browser_apps_in_the_terminal_with_ai/)
- **外部連結**: [https://youtu.be/VCegxOCAPq0](https://youtu.be/VCegxOCAPq0)
- **發布時間**: 2025-04-03 20:30:26
### 內容
Hey all,
Its been a couple weeks since I launched Plandex v2 in this sub: [https://www.reddit.com/r/ChatGPTCoding/commen/1jgmbsa/plandex\_v2\_an\_open\_source\_ai\_coding\_agent\_with/](`https`://www.reddit.com/r/ChatGPTCoding/commen/1jgmbsa/plandex_v2_an_open_source_ai_coding_agent_with/)
Since then, most importantly, a lot of bugs have been squashed. If you just so happened to have tried the v2 right after launch and ran into model errors or other issues, those are most likely fixed now, so give it another shot!
While the main focus has been on fixes and reliability, there are also new features and some new built-in models and model packs.
Feature-wise, I think the coolest one is a new ability to automatically debug browser applications. When launching browser apps, Plandex can now do so in a way that forwards console logs and errors to the terminal so they can be used in debugging. This feature requires Chrome, but other than that, no configuration is neededit just works.
Please me know if you have any though``` or questions!
---
## 24. ```
A few questions
``` {#24-```
a-few-questions
```}
這篇文章的核心討論主題是:
**「開發者對使用AI生成代碼的疑慮與實用性探討」**,具體分為兩點:
1. **AI生成代碼的操作方式與真實性**
- 作者質疑所見範例(如輸入「紅色方塊」即生成對應代碼)是否真實可行,反映對AI工具實際能力的好奇與不熟悉。
2. **AI輔助編程的動機與價值爭議**
- 作者肯定AI在「優化現有代碼」(如SQL查詢效率分析)的教學意義,但質疑完全依賴AI生成代碼的動機,認為親手編寫才是開發樂趣所在。
整體聚焦於開發者對AI工具「輔助學習」與「取代手動編碼」之間的界線思考。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jpxrd6/a_few_questions/](https://reddit.com/r/ChatGPTCoding/comments/1jpxrd6/a_few_questions/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jpxrd6/a_few_questions/](https://www.reddit.com/r/ChatGPTCoding/comments/1jpxrd6/a_few_questions/)
- **發布時間**: 2025-04-03 03:41:12
### 內容
Hello,
I have a few questions. First of all Im a software developer and I have never used AI to write code. I actually didnt know it was a thing until recently. I am not interested in using AI to write code because my favorite part of my job is writing code. but here are my questions:
-
How do you write code using AI? I saw something on Twitter where someone was just typing in promp``` like a red square and it would generate the code and a red square would appear on the screen. I couldnt tell if this was real or a joke. Is this real?
-
Why do people want to do this instead of actually writing code? I used ChatGPT one time because someone said that an sql query would be inefficient (it was someone elses code), and I was curious about how one would go about making it more efficient, so I typed into ChatGPT what is an alternate way to write this code? And I pasted the code. It showed me an alternate way and explained what the difference was, how performance would be affected, etc. i was actually able to learn a lot from it. But at least in that case I already had the code, I was just asking for assistance in how to write it in a more efficient way. I feel like thats different than just talking to an AI and having it create code for you.
---
## 25. ```
Which models are you using most right now? Which models do you find are the best overall and which do you find to strike the best balance of cost, ability, and speed?
``` {#25-```
which-models-are-you-using-most-right-now-w}
該句的核心討論主題是關於**根據任務難度選擇不同模型的使用策略**。具體探討是否在處理簡單任務時使用某些模型,而在面對更複雜任務時切換到其他模型,以實現效率或性能的最佳化。這可能涉及模型資源分配、成本效益考量,或針對不同任務特性選擇合適的技術方案。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jq7zh0/which_models_are_you_using_most_right_now_which/](https://reddit.com/r/ChatGPTCoding/comments/1jq7zh0/which_models_are_you_using_most_right_now_which/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jq7zh0/which_models_are_you_using_most_right_now_which/](https://www.reddit.com/r/ChatGPTCoding/comments/1jq7zh0/which_models_are_you_using_most_right_now_which/)
- **發布時間**: 2025-04-03 11:19:15
### 內容
Also, do you use some models for easier tasks, and move to others for more difficult tasks?
---
## 26. ```
Augment Agent is live today. Unlimited usage?
``` {#26-```
augment-agent-is-live-today-unlimited-usage}
這些討論的核心主題是對某個月費30美元的服務或產品(可能是AI代理或工具)的負面評價和批評。用戶們普遍認為該產品不值得這個價格,批評其功能不足(如「very dumb」)、性價比低(與其他更便宜的選項如GH、deepseek、open router相比),並且存在技術限制(如無法處理超過25萬個文件的代碼庫)。整體討論圍繞著對該產品的高定價與低性能之間的不滿。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jq2c88/augment_agent_is_live_today_unlimited_usage/](https://reddit.com/r/ChatGPTCoding/comments/1jq2c88/augment_agent_is_live_today_unlimited_usage/)
- **外部連結**: [http://augmentcode.com/](http://augmentcode.com/)
- **發布時間**: 2025-04-03 06:50:30
### 內容
Yet another agent. 30 bucks a month vs 10 bucks from GH? Or even better, less with deepseek and open router? Yeah right, no thanks
CUSTOMER: Is this the right room for an argument?
MR. BARNARD: Ive told you once.
used it for a while, it's not worth 30 bucks, it's very dumb
For 30 bucks i``` unlimited for now. If codebase has more than 250k files it refuses to open.
Tried it today, dumb it isz
---
## 27. ```
Vibe coding from my phone?
``` {#27-```
vibe-coding-from-my-phone-
```}
這段文字的核心討論主題是:
**「如何方便地在手機上遠端監控伺服器端程式執行的 console logs 和聊天訊息,而不需使用複雜的遠端桌面方案(如 RDP/VNC),並尋求替代工具或方法(不限於現有技術 windsurf)。」**
具體要點包括:
1. 當前使用 `windsurf` 進行開發,但需要更便捷的手機端監控方式。
2. 希望直接查看 `console logs` 和 `chat` 訊息,而非透過遠端桌面連線。
3. 開放替代方案建議(不限定現有工具)。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jq0nht/vibe_coding_from_my_phone/](https://reddit.com/r/ChatGPTCoding/comments/1jq0nht/vibe_coding_from_my_phone/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jq0nht/vibe_coding_from_my_phone/](https://www.reddit.com/r/ChatGPTCoding/comments/1jq0nht/vibe_coding_from_my_phone/)
- **發布時間**: 2025-04-03 05:39:09
### 內容
I've been working on a POC with windsurf and it's been going great, but I often fire and forget reques and come back to them later, check the resul and steer in the right direction.
I often don't need to look at the code for this now that I know the structure, I just need the console logs and the chat, is there a way I can get that on my phone easily? It's running on a server I can connect to from anywhere, so I could potentially rdp/vnc into the machine, but that's not ideal on a phone.
I'm not tied to windsurf so any alternatives that achieve the same would be great too.
---
## 28. ```
Agentic coding with tools like Aider, Cline, Claude Code, etc. is a waste
``` {#28-```
agentic-coding-with-tools-like-aider-cline-}
這篇文章的核心討論主題是:**「使用AI編程代理工具(如Claude Code)與手動提供精確上下文的方法相比,在成本、速度和代碼質量上的劣勢」**。
具體要點包括:
1. **成本效益**:AI代理工具(如Claude Code)因冗長的系統提示、文件讀取等額外操作,導致API費用高昂(範例中貴5倍)。
2. **效率問題**:代理工具處理速度較慢,因涉及不必要的上下文分析、工具切換等開銷。
3. **質量疑慮**:過多無關的上下文可能分散模型注意力,降低輸出代碼的準確性。
4. **現階段建議**:作者認為,目前手動篩選並提供精確上下文(如直接貼入相關代碼片段)是更經濟、快速且可靠的方式,而代理工具可能待未來模型成本降低後才更具實用性。
總結:文章批判性地比較了兩種AI輔助編程方法,主張現階段「精簡人工提示」優於「全自動代理工具」。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqoagl/agentic_coding_with_tools_like_aider_cline_claude/](https://reddit.com/r/ChatGPTCoding/comments/1jqoagl/agentic_coding_with_tools_like_aider_cline_claude/)
- **外部連結**: [https://www.reddit.com/r/ChatGPTCoding/comments/1jqoagl/agentic_coding_with_tools_like_aider_cline_claude/](https://www.reddit.com/r/ChatGPTCoding/comments/1jqoagl/agentic_coding_with_tools_like_aider_cline_claude/)
- **發布時間**: 2025-04-04 01:18:33
### 內容
Using an agent like Cline, Aider, Claude Code, etc. to code is:
-
Significantly more expensive (if you are paying for API use)
-
Slower
-
Worse quality
For comparison I tried to add a small feature to my codebase using two methods using Claude Sonnet 3.7:
Method 1: I use a script that le me quickly select relevant files from my codebase for a given task and copies their conten to the clipboard along with a directory tree. I pasted this into a conversation and gave it a task. It returned the code changes and I pasted them into vscode. Total cost: $0.05
Method 2: I open Claude Code in my code folder and ask it to add the same feature. It does i``` thing, churns for while, and makes the needed changes. Total cost: $0.28
Both methods were able to get the correct answer in a single shot, but Claude Code cost over 5x as much while being slower. This really adds up when you are working with these tools all day long.
Agentic coders add a ton of overhead with lengthy system promp```, back and forth tool use, reading unnecessary files, writing summaries of what it did, etc. Mostly all these extra tokens are spent doing what is actually the easy part for a human to do: identifying the relevant context. Less than 1/5 of the tokens are actually spent writing code.
Based on the premise that the more focused your prompt, the better the output will be, all these extra tokens also have the potential of confusing the model and reducing the overall quality of the final output.
In the future when models are amazing and cost basically nothing I could see myself opting for the agentic approach more often. Right now I'm not saying these tools don't have a place, but for day to day coding I find manually prompting the model with just the right context to be quicker, cheaper, and more accurate.
---
## 29. ```
I'll sell it for 1,000 bucks.
``` {#29-```
i-ll-sell-it-for-1-000-bucks-
```}
這三則討論的核心主題圍繞以下幾點:
1. **對產品「Manos Pro」的價值質疑**
第一則留言重複提及購買選項,可能暗示推銷意圖過於明顯;第二則直接批評該產品在擁有ChatGPT Plus的情況下「不值5美元」,並提到等待名單的取得門檻極低(10分鐘),反問他人是否真需費力取得,顯示對產品實際價值的懷疑。
2. **用戶體驗與市場反應的落差**
第二則留言進一步質疑市場需求(「人們真的難取得邀請嗎?」),暗示官方宣傳與實際用戶體驗存在矛盾。第三則以嘲諷語氣(「哈哈…才不!」)強化對產品的不認同,反映部分用戶的負面評價。
3. **與競爭產品(ChatGPT Plus)的比較**
批評者將Manos Pro與ChatGPT Plus對比,認為前者功能或性價比不足,凸顯用戶在相似工具中的選擇傾向。
**總結**:討論聚焦於Manos Pro的市場定位問題,包括其定價合理性、獲取難易度與實際價值的爭議,並透過與競品的比較,質疑其吸引力。整體氛圍偏向負面,反映用戶對產品的不滿或失望。
- **Reddit 連結**: [https://reddit.com/r/ChatGPTCoding/comments/1jqqc2e/ill_sell_it_for_1000_bucks/](https://reddit.com/r/ChatGPTCoding/comments/1jqqc2e/ill_sell_it_for_1000_bucks/)
- **外部連結**: [https://i.redd.it/5fib51q6znse1.png](https://i.redd.it/5fib51q6znse1.png)
- **發布時間**: 2025-04-04 02:35:29
### 內容
What?
\> the second offer is for you to buy the Manos Pro for yourself, and the third offer is for you to buy the Manos Pro for yourself
Manus isn't worth $5 at this point if you have ChatGPT plus. Also I got my invite 10 minutes after joining the waitlist. Are people having trouble getting it?
HAHAHAHAH.... NO!
---
# 總體討論重點
以下是29篇文章的摘要與重點條列整理,並附上對應的錨點連結:
---
### #1 [hot take: Vibe Coding will be dead before most people understand](#anchor_id_1)
1. **AI在軟體開發中的局限性**
- AI(如LLM)創造的價值有限,技術能力仍是關鍵。
2. **軟體工程師的不可替代性**
- 工程師在核心問題上仍具經濟可靠性,AI生成代碼無法取代主導地位。
3. **編程的本質是解決問題**
- 重點在解決問題能力,而非單純代碼生成。
---
### #2 [slurp-ai: Tool for scraping and consolidating documentation websites into a single MD file.](#anchor_id_2)
1. **工具功能**
- 將文檔網站轉為Markdown,提升LLM回應質量。
2. **與Cursor Pro比較**
- 探討是否為更優的開源替代方案。
3. **實際應用測試**
- 詢問兼容性(如ArcGIS Pro文檔)。
---
### #3 [RA.Aid Update: Claude 3.7, Gemini 2.5 Pro, Custom Tools, Ollama & More!](#anchor_id_3)
1. **功能擴展**
- 支援Claude 3.7、Gemini 2.5 Pro等模型,整合Ollama。
2. **開發者體驗**
- 新增API文件、成本監控工具。
3. **開源精神**
- 鼓勵社群貢獻(Apache 2.0授權)。
---
### #4 [Gemini 2.5 Pro saving me from duplication hell](#anchor_id_4)
- **簡短口號**:傳達「英雄精神不朽」的激勵性概念。
---
### #5 [Like fr](#anchor_id_5)
1. **自然語言提示的局限**
- 結構化符號化(symboling)更高效。
2. **諷刺技術演進**
- 未來可能將既有技巧當作新發現。
---
### #6 [Best AI tools to analyze full codebase](#anchor_id_6)
- **需求背景**:尋求優化NodeJS/Express遊戲專案的AI工具推薦(如GitHub Copilot)。
---
### #7 [Vibe coding creates a mess, but it can be solved faster](#anchor_id_7)
1. **AI編程痛點**
- 無限除錯循環耗時。
2. **解決方案**
- 開源工具「Composer Web」自動收集日誌、截圖。
3. **社群協作**
- 計劃擴展支援iOS模擬器、AWS日誌。
---
### #8 [Vibe Coding vs Vibe Engineering](#anchor_id_8)
- **批判流行術語**:嘲諷「氛圍工程」定義模糊且缺乏實質內容。
---
### #9 [Hot take](#anchor_id_9)
1. **AI趨勢不可逆**
- 呼籲開發者學習AI工具,避免被淘汰。
2. **歷史教訓**
- 引用黑莓抗拒觸控技術的失敗案例。
---
### #10 [M/L Science applied to prompt engineering for coding assistan](#anchor_id_10)
1. **元認知架構**
- 結合流程圖與記憶銀行提升AI決策能力。
2. **開源理念**
- Apache 2.0授權,強調技術民主化。
---
### #11 [Oops, at least it works...](#anchor_id_11)
- **溝通問題**:非技術人員(如PM)因缺乏背景知識無法理解代碼。
---
### #12 [Has anyone tried Exponent?](#anchor_id_12)
- **工具初體驗**:詢問社群對新工具的使用反饋。
---
### #13 [Any idea to work around claude ai free plan limitations?](#anchor_id_13)
- **免費方案限制**:尋求超額後繼續使用的方法。
---
### #14 [Screw Coding Assessmen](#anchor_id_14)
1. **工具功能**
- 自動破解HackerRank等平台題目。
2. **免責聲明**
- 不承擔使用者風險。
---
### #15 [Kerricks Wager: on the Future of Manual Programming](#anchor_id_15)
1. **AI風險賭注**
- 主張預防AI潛在威脅(即使機率低)。
2. **反駁質疑**
- 對比