one fresh software engineer about AI

回答: AI撞牆時刻,三國殺與代碼的黃昏BayFamily2026-02-03 20:14:14

我的觀點原本是:隻要你真的懂自己在幹什麽,驗證 AI 生成的輸出往往比自己寫代碼更慢、也更容易出錯,因為 AI 的輸出實在太囉嗦了。而如果你本來就不太懂,那用 AI 反而更不靠譜——你基本沒法真正驗證或事實核查它的結果,最多隻能看看代碼能不能跑(說白了就是在“憑感覺寫代碼 / vibe coding”)。

但現在我才意識到,AI 是可以定製成輸出非常不囉嗦的,這樣驗證起來就容易多了。我完全不知道這點,真的有點離譜。畢竟我見過那麽多人抱怨 AI 輸出太花哨、太冗長了 ,你會以為大家早就在討論這個了。

如果一開始需要驗證的內容就更少,那我確實能理解為什麽 AI 會提升生產力了。

 

My argument was that validating output from AI takes longer and is more error-prone than writing code yourself as long as you know what you're doing because output from AI is super verbose. And if you don't know what you're doing, using AI is even less advisable because you can't really validate or fact check it well enough other than just seeing if the code actually runs (you're basically vibe coding at that point). Now, I'm realizing that AI can be customized to have much less verbose output, which makes validation a lot easier. I have no idea why I didn't know about this. You'd think everyone would be talking about this given how many people I've seen complain about AI output being too flowery and verbose . If I can validate output faster thanks to there being less output to verify in the first place, then I can see how AI does improve productivity. 

請您先登陸,再發跟帖!