How 10x Developers Actually Use AI

nunomaduro| 00:10:29|Mar 30, 2026
Chapters9
The speaker emphasizes preferring first party tools and seeks drastic improvements when changing tooling.

AI tools work best when they’re clearly suited to the task, and Nuno and Ian argue that Claude shines for reliability while Codeex excels at power—but you're choosing tools by how well they fit your workflow, not brand loyalty.

Summary

Nuno Maduro’s chat with Ian Del Valle dives into how they actually use AI in software work. They compare Claude and Codeex, noting Claude’s user-friendliness and reliable answers versus Codeex’s deeper, more complete outputs that can sometimes be overly confident. They emphasize sticking with first-party tools (Codeex CLI, Cloud CLI, GitHub Desktop) and using AMP as a third-party harness for multi-model querying. The conversation also touches on practicalities like IDE choices, editor preferences, and how AI impacts code review, debugging, and project navigation. Ian discusses how he relies on Claude for most tasks, but still uses Codeex for specific, more demanding scenarios, while Nuno leans heavily on Cloud Code Opus 4.6 and the built-in CLI experiences. They also speculate about future editor paradigms, favoring AI-assisted prompting review over traditional project folds, and they share real-world habits like using GitHub Desktop for PR reviews and Typora for Markdown editing. The overall takeaway is that 10x developers optimize their stack for speed, reliability, and a strong integration between AI, tooling, and environment—prioritizing first-party surfaces and practical workflows over the latest hype.

Key Takeaways

  • Claude is favored for frequent, reliable results and ease of use, making it the go-to for day-to-day questions and quick decisions.
  • Codeex is valued for deeper, more complete reasoning but can be overly authoritative and occasionally misleading, leading to cautious use in critical tasks.
  • AMP provides built-in tooling (The Oracle and The Librarian) that streamlines model evaluation and GitHub search, enhancing solo projects like Solo.
  • Nuno’s preferred setup is Cloud Code + Opus 4.6, with a strong preference for first-party toolchains over third-party desktops or complex integrations.
  • GitHub Desktop is trusted for code reviews and PR-driven workflows, sometimes even when working solo, to gain different contextual views.
  • Typora is adopted for focused Markdown editing, replacing clunky transitions between editors and large IDEs for document work.
  • The editors of the future should prioritize prompting review experiences and AI-assisted change review rather than traditional file-and-folder navigation.

Who Is This For?

Essential viewing for developers integrating AI into large codebases or solo projects who want concrete tool opinions and practical workflow optimization, not hype-filled endorsements.

Notable Quotes

"Claude is way more friendly and way easier to use and generally makes good decisions pretty often."
Nuno compares Claude favorably on usability and reliability.
"Codeex I feel like is a little more neck beardy and does things with a little more completeness but it's just not as nice to use."
Nuno contrasts Codeex’s depth with user experience.
"The Oracle does deep investigation and research. And then they have one called the librarian, which has been incredibly useful as I'm building solo."
Discussion of AMP’s built-in tooling for model evaluation and search.
"I just feel really good with this tool set of cloud code and cloud code opus 4.6 for everything and uh really works well."
Nuno states his preferred AI stack.
"GitHub desktop is awesome. I use even when I'm solo on a project, I will open PRs just so I have a different environment to look at it in."
Value placed on their PR workflow even when solo.

Questions This Video Answers

  • How do Claude and Codeex compare in reliability and usability for real-world coding tasks?
  • What role does AMP play in multi-model AI workflows for solo developers?
  • Why do some developers prefer GitHub Desktop over CLI git for code reviews?
  • What editor paradigms could replace traditional IDEs in an AI-assisted future?
  • Which AI tools and versions are best for PHP projects and why?
AI-assist toolsClaudeAICodeexAMP (AI harness)GitHub DesktopCloud CodeOpus 4.6VS CodePHPStormSublime Text (editor preferences)
Full Transcript
So I use codeex CLI, cloud CLI, I use GitHub desktop. If I'm going to change [music] my tooling, it needs to be drastically better. The thing I don't like about code, I feel like it misleads you [laughter] more. IDE is in the way that we know them today. They are over. What's up everyone? Just a reminder that more than 50% of the people watching this video are not subscribers. So if you enjoy my content, [music] subscribe the channel. And now enjoy the video. I got to get my Celsius on to match the Nuno energy. What's up, chat? While billing solo, which AI model have you end up using the most? The most in terms of lines of code written for Solo, it's probably Claude, but in terms of recency, it's probably Codeex. I find that they're they're good at different things. Claude is way more friendly and way easier to use and uh generally makes good decisions pretty often. Codeex I feel like is a little more neck beardy and does things like does harder things and does things with a little more completeness but it's just not as nice to use. Um I use all the first party CLIs. So I use codeex CLI cloud CLI. I don't use anything like uh the codeex desktop app or open code or anything like that. So I think a big part of my enjoyment comes from like the first party surface area and I like the cloud surface area but the codeex models are now they're now really good. You said that you use cloud code using cloud code and you use codec using codec cli. Yeah, I only use the stuff that they ship. The only third-party harness I use is AMP which is uh previously by SourceCraft. They're now their own company. Um, and AMP is similar to Open Code in that it is a harness around other people's models. I'll use AMP sometimes because they have really good built-in tooling. They've got a tool called the Oracle um that does like deep investigation and they they control the model. So, I have no idea what models they're using, which is interesting. The Oracle does deep investigation and research. And then they have one called the librarian, which has been incredibly useful as I'm building solo. And the librarian uh its main purpose is to search GitHub. And so I can be like, "Hey, I'm using Xterm.js. The biggest exterm app in the whole world is VS Code. I need you to use your librarian to go figure out how they are doing this in VS Code." And instead of like me saying uh go to github.com or like me cloning down VS Code, their librarian just handles it sometimes on the cloud, sometimes on my machine. So AMP has really good built-in tooling and their threading is very good but beyond that it's all it's all first party for me and Ian now going to you a little bit because you have done probably 10 times Laval new in the past year I would say so which a model you typically use to interact with old stuff but also to interact with the new stuff it's the same model different ones I'm curious mo mostly I'm using claude I like claude the best I agree it's not quite as powerful as codeex at this right now I mean I also like this kind of thing, right? Like Opus is going to have 4.7 come out, right? And then it'll be as good as codeex [clears throat] 5.4. It'll be a little better. Eh, do I need to switch back and forth constantly? I kind of like I like Claude, it's fine. It's more than sufficient for almost everything. Um, the thing I don't like about Codeex, while I agree it's kind of better uh some to a slightly better than Claude if you were just like, well, I'm just going to look at these answers. Uh, it often will like talk so authoritatively, but then it would be incorrect. And so I feel like it misleads you more than Claude does. Like Claude might just not do something, but like I feel like Codeex more often like actively misleads me. And so like that's the part I don't really care for. And so that's kept me mostly in Claude. I do use Codex a little bit here and there. I do especially use it with uh Aaron Francis's counselor's uh little app if you've seen that, but it's a little tool he put together that basically lets you give a question to a whole bunch of different AI platforms at once. Claw, Codeex, AMP, Gemini, whatever. So, send it out to a whole panel of experts. Each of them grinds on it. They all return uh a summary back of their findings and then the main thread AI, whichever one you could do it from any of them, but I usually do it from Claude, uh summarizes all that stuff and says, "Hey, the three of them agree on this and one of them disagrees and whatever." And so I still use Gemini and Codeex a lot as second opinions on what Claude's doing and planning and things like that. I feel like personally I've been using cloth code since it's out, you know, and I am one of those type of dudes where if I'm going to change my tooling, it needs to be drastically better. Just to just to give you an example, I was a term 2 user for years. Only when Ghostly came out, it took me a while to even change to Ghostly. But yeah, and personally feel that I'm using cloud code opus 4.6 for everything and uh really works well. you will have to give me like a very good reason to try anything else including codeex. Um because you know I'm just I just feel really good with this tool set of cloud code and cloud code. I must say though I was kind of in love with open code. Open code just it stopped working with cloud code for for a while and I had to just go back to cloud code and now do Eron do you remember when I asked you like which tool do you use to actually speak with a with a CLI? Mhm. So Cloud Code actually have that built in on the thing. You just press the space and you just talk with the CLI. So I'm just using that all the time. So Cloud Code CLI with Cloud Code Opus 4.6 is my go-to. And I want to give you my take on IDs and you guys let me know what you think about this ideiext, PHP Storm, VS Code, like all the traditional editors. You just open a project and you see the folder structure on the left and you see the full main editor on the middle. Um, I think that concept is gone and I think like what I really want from an editor and I don't think this problem is still solved yet. I want an editor to be focused on the prompting review experience, you know, but not like what this this prompt did. More about like what I'm about to commit out of this session, out of this interaction. So I don't think uh editors have solved it yet. So my currently current IDE is Sublime Text for quick editing and then I use uh PHP Storm for real projects. You know if I have to open a real project. So you know you starting with you a little bit you have you work with projects with more than 10 years some of them probably even longer than that. 20 years you know old man river. Yeah. So when you interact with those projects for bug fixes for example can you do it through AI or you still go back to this huge IDE to actually get stuff done when I am in there glass shield on you know [laughter] I don't look at the code the the AI does the code now I will say in terms of IDE the number one reason I'm in there is like to look at environmental files or to add something to the environmental file like right so like I'll just pop in sublime text for that I am a PHP storm guy so I do a PHP storm for like I really need to dig in there and like navigate around nicely, right? Cuz like it knows all the PHP stuff and you can navigate back to the classes and all the stuff. I do do that occasionally, but for the most part, yeah, I'm just an AI and I agree with you that like there's something that needs to come post IDE, which is like what the code that the AI generated that like lets me review it quickly because sometimes it's a lot of files, right? And like Right. So you kind of need an AI layer on that. I almost feel like like hey, like these are the big changes. you should look at this big change like or these are the important bits like this isn't we made this it's one line but it's like a really important one line like you should check this out so I do feel like there's like a another evolution to come to some of that stuff but cuz yeah I agree I I mean save for a few rare instances I haven't opened PHP storm since Thanksgiving to be honest um holy I do I use GitHub desktop um right now to review I love the GitHub desktop I love that tool so much. I don't care what anybody says about you should use git on the command line. Don't care. GitHub desktop is awesome. I use even when I'm solo on a project, I will open PRs just so I have a different environment to look at it in. So if it's like a small thing, I'll just look at GitHub desktop and then just yolo domain. But if it's kind of like a big refactor, I will have the agent open a PR just so that I can go into a different environment and look at it and feels like it puts you in a different mindset. Um, and opening a PR, you can then tag like Code Rabbit or GPile or GitHub uh co-pilot and say like review this PR. And so that's kind of a nice surface to do that. I've just recently downloaded an app called uh Typora. um don't know who they are, never spoken to them, but Typora is a specific markdown editor. That's it. That's all it does because a lot of the files that I need to edit or look at or read, they're markdown now. And so I needed an app to be like, actually, I want to open this research document or this plan document that one of the clankers wrote and like modify it just a little bit or at least read through it in a nice uh readable way. And I got tired of double clicking on markdown files and having Xcode open for eight minutes. And so I bought uh this little app called Typora that's just a just a little markdown editor. Uh a lot of people's using Sublime Text 2, PHP Storm, Vim Diff, Dreamweaver. It's been a while. Okay. Since I last met Yeah, the name Studio Fusion Studio for life. Oh my god. Notepad++. A lot of people using Zed, which a lot of people mentioned to me. I never use it. Did you guys ever use Z? I tried it the other day a couple weeks ago. See, to me, zed is like it's not as minimal as Sublime or BBEdit and but it's like right, you know, but it's less than PHP Storm. So, it's like kind of a weird I don't really get it basically. Um, so yeah, [laughter] it didn't it didn't stick with me. It feels like too much of a middle ground. Like kind of just want super fast and minimal or give me the whole thing with all the options if I if I need that, you know? So,

Get daily recaps from
nunomaduro

AI-powered summaries delivered to your inbox. Save hours every week while staying fully informed.