Loading video...

Video Failed to Load

Go Home

This is how i build everything now. Before the agents touch a line of code "before you do any building make 10 mock ups in html of how we can make it look" I then pick a path and ask for more mockups until I feel happy with the...

25,695 views • 4 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

There's so much focus on "how can AI do my work for me?" I think the more important question is "what work can I now do with AI that I would have never attempted before?" Earlier this year I wrote freestiler, a vector tiling engine for R and Python, with the help of Claude and Codex. I knew what the ideal engine looked like and how it would work at a high level. I didn't know how to put it together, and I don't know Rust, the language I wanted under the hood. Previously I would never have attempted this project as the ROI wasn't there. It would have taken me a year or more to learn the internals of a vector tiling engine and enough Rust to implement one. With Opus-level models, I could take it on. freestiler now powers all my vector tiling pipelines, including the map below rendering 143 million jobs from LODES, and it has 114 GitHub stars. Building this way has required a different set of skills. I don't review the code line by line. I set up adversarial agents to do that and write the test suites. What I review is the architecture, the behavior, and the results. Agent teams surface findings and explain their reasoning; I evaluate and critique. My job isn't to stress over code formatting, but instead to focus on questions like whether the engine is designed right, whether the output is correct, and if the UX makes sense. This means that I haven't "replaced my work." I've taken on entirely new work, with the help of agents, that I would have never done otherwise. It has taken some getting used to shipping code I haven't personally typed. In the old way of working, I built understanding through writing that code. Now I build understanding through managing the project - writing a spec, reviewing structure, evaluating UX. And that's helped me think a whole lot bigger in terms of what I can now do.

Kyle Walker

13,740 views • 22 days ago

🖤: "Lastly, could you please do a 3-line acrostic poem for me?" 🩷: "No, no. 3-line acrostic poem is a bit of a burden for me. I actually have something I want to say to Hamin." 🖤: "Oh you do? What is it?" 🩷: "Of course I do." 🩷: "Honestly, I'm someone who express myself more to Hamin, right?" 💙🖤: "Yeah." 🩷: "(There's a reason) how that could happen. Hamin is actually a maknae but even so he takes care of the hyungs very well. To me, also, I could feel how I'm being taken care of (by him) a lot. As a fellow Dance line, when we work and make choreography (together), we rely on each other a lot. I also rely on him a lot. Usually, Hamin also like 'how is it? how is that?' (discuss things) to me and it makes me feel good. So now, I feel like without Haminnie I can't do anything. So on his birthday today, I want to express my gratitude to him." 🩷: "Now, I can't do anything if you are not there." 💙🖤: "Woah..." 🩷: "That's the truth. As PLAVE member too, when we work together, when you are there... I don't know. I'm just glad you are here." 🖤: "Me too." 🩷: "It's the truth, really." 🖤: "Same goes for me." 🩷: "From the bottom of my heart." 🖤: "For Bamby hyung to be able saying things like this seems hard (for him) so I could also feel how much he likes me." 🩷: "Exactly, I hope you can feel more (of his affection) but it seems like I can't show much of it." 🖤: "No, no. As for me, of course I feel the same way for other members too, but there's something that makes me feel good towards you. So I want to make you feel good too." 🩷: "That's right, we always have a lot of fun." 🖤: "Even though we see each other all the time, hearing this words from you..." 🩷: "It feels different." 🖤: "It does and I like it." 💙: "WHAT THE?? ISN'T IT HEART SIGNAL?????" 🩷: 😂😂😂 🖤: "Ahh... You are not leaving yet???"

it is rain

27,509 views • 1 year ago

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,409 views • 1 month ago