跳到主要內容

All or Nothing: The Real Impact of AI

This is a short conclusion as of February 2026.

In the AI era, senior people (those with ability and manpower) do not need to worry. Because human ability and experience are combined skills that AI still cannot replace.

I still say the same thing:

“Engineers will definitely still have work. Frontend will become even more important. People who build applications will never be unemployed. The only question is who you build for. Demand will only increase.”

Now I will share three key points I see.


Changes in Company Structure

I believe there are several direct impacts and results.


All or Nothing

All

If a company does not have people with this new ability, it will go backward. Such companies will first declare that “agents are useless.” The company structure and staff will still exist. People will still receive salary. Everything looks normal.

But you will realize: The company making money has nothing to do with you.

Nothing

Entire departments may be removed.

Simply put: Now one person can function as a whole team.

There may no longer be a marketing department. Instead, one marketing leader manages many marketing agents.

One person can work like ten people. Ten people can equal what used to be a 100-person company. Revenue can reach hundreds of millions. Everyone is happy.


The “Efficiency First” Myth

“Efficiency” alone becomes a fake topic.

Increasing speed is not enough. What matters is results.

Before, people analyzed data, ran ads, handled digital tasks. Now AI agents can do all of that — and do it well.

If a human’s only role is to “take the blame,” then that is all they will end up doing.


Willing to Believe

You must believe first to move forward. You must believe before you can see.

Unless you have already seen it.

When belief is strong enough, making money and expanding becomes natural.

In the past, expansion meant growing the team. Now expansion means who can efficiently use tokens and burn tokens.


Antifragile Thinking

Being antifragile means acting now causes less loss than doing nothing.

Back to the main point:

“Whoever can continuously burn enough tokens efficiently will win.”

While you hesitate over spending a few hundred or a few thousand dollars to register something, many companies are already quietly burning tokens.

They are training their digital consultants, digital assets, and digital systems. They are feeding agents as digital nutrients to every key person — unless there is an extremely serious data leak risk.

Doing something loses less than doing nothing.

This game must be top-down.

You can add many agents, add AI, build teams — but execution speed always gets stuck at people.

So AI adoption must be top-down.

Maybe 1% can succeed bottom-up, but that is too slow.

As people say: The ones responsible decide the speed of execution.

Leaders must personally do it with the team.


“Digital Work” Becomes Result-Based

All digital work — writing, media, design, research — will be judged by results.

More directly: Vertical focus is better.

Focus deeply. Focus enough to build your moat.

Like what we are doing with cymkube.com — vertical, real, manufacturing. AI cannot replace this quickly.

We believe in:

“Software defines manufacturing.”

These processes are not about influence, reach, or views. Those are only support metrics.

AI can collect and organize those easily.

The only true metric is:

Results.

Workers will not disappear, but their roles will shift.

Fewer people are needed in digital processes, but a small number of responsible humans (who take the blame) are still required.


One-Person Companies and Super Individuals

Next, more people — especially in aging societies — will move toward one-person work models.

As I said earlier:

We lack people with expertise, experience, and networks.

These people are senior. They will not easily work full-time for one company. Startups cannot afford them full-time.

Work will shift to:

• One-person companies • Outsourcing models

Before, these experts worked full-time inside companies. Now one person can serve multiple companies.

Their ability becomes distributed. Phase-based. Spread across multiple businesses.

This trend is already visible.

The rise of the super individual.


Conclusion

There is no final conclusion.

AI is still evolving.

留言

這個網誌中的熱門文章

Vibe Coding:到底?氛圍驅動程式開發必殺技?

Vibe Coding(氛圍編程) 是由 OpenAI 共同創辦人 Andrej Karpathy 在 2025 年提出的革命性程式開發方式,它讓開發者透過自然語言與 AI 對話來生成程式碼,徹底改變了傳統的編程模式。 這種開發方式的核心理念是 「順著感覺走」 ,讓 AI 處理技術細節,開發者專注於創意和需求描述。 Vibe Coding 需要基本上的規劃和執行,但並沒有強制規範,從日常經驗來說可分為三個階段, 前期準備、開發過程、和後期維護 三個關鍵階段。每個階段都有其特定的任務和注意事項,正確執行這些步驟將大幅提升開發效率和程式品質。 將靈感與需求透過 AI 快速轉化成產品功能或原型。以下幫你分成 「前、中、後」 三階段要做的事情,適合你自己做、或帶團隊做 前期:設定 vibe & 準備素材 這個階段的重點是 「建立開發語境」 ,因為 AI 的生成表現高度依賴前期提供的上下文與資料。 明確目標 :釐清要解決的問題、預期要做的功能與核心價值。例如在筆記軟體的情境中,可能是:「我要做一款讓使用者能用 Markdown 記錄筆記,並提供標籤與全文搜尋功能的簡單 App。」 收集靈感 :觀察同類產品(如 Obsidian、Notion)、蒐集市場痛點(例如太多筆記軟體無法脫機使用,或同步效能差)。 建立語境 :準備初步 prompt、背景知識、產品定位、品牌調性、目標使用者輪廓等。 確認資源 :決定用哪些工具(Gemini、ChatGPT、設計軟體、流程管理工具等)。 確認完上述內容之後,就可以先開始進行準備規格,進行第一次的 Vibe Coding 方向驗證 提示詞模板準備 很多人會跳過這步驟,但一份 「好的 AI 提示詞模板」 將決定接下來每一次 AI 對話的品質。有效的提示詞模板需具備: 描述具體且無歧義 包含技術要求和約束條件 提供範例資料和測試案例 指定程式碼風格和慣例 例如針對筆記軟體的案例:   「建立一個支援 AI 功能純文字筆記,輸入內容可即時渲染;需支援儲存到本地檔案,提供標籤欄位做分類;以 React 架構,程式風格採用 Tailwind style components 並使用 hooks。」 開發工具選擇 開發工具的選擇 同樣重要,目前市場上主要的 ...

Claude Code Hooks:自動化與安全的最佳實踐

寫在最前頭,這份文章主要寫起來是給自己看, 同時內容是比較適合開發者,工程師們可以做些自動化處理的簡單筆記。 Claude Code hooks Claude Code hooks 是一種強大的自動化機制,允許用戶在 Claude Code 的不同生命週期階段,自定義執行 shell 指令。這種設計讓開發者能夠將規則和自動化行為嵌入到應用層級,確保每次都能可靠執行,而不必依賴 LLM(大型語言模型)是否會選擇執行某項操作。 Hooks 的核心用途 通知 :自訂收到 Claude Code 等待用戶輸入或執行權限時的提醒方式。 自動格式化 :如在每次檔案編輯後自動執行 prettier (針對 .ts 檔)、 gofmt (針對 .go 檔)等。 日誌記錄 :追蹤所有執行過的命令,便於合規或除錯。 自動反饋 :當 Claude Code 產生不符合團隊規範的程式碼時,自動給出反饋。 自訂權限 :阻擋對生產環境檔案或敏感目錄的修改[^1]。 配置與結構 Hooks 透過設定檔進行配置,分為全域( ~/.claude/settings.json )、專案( .claude/settings.json )、本地專案( .claude/settings.local.json )以及企業級策略設定。每個 hook 由「事件名稱」和「匹配器」組成: "hooks": { "PreToolUse": [ { "matcher": "Bash", "hooks": [ { "type": "command", "command": "jq -r '...'" } ] } ] } matcher :用於匹配工具名稱(支援正則表達式),如 Write 、 Edit|Write 、 Notebook.* 。 hooks :當匹配時要執行的命令陣列。 type :目前僅支援 "command" 。 ...

[CSS] z-index 在不同瀏覽器繼承問題

今天會討論到這個課題,是因為要實做一個Popup dialog,所以我們希望的結果如下圖。 可是在IE7 卻發生了這樣的情況。 Popup不論怎麼設定z-index都無法浮在最上層,我們看一下html架構發生什麼事情。