(评论)
(comments)

原始链接: https://news.ycombinator.com/item?id=43687767

这个Hacker News帖子讨论了“氛围编程”(vibe coding),即使用Copilot和ChatGPT之类的LLM进行软件开发。 commandersaki认为这些工具使缺乏经验的开发者能够创建有用的程序,并举了一个例子,说明“氛围编程”如何快速有效地开发出一个成功的产品。 linsomniac强调了LLM对经验丰富的开发者的潜力,使其能够快速尝试不同的方法(线程、异步、过程式)和功能(日志记录、调试、进度显示),而这些方法通常需要花费大量时间。这促进了探索并改善了设计。 SteveDR对linsomniac的使用方式提出了异议,声称“氛围编程”意味着忽略底层代码,这与普通的LLM辅助开发不同。tjpnz质疑缺乏经验的开发者在这种新的范式中如何获得经验。alchemist1e9认为这些工具最终会提高经验丰富开发者的市场价值,而pfraze则强调了理解程序和产品之间区别的重要性。

相关文章
  • (评论) 2025-03-30
  • (评论) 2025-03-22
  • (评论) 2025-03-22
  • “氛围编程”的问题 2025-04-15
  • (评论) 2025-04-05

  • 原文
    Hacker News new | past | comments | ask | show | jobs | submit login
    The Problem with "Vibe Coding" (dylanbeattie.net)
    17 points by jmmv 3 hours ago | hide | past | favorite | 6 comments










    One of the genuinely positive things about tools like Copilot and ChatGPT is that they empower people with minimal development experience to create their own programs. Little programs that do useful things - and that’s awesome. More power to the users.

    I've changed my outlook on vibe coding after seeing the results of this wholesome vibe coding: https://www.youtube.com/watch?v=4pJUXocn7aE .

    This guy didn't just make a small program, he made a product that is attuned to some very stringent requirements. If you gave this project to experienced software developers it would be heavy on process and light on impact, take forever to make, and stupid expensive.



    >they empower people with minimal development experience to create their own programs.

    The author goes out of their way to play up the toy aspect of the LLMs when driven by the inexperienced. No mention is made of them being used by experienced developers, but I get the impression he feels they aren't useful to the experienced.

    I'm just playing with a small client/server tool (rsync but for block devices), and vibe coding allowed me to figure out some rough edges of my design document, and experiment with "what would it look like built with threads? As async code? As procedural?) I would never have done that before because of the sheer amount of time it would take, I'd have picked what I thought was best and then lived with the sunk cost falacy until I had no other choice. It did a pretty good job of catching reasonable exceptions in the communication code which I probably would have just let throw a traceback until I got a bug report. It did a great job of adding logging and debugging options. And I had it take 4 attempts at making a "fancy" --progress display and picked the one I liked the best.

    LLMs give a level of exploration to software development that we haven't seen since the good old days when HP set up several groups to each build their next generation workstation environment, and then picked the best one.

    IMHO, the experienced software developers stand at a unique position to take advantage of these LLMs that far outstrip what an inexperienced developer can do.



    > vibe coding allowed me to figure out some rough edges of my design document, and experiment with "what would it look like built with threads? As async code? As procedural?”

    This doesn’t fall under my understanding of the phrase “vibe coding”. In the tweet from Karpathy which many point to for coining the phrase, he says that when vibe coding you essentially “forget the code exists”. I think it’s distinct from regular ol LLM-assisted development



    How does the inexperienced developer become experienced under said circumstances?


    I agree they may not and that’s very interesting. As an experienced developer myself I’m starting to think these tool’s are likely going to increase our market value not decrease it.


    Honestly just good advice for engineers in general - understand the difference between programs and products






    Join us for AI Startup School this June 16-17 in San Francisco!


    Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact



    Search:
    联系我们 contact @ memedata.com