Nelson retweeted
I'm pleased to announce v2.0 of my SwiftUI Pro agent skill! It's packed with improvements based on real-world testing of iOS 27 and iPhone Duo, and also integrates a variety of advice from Apple's own skills. Get it here: github.com/twostraws/swiftui…
Nelson retweeted
Achei que o brinquedo ia roubar a cena… mas o gato entregou TUDO no drama
Essa reação foi digna de tapete vermelho .
Nelson retweeted
#1 一家牙膏公司悄悄把整个市场调研产业给干掉了,却几乎没人在讨论。
高露洁(Colgate)发表了一篇论文:只要让大模型(LLM)扮演消费者,就能以90%的准确率预测真实购买意愿。
这也太离谱了吧。
Nelson retweeted
雖然章萬安用特權改姓蔣這題真的沒什麼好打的,但未免也太多人不知道蔣萬安用特權改姓了吧?這根本不是多久以前的事欸!2005左右吧?
章萬安原本姓章,28歲才為了要從政而改姓蔣。
改姓的方法是章萬安他爸用特權去認死去的小蔣當爹,全台古往今來唯一不用驗DNA特權改姓。
蔣家從頭到尾都否認章家認親,蔣宋美齡、蔣方良、蔣孝勇、蔣孝勇全都反對,而蔣經國在日記早就否認章家,但章萬安他爸還故意等小蔣那輩S光才去改。
順便再補充,章萬安的爸爸章孝嚴,有一個雙胞胎兄弟叫做章孝慈,章孝慈也是嚴正反對改姓的,所以章孝慈到S了都沒改姓蔣。
而章孝嚴是在雙胞胎兄弟章孝慈S後才去改,以免被雙胞胎兄弟的DNA踢爆。
反正簡單說全部相關人員,無論是蔣家還是章家,全都反對章萬安的爸爸章孝嚴改姓。
但章孝嚴還是硬改,而特權會過的原因是當時台北市長是馬英九😑
章孝嚴改蔣孝嚴之後,章萬安才改蔣萬安。
所以麻煩台灣人還是要有點常識好嗎⋯
P.s我上次去髮廊剪頭髮,旁邊一個很年輕的設計師聽到我跟我的設計師聊天,她說她真的不知道蔣萬安以前姓章,她說:「我以為你們講章萬安是開玩笑欸,髒萬安的意思,沒想到是真的」
所以這種兩千後近代台灣時事不講怎麼行?
附圖為蔣萬安自己公布的綠卡資料,上面寫著章萬安。
#github #macshot 这可能是目前最强的开源 macOS 截图工具:MacShot 🚀
github.com/sw33tLie/macshot
告别付费订阅,它不仅原生、轻量,还把 CleanShot X 和 Shottr 的活儿全干了:
✅ 自带 18+ 标注工具
✅ 录屏支持 MP4/GIF(最高 120fps)
✅ 长截图、OCR 提取文字
✅ 一键美化截图(加渐变背景)
✅ 支持 S3/Cloudflare R2 自建图床
最硬核的是它不用 Electron,纯 Swift 编写。推荐给各位“工具控”!
Its open source, so anyone can contribute, fork it, or customize it: 👉 github.com/pluk-inc/md-previ…
Download: md-preview.app
花了一天时间,把我自己常用的 Skill Release 成一个新玩意叫 Waza 在日语中是 技(わざ) 的意思,常用于武术领域的招式,第一次开源一个没有代码只有 md 的产品,在没有 AI 的年代对于程序员而言是很羞耻的 github.com/tw93/waza
之前 Superpowers 出来的时候,我安装一次就卸载了,感觉太重了,不是很适合我,会有不少人给我推荐 "你知道 Superpowers 吗?这个都不用那你就不潮流了,非常牛逼",后面发现了 gstack,好了不少,但还是太多了,还是不习惯,我期待简单好用,同时清楚它在做什么。
所以我按自己的习惯做了 Waza,对我而言装上这一套就够了,其他 skill 不用再折腾,不多不少刚好够用,后面有新的迭代可以持续优化下去。8 个 skill 对应我认为在 AI 时代一个好的工程师应该具备的 8 个能力:
1、会思考,AI 写代码很快,但方向错了越快越远,好的工程师在动手前会先质疑问题本身,压测方案,脑子里有清晰的架构再让 AI 去执行,/think 就是把这个习惯固定下来。
2、会设计,做产品不只是把功能实现了,AI 生成的东西很容易千篇一律,好的工程师对交付物有审美要求,出来的东西要有明确的设计方向,/design 做的就是这件事。
3、会排查,AI 改 bug 最容易陷入"改了试试"的循环,好的工程师遇到问题会系统化定位,确认根因再动手修,一次到位,这个习惯我沉淀成了 /hunt。
4、会检查,AI 生成的代码更需要人来把关,合并前先审一遍 diff,能自动修的修掉,需要判断的归拢到一起,用证据验证而不是凭感觉收工,这个是 /check。
5、会阅读,好的工程师习惯读一手资料而不是二手总结,把 URL 或 PDF 转成干净的 Markdown 直接进工作流,/read 做的就是这件事。
6、会写作,技术再强,写不清楚别人就接收不到,好的工程师能把学到的、想表达的东西清晰地传递给对应的受众,/write 帮你把这一步做好。
7、会学习,AI 时代技术迭代更快,进入一个陌生领域不是刷几篇文章就完了,而是收集、消化、提纲、初稿、打磨、发布,用输出驱动学习,/learn 就是这套流程。
8、会维护,好的工程师不只关注业务代码,工具链本身也需要体检,CLAUDE.md、rules、hooks、MCP 这些配置感觉不对的时候跑一下 /health 就知道问题在哪。
Nelson retweeted
Wow, this tweet went very viral!
I wanted share a possibly slightly improved version of the tweet in an "idea file". The idea of the idea file is that in this era of LLM agents, there is less of a point/need of sharing the specific code/app, you just share the idea, then the other person's agent customizes & builds it for your specific needs.
So here's the idea in a gist format: gist.github.com/karpathy/442…
You can give this to your agent and it can build you your own LLM wiki and guide you on how to use it etc. It's intentionally kept a little bit abstract/vague because there are so many directions to take this in. And ofc, people can adjust the idea or contribute their own in the Discussion which is cool.
LLM Knowledge Bases
Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So:
Data ingest:
I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them.
IDE:
I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides).
Q&A:
Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale.
Output:
Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base.
Linting:
I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into.
Extra tools:
I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries.
Further explorations:
As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows.
TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.
Nelson retweeted
🚨📕 THE BOOK OF ELON IS NOW LIVE!!! 🎉🚀
This is the book we WISHED @elonmusk would write…
“All of Elon's most useful ideas, in his own words.”
Learn directly from the world’s greatest entrepreneur, like you’re sitting across from him at dinner.
It took FIVE YEARS to make this for you.
Because it's built from hundreds and hundreds of Elon's public appearances.
I went through 3,000,000+ words to collect the most useful and timeless ideas.
The final book is ~50,000 words.
Every word is USEFUL.
(This is what I do. My first book, The Almanack of Naval Ravikant, is one of the top 100 most highlighted books of all time on Kindle.)
Then, I spent $50,000+ on editing and design so it looks and feels beautiful.
Then…
> Foreword by @naval.
> Visuals by @jackbutcher.
> Blurb from @mrbeast.
> Published by @scribemediaco.
> And yes, approval on this idea from Elon himself, thanks to @samteller.
I went Maximum Effort to make this an all-timer.
We got 10/10 on reviews from early readers, then worked on it for ANOTHER YEAR.
Why so much effort?
My mission is to create One Million Musks.
For a generation to lift our gaze and build, so our grandchildren live in a world beyond our wildest dreams.
I’m an independent author.
I don’t get an advance.
I risk my own time and money to make these books.
Then we give away millions of them. Digital versions are free.
I believe this book can benefit every human, and if you can’t pay five bucks for it, I want to personally gift it to you.
Because I know it is useful.
Useful how?
You may be seeking purpose, a mission worthy of your life’s effort.
You may have a clear purpose and seek the tools for success.
You will find both in this book.
Get the benefits of Elon’s entire life of hard-won lessons in a five-hour, easy read.
(I checked, it’s a 5th-grade reading level.)
You’ll feel personally mentored by the greatest entrepreneur in history.
Click below to buy it now on Amazon, Audible, or directly from me.
Amazon: amzn.to/47avSuh
Audible: lnkd.in/gi_7HrFP
Me: lnkd.in/gS2xWUWH
If you’re not sure it’s worth $4.99 yet, just start reading the free version.
PLEASE take 6 seconds to Like, Bookmark, and Repost.
Even better: send this to your friends, team, or Group Chats!
I guarantee this book will improve their lives.
Spread the word!
Every little thing helps.
Your support spreads good ideas around the world, helping people and making the future better for everyone.
Thank you!
Forward. Together.
Nelson retweeted
复古的界面布局,丝滑的加载速度和刷推体验,默认去广告无算法的时间线,新推文不再自动滚动置顶,时间线强迫症的福音,内置视频下载,整合了地理位置显示。用了一圈插件,还是这个最符合我使用习惯
github.com/dimdenGD/OldTwitt…
Nelson retweeted
1920年在八田與一的設計下開始興建嘉南大圳,但在泥沙淤積、颱風和地震的影響下,於2009年斷裂
在民進黨政府二年多的努力下,
百年後將濁幹線和北幹線連結起來,這是五十年最偉大的水利工程
這麼好的事情,我們要幫忙宣傳,讓台灣人都知道



































