正在加载视频...

视频加载失败

I've built a bunch of tools this summer to move my whole workflow to using things that are "pure text" so I can use AI on top. Here's the first: a modern paper reader. PDFs suck. Ugly, terribly interface, big files, fixed. I want papers that are adaptive, interactive,...

23,310 次观看 • 1 年前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Everyone's talking about vibe coding without looking at code. I was skeptical. I decided to give it a shot on a challenging problem and was blown away by what I could accomplish in 8 hours. I'm not skeptical anymore, but I also do NOT think it kills SaaS Notes: - I tried to replicate some of my favorite features from the Solve-It platform as a jupyter extension - I've tried this many times before, and it didn't work. - I gave my agent specific testing tools that I packaged as skills. I used AI to write the skills. I found the right testing workflow for this Jupyter extension by having AI peruse lots of other extensions and the Jupyter source code. - I had the AI write and maintain a large suite of tests the whole time. I think this was important in keeping the AI on track. - I watched the diffs and the thinking traces as they streamed by. From time to time, I would see something very suspicious like " try ... except: pass" And would stop the AI and tell it to stop this behavior. Then trigger a comprehensive code review using AI. - Most importantly, I don't think this kills SasS at all. Even if I can create software that replicates some of my favorite features, there is an insanely long tail of paper cuts and features I don't want to manage. The models and capabilities are improving so fast that I don't want to constantly tune everything. So I would rather leave that up to people who are focused on that daily and have good taste, with the knowledge that it has been battle tested against many users.

Hamel Husain

48,930 次观看 • 7 个月前