←News detail

AYi AI NotesUpdated Oct 25 22:01

Neuralink President on Musk-Style Scheduling Logic

AI summary

Neuralink co-founder and president DJ Seo explained Musk's "all-green-light timeline" in an interview: first strip out all human bottlenecks such as approvals and logistics, calculate the fastest possible time according to the laws of physics, and then work backward to the real-world process. The author believes this first-principles scheduling method can expose internal team friction, but also notes that Seo admits it brings high pressure, shifting priorities, and staff attrition, and that the regulatory red lights for brain-computer interface medical devices cannot be run by force.

Quoted post

AYi

@AYi_AInotes

Today Musk just reposted an interview video with Neuralink co-founder and president DJ Seo, directly exposing the foundation of the Musk-style deadline-driven scheduling that many people have criticized for a decade. On the show, Seo came clean: when you use Musk's all-green-light timeline to work backward on a hardcore engineering project, you'll find that at least 80% to 90% of project delays are not due to technical snags at all, but are illusions conjured up by the team itself. When talking about how to build brain-computer chips and surgical robots, Seo recreated the logic of Musk's original words when pressing the engineering team: If the entire path right now were all green lights, with no administrative approval wrangling, no logistics shipping delays, and no legacy process baggage, and you acted only according to the laws of physics, how many days at the fastest could you build this chip and run the tests? Normally, when we schedule projects at work, the default approach is to first look at how many months it took to do this last time, then leave a buffer period for procurement, approvals, and cross-department alignment, and finally put together a schedule that everyone feels is safe. But Musk's all-green-light timeline directly reverses the logic of scheduling. He is not relying on off-the-cuff decisions to force employees to work through the night; rather, he uses first principles for engineering scheduling: first strip away all human bottlenecks, calculate the fastest possible time limit for something in the physical world, and then use that limit to push back against the procedural nonsense in reality. It's like driving across half the city during evening rush hour takes two hours. Ordinary people would honestly plan based on two hours, but all-green-light thinking first calculates that at 3 a.m. with all green lights it actually takes only fifteen minutes. Since the physical distance only requires fifteen minutes, the remaining one hundred and five minutes are not the journey itself, but the red lights you must find a way to bypass or smash through. To put it plainly, this gives all of us who lead teams, build products, and write code an extremely useful scalpel. Starting tomorrow, when you encounter those slow projects with schedules of three months, don't haggle along the flowchart anymore. Just ask the team one question: assuming all external coordination replies instantly and all approvals are waived, how many hours does the pure work actually take? Put that number next to three months, and the 80% gap in between is the internal friction you should cut directly tomorrow. However, from a more realistic perspective, we should also stay clear-headed. In the latter half of the interview, Seo also admitted that this scheduling method, which always assumes the path of physical limits, carries an extremely high organizational cost. It creates enormous pressure, frequent priority swings, and staff attrition. Not every engineer can survive under an all-green-light pace. Moreover, brain-computer interfaces involve Class III medical device clinical approvals, and regulatory red lights absolutely cannot be run by force. Mediocre teams use historical average speed to give themselves a sense of security; top teams use physical-limit speed to force out the laziness hidden in processes. https://t.co/CvJSr2Pe1U

View original

老马今天刚转发了脑机接口公司 Neuralink 联合创始人兼总裁 DJ Seo 的一段访谈视频,直接把很多人骂了十年的马斯克式催命排期给掀了底, Seo 在节目里交了个底,当你用老马的全绿灯时间表去倒推一个硬核工程时,会发现至少 80% 到 90% 的项目延期,根本不是技术卡壳,而是团队自己脑补出来的假象。 在聊到怎么造脑机芯片和手术机器人时,Seo 还原了老马逼问工程团队的原话逻辑, 如果现在整条路上一路绿灯,没有行政审批扯皮,没有物流发货耽误,也没有历史遗留的流程包袱,只按物理定律办事,你最快几天能把这颗芯片造出来并跑完测试。 平时我们在公司排项目进度,默认做法是先看上次干这活花了几个月,再给采购、审批、跨部门对齐各留一截缓冲期,最后汇总出一份人人都觉得稳妥的排期表。 但老马这套全绿灯时间表直接把排期的逻辑反了过来,他根本不是靠拍脑袋逼员工通宵加班,而是用第一性原理做工程排期,先把所有人为瓶颈全部剃光,算出一件事在物理世界里的最快极限耗时,再拿这个极限值去倒逼现实里的流程废话。 这就像你在晚高峰开车穿过半个城市要花两个小时,普通人排计划会老老实实按两小时算,但全绿灯思维会先算出凌晨三点一路绿灯其实只要十五分钟,既然物理距离只需要十五分钟,那剩下的一百零五分钟就不是路程本身,而是你必须想办法绕开或撞碎的红灯。 说白了,这给我们所有带团队、做产品和写代码的人提供了一把极好用的手术刀, 明天起遇到那种动辄排期三个月的慢项目,别再顺着流程图讨价还价了,直接问团队一个问题:假设现在所有外部配合秒回、所有审批全免,纯干活到底要几个小时,把那个数字和三个月摆在一起,中间差出来的那 80%,就是你们明天该直接砍掉的内部摩擦。 不过站在更现实的视角也得留个清醒,Seo 在整场访谈的后半段也坦白过,这种永远假设走物理极限路径的排期法有极高的组织代价,它会制造巨大的高压、频繁的优先级摇摆和人员流失,并非每个工程师都能在全绿灯的节奏下活下来,况且脑机接口涉及三类医疗器械临床审批,监管红灯更是不能硬闯的。 平庸的团队用历史平均速度给自己找安全感,顶尖的团队用物理极限速度把藏在流程里的懒惰逼出来。 https://t.co/CvJSr2Pe1U

View original post

Body · AI translation

Seo laid it out on the show: when you work backward from Musk's all-green-light schedule to a hardcore engineering project, you'll find that at least 80 to…

Source

AYi AI Notes