WEBVTT 00:00:01.520 --> 00:00:03.520 Morning. 00:00:03.520 --> 00:00:04.040 >> Good morning. 00:00:04.040 --> 00:00:06.560 >> Yeah, I'm I'm back at work after a week 00:00:06.560 --> 00:00:08.600 holiday from Oh, you got You grew a 00:00:08.600 --> 00:00:11.040 beard. 00:00:11.040 --> 00:00:11.680 Oh, yeah, again. 00:00:11.680 --> 00:00:13.960 >> uh no, I just I'm I haven't shaved for a 00:00:13.960 --> 00:00:16.440 while. 00:00:16.440 --> 00:00:18.000 >> Since you've been 00:00:18.000 --> 00:00:19.360 uh 00:00:19.360 --> 00:00:20.720 I don't know. You 00:00:20.720 --> 00:00:22.920 You didn't giving me a lot of AI 00:00:22.920 --> 00:00:24.920 updates, so I guess you're you're deep 00:00:24.920 --> 00:00:26.320 in it. 00:00:26.320 --> 00:00:28.960 >> You were You were like on holiday, I'm 00:00:28.960 --> 00:00:31.680 addicted, and so I I started to No, you 00:00:31.680 --> 00:00:34.120 said like let's let AI get get like some 00:00:34.120 --> 00:00:36.400 rest. So, I started to to be like, 00:00:36.400 --> 00:00:38.040 "Well, haven't you seen the news? 00:00:38.040 --> 00:00:39.300 There's so much happening." 00:00:39.300 --> 00:00:41.520 >> [laughter] 00:00:41.520 --> 00:00:43.600 >> So, what what did I miss? I was hoping 00:00:43.600 --> 00:00:45.160 you could brief me before I go to this 00:00:45.160 --> 00:00:48.200 AI conference in London. 00:00:48.200 --> 00:00:49.080 >> Yes, so 00:00:49.080 --> 00:00:51.120 >> What's the hardest thing? 00:00:51.120 --> 00:00:53.200 >> The hardest thing, to be honest, is the 00:00:53.200 --> 00:00:55.280 um is the actual dynamic workflows in 00:00:55.280 --> 00:01:00.080 Claude Code. They seem to work. 00:01:00.080 --> 00:01:02.160 >> Okay, so 00:01:02.160 --> 00:01:04.680 I've been using workflows I mean, I've 00:01:04.680 --> 00:01:06.840 been wanting workflows, and I guess I've 00:01:06.840 --> 00:01:09.840 been getting my workflows 00:01:09.840 --> 00:01:13.520 Basically, I was using that NA N8 00:01:13.520 --> 00:01:14.480 N 00:01:14.480 --> 00:01:15.480 I don't know how to pronounce the 00:01:15.480 --> 00:01:16.800 project's name. 00:01:16.800 --> 00:01:19.080 I using NA N for a little bit, but then 00:01:19.080 --> 00:01:21.400 I ended up just converting my 00:01:21.400 --> 00:01:24.680 automations to system D. 00:01:24.680 --> 00:01:25.680 But, 00:01:25.680 --> 00:01:27.360 what do you use Cloud 00:01:27.360 --> 00:01:30.880 workflows for? 00:01:30.880 --> 00:01:31.840 >> Okay, um 00:01:31.840 --> 00:01:33.440 >> there? What I 00:01:33.440 --> 00:01:34.520 >> Can you hear me? 00:01:34.520 --> 00:01:35.000 >> Yeah, yeah. 00:01:35.000 --> 00:01:37.440 >> Yes. Yeah, sorry. I got a message and I 00:01:37.440 --> 00:01:40.160 got distracted. So, um basically, what 00:01:40.160 --> 00:01:41.720 happened 00:01:41.720 --> 00:01:42.480 um 00:01:42.480 --> 00:01:45.920 they launched Opus 4.8 on I think 00:01:45.920 --> 00:01:48.920 Vietnam it was Friday morning. 00:01:48.920 --> 00:01:51.280 And with it, in Claude Code, they 00:01:51.280 --> 00:01:53.000 released dynamic workflows, which is a 00:01:53.000 --> 00:01:58.280 tool that can execute uh JavaScript file 00:01:58.280 --> 00:02:00.920 that um 00:02:00.920 --> 00:02:03.080 the JavaScript script 00:02:03.080 --> 00:02:04.720 >> that on a schedule, all right, I'm 00:02:04.720 --> 00:02:05.479 assuming. 00:02:05.479 --> 00:02:07.600 >> No, no, not on a schedule. Dynamic 00:02:07.600 --> 00:02:10.600 determinate dynamic workflows 00:02:10.600 --> 00:02:14.560 is lets the agent take your context then 00:02:14.560 --> 00:02:17.320 build a graph of agents and each agent's 00:02:17.320 --> 00:02:19.440 prompt and then 00:02:19.440 --> 00:02:23.200 execute it. So, the tool just runs 00:02:23.200 --> 00:02:25.320 a deterministic workflow that gets 00:02:25.320 --> 00:02:27.560 dynamically generated depending on the 00:02:27.560 --> 00:02:31.400 tasks at hand. So, I with the spec 00:02:31.400 --> 00:02:33.200 driven development workflow, like for 00:02:33.200 --> 00:02:34.920 example, if if we put this in terms of 00:02:34.920 --> 00:02:36.440 spec driven development workflow and 00:02:36.440 --> 00:02:38.360 our, you know, we are familiar with Open 00:02:38.360 --> 00:02:41.200 Spec or Spec It, specifically Spec It, 00:02:41.200 --> 00:02:43.240 they you have the specify phase where 00:02:43.240 --> 00:02:44.680 you have the user stories, then you have 00:02:44.680 --> 00:02:45.600 the 00:02:45.600 --> 00:02:47.680 planning and research phase where you do 00:02:47.680 --> 00:02:49.680 some tech spikes, you identify exactly 00:02:49.680 --> 00:02:50.760 what is the libraries you're going to 00:02:50.760 --> 00:02:52.520 use, what's the tech stack, how is the 00:02:52.520 --> 00:02:54.959 technical implementation, and then 00:02:54.959 --> 00:02:56.880 usually you generate 00:02:56.880 --> 00:02:59.200 a task graph. Like first we have this 00:02:59.200 --> 00:03:01.120 phase of like foundational setup and 00:03:01.120 --> 00:03:02.320 then we have another phase of 00:03:02.320 --> 00:03:04.280 implementing the the necessary 00:03:04.280 --> 00:03:06.440 functionality modules required for this 00:03:06.440 --> 00:03:08.480 first user story, and then we have the 00:03:08.480 --> 00:03:09.880 second user story, and then we have 00:03:09.880 --> 00:03:11.360 priorities and things that we can do in 00:03:11.360 --> 00:03:13.600 parallel and all that, right? And and 00:03:13.600 --> 00:03:15.840 then we go into an implementation phase 00:03:15.840 --> 00:03:18.959 which goes through this preset 00:03:18.959 --> 00:03:22.360 you know, graph of tasks to execute, and 00:03:22.360 --> 00:03:24.440 you basically have a prompt that loads 00:03:24.440 --> 00:03:26.320 it, right? So, you can get rid of that 00:03:26.320 --> 00:03:29.160 task breakdown and implementation step 00:03:29.160 --> 00:03:31.800 completely now. You can just go straight 00:03:31.800 --> 00:03:33.440 Yeah, you don't need to do the task 00:03:33.440 --> 00:03:34.760 breakdown anymore because you're using 00:03:34.760 --> 00:03:36.720 Opus. Before 00:03:36.720 --> 00:03:38.640 you would do the task breakdown and you 00:03:38.640 --> 00:03:40.560 would review the task and you say, "Yes, 00:03:40.560 --> 00:03:42.720 I agree. User story one is this module 00:03:42.720 --> 00:03:43.880 that needs to be built first. The 00:03:43.880 --> 00:03:45.840 priority is correct. We can skip the 00:03:45.840 --> 00:03:47.800 second part because that part is like 00:03:47.800 --> 00:03:49.720 nice to have." So, you would have this 00:03:49.720 --> 00:03:51.280 like ability to decide what you want or 00:03:51.280 --> 00:03:53.000 what you don't want on that on that 00:03:53.000 --> 00:03:55.040 implementation like multi multi phase 00:03:55.040 --> 00:03:58.000 plan. Um so I guess if you still want 00:03:58.000 --> 00:04:00.720 that, you you still get that because the 00:04:00.720 --> 00:04:02.920 the dynamic workflow will present to you 00:04:02.920 --> 00:04:06.280 exactly the phases and the the the the 00:04:06.280 --> 00:04:07.800 workflow that's going to get done. 00:04:07.800 --> 00:04:10.520 >> controls Does it also generate the tasks 00:04:10.520 --> 00:04:12.320 and the order of the tasks, I guess, 00:04:12.320 --> 00:04:13.200 right? 00:04:13.200 --> 00:04:15.840 >> Yes, it it it So in my case, because I 00:04:15.840 --> 00:04:18.000 give it I use it with Spec kit, it 00:04:18.000 --> 00:04:20.320 creates phase one tasks like phase two 00:04:20.320 --> 00:04:22.520 tasks. And each task is basically an 00:04:22.520 --> 00:04:24.760 agent that goes and does does a task. So 00:04:24.760 --> 00:04:26.800 in the past I was trying to run parallel 00:04:26.800 --> 00:04:29.960 agents that didn't work. But now today 00:04:29.960 --> 00:04:31.560 and a lot of people like working with 00:04:31.560 --> 00:04:33.120 Git work 00:04:33.120 --> 00:04:36.000 Git work trees or like using agent mail 00:04:36.000 --> 00:04:39.000 or agent communication to lock files. If 00:04:39.000 --> 00:04:40.640 you don't use work trees, that was all 00:04:40.640 --> 00:04:42.120 things that people were trying to do it 00:04:42.120 --> 00:04:44.600 on a single box to go and build with 00:04:44.600 --> 00:04:45.960 multiple agents and then have the 00:04:45.960 --> 00:04:48.360 coordination and all of that, right? Now 00:04:48.360 --> 00:04:50.040 with dynamic workflows, it's all done 00:04:50.040 --> 00:04:51.919 for you. 00:04:51.919 --> 00:04:54.560 The the the master agent does 00:04:54.560 --> 00:04:56.600 >> The The This is a cloud-only feature, 00:04:56.600 --> 00:04:58.560 right? So what are you going to support 00:04:58.560 --> 00:04:59.960 >> Yeah, and if you're on enterprise, you 00:04:59.960 --> 00:05:01.720 need to ask your admin to enable it 00:05:01.720 --> 00:05:03.480 because it by default dynamic workflows 00:05:03.480 --> 00:05:06.360 is disabled. It The main The main feed 00:05:06.360 --> 00:05:07.600 feedback 00:05:07.600 --> 00:05:09.680 from most people was that this is 00:05:09.680 --> 00:05:12.919 extremely expensive. Like in 20 minutes, 00:05:12.919 --> 00:05:14.400 it burns the equivalent of what would 00:05:14.400 --> 00:05:17.160 normally take me 4 hours to 00:05:17.160 --> 00:05:19.520 to to use because it spins up like 12 00:05:19.520 --> 00:05:22.240 agents to do the work. And the orchestra 00:05:22.240 --> 00:05:23.600 And then also merge agents. But you 00:05:23.600 --> 00:05:24.800 don't need to use it just for that, 00:05:24.800 --> 00:05:27.560 right? I also do it for like 00:05:27.560 --> 00:05:29.280 adversarial reviews. 00:05:29.280 --> 00:05:30.760 And 00:05:30.760 --> 00:05:32.400 I saw this very funny post from Antal 00:05:32.400 --> 00:05:34.720 Babenko about like you need three review 00:05:34.720 --> 00:05:38.280 agents to to come to a consensus. So you 00:05:38.280 --> 00:05:39.720 always need to spin up three of them and 00:05:39.720 --> 00:05:42.800 I was like Yeah, I mean I I I'm okay 00:05:42.800 --> 00:05:44.440 with one or two. 00:05:44.440 --> 00:05:46.840 Um but it's funny because you can you 00:05:46.840 --> 00:05:49.480 ask new ways to use agents. 00:05:49.480 --> 00:05:51.440 Well, it's more like 00:05:51.440 --> 00:05:53.600 the way Yeah, the way that you were 00:05:53.600 --> 00:05:55.920 using agents or that you everyone was 00:05:55.920 --> 00:05:57.560 building like their their own agent 00:05:57.560 --> 00:05:59.320 orchestration tooling. 00:05:59.320 --> 00:06:01.960 It's kind of like all been taken care of 00:06:01.960 --> 00:06:06.040 by this workflows solution. It's like I 00:06:06.040 --> 00:06:08.000 found it amazing because the workflows 00:06:08.000 --> 00:06:09.520 are generated and then they are 00:06:09.520 --> 00:06:11.160 deterministic. So you can save them. 00:06:11.160 --> 00:06:13.240 It's almost like swamp but built into 00:06:13.240 --> 00:06:15.320 cloud, right? It has its own little 00:06:15.320 --> 00:06:17.440 schema of of building a 00:06:17.440 --> 00:06:19.360 workflow and then you can save those 00:06:19.360 --> 00:06:21.560 workflows and you can reuse them and you 00:06:21.560 --> 00:06:23.840 can share them and and you can generate 00:06:23.840 --> 00:06:25.919 adversarial. So it will spin up three 00:06:25.919 --> 00:06:28.120 agents to do an adversarial review and 00:06:28.120 --> 00:06:29.640 then it will merge all of their findings 00:06:29.640 --> 00:06:31.720 into a single report. 00:06:31.720 --> 00:06:33.280 They find different things. I like I 00:06:33.280 --> 00:06:35.960 have three Opus 4.8 review agents 00:06:35.960 --> 00:06:38.200 running with a with a blind context 00:06:38.200 --> 00:06:39.960 validating the the constitution, 00:06:39.960 --> 00:06:41.480 validating the 00:06:41.480 --> 00:06:43.160 the user stories and the definition of 00:06:43.160 --> 00:06:45.120 tons that are derived from the 00:06:45.120 --> 00:06:47.480 acceptance criteria. 00:06:47.480 --> 00:06:48.640 To me they're like pretty much the same 00:06:48.640 --> 00:06:51.320 thing and on or from the functional 00:06:51.320 --> 00:06:52.919 requirements you you get that. 00:06:52.919 --> 00:06:55.520 >> Obviously it works well cuz I think I 00:06:55.520 --> 00:06:57.480 can sense your excitement. 00:06:57.480 --> 00:06:59.840 You're getting stuff done or 00:06:59.840 --> 00:07:01.000 >> Yes, 00:07:01.000 --> 00:07:02.760 I built quite a few agents. 00:07:02.760 --> 00:07:04.680 >> But the quality work. 00:07:04.680 --> 00:07:07.720 >> It is probably because these are Opus 00:07:07.720 --> 00:07:10.640 4.8 like high effort agents. You do need 00:07:10.640 --> 00:07:13.120 to be careful like make sure that you 00:07:13.120 --> 00:07:15.360 you confirm the model and you confirm 00:07:15.360 --> 00:07:17.120 the effort like by default it will 00:07:17.120 --> 00:07:18.800 inherit. So So if you're doing an 00:07:18.800 --> 00:07:21.880 orchestration and at like 4.8 extra high 00:07:21.880 --> 00:07:23.680 effort and then you you trigger a 00:07:23.680 --> 00:07:25.760 workflow, it's got if you don't tell the 00:07:25.760 --> 00:07:27.240 orchestrator to create a workflow where 00:07:27.240 --> 00:07:28.880 the model is defined for each workflow 00:07:28.880 --> 00:07:30.680 step, it's going to inherit the model 00:07:30.680 --> 00:07:31.880 and the effort and then it's going to 00:07:31.880 --> 00:07:33.800 burn like crazy. So you have to be 00:07:33.800 --> 00:07:34.800 mindful of that. 00:07:34.800 --> 00:07:36.520 >> So you're you're on the max plan. Have 00:07:36.520 --> 00:07:38.840 you managed to exhaust your tokens? 00:07:38.840 --> 00:07:41.720 >> I'm I'm getting there. Like I was 00:07:41.720 --> 00:07:44.320 it was resetting in 5 days and now I'm 00:07:44.320 --> 00:07:46.240 actually starting like on I'm on on the 00:07:46.240 --> 00:07:48.200 marker. I use this codex bar which gives 00:07:48.200 --> 00:07:50.520 me an indicator on on how much I I 00:07:50.520 --> 00:07:52.920 should be at if I I want to 00:07:52.920 --> 00:07:53.720 I'm exhausted. 00:07:53.720 --> 00:07:57.280 >> Basically your your life is basically 00:07:57.280 --> 00:07:58.480 um 00:07:58.480 --> 00:08:00.800 proportional to how much your token 00:08:00.800 --> 00:08:03.280 spend is is like you slow down when it 00:08:03.280 --> 00:08:05.560 when you come to the end. Or anyway, I'm 00:08:05.560 --> 00:08:07.000 getting 00:08:07.000 --> 00:08:15.480 Oh. 00:08:15.480 --> 00:08:17.720 >> Sorry, um hello. 00:08:17.720 --> 00:08:18.040 Hello. 00:08:18.040 --> 00:08:19.640 >> Yeah, you have you got you got some 00:08:19.640 --> 00:08:21.600 people around you? 00:08:21.600 --> 00:08:24.240 >> Yeah, my my bike front wheel was had had 00:08:24.240 --> 00:08:25.480 a leak. 00:08:25.480 --> 00:08:28.280 Yeah, no like I started to trust it a 00:08:28.280 --> 00:08:30.320 lot more. I feel like it's way more 00:08:30.320 --> 00:08:32.599 automated now. I can because you use a 00:08:32.599 --> 00:08:34.200 dynamic workflow, you set it to auto 00:08:34.200 --> 00:08:36.919 mode, you go for I went for breakfast 00:08:36.919 --> 00:08:39.080 and I see I I check my GitHub and I see 00:08:39.080 --> 00:08:41.520 comments happening like as I was eating. 00:08:41.520 --> 00:08:44.000 The auto mode just keeps going. Um I 00:08:44.000 --> 00:08:46.160 have a I have a few really really nice 00:08:46.160 --> 00:08:48.160 stories about auto mode like situations 00:08:48.160 --> 00:08:50.320 where I was very impressed by by it it's 00:08:50.320 --> 00:08:52.520 >> Yeah, yeah, I'm using auto mode. I I I 00:08:52.520 --> 00:08:55.760 had like a an alias for super cloud 00:08:55.760 --> 00:08:57.880 dangerously skip permissions but I never 00:08:57.880 --> 00:09:00.200 use it anymore. On auto auto does the 00:09:00.200 --> 00:09:01.600 trick. 00:09:01.600 --> 00:09:03.960 So yeah, it's 00:09:03.960 --> 00:09:06.320 So what does it do that impressed you? 00:09:06.320 --> 00:09:08.120 It gives you confidence. It's all like 00:09:08.120 --> 00:09:10.160 it tells you like I stopped this. 00:09:10.160 --> 00:09:11.800 >> Exactly like 00:09:11.800 --> 00:09:13.600 I mean, the thing is it does it blocks 00:09:13.600 --> 00:09:15.839 certain actions and then the the LLM 00:09:15.839 --> 00:09:17.520 tries to work around them and then auto 00:09:17.520 --> 00:09:20.480 mode like blocks them or the LLM the the 00:09:20.480 --> 00:09:21.760 auto mode gives it a good reason and 00:09:21.760 --> 00:09:24.680 then the LLM ask me but sometimes I it's 00:09:24.680 --> 00:09:26.560 been trying and it's like it tries three 00:09:26.560 --> 00:09:28.880 four times to circumvent auto mode and 00:09:28.880 --> 00:09:30.600 then it's it stops it says like yeah, 00:09:30.600 --> 00:09:32.520 I'm I'm not able to do this and it went 00:09:32.520 --> 00:09:33.839 really far. It went like way off the 00:09:33.839 --> 00:09:35.560 mark like what I what we went off and 00:09:35.560 --> 00:09:36.840 off and I was like no, no, no, stop. 00:09:36.840 --> 00:09:38.560 Your first action was correct." And the 00:09:38.560 --> 00:09:40.960 correct thing it needs to do is it needs 00:09:40.960 --> 00:09:43.360 to pause, and I need to say it 00:09:43.360 --> 00:09:45.560 explicitly. For example, 00:09:45.560 --> 00:09:47.720 um I was doing work on a development AWS 00:09:47.720 --> 00:09:49.840 account, and I asked or I said, "And 00:09:49.840 --> 00:09:51.600 while you're at it, check if staging is 00:09:51.600 --> 00:09:53.520 also aligned or would also face this 00:09:53.520 --> 00:09:55.400 issue." And so, while I was doing all 00:09:55.400 --> 00:09:57.680 the work, a little bit, you know, going 00:09:57.680 --> 00:09:59.760 down the context, it finally came to the 00:09:59.760 --> 00:10:02.120 point, "Let me go check staging." And 00:10:02.120 --> 00:10:04.040 Auto Mode says, "You can't. It's blocked 00:10:04.040 --> 00:10:07.320 because this is like um exploration past 00:10:07.320 --> 00:10:08.800 your scope. You're not You're You're 00:10:08.800 --> 00:10:10.360 working on dev. You're not supposed to 00:10:10.360 --> 00:10:13.280 go into other accounts." And and basic 00:10:13.280 --> 00:10:14.840 Yeah, and it stopped At that time, it 00:10:14.840 --> 00:10:16.680 stopped really nicely, told me, "I've 00:10:16.680 --> 00:10:18.040 been blocked because I'm going into 00:10:18.040 --> 00:10:20.360 staging." And it only allows it if I 00:10:20.360 --> 00:10:22.240 explicitly say, "Now go to staging and 00:10:22.240 --> 00:10:23.720 check." And then Auto Mode will say, 00:10:23.720 --> 00:10:26.280 "Okay, you're allowed to go." So, so 00:10:26.280 --> 00:10:28.520 that's uh one of the stories. 00:10:28.520 --> 00:10:28.680 Um 00:10:28.680 --> 00:10:29.200 >> Mhm. 00:10:29.200 --> 00:10:30.240 >> There was another one. 00:10:30.240 --> 00:10:31.680 >> But but but but it sounds like you're 00:10:31.680 --> 00:10:34.160 totally Claude red-pilled right now. I 00:10:34.160 --> 00:10:36.920 mean, it Do you ever use Codex and the 00:10:36.920 --> 00:10:37.720 the other 00:10:37.720 --> 00:10:39.880 >> I'm actually setting up a Hermes agent. 00:10:39.880 --> 00:10:41.600 I mean, my son is on summer holiday, so 00:10:41.600 --> 00:10:43.640 I'm asking him to set up Hermes for his 00:10:43.640 --> 00:10:45.240 exploration, and we're using our chat 00:10:45.240 --> 00:10:47.839 GPT Codex 00:10:47.839 --> 00:10:49.960 uh what for this, yes. Cuz otherwise, 00:10:49.960 --> 00:10:52.320 API cost on Anthropic would be insane. 00:10:52.320 --> 00:10:54.360 And in terms of like, do I try other 00:10:54.360 --> 00:10:56.640 tools? I'm still not hitting my budget 00:10:56.640 --> 00:10:58.280 with with Claude code, so I have no 00:10:58.280 --> 00:11:00.520 incentive. Like, if I do, and I still 00:11:00.520 --> 00:11:02.240 have budget, like I used to have budget 00:11:02.240 --> 00:11:04.360 on Gemini CLI, but apparently that's 00:11:04.360 --> 00:11:05.839 been completely locked down, and the 00:11:05.839 --> 00:11:08.360 cost has gone up. And Codex is probably 00:11:08.360 --> 00:11:10.080 the only other one that I would use, and 00:11:10.080 --> 00:11:11.720 I'm trying to get use out of it with 00:11:11.720 --> 00:11:13.040 Hermes right now. 00:11:13.040 --> 00:11:15.560 >> One of the last things I sent you or was 00:11:15.560 --> 00:11:17.640 trying to tell you about was I tried 00:11:17.640 --> 00:11:19.600 anti-gravity, too, and it was 00:11:19.600 --> 00:11:20.120 >> Yes. 00:11:20.120 --> 00:11:21.640 >> not a great experience. 00:11:21.640 --> 00:11:23.480 >> Well, your your Your issue was that it 00:11:23.480 --> 00:11:25.360 that it didn't give you any any warning 00:11:25.360 --> 00:11:27.040 that it was going to run out of tokens, 00:11:27.040 --> 00:11:28.240 and it just stopped in the middle of the 00:11:28.240 --> 00:11:30.760 work and left your your work a little 00:11:30.760 --> 00:11:33.080 bit unfinished, which was frustrating. 00:11:33.080 --> 00:11:34.640 Um but you should have committed the 00:11:34.640 --> 00:11:36.272 working versions in between. 00:11:36.272 --> 00:11:38.400 >> [laughter] 00:11:38.400 --> 00:11:39.800 >> Well. 00:11:39.800 --> 00:11:41.560 >> another cool version uh story with Auto 00:11:41.560 --> 00:11:43.800 mode I just remembered. I was working 00:11:43.800 --> 00:11:45.480 and I created a public repo and I was 00:11:45.480 --> 00:11:48.320 working locally on on code for quite a 00:11:48.320 --> 00:11:50.920 while and I told it to push the remote 00:11:50.920 --> 00:11:53.800 to the remote and uh like do the do a 00:11:53.800 --> 00:11:55.880 bunch of work cuz usually it's like Auto 00:11:55.880 --> 00:11:57.360 mode doesn't see the original request 00:11:57.360 --> 00:12:00.280 included my approval to go push. Um or 00:12:00.280 --> 00:12:01.720 it was just being extra careful. Anyway, 00:12:01.720 --> 00:12:04.120 I told it to go push and and Auto mode 00:12:04.120 --> 00:12:05.960 blocked it uh saying that this is a 00:12:05.960 --> 00:12:07.760 public repo. You must be aware of the 00:12:07.760 --> 00:12:08.520 risk. 00:12:08.520 --> 00:12:09.320 >> Okay. 00:12:09.320 --> 00:12:10.840 >> whatever you going to post is going to 00:12:10.840 --> 00:12:14.240 be public and um you need to approve 00:12:14.240 --> 00:12:16.280 that. Like are you aware and approve it? 00:12:16.280 --> 00:12:18.040 Only then. Yeah. Yeah, that's like 00:12:18.040 --> 00:12:20.640 >> Okay, getting Okay, let's talk about uh 00:12:20.640 --> 00:12:22.200 Git commits here. 00:12:22.200 --> 00:12:25.240 As you as you were saying, how do you 00:12:25.240 --> 00:12:27.720 instruct the you you you you said for 00:12:27.720 --> 00:12:30.000 example in my anti-gravity two uh 00:12:30.000 --> 00:12:32.040 session, I should have been committing 00:12:32.040 --> 00:12:34.720 as I went. So, how do you think I should 00:12:34.720 --> 00:12:37.040 have done that? I should have just 00:12:37.040 --> 00:12:39.920 just uh at at at the phases dropped into 00:12:39.920 --> 00:12:41.040 a shell 00:12:41.040 --> 00:12:43.120 and uh committed the code myself. What 00:12:43.120 --> 00:12:45.120 what do you What What was What was I 00:12:45.120 --> 00:12:46.600 supposed to do there? 00:12:46.600 --> 00:12:49.240 >> I don't like to commit myself because 00:12:49.240 --> 00:12:50.520 then I have to come up with the commit 00:12:50.520 --> 00:12:52.839 message and I find the model is doing it 00:12:52.839 --> 00:12:55.560 way better. So, intermediately I I when 00:12:55.560 --> 00:12:58.000 something works, I ask it let's commit. 00:12:58.000 --> 00:13:00.320 And and it depends on your prompt, but I 00:13:00.320 --> 00:13:03.480 find Opus is very very um you know, 00:13:03.480 --> 00:13:05.080 maybe anti-gravity doesn't do that, but 00:13:05.080 --> 00:13:06.680 Opus is like, "Hey, we finished a a 00:13:06.680 --> 00:13:08.240 decent amount of work. Let's commit." 00:13:08.240 --> 00:13:09.520 Like it's pushing me. It's like, "Let's 00:13:09.520 --> 00:13:11.680 commit. It's working. Let's commit." And 00:13:11.680 --> 00:13:12.880 I'm like, "Let's do one more." I mean, 00:13:12.880 --> 00:13:14.800 it's like we have all the other stuff to 00:13:14.800 --> 00:13:16.960 do, but we're at a decent point where we 00:13:16.960 --> 00:13:18.880 should like be able to commit. And it 00:13:18.880 --> 00:13:20.120 says, "Do you want me to commit and then 00:13:20.120 --> 00:13:21.880 continue or do you want to just continue 00:13:21.880 --> 00:13:23.000 and then do a bigger commit?" 00:13:23.000 --> 00:13:24.440 >> So, what what Claude is doing that by 00:13:24.440 --> 00:13:26.600 default for you then? 00:13:26.600 --> 00:13:28.080 >> I guess it's a little bit related to the 00:13:28.080 --> 00:13:29.840 prompt and the type of work. With Spec 00:13:29.840 --> 00:13:32.800 Ledger now, even I have like branches 00:13:32.800 --> 00:13:34.560 and they're like 20 commits and I didn't 00:13:34.560 --> 00:13:36.400 never ask it to commit. It's on auto 00:13:36.400 --> 00:13:38.760 mode. It has like things to do and it 00:13:38.760 --> 00:13:41.120 just go maybe one time when it's like 00:13:41.120 --> 00:13:43.480 generates the spec, I say like push and 00:13:43.480 --> 00:13:45.680 commit for team alignment alignment. I 00:13:45.680 --> 00:13:47.600 always want to like I want to build into 00:13:47.600 --> 00:13:49.120 the model the concept that we have to 00:13:49.120 --> 00:13:50.640 get alignment from other people even 00:13:50.640 --> 00:13:51.480 though it's just me. 00:13:51.480 --> 00:13:53.640 >> increasingly that I need it it sounds 00:13:53.640 --> 00:13:55.800 increasingly that I I have to use Claude 00:13:55.800 --> 00:13:58.520 and nothing else because Claude does get 00:13:58.520 --> 00:14:01.240 commits right and get and Claude does 00:14:01.240 --> 00:14:03.680 commissioning right and Claude does 00:14:03.680 --> 00:14:04.800 >> It's just I I 00:14:04.800 --> 00:14:07.320 I I have I have a budget on it that I 00:14:07.320 --> 00:14:09.920 paid for it so I'm using it and I'm I'm 00:14:09.920 --> 00:14:12.120 happy with it. Um, I'm excited to try 00:14:12.120 --> 00:14:14.160 out Pilot Dev and to rebuild it. I'm 00:14:14.160 --> 00:14:17.440 also using open code with Git GitHub 00:14:17.440 --> 00:14:20.880 Copilot's seats for like just for demos 00:14:20.880 --> 00:14:22.440 just to show to people that hey, this is 00:14:22.440 --> 00:14:23.920 how you can use this and that but like 00:14:23.920 --> 00:14:25.800 my main driver is mainly Claude Code, 00:14:25.800 --> 00:14:27.760 yeah. Cuz I have the budget for it, 00:14:27.760 --> 00:14:30.240 yeah. 00:14:30.240 --> 00:14:33.120 >> We should rename the podcast the Claude 00:14:33.120 --> 00:14:34.560 AI infrastructure. 00:14:34.560 --> 00:14:36.360 >> Because this is always always we're 00:14:36.360 --> 00:14:37.440 always looking at the different 00:14:37.440 --> 00:14:38.800 trade-offs and like a lot of people are 00:14:38.800 --> 00:14:41.920 complaining uh that Opus 4.7 was really 00:14:41.920 --> 00:14:43.640 missing the mark and Codex give you so 00:14:43.640 --> 00:14:44.880 much more for 00:14:44.880 --> 00:14:47.200 you know, to cost value. 00:14:47.200 --> 00:14:48.800 >> So tell me about 4.8. What's your 00:14:48.800 --> 00:14:50.320 experience? 00:14:50.320 --> 00:14:52.920 Between 4.8 and 4.7. 00:14:52.920 --> 00:14:54.680 I guess you just prefer the larger 00:14:54.680 --> 00:14:56.400 model. 00:14:56.400 --> 00:14:59.160 >> Yeah, I mean I don't really notice. Um, 00:14:59.160 --> 00:15:00.960 I'm not going I don't have a benchmark. 00:15:00.960 --> 00:15:02.640 I don't do the same task to see how it 00:15:02.640 --> 00:15:04.040 does better or anything like that. I 00:15:04.040 --> 00:15:06.000 just want things to get done and it's 00:15:06.000 --> 00:15:08.720 getting things done and I feel 4.8 plus 00:15:08.720 --> 00:15:11.600 auto mode plus um the new workflow 00:15:11.600 --> 00:15:14.440 feature with the budget on max is 00:15:14.440 --> 00:15:17.440 getting done things done for me and and 00:15:17.440 --> 00:15:19.680 I'm very happy like I was able to turn 00:15:19.680 --> 00:15:21.160 through quite a lot of things. I'm still 00:15:21.160 --> 00:15:22.200 very 00:15:22.200 --> 00:15:23.560 careful because I think the biggest 00:15:23.560 --> 00:15:24.560 issue 00:15:24.560 --> 00:15:26.520 is that you and this was an interesting 00:15:26.520 --> 00:15:27.600 conversation I had with my friend 00:15:27.600 --> 00:15:29.800 yesterday is that 00:15:29.800 --> 00:15:33.200 you still need to have a way to 00:15:33.200 --> 00:15:34.680 define what needs to be validated 00:15:34.680 --> 00:15:37.360 against, right? So, either you are very 00:15:37.360 --> 00:15:39.440 explicit in your plan or you're you're 00:15:39.440 --> 00:15:41.640 specifying your user stories and then 00:15:41.640 --> 00:15:43.360 you can get a high confidence that you 00:15:43.360 --> 00:15:45.240 get what you want. Then you can have 00:15:45.240 --> 00:15:47.680 multiple adversarial reviews. 00:15:47.680 --> 00:15:49.480 >> was That was my next question. So, 00:15:49.480 --> 00:15:52.280 you're you've adapted your spec hit 00:15:52.280 --> 00:15:54.080 workflow for 00:15:54.080 --> 00:15:56.400 leveraging Claude, right? You're You're 00:15:56.400 --> 00:15:58.000 using that 00:15:58.000 --> 00:16:00.960 workflow to get your work done. 00:16:00.960 --> 00:16:02.360 Right? Or not? 00:16:02.360 --> 00:16:03.880 >> the moment I have not up streamed it 00:16:03.880 --> 00:16:06.000 into the binary. It's It's a It's a 00:16:06.000 --> 00:16:09.320 custom prompt in my current project. I 00:16:09.320 --> 00:16:12.280 do want to take those updated templates 00:16:12.280 --> 00:16:13.800 and put them They're actually They're 00:16:13.800 --> 00:16:15.440 the same. They're They're called 00:16:15.440 --> 00:16:18.480 verify-workflow and implement-workflow 00:16:18.480 --> 00:16:20.280 and they're They have adjustments saying 00:16:20.280 --> 00:16:21.880 that we do not need the task to be 00:16:21.880 --> 00:16:23.800 broken down because we will break down 00:16:23.800 --> 00:16:25.760 the tasks. So, so there's a difference 00:16:25.760 --> 00:16:28.400 between the normal task and implement 00:16:28.400 --> 00:16:29.800 and now there's a just one 00:16:29.800 --> 00:16:32.240 implement-workflow that does both. So, 00:16:32.240 --> 00:16:33.400 they're separate. I could keep them 00:16:33.400 --> 00:16:35.720 separate and make an a little annotation 00:16:35.720 --> 00:16:37.160 that this only works with the Claude 00:16:37.160 --> 00:16:39.080 >> remember your your spec hit has a has a 00:16:39.080 --> 00:16:41.440 UI. Do you actually use the UI to like 00:16:41.440 --> 00:16:42.480 track 00:16:42.480 --> 00:16:43.520 the implementation? 00:16:43.520 --> 00:16:46.720 >> tried so many. So, the problem of 00:16:46.720 --> 00:16:49.720 collaborative reviews or even just 00:16:49.720 --> 00:16:53.400 getting like a nice markdown web view of 00:16:53.400 --> 00:16:55.440 the of the specification, the user 00:16:55.440 --> 00:16:57.560 stories, the ability to highlight a 00:16:57.560 --> 00:16:59.160 section, leave a comment on that 00:16:59.160 --> 00:17:01.600 section. Uh that's obviously a hot 00:17:01.600 --> 00:17:03.960 topic. There's a hundreds of tools that 00:17:03.960 --> 00:17:06.439 do this. You shared with me Trit. 00:17:06.439 --> 00:17:08.240 >> Yeah, well, why didn't it work for you? 00:17:08.240 --> 00:17:10.079 It works for me. I'm I'm able to look at 00:17:10.079 --> 00:17:11.319 it differently. 00:17:11.319 --> 00:17:12.720 Put comments in and then it goes back 00:17:12.720 --> 00:17:14.560 into the agent and 00:17:14.560 --> 00:17:16.800 >> Okay, but that's not what I use it for, 00:17:16.800 --> 00:17:19.520 right? I I use it for single artifact. I 00:17:19.520 --> 00:17:22.400 don't know if you tried that. But I 00:17:22.400 --> 00:17:24.280 I tried 00:17:24.280 --> 00:17:26.240 Crit has two modes. Shows how much you 00:17:26.240 --> 00:17:28.640 use it. Crit has has a 00:17:28.640 --> 00:17:31.120 a diff mode with multiple files or has 00:17:31.120 --> 00:17:33.640 an a single artifact mode. 00:17:33.640 --> 00:17:36.240 >> Okay. I haven't used that one. So, yeah. 00:17:36.240 --> 00:17:38.120 >> Yes, it doesn't work. And also the 00:17:38.120 --> 00:17:40.600 folder in like 2 weeks the the source 00:17:40.600 --> 00:17:43.320 code folder became littered with like I 00:17:43.320 --> 00:17:45.840 don't know, 20 go source code files in 00:17:45.840 --> 00:17:48.680 the in the root. The web app is like I 00:17:48.680 --> 00:17:51.000 don't I don't it's it's it's completely 00:17:51.000 --> 00:17:52.800 sloppy fine in just 2 weeks. I I was 00:17:52.800 --> 00:17:54.080 really surprised looking at the code 00:17:54.080 --> 00:17:55.680 after 2 weeks and I was I had no 00:17:55.680 --> 00:17:57.840 confidence. If you cannot as an 00:17:57.840 --> 00:18:00.480 architect tell the agents to build the 00:18:00.480 --> 00:18:04.360 code in like a well like organized way, 00:18:04.360 --> 00:18:06.080 then I'm already have a lot less 00:18:06.080 --> 00:18:07.800 confidence. Like, you know how people 00:18:07.800 --> 00:18:09.440 share their project on Reddit and they 00:18:09.440 --> 00:18:11.240 go like I built this with with AI or 00:18:11.240 --> 00:18:12.800 like look at my project and then the 00:18:12.800 --> 00:18:14.160 first comment is like I looked at the 00:18:14.160 --> 00:18:17.160 source code. It's It's absolute slop. 00:18:17.160 --> 00:18:19.080 And I think 00:18:19.080 --> 00:18:20.840 I mean, it's it's a stupid criticism 00:18:20.840 --> 00:18:22.480 because I think if it works, it works. 00:18:22.480 --> 00:18:23.760 But still, 00:18:23.760 --> 00:18:25.400 you need to be able to instruct the 00:18:25.400 --> 00:18:26.520 models to do it properly. 00:18:26.520 --> 00:18:28.040 >> Okay, single single artifact didn't 00:18:28.040 --> 00:18:30.160 work. Did you Did you try the diff mode 00:18:30.160 --> 00:18:31.360 at least? 00:18:31.360 --> 00:18:33.960 >> No, no, no. But that's not my target. My 00:18:33.960 --> 00:18:38.040 My target is to review the user stories, 00:18:38.040 --> 00:18:40.960 highlight This is very very like This is 00:18:40.960 --> 00:18:42.880 the hardest part of the job right now 00:18:42.880 --> 00:18:45.600 for me, which is like 00:18:45.600 --> 00:18:47.960 do these user stories make make sense? 00:18:47.960 --> 00:18:49.400 Like for example, I'm building a tool 00:18:49.400 --> 00:18:51.760 that does a a verify, which is a content 00:18:51.760 --> 00:18:54.680 sha verification on on skills to verify 00:18:54.680 --> 00:18:56.400 that the skills haven't been maliciously 00:18:56.400 --> 00:18:58.680 manipulated. And and I then also have a 00:18:58.680 --> 00:19:00.760 doctor version, which is doing that 00:19:00.760 --> 00:19:02.880 verify but also a full review of the 00:19:02.880 --> 00:19:04.800 setup if if the like according certain 00:19:04.800 --> 00:19:06.040 rules. 00:19:06.040 --> 00:19:08.600 Um it's not an AI like rule verifier. 00:19:08.600 --> 00:19:10.760 It's just like, hey, um 00:19:10.760 --> 00:19:12.600 is the origin set 00:19:12.600 --> 00:19:15.040 um correctly? Are the skills like 00:19:15.040 --> 00:19:17.320 correct? So it must it must very very 00:19:17.320 --> 00:19:20.280 validate some things. And somehow the 00:19:20.280 --> 00:19:22.240 Opus thinks that this is a full offline 00:19:22.240 --> 00:19:24.640 mode. But at the same sentence it says, 00:19:24.640 --> 00:19:26.520 but we are doing a remote check like to 00:19:26.520 --> 00:19:28.400 get remote. And I'm like, yeah, but 00:19:28.400 --> 00:19:30.080 that's that doesn't make sense. And then 00:19:30.080 --> 00:19:31.880 when I highlight that one thing saying 00:19:31.880 --> 00:19:33.480 like, hey, you said it's offline and 00:19:33.480 --> 00:19:34.760 then here you say we're validating the 00:19:34.760 --> 00:19:37.520 get remote, then that's not offline. And 00:19:37.520 --> 00:19:38.920 then it goes through the whole document 00:19:38.920 --> 00:19:40.480 and says, actually you're right. There's 00:19:40.480 --> 00:19:42.320 quite a few areas where there's this 00:19:42.320 --> 00:19:43.640 tension and there's some 00:19:43.640 --> 00:19:47.200 inconsistencies. So so so going through 00:19:47.200 --> 00:19:49.640 this like 500 lines and trying to 00:19:49.640 --> 00:19:53.240 identify this is is is damn hard. Um, 00:19:53.240 --> 00:19:54.960 and and then once I'm feel confident in 00:19:54.960 --> 00:19:55.520 that because 00:19:55.520 --> 00:19:58.200 >> five 500 lines of user stories you mean, 00:19:58.200 --> 00:19:59.600 right? 00:19:59.600 --> 00:20:01.920 >> Yeah, 500 lines markdown. 00:20:01.920 --> 00:20:03.120 >> That's what you focus on. 00:20:03.120 --> 00:20:04.760 >> functional requirements, acceptance 00:20:04.760 --> 00:20:07.120 criteria. Yeah, I'm trying to identify 00:20:07.120 --> 00:20:08.960 if they make sense. 00:20:08.960 --> 00:20:10.000 And then I also need to make a 00:20:10.000 --> 00:20:12.440 verification that no 00:20:12.440 --> 00:20:15.000 term confusion because it will it will 00:20:15.000 --> 00:20:17.640 have the terminology in the user story 00:20:17.640 --> 00:20:19.640 will be one word and then in the 00:20:19.640 --> 00:20:22.280 implementation plan originally in the it 00:20:22.280 --> 00:20:24.120 will will be another word. And then the 00:20:24.120 --> 00:20:25.480 agent doing the implementation would be 00:20:25.480 --> 00:20:26.960 confused 00:20:26.960 --> 00:20:28.480 because of the meaning behind the word 00:20:28.480 --> 00:20:30.000 and then it would do things that are 00:20:30.000 --> 00:20:32.480 unexpected. So I found that those are a 00:20:32.480 --> 00:20:34.120 lot 00:20:34.120 --> 00:20:35.880 >> I'm boarding a train now 00:20:35.880 --> 00:20:38.720 and so probably won't work. 00:20:38.720 --> 00:20:40.480 Yeah, probably won't work. 00:20:40.480 --> 00:20:42.960 Things are starting to move. 00:20:42.960 --> 00:20:43.720 >> Uh 00:20:43.720 --> 00:20:45.640 >> Cuz you're in like this underdeveloped 00:20:45.640 --> 00:20:47.720 country, right? I guess the internet 00:20:47.720 --> 00:20:49.440 doesn't work in trains. 00:20:49.440 --> 00:20:51.760 >> It doesn't really work. 00:20:51.760 --> 00:20:54.120 >> It works in Vietnam, though. 00:20:54.120 --> 00:20:54.760 >> It does? 00:20:54.760 --> 00:20:57.840 >> Not in UK as far as I know. 00:20:57.840 --> 00:20:59.240 >> Okay, anyway, 00:20:59.240 --> 00:21:01.880 let's just call it a day right now. 00:21:01.880 --> 00:21:03.280 And uh 00:21:03.280 --> 00:21:05.160 and I'll I'll catch up with you tomorrow 00:21:05.160 --> 00:21:08.040 or something, okay? 00:21:08.040 --> 00:21:10.240 >> Yeah, so I think 00:21:10.240 --> 00:21:12.840 yeah, have a nice uh trip. 00:21:12.840 --> 00:21:13.760 >> Thanks. 00:21:13.760 --> 00:21:17.040 I'll give you updates on WhatsApp. Bye. 00:21:17.040 --> 00:21:19.560 >> Yeah, bye-bye.