Recent posts
僕たちは皆、人類の偉大さと同胞への愛を中心に、万人の利益のためにAIを築かなければならない。
原文を表示 (en)
We must all build AI for the benefit of all, centered on the grandeur of humanity and love for fellow man.
Snow Crash を読み直すには変な時代だな
原文を表示 (en)
It's a weird time to be rereading Snow Crash
UPDATE: According to sources who have seen the final text, Pope Leo XIV’s AI encyclical, set for release tomorrow, will argue that humanity faces a defining choice regarding AI. He uses the Tower of Babel — the ancient story of a people who tried to engineer their way to godhood and collapsed under the weight of their own power — as a warning about where unchecked technical mastery leads. Instead, the U.S.-born pontiff will urge the world to build something humbler in its place: a civilization where God and humanity can dwell together.
10:30am: マイクに欲しいソフトウェアを言う 10:32am: そのソフトウェアが手に入っている あああ
原文を表示 (en)
10:30am: You say what software you want into a microphone 10:32am: You have that software oh no
10:30am: You slip and fall in front of some store, get up, shake yourself off, move on with your day. 2:30pm: Claude texts you that you have received your $17 settlement. (The judge assigned to your case was GPT-9.7-ASI3-Codex-Max (xhigh).)
17個の正方形をパッキングしたみたいに見えなくてほんと良かった。
原文を表示 (en)
I am so glad this doesn't look like packing 17 squares.
Following up on the suggestion from Will Sawin, here is an illustration of the new configurations that disprove Erdos' unit distance conjecture (made with the help of ChatGPT 5.5 Thinking).
ChatGPT に数学の質問をしたことがあるなら、君のエルデシュ数は今や 2 だ。
原文を表示 (en)
If you've ever asked a math question to ChatGPT, your Erdos number is now 2.
AI has now solved a major open problem -- one of the best known Erdos problems called the unit distance problem, one of Erdos's favourite questions and one that many mathematicians had tried. https://openai.com/index/model-disproves-discrete-geometry-conjecture/
チップ文化が本当にエスカレートしてる
原文を表示 (en)
Tipping culture has gotten WAY out of hand
最初の質問をまだ続けてる？ 次の段階に進んで満足してる？ 今こそ3番目のような質問をする覚悟をするときだ。 ベネディクト・エヴァンスより
原文を表示 (en)
Are you still asking the first question? Moved on to the second and feeling good about yourself? Time to buckle up and ask questions like the third. From Benedict Evans.
ChatGPT の有料ユーザー数の推定を初めて見た: Ben Evans からの 4500万。 そのうち 700万〜1000万がビジネスユーザーと思われるので、約 3500万がコンシューマー。 ちなみに Netflix は 3億です。
原文を表示 (en)
First time I've seen an estimate of ChatGPT paid users: 45M, from Ben Evans. 7-10M of that is likely busines, so ~35M consumer. Netflix has 300M, by the way.
a) 企業がAIエージェントの必要性に対応できるようになり、かつ b) ASIに至らなければ、エンタープライズSaaSは大丈夫なはず。 でも多くの企業は自分たちを時代遅れにすることに必死で頑張ってるんだよね。
原文を表示 (en)
If a) companies can transition to serving a need for AI agents and b) we don't end up with ASI, enterprise SaaS should be OK. But many companies are actively working as hard as they can to make themselves obsolete, too.
For the last few months, I profiled one public software company per day (50 total) and wrote about the impact of AI on each. Posts collated here: https://t.co/cyEQtxFfYN My takeaways after reflecting this morning: 1) This is not an innovator's dilemma situation like the on-prem to SaaS transition. The on-prem software companies were in deep trouble- they had legacy products and a legacy pricing model, and getting to the cloud meant sacrificing near-term revenue/profits/cash (subscription transition) AND moving each of their customers from an on-prem version of their software to the new cloud-native version, which created a significant change event- i.e. an occaison for their customers to consider whether the cloud-native option might be better, since they were going to have to make a big change anyway. For better or worse, the SaaS companies are not experiencing dynamics like that- no one is targeting them and running a successful "rip and replace" strategy at any scale. Net retention is stable to up, even for companies disappointing at the margins. The existing business model is intact for now- even growing (and in some cases accelerating). 2) The greater the long-term risk, the better the short-term case for acceleration. The paradox of investing in SaaS right now is that the more threatened a SaaS company is in the long term, the better the odds that it will accelerate and "disprove" the bear case in the near term. It is the companies closest to killer-app AI use cases (code, image/video gen/CX, etc.) that have both the best prospects for near-term upside and the most ferocious AI native competition. In many other categories, it simply isn't clear yet that AI adds enough value and/or is token-intensive enough to generate the incremental revenue required to accelerate. It seems likely that some SaaS companies will accelerate into their own obsolescence, and companies that don't accelerate near term are paradoxically better off in the long run (because they will have more time to adapt). 3) Most software management teams don't seem to have made wholesale organizational changes due to AI yet, and that's a disappointment. I would have expected to have read/heard widespread stories about increased operating leverage, cost takeouts, etc. but instead SaaS hiring continues apace and it shows up in management commentary. There is clearly a major struggle to change the culture of SaaS companies and elite talent is being poached by AI natives. I haven't seen a single management team talk about this honestly and put forward a strategy for attracting/retaining top talent in this environment- and I think that's a huge issue in the long run. 4) The mythical "shitty thin SaaS company with no moat" doesn't really exist in public markets. These companies have all gone through the gauntlet- competition with other VC-backed startups, competition with Microsoft, etc. Almost by definition, they've built up complex, moated businesses with brand equity, network effects, exceptional complexity, etc. That doesn't mean AI isn't an issue for them, but the "issues" I found that concerned me were more around disruption to the workflow the software company serves (see: Figma, Five9, etc.) than a disruption to the SaaS business model writ large. Summing it up, the broad-brush SaaS bear case melts away somewhat when you go company-by-company. The median SaaS company is seeing little to no impact (in either direction today), while saying all of the right things on the product side and none of the right things on the organizational side. That doesn't mean there won't be some sort of wholesale disruption down the road- but I don't yet have a clear picture of what it will look like. If you feel like you do, please pick a specific company, respond to or quote-tweet its profile, and explain what you think is going to happen. That's much more fun than debating in the abstract. :)
Libby の本を読み終わったら手動で返すのは道徳テスト
原文を表示 (en)
Manually returning your Libby books when you finish reading them is a morality test
4 時間デバッグに費やした後、Opus じゃなくて Sonnet を使ってたことに気付いた
原文を表示 (en)
Spent four hours debugging before I realized I was using Sonnet, not Opus
これで Grok の質が説明つくな
原文を表示 (en)
This explains Grok's quality
i dug into this in the transformer, all of the actual transformer parameters are zeroes?? so either they're hiding that or for some reason they put a transformer that does nothing in the stack also, there's a lot missing overall...
これはソフトウェア開発の未来におけるXerox PARC's Mother Of All Demosだ。
原文を表示 (en)
This is the Xerox PARC Mother Of All Demos for the future of software development.
VS Code was already used by millions of developers for agentic coding. However, the editor layout has traditionally been optimized for single-task and single-workspace workflows. Today, we're introducing a new window to enable our users (and ourselves!) to work with multiple agents across multiple projects: Agents. Now available in VS Code stable!
みんな goal-directed coding agents 使ってなかったの??
原文を表示 (en)
You all weren't using goal-directed coding agents??
Congratulations to everyone who has discovered /goal in the last two weeks. Copilot CLI shipped `autopilot` mode in January.
今日分かったんだけど、Claude Code には企業ごと、分単位のクエリ制限がある。
原文を表示 (en)
I found out today that there is a per-company, per-minute query limit on Claude Code.
それは人間でもなく、ツールでもない!AIに関連させるのに完璧なメタファーは存在しない...
原文を表示 (en)
It's not a human, and it's not a tool! The perfect metaphor to relate to AI doesn't exi...
シンプルです。パブリック、テナント全体、チーム、共有、プライベートなSkillsのカタログを使用しています（MCPとサブエージェントでも同じことをしています）。 使用状況レポート、再親付け、API、そしてこれら全てに対する細粒度のパーミッションを備えたUX。 Copilot Coworkの場合。
原文を表示 (en)
Simple. We use a catalog of public, tenant-wide, team, shared, and private Skills (we do the same for MCP and sub-agents). Usage reporting, reparenting, APIs and UX with fine-grained permission over it all. For Copilot Cowork.
How are y'all handling company-wide skills? Putting them in a repo? Does that work for Cowork and less technical teams? I feel like there has to be a better way to organize these.
Microsoft 365のCopilot Coworkにプラグインマーケットプレイスが登場しました！ SkillsとRemote MCPサーバーを含むプラグインを開発できます。公開カタログ向け、1社向け、または個人向け。管理者は完全な可視性と制御ができます。 開発者向けの説明とウォークスルーはこちら。
原文を表示 (en)
Copilot Cowork in Microsoft 365 now has a plugin marketplace! Develop plugins including Skills and Remote MCP servers for the public catalog, for one company, or for yourself. Admins get full visibility and control. Here's my dev-focused explainer and walkthrough.
