Pikku!、Biscuit、コピペ帳、日々のログ、ナノノートなどを作っています
Joined April 2007
- Tweets5.1K
- Following2.2K
- Followers2.4K
- Likes11.1K
Agata retweeted
"Software development is dead" they said.
Last month a client paid me $20,000 for an app. My cost was $200 for Claude Code.
It's a kiosk mode app for android tablets in taxis. Ads for partner companies, tipping the driver, admin, backend, the whole thing. Now live in production.
I didn't write a single line of code. Still took 1 month of constant work.
The best part? The client came to me with a vibecoded version first. It was horrendous.
He paid $20k because he needed someone who has done this before, professional design, real assurance, and 12 months of support.
You can't vibe code that.
Without AI it would have taken 3 months and cost him 2-3x more.
Developers using AI will always win. Stop listening to people who say software is dead for views.
今後はよりPRの検証に使用するトークンがより大きくなる気がする。
検証はいままでは人間の目によるコードレビュー＋単体テスト、実際の動作検証など保証していた部分。
人間がコードを読まないも当たり前になっているし、人間が動作検証やらないものあたりに前になるとおもう。動作検証をAIにうまくやらせるのを頑張る感じ。
ここは薄くやることも、厚くやることもできる領域だとおもうけど、網羅的かつ探索的にエージェントが受け入れテストをおこなうと、かなりのトークンが必要になるし、エージェント開発と同様に検証の仕組みの検証機構（Eval、Trace、コストなどなど）も一式必要になりそう。
Strongly agree.
A year ago, I was trying hard to get AI to write code and choose architectures that I considered best. Now I’m starting to wonder if my detailed instructions might actually be becoming a bottleneck.
Frontier models can already write solid code without much hand-holding. Maybe we’re just projecting our human preferences onto something that works differently.
Clean code evolved around how humans think and work. AI agents have different constraints — context windows, reasoning, tooling, etc.
Who knows? Maybe the best code and architecture for AI look nothing like what works best for humans.
Perhaps I’ve just spent the past year teaching AI my personal preferences 😂
And there’s a separate question: do humans really need to read code to verify correctness? Reading code has never guaranteed that a system actually works.
I think we need to rethink both how AI should structure code and how we verify its correctness.
We don’t know the answers yet, and that’s what makes this so interesting.
it's very interesting how many replies i've gotten about maintainability and clean code being still important. i would argue that that is no longer true and we all need to update our priors on what Good Code really means in 2026.
clean code has always come at a cost - performance. indirection and making code readable/understandable for a human is not free, it often comes at the cost of worse performance. we have historically been okay with this because of Moore's Law and the fact that most code is not on the hot path.
these principles also came from a time where humans maintained code. it made sense to optimize for humans then, but it makes less sense now when agents are already writing all the code. we will in fact probably discover and come up with new principles: principles of agent friendly architecture (i plan to write more thoughts about this soon)
OmarchyならレスキューUSB使ってCodex/Claudeと一緒に復旧作業ができちゃう
Introducing Omarchy Rescue.
A rescue USB that comes with Claude, Codex, and OpenCode.
Fix everything.
github.com/crmne/omarchy-res…
Agata retweeted
Experience gives perspective. Programming is not dead, and never will be.
It's late September 2026. Sometime in September 1976, just after I entered college, I wrote and ran my first serious program. I have now been a programmer for literally 50 years.
And man, I have seen it *all*. Punched cards to glass ttys on minicomputers to workstations to the earliest micros. I've written business software, communication programs, development tools, games, language implementations, kernel device drivers, graphics libraries, a few critical pieces of infrastructure, and all manner of odd programs for which there is no taxonomy. Coded in a score of languages some of which are now forgotten. I've run over 70 open-source projects and contributed to at least as many more.
Along the way I noticed a few things, and wrote about them, and that made me famous. But I'm not here to write about that today. I'm here to write about what it means to be a programmer and a technologist with the Singularity upon us.
I have lost count of the number of times I have been told "programming is over". You kids may think this is a new claim that came into the world with LLMs. Hah! There's been that kind of talk at every step function in the quality of our programming tools. I first heard it when compilers were replacing hand-hacked assembler in the early 1980s, and I wouldn't be a bit surprised if somebody said it earlier when in-memory code replaced plugboards.
One constant amidst all this change is that the intentions in a user's head do not magically turn into executable instructions that a computer can run. Another constant is the mindset of the people who specialize in bridging the gap between wish and algorithm. A programmer is a programmer is a programmer - the tools are secondary.
"But it's different this time!" some people will say, "AIs are superhuman now!" So? What did you think the optimization stage of a compiler was, chopped liver? We've been relying on tools that exceeded human capabilities all along - we built them precisely because our meatbrains could not otherwise keep up with the demands of the job.
It's been a hell of a ride, that 50 years. I've succeeded and failed and succeeded again. Done a lot of work I'm proud of. Built at least a few things that look like they're going to last. None of that goes away because, hypothetically, an AI might have made me faster.
The work is never done, even if the tools can talk to us now. Because intentions still have to be communicated; people who specialize in that and develop right mindset to do it still have a major advantage over people who don't.
If you're feeling depressed because you spent years or decades developing hand-coding skills that are obsolete now? Buck up. You still have the most important asset - a mind that knows how to think that way.
I'm facing the winds of the Singularity with a smile. Because 50 years and I'm still standing - still shipping code that people can use, still learning, still refusing to be paralyzed by the pace of change.
The best therapy for your uncertainty? Get to work on something.
Agata retweeted
DHHが omarchy について語る会 / htn.to/3SLHm6FU6Q
この不安はかなり分かるなー。DHHの動画を見る前は、自分もわりと強くその不安を感じていたし。楽しさ半分、不安半分みたいな。
自分は昔『良いコードを書く技術』という本を書いていて、それは「良い仕事をしたい普通のプログラマ」のための本でした。
特別な才能がなくても、考え方とか習慣を身につければ、ちゃんと良いコードは書けるようになる。そういうスタンスの本です。
なので、「コツコツ技能を身につければ、ある程度は報われる」という道が細くなることへの不安は、自分もめっちゃ分かっているつもり。
ただ、DHHの話は、成功者だから気楽に「makerになろうぜ」と言っているというより、コーディングがここまで急速にコモディティ化していくなら、そこを守ろうとしてもあまり良い未来はない。だったら早めに次へ行こうぜ、という話に自分には聞こえた。
その先が今より厳しい戦いになる可能性はあるとしても、たぶんもう、そっちに進むしかないんだと思う。
ただ、その先を「クリエイター」と呼ぶと、ちょっと違う気もするし、ハードルが一気に上がりすぎる感じもする。
何を作るか、誰の何を解くか、どう試すか、どう良くするか。コードを書くよりずっと曖昧で、正解もない世界にはなると思う。
でも、そこも全部センス勝負になるわけではなくて、成功確率を上げるための技術とか方法論は、たぶん作っていけるんじゃないかと思っています。
考えてみればプログラミング自体も、昔はかなり限られた人のものだったのが、PC、Web、OSS、クラウドと何度も裾野が広がってきた。
LLMもその延長で、今度は「作る人」の範囲を一気に広げているんだと思う。自分も、そうやって裾野が広がってきた恩恵を受けてきたひとりだし。
「良いコードを書く技術」の次は、AIを使って「ちゃんと役に立ち、使われるソフトウェアを作り続ける技術」を考えることなのかもしれない。
DHHの基調講演にモヤること
DHHは手でコードを書くことから新しい開発手法に移れと言っているのではなく、
「エンジニアからクリエイターになれ」
と言っていると思った（「プログラマー引退してmakerになります」発言）
その証拠に「次はアーキテクトになろうと思っているならそれもLLMに取られるよ」ともツイートしている
プログラマーとして成功することはある程度の再現性があり、努力をすれば報われる可能性が高かった
でもクリエイターはそうではない
努力すれば米津玄師や宮崎駿になれるか。その再現性はほとんどないよね、という僕の直感は多くの人が共感してくれるところと思う
でもそれができなければ「クソッタレの負け犬」になりますよと
実際そのような世界になる可能性はある気がする
LLMは「一発逆転のチャンス」みたいに捉える向きもあるが、実際には後天的な努力で得られる技能を無意味化しつつある
実際には今まで数多くあった逆転の芽が潰されるケースの方が多いように思う
先天的なセンスがなければ成功できない時代が良いことなのかわからない
以前、「誰でもアプリを作れる」的な文脈でAnthropicハッカソンがよく引き合いに出されていたが、受賞者のプロフィールを見ると医者や弁護士など、まあ自分からするといわゆる知的上流階級的な人たちだなと思った
誰でもアプリは作れるけど、成功するアプリを作れる人は一握りである
誰もが自分のプロダクトで一発当てる夢追いクリエイターであることを強いられる時代？
それはすでに生活の心配をしなくていい大金持ちや、太い実家などのパトロンがある人にはただ楽しい余暇の延長なのかもしれないけど、人類の99%にとってはそうではない
Agata retweeted
OmarchyでXの動画を日本語で見るためだけに翻訳字幕をでっかくつけられるやつ作った。
最近Xでしか見れない動画とかあるし、Chromeのライブ字幕も使い勝手微妙なので。
github.com/agata/omarchy-jim…
自分専用アプリがおもいついた瞬間に完成している、素晴らしい時代だとおもう。
Computer useがOmarchy で使えるようになるとOmarchy自体の開発も加速しそう。
1/ Today we're announcing the stable Cua Driver release for Omarchy - a new foundation for computer use, built into the OS from the ground up.
Over the last month, we worked directly with @dhh, @SpencerGBull and @vaxryy to bring a native synthetic cursor to Omarchy's Hyprland compositor, enabling true multi-cursor computer use at the OS level.
Cua Driver is open source and available at github.com/trycua/cua