
Building @dinii_jp’s All in One Restaurant Cloud.
Tokyo, Japan
Joined July 2009
- Tweets16.2K
- Following937
- Followers766
- Likes841
lethain.com/passing-100-prs-…
AIによる開発の制約を都度解決してきた今まだ残っていること
- 顧客理解や複雑な判断が必要な開発の高速化をどうやるか
- 複雑な変更をどうやって確実に検証するか
- AI の自律性をさらに高めて人間の介入をもっと減らす
17
Shingo Sato retweeted
A toothpaste company has quietly killed the entire market research industry and nobody is talking about it.
Colgate published a paper showing you can predict real purchase intent by simply asking LLMs to roleplay customers.
And this is beyond insane.
If you ask an AI, "Rate this product from 1 to 5," it gives safe, middle-of-the-road garbage.
So researchers invented a method called Semantic Similarity Rating (SSR).
Instead of asking the AI for a number, they asked it to roleplay.
They gave the LLM a demographic profile. They showed it a product concept. And they asked it to write down its raw, unfiltered thoughts.
Then, they used a semantic model to translate those written thoughts into a numerical score.
The results are staggering.
Tested against 57 real personal care product surveys and 9,300 human responses, the synthetic consumers hit 90% of human test-retest reliability.
They perfectly mirrored how different age brackets and income levels react to price changes.
And they provided detailed, qualitative feedback that was deeper and more critical than what actual humans wrote.
This destroys the economics of traditional market research.
You don't need to wait a month to see if a product will sell.
You can simulate 1,000 hyper-targeted customer interviews overnight.
You can A/B test pricing across every demographic instantly.
INSPIRED を読んだ。プロダクト開発の本質的な原則は変わらないと思うけど、職種の境界や Discovery, Delivery のあり方はすでに変わってきてるし従来のチーム構成や役割分担もやはり再考する必要ある
2
86
Never gonna give Yo up.
iOS TestFlight: testflight.apple.com/join/V3…
Android soon.
Shingo Sato retweeted
STATE OF THE TECH JOB MARKET IN 2026
Twice a year, I dig into trends in hiring and job openings. This is the fifth report I've done, and the most surprising yet:
1. PMs are winning in the AI era
2. Engineering demand has stalled
3. Design openings are at a record low
4. Every role now requires AI skills
5. Tech jobs are concentrating in the Bay Area
6. Remote roles are at a record low
7. The tech job market is growing fast, but mostly outside of software (gasp!)
Full report here: lennysnewsletter.com/p/state…
Shingo Sato retweeted
ビッグテックで働いてる人の一部には、製品に思い入れはないしプロモにも興味ないけど、好きなコーディングだけしてて高い給料もらえて幸せ、って人がいてそういう人たちはエージェントのお守りするだけのつまらない仕事になった、ってことなのかなと
Shingo Sato retweeted
libghostty 1.0 is here! I started Ghostty ~5yrs ago to work towards this. Today, libghostty is in hundreds of projects used by tens of millions of people. 1.0 marks ABI stability, quality, and an invite for distros to begin packaging. mitchellh.com/writing/libgho…
Since starting the Ghostty project in 2022, the most common question I've been asked is "why?". Today, I'll answer this by showing the broad industry impact libghostty has already had.
On top of JetBrains and Neovim already mentioned (that alone being over 10 million users):
-KDE developers are experimenting with a Konsole replacement built on it.
- Vercel's Turborepo uses it to render task output in its TUI.
- devenv uses it to drive shells.
- Antithesis used it to fuzz TUI programs and found real bugs in btop and others.
-Ghostel brings it to Emacs.
- ghostty-web is the WASM build with an Xterm.js-compatible API.
- Commercial products like OrbStack embed it.
- And a whole wave of new terminals and "agentic" coding tools, such as herdr and cmux, have been built on it rather than writing yet another emulator.
There are community bindings for Rust, Go, JavaScript, Swift, Python, .NET, Elixir, Dart, Java, and more, and the awesome-libghostty list tracks well over a hundred projects.
More people today use a terminal powered by libghostty than use Ghostty the application, by a very large multiple. And libghostty is having a much larger impact than being "just" a terminal emulator.
I'm excited to see where people take it from here.
Shingo Sato retweeted
/
📢 イベント登壇の内容が記事になりました!
\
弊社荻野が技術的負債に向き合うConference 2026にて発表した内容を、記事にしていただきました。
大規模な認証認可基盤のリアーキテクチャに関する内容となっています。
発表を見られなかった方はぜひご覧ください!
findy-tools.io/articles/debt…
Shingo Sato retweeted
Playwright and browser security reminder.
We saw a post suggesting that you delete Playwright because it bundles browsers with CVEs. That is a misconception. Do not delete Playwright🙃. Here is how it works and what you should do.
No Playwright package bundles a browser. Agents on Playwright MCP or CLI run your stable Chrome, which gets Chrome's security updates, with the sandbox on.
🤖 If you use Playwright MCP or the Playwright CLI
They use the stable Chrome / Edge on your machine, so it gets its normal updates. No config edit is needed.
🧪 If you use the test runner
When you run npx playwright install, Playwright downloads Chrome for Testing, pinned to the build we tested that release against. The pin is on purpose. Your tests run on the same browser on every laptop and CI machine, and a browser
update cannot suddenly break your suite. You choose when to move by upgrading Playwright. New releases usually pin a build ahead of stable Chrome, so you see breakage before your users do.
We recommend this for full e2e test suites on your own trusted app. This build can miss Chrome security fixes until the next Playwright release, and by default it runs with the sandbox off. Do not use it on the hostile web.
📚 If you use the library API
chromium.launch() has the same defaults: the pinned build with the sandbox off. If your code visits pages you don't control (scrapers, agent scripts), max out protection:
chromium.launch({ channel: 'chrome', chromiumSandbox: true })
🔒 Always keep Chrome / Edge updated. Some bugs can escape a sandbox.
Happy testing!
Shingo Sato retweeted
✨ SWE の riya amemiya さんによるブログが公開されました!
Chromium(V8)のArray.prototype.lastIndexOfを最大約26000倍高速化した
Chromium 改善シリーズの第 5 弾 (!) です。改善幅がとても大きく、インパクトのある変更の詳細を記事にしていただきました。
zenn.dev/dinii/articles/2f66…
Shingo Sato retweeted
Announcing Dagger 1.0 beta.
Replace Jenkins and GitHub Actions with CI that matches the speed and scale of coding agents without wasting compute or tokens.
Featuring: test-native CI, dev shells, local and remote execution, official modules, and more.
dagger.io/blog/dagger-10-bet…
Shingo Sato retweeted
✨ SWE の riya amemiya さんによるブログが公開されました!
Chromium(V8)のArray.prototype.fillを最大約7倍高速化した
Array.prototype.flat の改善に続き、V8 の改善シリーズです。
普段意識しない V8 の裏側を知ることができる記事ですので、ぜひご覧ください!
zenn.dev/dinii/articles/5b8e…
Shingo Sato retweeted
AIでPRが増えすぎたレビュー負荷を、条件を満たす小さな変更の自動承認で減らす試み。
・Imprintではこの2年でマージされるPRが平均4倍に増えた
・一部のチームでは10倍、個人では25倍に達している
・品質は落ちておらず、インシデントは42%減、重大インシデントは78%減
・一方で、PRのレビュー時間は2年前の約33分から77分に延びた
・レビュー数がPR数の増加に比例して増え、スケールしなくなった
・そこで作ったのが、条件を満たすPRを自動で承認するsmall-change
・その条件は以下の通り
・変更が1,000行未満であること
・AIの自動レビューで重大な指摘がないこと
・担当サービスでの過去のマージ実績が10件以上あること
・影響範囲が最大3サービスまでであること
・例外は`.small_change`ファイルで設定できる
・承認は自動スキルが行い、approveかignoreのみでコメントは付けない
・人間が形だけ見て通すmeat proxy reviewを避ける狙い
・実装は2日で終わった
・現在は約10%のPRがsmall-changeの対象になっている
・まだ初期段階だが、検証の仕組みを強化して対象を広げていく予定
lethain.com/small-changes/
anthropic.com/engineering/re…
AIエージェント向けVCS自作したのか。プロダクトとして or オープンソースとして公開してくれないかな
3
218















