本業はソフトウェアアーキテクトです。
Kawasaki, Japan
Joined January 2010
- Tweets92.9K
- Following432
- Followers1K
- Likes35.2K
ノー残業デーの権利を行使して帰宅し、今日は自宅でルヴァンカップ川崎 vs. 柏を観戦する。小林悠の驚きの先発起用が満を持してなのかそれとも神頼み的な何かなのかは一旦考えないことにする。
jleague.jp/match/leaguecup/2…
1
249
Takuma SHIRAISHI retweeted
元タツノコの社長がタイムボカン始めるにあたって、天野喜孝に「悪を書いてこい」と概念のでかすぎるオーダーを出し、悩みに悩んだ末に出てきたデザインがあのマージョ様・ワルサー・グロッキーの三悪なの本当にすごいと思う
Takuma SHIRAISHI retweeted
大名作『Doom』が、なんとデータベース言語「SQL」に勝手移植!!
本作は、ゲームロジックから3D描画エンジンまでSQLで再構築し、BSPツリーによる描画処理や敵のAI、ゲーム内の物理演算まで実装。
さらに、最大60fpsで動作し、最大4人でのオンライン対戦にも対応と、もはか完全に仕上がっている感じだぞッッ!!
cedardb.com/blog/sqldoom/
※オンラインが満室の時は待っていればプレイ可能な模様
なるほど。
「ウォール街の見方は概ねオッペンハイマーと一致している」
『米オッペンハイマー、AMDを「アウトパフォーム」に格上げ 目標株価600ドル、2027年のデータセンター売上135%増を予想』 finance.biggo.jp/news/49b934…
1
92
Takuma SHIRAISHI retweeted
Reporter: “Pete Hegseth says you want to see him in prison.”
Rep. Thomas Massie: “ There’s no way that I would go to visit him”
Takuma SHIRAISHI retweeted
「Leanでこれ見つけられるの希望ありすぎるだろ」
vs
「えっ、これからのAIはこういうところを足がかりに攻撃してくるかもってこと！？ヤバい世界だ……」
Takuma SHIRAISHI retweeted
LLMのふわふわ推論にprologみたいな論理推論の骨格を相補的に組み合わせて堅牢なシステムを作る…ってLLM登場当初から出てたアイディアで、論文もいくつか出てたけど、leanによる形式検証がここ最近で急に普及し始めて、Lauren Tanはもうgrok bot開発に実運用してて、って展開が速すぎる。おじさんついて行けない。
Takuma SHIRAISHI retweeted
フォトン数はびっくりするほど少ないが、その光は粒なのでエネルギーの最低値は保証されていて、数粒目に入ると光って見える。もし仮に、光が量子化されておらず均一に慣らされていたとしたら、夜空の星は見ることができない。
ピンポン玉1000個当たっても人は死なないが、銃弾1つで死ぬみたいなもん。
Takuma SHIRAISHI retweeted
If by "Software Factory" you mean another grandiose name for a collection of scripts, loops, and workflows, invented by people who need something new to put in their pitch decks, a phrase designed to get developers excited and VCs to open their wallets, a bandwagon for people who have discovered cron jobs and would now like to raise a Series A, then I am against Software Factories.
But if by "Software Factory" you mean a real and rather interesting change in how software gets built, where engineers who were previously using agents to write features and fix bugs are now building systems that get agents to do those things autonomously, where the engineer has moved up a layer of abstraction, from working on the product to working on the machinery that builds the product, then I am for Software Factories.
Because that's the distinction I'm interested in. We're no longer just using agents to build software. We're building the thing that uses agents to build software.
You can call them loops. You can call them workflows. You can call them whatever you like. But "Software Factory" seems as good a name as any, and I rather like the idea that we're no longer merely product engineers, but factory engineers.
This is my stand. I will not compromise.
Just wanted to defend the term "Software Factory" for a second.
First, the caveats:
It's bullshit. It sounds fancier than it really is.
It's a bandwagon. People are using it to get you and their VC's hyped.
But it's also referring to a real change.
Earlier this year, most SOTA teams were using agents to work on the product. Shipping features, fixing bugs.
But now, they're building automations to help agents work on the product for them. They've moved up a layer.
What do we call the thing they're building? Loops? Workflows? Some other generic label?
"Software Factory" is as good a term as any other.
- "We're not working on the product, we're working on the factory that builds the product."
- "We're not product engineers, we're factory engineers."
I like it. I'll continue using it.
