Steve Ma

退休工程師．AI狂熱者．台灣人

[Steve Ma @stevema]

@gotabi_jp 「冷えたたけのこサラダ」は台湾の緑竹（リョクチク）というタケノコで作られていて、今が一番美味しい季節なんですよ。 鼎泰豊の涼筍は本当に最高なのですが…

[Steve Ma @stevema]

@Dan_Jeffries1 As a Taiwanese, it’s hilarious to hear him basically say: "We need Taiwan for now, which is awkward. Let’s cut a deal with China to stop arms sales, so once we have our own chip capacity in 18 months, China can do whatever they want to them."

[Steve Ma @stevema]

Attention 跟 intention 是很有效率的輸入，Google 已經注意到這一點了。

[Google DeepMind @GoogleDeepMind]

We’re reimagining a 50-year-old interface - the mouse pointer - with AI. 🖱️

These experimental demos show how people can intuitively direct Gemini on their screens using motion, speech, and natural shorthand to get things done 🧵

[Steve Ma @stevema]

Karpathy 這篇提醒大家：如果人還在 loop 裡，瓶頸就會在人的 I/O頻寬。
所以機器多花一點算力，換來人更快理解、回饋、決策，是划算的。人輸出最快是聲音，輸入最快是影像，AI 介面自然會往這個方向走。

[Andrej Karpathy @karpathy]

This works really well btw, at the end of your query ask your LLM to "structure your response as HTML", then view the generated file in your browser. I've also had some success asking the LLM to present its output as slideshows, etc.

More generally, imo audio is the human-preferred input to AIs but vision (images/animations/video) is the preferred output from them. Around a ~third of our brains are a massively parallel processor dedicated to vision, it is the 10-lane superhighway of information into brain. As AI improves, I think we'll see a progression that takes advantage:

1) raw text (hard/effortful to read)
2) markdown (bold, italic, headings, tables, a bit easier on the eyes) <-- current default
3) HTML (still procedural with underlying code, but a lot more flexibility on the graphics, layout, even interactivity) <-- early but forming new good default
...4,5,6,...
n) interactive neural videos/simulations

Imo the extrapolation (though the technology doesn't exist just yet) ends in some kind of interactive videos generated directly by a diffusion neural net. Many open questions as to how exact/procedural "Software 1.0" artifacts (e.g. interactive simulations) may be woven together with neural artifacts (diffusion grids), but generally something in the direction of the recently viral https://t.co/z21CP5iQfu

There are also improvements necessary and pending at the input. Audio nor text nor video alone are not enough, e.g. I feel a need to point/gesture to things on the screen, similar to all the things you would do with a person physically next to you and your computer screen.

TLDR The input/output mind meld between humans and AIs is ongoing and there is a lot of work to do and significant progress to be made, way before jumping all the way into neuralink-esque BCIs and all that. For what's worth exploring at the current stage, hot tip try ask for HTML.

[Steve Ma @stevema]

這是我最近看過覺得最重要，感受最深的 AI 文章。重點不在生產力提高，而是複利。當每個環節的進步都能讓別的環節變得更好時，系統運轉起來就是指數級成長。

[Garry Tan @garrytan]

https://t.co/XTqXqWuQn5

[Steve Ma @stevema]

企業開始蒸餾員工了。
https://t.co/NVaK1Fddk9

[Steve Ma @stevema]

@SaiyamPathak Thanks for sharing a great read. Will it be even faster in NVFP4?

[Steve Ma @stevema]

AIが「毎回自己紹介が必要なツール」から「あなたのことを覚えているパートナー」に変わった——それがAgentが爆発的に広まった本当の理由だと思う。

OpenAI + AWSのStateful Runtimeは、そのメモリをクラウドに移そうとしている。

便利になるほど、関係は深まる。でも深まった分だけ、離れにくくなる。
https://t.co/KRwyGkGMpu

[Steve Ma @stevema]

@AlexFinn very cool setup. One question, won't the memory size of DGX Spark limit the model you can use if the prefill go through it? Your Mac Studio can handle much larger model than the Spark.

[Steve Ma @stevema]

@pop_ikeda 18ヶ月後を待つまでもなく、仕事の消失はすでに起きている。Jack Dorseyが自分の会社の従業員のほぼ半数を解雇したばかりだし…。https://t.co/KYdPaUlE6q

[jack @jack]

we're making @blocks smaller today. here's my note to the company.

####

today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone.

first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay.

we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly.

i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures.

a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers.

we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold.

to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward.

to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow.

jack

[Steve Ma @stevema]

Jack の手紙を読んだ。4000人に向けて書かれた言葉の中に、ソフトウェア産業の終わりの始まりを感じた。アプリは消え、SaaSは消え、残るのはAPIと、それを使いこなす「意志」だけ。AIは道具ではなく、もう産業の構造そのものを書き換えている。

[jack @jack]

we're making @blocks smaller today. here's my note to the company.

####

today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone.

first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay.

we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly.

i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures.

a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers.

we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold.

to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward.

to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow.

jack

[Steve Ma @stevema]

「Claws」と命名された瞬間、時代が確定した。コードを書くのではなく、エージェントに指示し、成果を管理する時代へ。必要なのはプログラミングスキルではなく、タスクを分解し、品質を見極める「指揮力」だ。

[Andrej Karpathy @karpathy]

It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow.

Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: “Here is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for me”. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didn’t touch anything. All of this could easily have been a weekend project just 3 months ago but today it’s something you kick off and forget about for 30 minutes.

As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now.

It’s not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.

[Steve Ma @stevema]

Andrej Karpathyのこのポストが、今後の方向性を明確に示してる。 多くのサービスのメイン顧客は、もはや「人間」ではなく「エージェント」だ。
It's 2026. Build. For. Agents.

[Andrej Karpathy @karpathy]

CLIs are super exciting precisely because they are a "legacy" technology, which means AI agents can natively and easily use them, combine them, interact with them via the entire terminal toolkit.

E.g ask your Claude/Codex agent to install this new Polymarket CLI and ask for any arbitrary dashboards or interfaces or logic. The agents will build it for you. Install the Github CLI too and you can ask them to navigate the repo, see issues, PRs, discussions, even the code itself.

Example: Claude built this terminal dashboard in ~3 minutes, of the highest volume polymarkets and the 24hr change. Or you can make it a web app or whatever you want. Even more powerful when you use it as a module of bigger pipelines.

If you have any kind of product or service think: can agents access and use them?

- are your legacy docs (for humans) at least exportable in markdown?
- have you written Skills for your product?
- can your product/service be usable via CLI? Or MCP?
- ...

It's 2026. Build. For. Agents.

[Steve Ma @stevema]

Claude CodeがCOBOLをモダナイズできるって発表して、IBMの株価が一気に13%も落ちたらしい😨 COBOLエンジニアっていう希少人材を抱えてる「企業の堀」でさえ、AIの進化の前では一溜まりもないんだな…。時代が変わるスピードが早すぎる。
https://t.co/B7L5vL965L

[Steve Ma @stevema]

おっしゃる通りですね！確かに今のAIエージェントはまだ技術的なハードルがあります。でも、今後の開発でその壁はどんどんなくなっていくはずです。 現にOpenClawはすでに馴染みのあるTelegramやラインをメインUIとして使えますし。友達とチャットするような感覚で仕事が完結するエージェントも、すぐに出てきそうですね！

[Steve Ma @stevema]

イーロン・マスクも警告してる！OpenClawにroot権限を渡すのは超危険🚨 最近OpenClawバズりすぎてるけど、みんな本当に気をつけて⚠️
#OpenClaw #ElonMusk #セキュリティ

[Elon Musk @elonmusk]

People giving OpenClaw root access to their entire life

[Steve Ma @stevema]

MetaのAI専門家、自分のメールをOpenClawに全部消し飛ばされたらしい…。 OpenClawにメール連携する人は本当に気をつけて！💦

[Summer Yue @summeryue0]

Nothing humbles you like telling your OpenClaw “confirm before acting” and watching it speedrun deleting your inbox. I couldn’t stop it from my phone. I had to RUN to my Mac mini like I was defusing a bomb.

[Steve Ma @stevema]

@pop_ikeda 恐ろしいのは、影響が18ヶ月後に始まるわけではないこと。この事実を知った経営者たちは、もう「今から」新規採用をストップするだろう…。