Kevin Lin (@Slutsky___) header
Kevin Lin (@Slutsky___) profile picture

Tokenizing dev @kaio_xyz / Chief GTME @Signalsurf / Co-founder & Core Contributor @xuedao_tw /

Taipei City, Taiwan
Joined December 2021
Photo by Kevin Lin (@Slutsky___)Photo by Kevin Lin (@Slutsky___)Photo by Kevin Lin (@Slutsky___)Photo by Kevin Lin (@Slutsky___)Photo by Kevin Lin (@Slutsky___)Photo by Kevin Lin (@Slutsky___)Photo by Kevin Lin (@Slutsky___)Photo by Kevin Lin (@Slutsky___)Photo by Kevin Lin (@Slutsky___)Photo by Kevin Lin (@Slutsky___)
🇹🇼 🇹🇼
🇯🇵일본인 친구들에게 비밀스럽게 질문 하나 할게. 일본과 지리적으로 가까운 나라인 🇰🇷한국, 🇹🇼대만, 🇨🇳중국, 🇷🇺러시아, 🇵🇭필리핀 이 5개의 나라 중에 일본 입장에서는 한국인이 그래도 제일 괜찮지 않냐? 인종적, 정치적, 경제적, 문화적 거리감도 가깝고. 이젠 솔직히 말해봐. 괜히 츤츤거리지 말고. 솔직히 5개 나라 중 하나를 반드시 골라야 한다면, 한국을 고르는 일본인이 90% 이상은 될 거 같은데. 맞지?🤔
2
193
This one is really helpful!
TL;DR - Fast runners (ex Blacksmith) - Oxlint for ESLint, bun check for tsc - Bigger test machines, Vitest isolation off - Fix caching, Blobless clones - Parallel jobs, nx affected - Pre-push hooks What are you waiting for? Send this to your agent :)
1
3
278
以前我會說 Web3 既像科技業,有很多創新,又像在金融業,當然,這是基於其業務本質嘛。 但我認為 2026 之後,它比以往都更貼近金融業了。只會是 FinTech,不會是 TechFin。 甚至是在 LLM 帶來的 software productivity 暴增,並沒有在 Web3 上獲得很好的體現。這主要是智能合約的開發週期以及風險性所導致的。 歸根究底來說,區塊鏈還是一項防禦性的創新。
9
280
100% agree my approach is to separate the human TL;DR version and agent version cuz at the end of the day, your agent docs are reading by other’s agent so it make sense to left some evidence for other agent to be able to fetch the source or validate it.
We instituted an official AI Writing Policy at @Clay. Massive thanks to @sophiebits on our engineering team who wrote this. Originally this was just for eng, but other teams found it so helpful we expanded it company-wide. Here are the four guiding principles: 1. You must stand behind every idea and sentence It is your responsibility to make sure that the entire document is representative of your own thoughts before you share it. 2. Writing is thinking Spending time on the writing process teaches you more about your topic. If you circumvent this process, you will walk away with a poorer understanding of the subject matter. 3. More time should be spent writing a document than consuming it If you generate a document from a short prompt then ask your readers to go through the longer output, you are disrespecting their time. They can talk to ChatGPT themselves if they want to. 4. Longer is not better AI makes it easy to generate long docs, and it loves padding them with sentences that say nothing. If you're producing docs from a short prompt, consider just sharing the prompt. You can read (and borrow) the full policy below. Hopefully we all communicate a bit more clearly now :)
6
288
第一次使用 @FathomDotAI 是2023,那時候發現他是所有競品裡效果最好的,剛一看收到 email 發現團隊居然被 @Superhuman 收購了,真是了不起! 這個品項繼續卷也辛苦,Notion 免費爆送一堆額度,Gronola 瘋狂買廣告。 techcrunch.com/2026/09/14/su…
1
3
196
先用方便快速迭代的語言拼功能和增長,未來重構架構和技術棧是帶著明確的瓶頸才考慮的。 新創需要 PM 與全端融合一體的 product builder(也許甚至不是 engineer background 了),業務需求明確了且 PMF 才來考慮 hire 甚至 outsource performance improvement work
果然任何公司都会有技术债,只是这次 OpenAI 选择了把技术债留给未来的 AI 来还。 OpenAI 刚公开了 ChatGPT 背后的存储系统 Habitat。 它现在每秒处理超过 7000 万次请求,保存 500PB 以上数据,服务每周超过 10 亿用户。但它最早只是一个连接数据库的小型 Python 库。 有意思的是,OpenAI 很早就知道 Python 扛不住未来的规模,也知道迟早要重写,但当时没有立刻动手。他们做了一个很大胆的判断,先用 Python 快速扩张,等必须重写时,未来的 Codex 和 GPT 会让迁移便宜很多。 后来这笔赌注真兑现了。 2026 年第二季度,两名工程师加上 Codex 和 GPT‑5.5,把整个服务重写成了 Rust。现在新版本已经承接 95% 的生产流量,CPU 效率提高 6 倍,内存效率提高 15 倍。 过去我们说技术债,是把今天省下来的时间,留给未来的工程师加班偿还。 OpenAI 这次做的是把债留给未来更强的模型。 这可能会改变软件开发里一个很基础的判断。 以前选错语言、架构不够完美,意味着以后要付一笔很贵的迁移费;如果 AI 能让大规模重写越来越便宜,公司就可能更愿意先用最快的方法把产品做出来,再让未来的模型收拾残局。 当然,这不是鼓励大家随便写。OpenAI 敢这么干,是因为系统边界、测试和监控都足够清楚。 没有这些,AI 重写的不是系统,可能是事故。
1
1
8
1,407
The Remote-First Generational Company🫡 @linear respect
Today we're announcing our second employee tender offer. We passed $100m ARR earlier this year and now have more than 40,000 paying customers. The tender lets our teammates participate in that success at a $2.5B valuation: linear.app/now/sharing-growt…
2
256
I thought everyone just symlink the CLAUDE.md and ./claude 🤔
I’m thinking about banning Claude code at Shopify until they change their mind and read AGENTS.md and .agents/skills etc. Insisting on only reading CLAUDE.md sometimes leads to split brain problems when different team members use different tools. Just unnecessary.
179
人腦也是一個 black box,從公司角度來說你的 token 可以大概透過你的 compensation 回推。也就是說人作為 input token 和 output token 都極貴的一個 human agent,其實很多時候必須要好好想想什麼時候該用(就像你不會開著 Fable 5 ultramode,這是一種炫富)。 人的 output 確實可以透過傳遞想法給 AI 讓它代為 output,但是 input 成本沒有辦法降低,換句話說現在最貴的是人類的 effective input token?
2
218
笑死完全 100% 正確
gpt 5.6 最让我受不了的就是: 我让它做一盘番茄炒蛋,它往里还加了东坡肉。 我说有必要加东坡肉吗?它说你说得对,然后把东坡肉去掉。 我说好,你提 PR 吧。再一看,它 PR 写着「番茄炒蛋(无东坡肉)」并且注释里会写一大堆为什么本道菜不需要加东坡肉。
1
262
Not only reviewing the code itself, but also examining how the code is generated.
Today we’re introducing Delta. Delta is a multiplayer environment for coding with agents and reviewing what they build, powered by DeltaDB. The first invites to our private beta are going out now. zed.dev/blog/introducing-del…
266
I ran out of all my reset 😭 and my streak just shutdown. @thsottiaux, can we only count the day with credit so that I can continue on my streak 😭
1
126
That’s exactly what AI-native SaaS today 😃 but still the opportunity is huge
everybody who's not shooting for AGI is building the same thing: * an interface that sits as close as possible to a user's workflow: slack, email, terminal, standalone app, other existing app * infra that can run long-running agents on schedule or on demand that progressively learns (search/finetuning) and gets cheaper (eval-driven routing/finetuning/oss models etc.) the interface you give away for ~free, and you charge a premium over your infra cost. lots of opportunity there for the ones that can cap their non-model infra costs and keep quality high without bleeding money to frontier models
2
131
我非常看好這類型的題目,作為一個企業或者團隊,如何衡量 AI 導入並且規模化的蒸餾員工絕對是每個 Tech Lead & CTO 的難點。 而且 @WorkWeave 的吉祥物🧶有點可愛⋯
We’re announcing our $13.5M Series A led by @Standard_Cap. AI has taken over engineering and companies are wasting millions. Weave gets you the most out of every dollar spent on tokens. Have fun watching a man attempt to conquer his fears in the video.
2
242
Codex kept resetting mid-session and I kept burning tokens all over again (the RESET week was very on-brand, @thsottiaux 😂) so I vibe-coded a tool: BrrrnBar 🔥 github.com/kevinsslin/brrrn A lightweight (~1.5MB) macOS menu bar app that shows how much you've burned on Claude Code & Codex (priced at API-equivalent rates), plus your own usage patterns: a burn calendar, 30-day trend, what hours you burn at, and personal records (peak hour, peak day, longest streak). I wear a WHOOP and love roasting friends over the sleep/recovery leaderboard, so I added one here too. Deploy a free Cloudflare Worker + KV (1-min guide in the repo), pull your friends in, and roast away. You can also run it locally, so nothing gets uploaded. Issues and PRs welcome 🙏
1
236
😱😱😱😱😱
Once we have completed our review for security vulnerabilities, we will make the entire codebase of 𝕏 open source, with no exceptions. Moreover, we will invite third party reviewers to examine the system that is running to confirm that the open source code is what is running. Trust through total transparency is the only thing that should be believed.
122
我想要大大推薦 @zeddotdev,從約兩三年前把 VSCode 換成 @cursor_ai 時就一直用 curosr 到現在,中間曾經試圖換成 Zed 但當時 cursor 還是太強,直到一年前 cli 時代大爆發 💀,cursor 就慢慢脫離我的主力。 我的開發場景通常是 codex in chatgpt app + claude code with cmux 作為花最多時間的地方,一些 non-trivial feature / fix,我還是會打開 IDE 看一下 branch diff 或特定 commit,但是在 agent worktree 多開的情況下小小 24 GB RAM 還是覺得很卡。 Zed 開啟的順暢程度以及他可以讓 external agent (codex/claude code) 有 cursor 般的體驗,你可以在 IDE 視窗下看到他在改哪到哪了之類的。
2
6
552