Brian retweeted
Après Elon Musk et Jensen Huang, j'ai rassemblé toutes les interviews de Steve Jobs, de 1980 à 2011, sur un seul site.
151 vidéos. 123 heures. 270 citations. Et 14 de ses prédictions vérifiées une par une.
Tout se regarde directement sur le site, en 10 langues.
silicon-valley.tech
Brian retweeted
I'm traveling across US on motorcycle, to explore a country I love and to meet people from all walks of life, especially in rural America, and learn about their life story, philosophy, and just celebrate their humanity. I'm about 1,000 miles in.
I know my mom will surely kill me when she reads this. So, mom, please don't worry, everything will be great 🙏❤️
Btw, I still need to publish videos on my trip through China, where I hitchhiked about 3,000km across rural China, also interviewed some of the top AI & robotics folks there. I'll do that soon.
I'm just slow with the editing thing & bad at the filming thing. I'll try to get better. Mostly, when I travel, I focus on taking it all in and being present with the people in front of me, learning from them, while allocating no thought to the camera. The camera is a side thing I bring along sometimes because it's nice to relive those moments & to share with others.
Anyway, I'll probably take breaks from the road on occassion (to do podcasts, etc). But the goal is to eventually crisscross the country. Who knows how far I'll actually get.
And to friends who will surely write me "wtf are you doing you idiot", please don't worry, while it's true that I'm kind of an idiot, I will also make sure to be safe. Exploring the country on a motorcycle is unlike anything else, it's freedom. It makes me love this country even more: its beautiful nature and all the variety of characters who make up America. And of course, I'm trying to stay off of the interstate, taking as many backroads as I can.
I'll post video if/when I get to it. Sorry to be slow.
Love you all ❤️
Brian retweeted
最近越想越觉得,人类的经济活动里有很大一块,其实就是人和人的链接。
▸ 广告:今年全球 1.3 万亿美元。Meta 一家去年营收就有 2000 亿,基本全是广告
▸ 房产中介:光美国一年的佣金就是 1700 亿美元,占 GDP 的 0.6%
▸ CRM 软件:一年 1280 亿美元
还有营销公司、销售公司、猎头、FA。。。
而这些生意到今天基本还是传统方式:投广告、打电话、填表、靠人一个一个去对接。
我觉得所有这些都应该被 AI 颠覆掉。但是现在市面上的产品都太缺乏想象力了,大部分就是在老流程上加一个 chatbot
@boardyai 算是少数让我觉得不 boring 的:一个 AI 直接跟你打电话聊,聊完帮你介绍该认识的人。到今天它聊过 27 万多人,做了 32 万次介绍
当然 @tuttihq 也不错 hhh,干掉红人营销市场问题不大。
评论区大家都在群嘲 JetBrain,突然想起来自己在2024年,AI Coding还没兴起时,也就是在黎明之前还买了一份Goland,现在发现IDE已经半截入土了。
To complete your code, just dot dot!
Command completion is an easy new way to access context-aware IDE actions, right where you’re coding.
Whatever OS you use and however you work, you just need two taps of one key.
Learn all about it: jb.gg/just-dot-dot
78
Brian retweeted
مشروع يحوّل ساعة Apple Watch إلى ماوس لاسلكي تتحكم فيه بالماك عن طريق حركة يدك ⌚️
وجّه ساعتك للشاشة وحرك المؤشر، ينفذ النقر والسحب وحتى التمرير مدعوم
بدون Wi-Fi أو سيرفرات، اتصال مباشر عن طريق Bluetooth
مفتوح المصدر
Brian retweeted
气死我了!今天发现,我的好几个 Skill 被 WorkBuddy 改名换姓上架了。
WorkBuddy,搬运我的开源 Skill,为什么连作者署名都省了?
完全没有获得商业授权,为什么能上架我禁止商业使用的 Skill?
甚至都不敢用我的 Skill 名称,拙劣地改了名字直接上架?
目前已经发现的有四个。
1. Lieflat Charts(github.com/larashero3-dotcom…)
在 WorkBuddy 上,展示名称被改成了“模板图表与报告”,截图里的标识是 `wbzl-lieflat-charts`,还给我加上了面向 Workbuddy 中文用户,谁允许你们用这种方式改编?
这个项目采用非商业使用许可,商业使用需要另行取得授权。请 WorkBuddy 说明,收录的是哪个版本,依据什么授权将它集成到产品并提供给用户使用?
2. Lieflat Gongwen (github.com/larashero3-dotcom…)
在 WorkBuddy 上,展示名称变成了“公文语料写作教练”。
这个项目同样采用非商业使用许可,项目说明明确写了,未经单独书面许可,不得集成到商业产品或商业服务中。请问,上架前有没有核对这些条件?对应的授权依据是什么?
3. 去 AI 味(lieflat-less-ai-tone)github.com/larashero3-dotcom…
到了 WorkBuddy 上,展示名称变成了“AI写作痕迹清理”,完全没有我的署名。
4. 写作 DNA 蒸馏器(writing-dna-skill)github.com/larashero3-dotcom…
安装前的展示页面里,我没有看到作者和原项目来源。安装之后,在正文底部能看到原项目链接和 MIT License 标注。
但作者和来源,为什么不能在用户选择、安装这个 Skill 时就清楚展示?为什么需要安装后翻到正文底部,才能看到出处?
自己花时间写的东西,被放进别人的产品里,换了名字,用户看到了可以直接安装,却不容易知道是谁做的。作为作者,这个感受非常糟糕。
我把作品公开分享,贡献给开源社区,使用条件写得非常清楚,也希望这些条件得到尊重。怎么到了产品上架的时候,内容拿走了,作者署名和使用限制却没有得到同样的重视?
我希望 WorkBuddy 正面回应:
- 说明这四个 Skill 的来源、收录时间、具体版本和授权依据。
- 补全作者署名,在安装前的详情页明确标注原项目链接及许可信息,说明名称和内容做过哪些修改。
- 逐项核查使用许可,停止不符合许可条件的使用,该下架的下架。
- 对涉及未经授权商业使用的项目,说明使用时间、范围及相关分发情况,承担相应责任,并就损失赔偿及合理维权费用提出处理方案。
- 说明以后如何审核来源和授权,避免其他作者遇到同样的问题。
请尊重开源创作者的创作,遵守资源使用规则,珍惜产品口碑。
Coze要下线了,而我在字节就是干Coze的
今天我的主主页还挂着Coze Workflow引擎开发者,估计明年再挂这玩意就没人知道Coze是啥了
对于这玩意走向结束比较感慨,说点外面看不到的:
1. workflow 不是被 AI 淘汰的,是被「模型自己会规划」淘汰的
2. 当年我们拼命做的拖拽节点,其实是在替模型的笨买单,实际上这玩意就是一种低代码平台延续出来的过渡模式,是一个中间产物
3. 业务KnowHow大于一切,当年人们学的如何搭建工作流的技能已经被Agent内化,一文不值
Brian retweeted
Every backend engineer should build these 15 projects at least once.
Not another CRUD app. Projects that help you understand what's actually happening under the hood.
1. Distributed Rate Limiter — Explore token buckets, sliding windows, Redis atomicity and distributed coordination.
2. High-Concurrency HTTP Server — Understand TCP sockets, event loops, async I/O, connection handling and backpressure.
3. API Gateway — Learn reverse proxies, request routing, load balancing, authentication and circuit breakers.
4. Message Queue (Mini Kafka) — Understand producers, consumers, partitioning, acknowledgements and delivery guarantees.
5. Distributed Job Scheduler — Implement worker pools, retries, exponential backoff, delayed jobs and idempotency.
6. Distributed Cache — Explore cache eviction, TTL, cache invalidation, replication and cache stampede prevention.
7. WebSocket Server — Handle persistent connections, heartbeats, broadcasting and thousands of concurrent clients.
8. Database Connection Pool — Understand connection lifecycle, pooling, resource exhaustion, timeouts and concurrency.
9. Mini Database / Storage Engine — Implement write-ahead logging, indexing, B-trees and crash recovery.
10. Distributed Key-Value Store — Explore consistent hashing, partitioning, replication and failure detection.
11. DNS Resolver — Understand DNS records, recursive resolution, UDP/TCP, TTL and caching.
12. Concurrent Task Scheduler — Work with threads, processes, locks, synchronization and worker pools.
13. Log Aggregation System — Build log ingestion, buffering, indexing, searching and retention.
14. Change Data Capture (CDC) System — Capture database changes and explore event streaming, ordering and checkpoints.
15. CLI Process Monitor — Understand OS processes, CPU and memory monitoring, signals and resource management.
The real learning comes from building these from scratch, testing failure scenarios, benchmarking performance and understanding the trade-offs.
Which one would you add to this list? 👇









































