跳到主要內容

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.

留言

這個網誌中的熱門文章

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

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

[教學] 快快樂樂刪除CodeIgniter index.php

預設的CI網址預設都設定為index.php同一層級,因此所有的程式都必須指定index.php導向才能開始,例如 http://localhost/ci/index.php/welcome/test http://localhost/ci/welcome/test 本文將說明如何將惱人的index.php消除,還你一個漂亮的URL。 設定開始: 接下來說明如何使用rewrite方式將惱人的index.php去除。 rewrite不清楚的人,煩請先自行google 首先要先確定Apache的 mod_rewrite 有 開啟 ,如果沒有開啟請設定好之後重新啟動apache。 接著,在根目錄底下建立一個新檔案,檔名為 .htaccess ,裡面程式碼如下: <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ index.php/$1 [L] </IfModule> 接著到 application/config/config.php ,開啟檔案修改 $config['index_page'] = ""; 注意: /index.php/$1 要根據你目錄,例如 http://localhost/index.php ,網站根目錄為 /ci/index.php 則要寫成 /ci/index.php/$1 接著至CI目錄下,尋找 config\config.php , 修改一下裡面的檔案,修改如下: $config['index_page'] = ""; 存檔後,如此一來大功告成。 參考資料 官方網站說明

[教學] Mojito 安裝與入門,install mojito for beginner.

mojito ,最近終於從 YDN 對外公開此專案,這個套件主要用於解決前端多重裝置及瀏覽器端的問題,後端服務採取 node.js ,因此使用上必定要先準備以下幾個元素 準備素材 c++ complier git Node.js > 0.4.x NPM > 1.0.x 安裝方式 git clone git://github.com/yahoo/mojito.git cd mojito/source sudo npm install -g . npm install . 以上四個簡單的步驟,就可以把 mojito module 完整安裝到服務器上,接著就可以開始進入 mojito 的世界 使用方式 mojito 提供了完整的 command line 給開發者使用,接著先建立一個基本 hello world 專案,跟著以下步驟完成第一個專案。首先建立一個 mojito application, mojito create app hello cd hello 切換到目錄之後,再接著建立自己的 mojit,這邊的 mojit 就像是一個應用(application)可能會包含許多個獨立網站體,擁有獨立架構的 MVC ,包含內部設定等,詳細資料可以參考官方的 說明 ,建立 mojit mojito create mojit HelloMojit 輸入指令後,會看到顯示結果如下, creating mojit called 'HelloMojit' (using "default" archetype) ✔ mojit: HelloMojit created! ✔ mojito done. 接著修改 application.json 這個 mojit 設定檔案,讓剛才新建立的 hellp application 指定底下有一個 mojit -> HelloMojit ,讓應用可以去執行 mojit controller ,修改如下, [ { "settings": [ "master" ], "appPort": 8666, "specs": { ...