poteto@poteto

我們得重建、重寫大量軟體，去適應一種全新的、更快的節奏。 以前程式碼是一滴一滴來的。很快（如果現在還沒有的話），程式碼會像一股連續不斷的水流一樣被寫出來，像一條狂暴的河，想怎麼轉就怎麼轉。 這不是什麼新鮮事：大廠早就因為工程團隊規模龐大而不得不面對這個問題。但現在 ai 讓每個工程師手上都有一支彈性極強、能力超強的勞動力。這現在是你的問題了，唯一的適應方法就是進化你的系統，讓 agent——即使是、尤其是那些不太了解正確做法的 agent——也能如魚得水。讓簡單的做法就是正確的做法。 你的程式碼庫正在變成有機建築。agent 的貢獻會圍繞著你設計的限制和護欄生長。好的軟體工程現在更重要了！而且不，這股連續不斷的程式碼流不是你只能無助旁觀的東西。野心大一點，去設計能駕馭混亂的系統、框架和語言。 為寫程式哀悼的時候早就過去了

we will need to rebuild and rewrite much of software to adapt to a new, faster pace. code used to arrive one drop at a time. soon, if not already, code will be written as if it were a continuous stream, like a violent river twisting and turning as it pleases. this is not a new thing: big tech cos have had to deal with this with the enormous scale of their engineering teams. but now ai has brought an incredibly elastic and capable workforce wielded by every engineer. this is your problem now, and the only way to adapt is to evolve your systems so agents - even and especially the ones with little context about the right way of doing things - can thrive. make the easy thing the right thing. your codebase is becoming organic architecture. agent contributions grow around the constraints and guardrails you’ve designed. good software engineering matters even more now! and no, the continuous stream of code is not something you have to watch helplessly. be more ambitious and design systems, frameworks, and languages to control the chaos. the time for mourning coding is long over