正在加载视频...

视频加载失败

I installed a new Visual Studio Code extension to help me write code. But this extension doesn't get in your way. It doesn't try to write code for you. It only gives you hints and recommendations about your code. I like that. Like a second pair of eyes, looking...

101,068 次观看 • 2 年前 •via X (Twitter)

11 条评论

Fernando 🇮🇹🇨🇭 的头像
Fernando 🇮🇹🇨🇭2 年前

Nice. I didn't know about this VSCode extension. I'll check it out, thanks!

Wole 的头像
Wole2 年前

These are the type of solutions we need to work smarter and faster. Thanks for sharing @svpino

Louie Bacaj 的头像
Louie Bacaj2 年前

I feel like the kinds of dev tools we’ll have & be able to use are about to level up by orders of magnitude. This was a cool one Santiago. Does it work with many languages or just python?

Santiago 的头像
Santiago2 年前

Typescript, Python and golang

Francesco Ciulla 的头像
Francesco Ciulla2 年前

I'll try it out, thanks Santiago

Hesam 的头像
Hesam2 年前

seems very exciting, have you also tried cursor IDE?

Santiago 的头像
Santiago2 年前

I have, yeah! I actually spent a few months using it, but I stopped because I needed to try all of these AI tools, and I needed a blank Visual Studio code for that. Cursor is awesome!

Traycer 的头像
Traycer2 年前

Great to see you using Traycer, Santiago! 🚀 By the way, we've recently added support for Golang, so that more developers can benefit from Traycer.

Santiago 的头像
Santiago2 年前

Cool!

stuxnet_juma254 的头像
stuxnet_juma2542 年前

Seems like the extension hasn't been enabled globally Here in Kenya I can't find it

Traycer 的头像
Traycer2 年前

@svpino Hi @SimonJuma88, we did not place any country specific restrictions. We will double check at our end and let you know

相关视频

This might be the best "AI Engineer" I've tried so far. ​ I'm an old school developer who started 30 years ago. I feel very uncomfortable letting AI take control of my code, but for the sake of science, I spent two hours building an application that took me weeks to build a couple of years ago. ​ I used Pythagora, a brand new tool backed by Y Combinator. They just released to the public. ​ Keep in mind that I use AI every day to write code, but Pythagora is something different: it's a tool that leads, and uses you—the human—as the copilot. ​ I go into more details in the video, but here is the TLDR; ​ 1. Holy molly! We've made a ton of progress on this front! This is way better than Devin when I tested it a few months back. ​ 2. Love the approach of generating a plan with sub-tasks before writing any code. ​ 3. The tools never tries to do too much: it tackles every small task one at a time, and gives you instructions so you test everything. ​ 4. It does exactly what you'd do when it gets stuck: writes a bunch of logs and uses those to correct itself. Pretty neat! ​ 5. It's fast. It runs locally. It's an extension to Visual Studio Code. ​ I'm impressed, but I don't think this tool is for me. ​ I'm not the type of developer who's ready to relinquish control. I felt I had no connection with the code because I didn't write it. It was not my code. ​ I know many people who don't care about this. I know many people who will get tremendous value out of Pythagora. I hope they keep pushing the limits, providing feedback, and helping this get to a point where old folks like me feel more comfortable using it. ​ Don't take my word for it. The best thing you can do is to give it a try and see how you feel using it. ​ Thanks to the team who built this, for all of the explanations and support, and especially, for sitting and listening to my dumb questions for 2 hours while I tested this.

Santiago

212,056 次观看 • 1 年前

Introducing /visual-plan - a skill to generate rich, visual plans for Claude Code and Codex. Plan mode in Claude Code is incredible. But I always find my eyes glazing over when it gives me this huge markdown essay in my terminal. I found I can make much better visual plans with reusable components. So I made a skill called `/visual-plan`. It generates plans as MDX with visual, interactive components. Diagrams, interactive API specs, schema design changes, annotated code, and even pan and zoomable wireframes. So for any UI work, you can look at a wireframe first, comment on it, iterate, and then have the agent work. I’ve found this to be a much more intuitive interface for reasoning about what the agent is doing. It’s somewhat inspired by that popular post about how HTML is better than Markdown. But HTML can be slow and verbose to write. And it doesn’t look good checked into a repo. This has really made me feel like humans and engineering are entering a new abstraction phase, where we reason about things at the plan level. As long as the plan is good, agents are getting more and more reliable at executing on it. Almost to the degree that we trust the C compiler to compile to assembly reliably. Plans are the new intermediate representation. I also made a skill for the reverse of this, called `/visual-recap`. After the agent works, it gives you a recap of everything it did. Same idea: wireframes, interactive API specs and diffs, schemas, annotated code, etc. So now when you’re reviewing what the agent did for you, or looking at a pull request of somebody else’s code, you can see a visual recap instead of just reading a wall of text. It’s all free and open source. You can find it on my GitHub. Will link to it in the reply because we all know how dumb these algorithms are with links.

Steve (Builder.io)

124,701 次观看 • 1 个月前

Ever seen a fresh (20x) Claude Max account's 5-hour usage allowance get drained in ~14 minutes? Feast your eyes on my bizarre life now with this screen recording of a recent live work session, something I've gotten at least 100 requests for over the past month. Maybe you can understand now why I need so many accounts and how I can work on so many different projects. You can also see the truth of what I was saying recently about how, once your plan is done and the beads made and polished, it's mostly just machine-tending the swarm that doesn't require much thought. Lots of just telling it to get the next bead and work on it, to review code, to re-read AGENTS dot md after a compaction, etc. And you can see how I use gemini-cli for code review. I give Google a lot of crap for the harness being broken and the capacity overloads, but when it works, it's actually really good for this code review use case. I don't usually let it write new code, though, because I think Opus and 5.2 do a better job. Also, sorry the recording is a bit blurry; I have a 5K resolution monitor and screen recordings usually are hard to watch from it. And btw, this really wasn't that normal of a session for me, it was more frenetic than usual, because I don't want to dox myself or my clients by accident. Hence all the ceaseless terminal tab swirling. I usually do more planning work while this stuff is going on, but I wanted to minimize the chances of leaking important information. That's also why I didn't refresh the Gemini login in the WezTerm window, which killed me, trust me. It's the reason I hate doing these screen recordings in the first place; it kills my productivity. Anyway, hope you liked it. I will also post to YouTube, see reply for link. Thanks for watching.

Jeffrey Emanuel

86,071 次观看 • 6 个月前