← 回到動態
poteto@poteto

順帶一提,最近關於軟體工程技能的討論滿多的(像是 ruby/rust/elixir 那場論戰)。我有點糾結,一方面我確實覺得軟體工程的原則和模式還是很重要,但同時我也在想,會不會有一天它們就不再重要了。不是說它們沒用了,而是當你用 agent 的時候,你自己的直覺就能把空缺補上,靠的是一種直覺上的感覺,而不是明確知道它們在做什麼 如果這聽起來不太好懂,我想到的比喻是第一代 iphone。20 年前你得是專業人士、有昂貴的器材才行,現在只要一支手機加上一點創意,就能拍出能打動新觀眾的內容。我不知道這有沒有專門的說法,但我想叫它「技能壓縮」。就是以前被門檻擋住、只有專家才玩得起的東西,變得對一群新的創作者開放,還帶來全新的玩法。細節慢慢淡去了,現在的功夫不在於懂器材、會用器材,而在於你怎麼有創意地去用它 我們會看到一整代從沒看過、也沒寫過一行程式的新 builder 做出超厲害的東西

on a related note, there's been some chatter recently about software engineering skills (eg the ruby/rust/elixir drama). i'm a bit torn because while i do feel like they're software engineering principles and patterns are still important, at the same time i wonder if there will come a point in time when they just won't matter anymore. not that they're no longer useful, but that your own intuition can fill in the gaps as you use agents in an intuitive sense rather than knowing explicitly what they're doing if that doesn't make sense, the analogy i have is the first iphone. 20 years ago you had to be a professional with expensive equipment, now just with a phone and some creativity you can film content that's compelling to a new audience. i don't know if there's a term for this but i want to call it "skill compression". where what used to be gatekept and prohibitive to experts becomes accessible to a new audience of creators with a whole new meta. the details have sort of faded away and now the craft is not in knowing the equipment and how to use it, but how you use it creatively we're going to see a whole new generation of builders who've never seen or written a line of code build incredible things
動態
poteto
順帶一提,最近關於軟體工程技能的討論滿多的(像是 ruby/rust/elixir 那場論戰)。我有點糾結,一方面我確實覺得軟體工程的原則和模式還是很重要,但同時我也在想,會不會有一天它們就不再重要了。不是說它們沒用了,而是當你用 agent 的時候,你自己的直覺就能把空缺補上,靠的是一種直覺上的感覺,而不是明確知道它們在做什麼 如果這聽起來不太好懂,我想到的比喻是第一代 iphone。20 年前你得是專業人士、有昂貴的器材才行,現在只要一支手機加上一點創意,就能拍出能打動新觀眾的內容。我不知道這有沒有專門的說法,但我想叫它「技能壓縮」。就是以前被門檻擋住、只有專家才玩得起的東西,變得對一群新的創作者開放,還帶來全新的玩法。細節慢慢淡去了,現在的功夫不在於懂器材、會用器材,而在於你怎麼有創意地去用它 我們會看到一整代從沒看過、也沒寫過一行程式的新 builder 做出超厲害的東西
← 回到動態