1 00:00:00,040 --> 00:00:04,280 Your notes can do so much more. Just imagine your notes become 2 00:00:04,280 --> 00:00:05,640 your second brain. Which then? 3 00:00:05,640 --> 00:00:07,360 Evolves into a powerful assistant. 4 00:00:07,720 --> 00:00:10,200 But how do we do it? On Episode 67, Tool use, we're 5 00:00:10,200 --> 00:00:13,400 joined by Artem Jutov. He's a physicist, PhD, exploring 6 00:00:13,400 --> 00:00:15,680 coding agents for non coding workflows. 7 00:00:15,880 --> 00:00:18,520 And we're going to discuss how you can use clod code in 8 00:00:18,520 --> 00:00:21,440 Obsidian to optimize your day, how you can build helpful 9 00:00:21,440 --> 00:00:24,240 automations for your general tasks, and how to make your 10 00:00:24,240 --> 00:00:26,480 system more reliable and affordable. 11 00:00:26,520 --> 00:00:28,440 I love using them. Same with AII, use it almost 12 00:00:28,440 --> 00:00:30,600 every single day. But Artem brings to a whole new 13 00:00:30,600 --> 00:00:32,000 level. So please enjoy this 14 00:00:32,000 --> 00:00:34,720 conversation with Artem. Jutov, why did you choose 15 00:00:34,720 --> 00:00:39,640 Obsidian for your notes? I've been trying to find the 16 00:00:39,640 --> 00:00:43,840 perfect workflow for me. I've been doing this not taking 17 00:00:43,840 --> 00:00:48,240 for a very long time I think. Or like five years ago, I start 18 00:00:48,240 --> 00:00:52,760 using Notion and it was like a big thing I think during the 19 00:00:52,760 --> 00:00:56,800 COVID, everyone starts like, I need to now change something in 20 00:00:56,800 --> 00:00:59,920 my life. And now I'll start setting 21 00:00:59,920 --> 00:01:05,560 goals, taking notes and so on. And I kind of start from there 22 00:01:05,720 --> 00:01:11,960 from Notion. But then I I kind of went on on 23 00:01:11,960 --> 00:01:15,120 track about how can I store my notes locally? 24 00:01:15,120 --> 00:01:17,440 I use the Emacs. Yeah. 25 00:01:17,440 --> 00:01:20,840 If you know Emacs, yeah. It allows you to kind of work 26 00:01:20,840 --> 00:01:27,000 locally with your files. And then I went back again on on 27 00:01:27,000 --> 00:01:31,400 Notion track. I think they used they created a 28 00:01:31,960 --> 00:01:38,960 very nice kind of way to like. I think that the, the kind of 29 00:01:38,960 --> 00:01:45,280 the buy point for Notion is databases where you can visually 30 00:01:45,280 --> 00:01:51,240 see and sort your items. And that's kind of something 31 00:01:51,240 --> 00:01:53,600 that I never could achieve in other systems. 32 00:01:53,920 --> 00:02:00,280 I start exploring calling agents and I I start storing my notes 33 00:02:00,280 --> 00:02:03,920 locally. I think maybe like this year I 34 00:02:03,920 --> 00:02:08,320 start using Obsidian once again and then I think during like in 35 00:02:08,320 --> 00:02:12,720 May when the cloud code became a big thing and everyone start 36 00:02:12,720 --> 00:02:15,440 using it for kind of for, for coding. 37 00:02:16,120 --> 00:02:19,400 I, I wanted to create sort of operational system for myself 38 00:02:19,440 --> 00:02:21,280 on. I start like creating different 39 00:02:21,280 --> 00:02:24,840 scripts for different automations. 40 00:02:25,400 --> 00:02:27,280 And I've been considering also different options. 41 00:02:27,280 --> 00:02:30,480 Maybe there is like NAN, maybe there is something else. 42 00:02:30,960 --> 00:02:37,600 And I think the key criteria for me was to be able to not to 43 00:02:37,600 --> 00:02:43,960 click buttons. So let the agent to manage like 44 00:02:43,960 --> 00:02:48,160 all of the scripts. And I think like doing this 45 00:02:48,160 --> 00:02:52,360 locally, whereas the agent can run commands, can execute 46 00:02:52,360 --> 00:02:55,120 scripts. It's something that really kind 47 00:02:55,120 --> 00:03:01,120 of enabled me to to take like full power of that and not be 48 00:03:01,120 --> 00:03:05,000 being restricted by APIs or that sort sort of stuff. 49 00:03:05,000 --> 00:03:08,280 Like I think I removed all the complexity and now I kind of 50 00:03:08,560 --> 00:03:12,800 work locally with all of my notes with according agents such 51 00:03:12,800 --> 00:03:17,120 as club code. Was there a like an adoption 52 00:03:17,120 --> 00:03:19,680 curve for you when you started using a coding agent in non 53 00:03:19,680 --> 00:03:23,240 coding manners? Was it like very intuitive or 54 00:03:23,240 --> 00:03:24,800 how did that process get started? 55 00:03:25,360 --> 00:03:31,160 You need to learn it for me, you know the kind of I need to eat 56 00:03:31,160 --> 00:03:34,800 right on that. And I think for me, one of the 57 00:03:35,320 --> 00:03:38,320 big problems which I had is trying to create a perfect 58 00:03:38,320 --> 00:03:42,840 system to manage everything. And I think that's just 59 00:03:42,920 --> 00:03:46,840 something that you waste a lot of energy, but then you don't 60 00:03:46,840 --> 00:03:49,120 see a result of the system working because it's too 61 00:03:49,120 --> 00:03:52,200 complex. And what I end up doing, I think 62 00:03:52,200 --> 00:03:58,360 is just building something right now what what brings immediate 63 00:03:58,360 --> 00:04:05,600 value. And I think it's kind of should 64 00:04:05,600 --> 00:04:11,160 not be sort of in a way that you try to design perfect system, 65 00:04:11,160 --> 00:04:15,120 but rather I was trying to like later on and learn that I should 66 00:04:15,120 --> 00:04:19,440 be doing this approach where I I need to solve the problem and 67 00:04:19,480 --> 00:04:23,120 let me design some MVP solution for that and see if it sticks. 68 00:04:23,840 --> 00:04:28,360 And it's very easy to see if if something that you like or not, 69 00:04:28,360 --> 00:04:30,720 you just like see if are you using it or not. 70 00:04:31,480 --> 00:04:36,600 And I think I kind of just start building the system and over 71 00:04:36,600 --> 00:04:42,600 time it grows and grows where you have like kind of workflows 72 00:04:42,600 --> 00:04:47,760 emerging. And I think for me, I'm a big 73 00:04:47,760 --> 00:04:51,760 fan of like custom slash commands, like something that 74 00:04:51,760 --> 00:04:55,000 you can package as an instructions and make it 75 00:04:55,400 --> 00:05:00,040 reliable and reproducible. And that's what I've been doing. 76 00:05:00,040 --> 00:05:03,280 I kind of collect, start collecting those workflows which 77 00:05:04,280 --> 00:05:08,240 I found valuable and I think right now in my Obsidian world, 78 00:05:08,240 --> 00:05:12,280 I have like hundreds of those custom flash commands, but I use 79 00:05:12,440 --> 00:05:18,440 maybe only 10 of them. And I think and that's you can 80 00:05:18,440 --> 00:05:23,400 kind of see like what you use and what you're not and things 81 00:05:23,400 --> 00:05:25,600 the pattern emerges naturally. Very cool. 82 00:05:25,600 --> 00:05:28,400 Before we get into the actual like implementation details of 83 00:05:28,400 --> 00:05:30,920 how you build these and orchestrate it and whatnot, 84 00:05:31,280 --> 00:05:34,680 could you just kind of touch on your thought process for how, 85 00:05:34,680 --> 00:05:39,080 how do you go about doing the the a planning for a workflow? 86 00:05:39,320 --> 00:05:42,160 I know a lot of people say oh I want to apply automations but I 87 00:05:42,160 --> 00:05:44,960 just don't have a use case and I really feel like anyone. 88 00:05:44,960 --> 00:05:46,760 That does any type of. Knowledge work, any type of work 89 00:05:46,760 --> 00:05:49,080 under computer, there are work flows that can be automated, but 90 00:05:49,200 --> 00:05:51,440 how do you identify it? And then how do you go from like 91 00:05:51,480 --> 00:05:55,000 idea to actually putting it into practice? 92 00:05:55,360 --> 00:06:00,000 Well, I think I do this step very gradually. 93 00:06:01,440 --> 00:06:06,600 Is that something that if I see that's something I'm going to be 94 00:06:06,600 --> 00:06:13,320 doing more than once, I try to package it into a workflow and I 95 00:06:13,320 --> 00:06:19,120 have a specific command where I can execute it mid session in 96 00:06:19,120 --> 00:06:21,560 code quote. You have those like chat, 97 00:06:21,680 --> 00:06:25,080 continuous chats and then you have a custom flash command. 98 00:06:25,120 --> 00:06:28,920 And then I kind of tell the agent, OK, let's package this 99 00:06:28,920 --> 00:06:34,360 into a that's kind of three, let's package this workflow like 100 00:06:34,360 --> 00:06:39,360 sort of this interaction, which we did into something that is 101 00:06:39,440 --> 00:06:42,640 reproducible. And next time you can execute it 102 00:06:42,640 --> 00:06:47,320 without like one shot. I think if I see the value and I 103 00:06:47,320 --> 00:06:53,320 want to capture that state and make it reproducible, I, I try 104 00:06:53,320 --> 00:06:57,560 to package it. And if I do it more than once, 105 00:06:57,560 --> 00:07:01,600 that kind of the criteria for me, the value plus doing it more 106 00:07:01,600 --> 00:07:06,360 than once. One way also to adopt those 107 00:07:06,360 --> 00:07:11,240 workflows is to make it easy of a process like make the process 108 00:07:11,240 --> 00:07:14,520 of those workflow creation is easy for you. 109 00:07:14,880 --> 00:07:17,800 And that example that I have another custom flush command 110 00:07:17,800 --> 00:07:22,360 that kind of OK via meet chat. And let's say, OK, I just run it 111 00:07:22,360 --> 00:07:24,400 and let's capture that into a workflow. 112 00:07:24,840 --> 00:07:28,240 And in terms of identifying, I think that's something that I 113 00:07:28,240 --> 00:07:32,120 want to do. I want to just track like, you 114 00:07:32,120 --> 00:07:34,720 know, like do experiment for like for a couple days. 115 00:07:34,720 --> 00:07:41,480 I, I just record what I do, like what, what, what, what, what 116 00:07:41,480 --> 00:07:44,120 actually I do. Like, what kind of work do I do 117 00:07:44,600 --> 00:07:47,440 and what kind of actions does it require for me? 118 00:07:48,240 --> 00:07:53,200 And see, are there any like patterns that can emerge? 119 00:07:53,480 --> 00:07:57,080 Is there anything I can make reproducible? 120 00:07:57,160 --> 00:08:02,040 And I think, yeah, I've been exploring that and I prepared 121 00:08:02,040 --> 00:08:03,160 some stuff. Excellent. 122 00:08:03,160 --> 00:08:05,560 Yeah. Being cognizant of the work that 123 00:08:05,560 --> 00:08:08,320 you're actually doing, making notes, which I love that idea. 124 00:08:08,320 --> 00:08:10,880 Just, you know, observing yourself and then trying to 125 00:08:10,880 --> 00:08:13,600 convert that into a workflow. Yeah. 126 00:08:13,600 --> 00:08:16,800 Do you want to start showing us the Obsidian Vaults and what 127 00:08:16,800 --> 00:08:19,400 you've got going on and some of your setups? 128 00:08:19,520 --> 00:08:20,000 Yeah. OK. 129 00:08:20,000 --> 00:08:22,560 So let's do that. I think for me it's a bit 130 00:08:22,560 --> 00:08:29,000 unconventional right now. I, I kind of innovate, don't 131 00:08:29,000 --> 00:08:30,480 interact much with that decision. 132 00:08:31,600 --> 00:08:38,559 And what I do instead, I, I saw how basically cursor opened and 133 00:08:38,559 --> 00:08:41,360 that's kind of how I work nowadays yeah. 134 00:08:41,360 --> 00:08:46,320 And basically that's the chat, right? 135 00:08:46,320 --> 00:08:52,120 And then you have all of that, all of this kind of notes which 136 00:08:52,120 --> 00:08:55,560 you have here. And that's my Obsidian Vault 137 00:08:56,120 --> 00:09:00,480 opened in cursor. And then then I have a bunch of 138 00:09:00,560 --> 00:09:08,000 folders and there's sort of some structure, but I didn't try it 139 00:09:08,000 --> 00:09:12,920 like to have perfect system. It's more or less in a way like 140 00:09:12,920 --> 00:09:18,400 self self organizing structure and. 141 00:09:18,720 --> 00:09:22,320 Sorry, just on that note of of the structure, do you do like 142 00:09:22,320 --> 00:09:24,680 wiki links to connect different notes to each other? 143 00:09:24,680 --> 00:09:25,800 Do you do tags? How? 144 00:09:25,800 --> 00:09:28,400 How do you help this to become aware of connected bits of 145 00:09:28,400 --> 00:09:29,760 information? Yeah. 146 00:09:29,760 --> 00:09:35,320 So for me, I do in this index sync, like for example, I use 147 00:09:35,320 --> 00:09:39,720 index files. And here what I do is for 148 00:09:39,720 --> 00:09:44,680 example, if during the workflow I created a multiple notes 149 00:09:44,920 --> 00:09:50,280 during the chart with the cloud, then I try to kind of connect 150 00:09:50,280 --> 00:09:53,920 those into something that can be packaged, right. 151 00:09:54,560 --> 00:09:59,320 And here's I do index, index files where you have one file 152 00:09:59,320 --> 00:10:03,000 and then inside of this file you have different links such that 153 00:10:03,000 --> 00:10:08,520 you don't lose like how, how, how those knots are related, 154 00:10:08,600 --> 00:10:11,080 right? And this is an example, right? 155 00:10:11,240 --> 00:10:15,000 I've been doing job applications and here like some companies 156 00:10:15,000 --> 00:10:19,920 which I've been considering and exhaust our in index file. 157 00:10:20,760 --> 00:10:24,360 And that's the way I try to keep track of what's going on. 158 00:10:25,080 --> 00:10:32,040 And another thing which I do is using Obsidian Basis is to have 159 00:10:32,600 --> 00:10:36,600 sort of way to have to to categorize your items. 160 00:10:37,120 --> 00:10:42,720 And here I have categories for different items which I have in 161 00:10:42,720 --> 00:10:45,680 my world. I try to create the categories. 162 00:10:45,720 --> 00:10:51,840 Is it like people? Is it like projects is like 163 00:10:51,840 --> 00:10:55,120 Castle Flash command? And I think what you can do is 164 00:10:55,120 --> 00:10:57,880 that once you have those categories, you can display them 165 00:10:57,880 --> 00:11:02,600 in Obsidian Basis. And I think here is an example, 166 00:11:04,360 --> 00:11:08,320 yes, for the like, for the goal, for example, right? 167 00:11:08,880 --> 00:11:14,240 And like what you do here, I think so you have categories, 168 00:11:15,000 --> 00:11:18,560 goals. And this way you can display all 169 00:11:18,560 --> 00:11:23,360 of your goals in in one place in a nice kind of format that helps 170 00:11:23,360 --> 00:11:26,400 me to see like what's going on really. 171 00:11:27,240 --> 00:11:29,480 Yeah, I know. I think that's really cool and a 172 00:11:29,480 --> 00:11:32,600 really good approach for being able to keep the information 173 00:11:32,600 --> 00:11:34,280 connected. So you you set up your 174 00:11:34,280 --> 00:11:35,960 categories, you set up different notes. 175 00:11:36,280 --> 00:11:40,200 How how do you actually leverage quad code to generate value out 176 00:11:40,200 --> 00:11:42,680 of that information? I think there are different 177 00:11:42,680 --> 00:11:45,680 ways. I I tried to use it as a 178 00:11:46,600 --> 00:11:53,080 compilot where for example, I tried to like work together with 179 00:11:53,080 --> 00:11:57,000 a quad code. And I think one example is my 180 00:11:57,000 --> 00:12:04,000 morning routine where quad code guys me throughout my morning 181 00:12:04,000 --> 00:12:06,520 process. I think that's a very important 182 00:12:06,520 --> 00:12:11,960 thing that I that each day even make a decision on like what to 183 00:12:11,960 --> 00:12:14,680 do, right? And I try to bring a structure 184 00:12:14,680 --> 00:12:19,320 into this process. And here example of this process 185 00:12:19,680 --> 00:12:23,680 where a cloud guides me through my morning routine. 186 00:12:23,680 --> 00:12:30,120 And what I have here is my main file which is executed this 187 00:12:30,240 --> 00:12:35,080 workflow, and then it opens my Spotify and it opens my 188 00:12:35,080 --> 00:12:39,720 permadora timer. I can actually try to run it. 189 00:12:40,200 --> 00:12:42,680 Let me see that it needs to cache. 190 00:12:42,680 --> 00:12:46,000 OK, Yeah, I don't know what's gonna happen, but let's see. 191 00:12:46,200 --> 00:12:53,160 OK, so it opens my Spotify app and it opens my permadora timer 192 00:12:54,360 --> 00:12:57,480 and you kind of start this morning routine. 193 00:12:58,400 --> 00:13:00,160 So sorry. I'll, I'll pause it right now. 194 00:13:00,160 --> 00:13:03,160 How like music playing certainly to pause it. 195 00:13:03,320 --> 00:13:05,920 Yeah. And then what code does? 196 00:13:06,320 --> 00:13:11,560 So it runs this command review yesterday and it reconstructs my 197 00:13:11,560 --> 00:13:17,720 day kind of using using the notes which I take throughout 198 00:13:17,720 --> 00:13:22,560 the day. And it kind of able to 199 00:13:22,560 --> 00:13:25,640 reconstruct the like 3 days patterns. 200 00:13:27,440 --> 00:13:31,520 And the way you do that, the way I collect this data is using 201 00:13:32,200 --> 00:13:35,280 this app just like a test. That's the test. 202 00:13:36,040 --> 00:13:39,800 But here it has notes and for example, if I start working on 203 00:13:39,800 --> 00:13:43,600 something, I can just record it and like my lessons like 204 00:13:43,600 --> 00:13:47,200 learnings and then it's going to appear here. 205 00:13:47,640 --> 00:13:51,960 And then I at the end of the day, I expert those notes into a 206 00:13:51,960 --> 00:13:56,320 Jason file and then cloud just reads it and it able to 207 00:13:56,320 --> 00:14:01,400 reconstruct like what happened yesterday, like hour by hour. 208 00:14:02,120 --> 00:14:04,600 And like I do this over three days. 209 00:14:05,800 --> 00:14:12,120 Now what I do next is I answer questions each day, answer 210 00:14:12,120 --> 00:14:17,840 questions like about my energy levels, what I'm excited about 211 00:14:17,840 --> 00:14:21,760 today. And this is all of the context. 212 00:14:22,320 --> 00:14:27,000 Now next step, you review your your goals. 213 00:14:27,800 --> 00:14:31,280 Here's a Claude pulls all of my goals. 214 00:14:32,320 --> 00:14:36,400 I think I showed those. I think this are my goals. 215 00:14:36,400 --> 00:14:41,440 And the Claude reads those files and then it asks me a question 216 00:14:41,440 --> 00:14:44,880 like what what's the what is the one step you can do towards 217 00:14:44,880 --> 00:14:47,760 achieving that goal? And then you do this answering 218 00:14:47,760 --> 00:14:50,880 those questions. And in the end of the day, you, 219 00:14:52,280 --> 00:14:55,840 you plan your, your day and the plot kind of proposes a schedule 220 00:14:56,520 --> 00:15:02,400 based on your working rhythm. And now here you have a schedule 221 00:15:02,400 --> 00:15:06,720 And then finally you kind of do back, back and forth and then 222 00:15:08,280 --> 00:15:12,920 you put it into your calendar. I think that's one way how you 223 00:15:12,920 --> 00:15:18,120 can like create a structured work flows and create value 224 00:15:18,280 --> 00:15:22,680 because I think that's something that I've been doing for a quite 225 00:15:22,680 --> 00:15:27,720 a long time and it's been really helpful, like gathering contacts 226 00:15:27,720 --> 00:15:29,560 and understanding like what what's going on. 227 00:15:29,800 --> 00:15:31,880 That's super cool. I love the idea of having your 228 00:15:31,880 --> 00:15:34,800 little coach go and help you out in the morning. 229 00:15:35,000 --> 00:15:39,000 How much of that morning routine did you pre code ahead of time 230 00:15:39,000 --> 00:15:41,600 and set into the the slash command versus how much of it is 231 00:15:41,600 --> 00:15:43,920 clawed? Just discovering what it needs 232 00:15:43,920 --> 00:15:46,560 to ask you and is like different every single day. 233 00:15:46,840 --> 00:15:49,320 Oh yeah, it's actually very structured. 234 00:15:49,560 --> 00:15:55,560 It's repeatable each day, it's more or less the same workflow, 235 00:15:55,720 --> 00:16:00,000 the same questions. And it's the same because those 236 00:16:00,000 --> 00:16:02,080 custom flash commands are the same. 237 00:16:02,160 --> 00:16:04,160 And I have a templates for the questions. 238 00:16:05,040 --> 00:16:09,560 And I think what's different, the different is once you 239 00:16:09,560 --> 00:16:13,320 progress towards your goal, the call starts asking different 240 00:16:13,320 --> 00:16:15,880 questions because now the context is different. 241 00:16:16,840 --> 00:16:23,560 And I tried to bring a variety. I think I tried to create a 242 00:16:23,600 --> 00:16:29,520 randomized kind of questions and create a script with a database 243 00:16:29,520 --> 00:16:31,320 of questions. And each day you kind of pull 244 00:16:31,320 --> 00:16:34,280 random questions from it. That's something like bring some 245 00:16:34,280 --> 00:16:37,920 novelty. But I think there is value in 246 00:16:37,920 --> 00:16:41,720 having this workflow structured because now I can iterate on it 247 00:16:42,400 --> 00:16:47,760 and it's reproducible, right. And it's a continuous process 248 00:16:47,760 --> 00:16:51,960 where you kind of at the end of session, you kind of see what 249 00:16:51,960 --> 00:16:57,040 you don't like and then you try to iterate on that. 250 00:16:57,160 --> 00:16:59,160 Yeah, and. What's the process of making 251 00:16:59,160 --> 00:17:01,080 these workflows? Do you actually use quad code to 252 00:17:01,080 --> 00:17:03,400 make it? Do you go to cursor like? 253 00:17:03,400 --> 00:17:06,000 How do you make these workflows to iterate on eventually? 254 00:17:06,200 --> 00:17:08,760 I do. I use another custom slash 255 00:17:08,760 --> 00:17:14,920 command which called update custom slash command and then 256 00:17:15,480 --> 00:17:20,160 what I tell Claude is to introduce a minimal change to 257 00:17:20,200 --> 00:17:23,720 address the issue which I'm talking about in this chat. 258 00:17:24,000 --> 00:17:26,760 I think it's very important to say they'll just minimal change, 259 00:17:26,760 --> 00:17:30,080 otherwise it's going to go crazy and completely off track. 260 00:17:30,240 --> 00:17:32,280 So basically it's another custom slash command. 261 00:17:32,640 --> 00:17:34,440 Nice. So you you create slash commands 262 00:17:34,440 --> 00:17:35,840 that help with other slash commands. 263 00:17:36,840 --> 00:17:38,920 You have workflows that help with your day planning. 264 00:17:38,920 --> 00:17:41,920 It's it's really showing how if you go a little meta with it, 265 00:17:42,080 --> 00:17:44,600 you can leverage these tools to improve the tools that you use 266 00:17:44,600 --> 00:17:46,600 and just becomes a positive feedback loop. 267 00:17:47,080 --> 00:17:49,360 Yes, exactly. Do do you mind going into any 268 00:17:49,360 --> 00:17:51,720 other workflows you have besides the morning routine? 269 00:17:51,760 --> 00:17:56,000 I've also been doing job search recently and then I think the 270 00:17:56,480 --> 00:17:59,960 obvious like scaling of those workflows is. 271 00:18:00,480 --> 00:18:04,320 I also do it in the evening, kind of a different style of 272 00:18:04,320 --> 00:18:08,440 reflection. I also do weekly review. 273 00:18:08,880 --> 00:18:11,000 I think that's kind of obvious extensions of that. 274 00:18:11,600 --> 00:18:15,880 And another one is a kind of personal coach. 275 00:18:16,440 --> 00:18:22,320 I know psychiatrist like the two kind of if you want to have a 276 00:18:22,320 --> 00:18:25,560 session about OK, what's going on, how do you feel, what are 277 00:18:25,560 --> 00:18:27,440 your emotions or what do you feel this way. 278 00:18:27,680 --> 00:18:30,840 I find it's very valuable to to better understand myself. 279 00:18:31,080 --> 00:18:33,520 I think those are the most ones which I use. 280 00:18:33,720 --> 00:18:39,240 I think also it's kind of becomes a general tool where you 281 00:18:39,320 --> 00:18:43,080 can do so much more. And one of the examples is job 282 00:18:43,080 --> 00:18:48,360 search, right? And this process where code can 283 00:18:48,360 --> 00:18:53,480 kind of work together with me on writing cover letters, on 284 00:18:54,880 --> 00:19:00,120 creating my resume and like actually finding the job search 285 00:19:00,120 --> 00:19:04,200 and still taking them by like what kind of job do I want? 286 00:19:04,400 --> 00:19:06,560 And that's been quite helpful. That would be awesome. 287 00:19:06,560 --> 00:19:10,480 And also curious, do you give Claude code web browsing? 288 00:19:10,480 --> 00:19:11,920 Do you find the job post and pull them in? 289 00:19:11,920 --> 00:19:14,560 What's what level of automation is in that aspect of it? 290 00:19:14,800 --> 00:19:19,160 Claude has Internal Explorer agents which are great at that 291 00:19:19,280 --> 00:19:23,520 so it can do job search for example. 292 00:19:24,400 --> 00:19:30,160 The task is to like house those like job postings and the cloud 293 00:19:30,160 --> 00:19:34,880 runs a sub agent like general purpose sub agent, which gets 294 00:19:35,080 --> 00:19:40,720 details about this job. And here is a website and this 295 00:19:40,720 --> 00:19:46,400 kind of sub agent can get information and that's the 296 00:19:47,000 --> 00:19:49,520 information which sub agent got from the website. 297 00:19:50,320 --> 00:19:56,680 So it's kind of all the internal cloud tools and it can do for 298 00:19:57,040 --> 00:20:02,440 for sort of every, every job. And then with that you can have 299 00:20:03,080 --> 00:20:07,800 created each file for each job. And then next you can view them 300 00:20:07,800 --> 00:20:12,600 in your Obsidian base. So and that's kind of example of 301 00:20:13,720 --> 00:20:18,320 how job search looks like. Each of the files which you see 302 00:20:18,320 --> 00:20:24,080 here is generated by the cloud code and it has like metadata 303 00:20:24,320 --> 00:20:27,880 for example. Yeah, here is all metadata for 304 00:20:27,880 --> 00:20:35,040 those jobs which called gathered and it has some comments about 305 00:20:35,040 --> 00:20:37,720 like, oh, why is this good? Sorry, do you make the comments 306 00:20:37,720 --> 00:20:40,560 or just Claude? Yeah, Claude, I, I provide 307 00:20:40,560 --> 00:20:44,000 general kind of instructions about what kind of job do I 308 00:20:44,000 --> 00:20:48,920 want. And then based on that, Claude 309 00:20:49,640 --> 00:20:55,720 finds those job postings and tries to filter them by this 310 00:20:55,720 --> 00:20:58,200 type of job. And I think what also works 311 00:20:58,200 --> 00:21:02,360 well, if you really like some type of like, I don't know, job 312 00:21:02,360 --> 00:21:05,560 posting, you can tell I want more of those. 313 00:21:05,560 --> 00:21:08,360 Can you please find those? And I think it does an excellent 314 00:21:08,360 --> 00:21:11,120 job in that. One question on that, is that 315 00:21:11,120 --> 00:21:14,120 feedback that you just give Claude for the current 316 00:21:14,120 --> 00:21:17,200 conversation? Or have you set up a way where 317 00:21:17,240 --> 00:21:20,560 when you give this feedback, it updates some type of document so 318 00:21:20,560 --> 00:21:22,920 it remembers that for future job searches? 319 00:21:22,920 --> 00:21:26,800 I think there is, but I I don't really do that. 320 00:21:27,000 --> 00:21:33,080 The way to to do that is to actually have a one file, one 321 00:21:33,080 --> 00:21:37,640 reference file with what kind of job requirements you want and 322 00:21:37,640 --> 00:21:42,640 then be able to cloud to analyse, to talk cloud analyse 323 00:21:42,920 --> 00:21:46,680 against this file. And this would make it kind of 324 00:21:46,680 --> 00:21:50,560 more explicit. But I kind of just tell like 325 00:21:50,560 --> 00:21:53,360 when I provide the link to to that job, I can just tell, oh, 326 00:21:53,360 --> 00:21:56,920 this sounds interesting, but well, that's kind of cool. 327 00:21:56,920 --> 00:21:59,640 I should apply. So that's kind of just like 328 00:21:59,640 --> 00:22:05,760 general comments from me. In terms of Cloud MD or like you 329 00:22:05,760 --> 00:22:09,240 mentioned the reference file, do you have any other helper files, 330 00:22:09,240 --> 00:22:11,760 reference files? Something that you set up which 331 00:22:11,960 --> 00:22:16,000 is more intended on helping guide Claude and get you to 332 00:22:16,000 --> 00:22:18,880 desired output rather than the core information you're storing 333 00:22:18,880 --> 00:22:22,280 itself. Yes, I I believe Claude MD is is 334 00:22:22,280 --> 00:22:27,240 very important. It's something that enables you 335 00:22:27,240 --> 00:22:31,400 to, to be able to just tell, oh, OK, I want to have a like a 336 00:22:31,400 --> 00:22:36,920 video idea which I want to like, for example, add and then you 337 00:22:36,920 --> 00:22:40,960 can document that in Cloud MD how to handle this request. 338 00:22:41,840 --> 00:22:48,080 And that's something I do a lot. Like I have a kind of different 339 00:22:48,080 --> 00:22:51,920 instructions in my Cloud MD for different type of kind of 340 00:22:52,520 --> 00:22:56,040 scripts to execute or different type of content which I want to 341 00:22:56,040 --> 00:22:59,240 capture. And then like without any 342 00:22:59,240 --> 00:23:03,840 context, without like any like references in the new chart, you 343 00:23:03,840 --> 00:23:10,400 can just tell, oh, OK, so let's add this video idea and then 344 00:23:10,400 --> 00:23:15,120 cloud like capture, then create a new file in Obsidian and it's 345 00:23:15,120 --> 00:23:17,920 going to be shown like with proper metadata. 346 00:23:17,960 --> 00:23:19,400 Yeah. And I think another thing, 347 00:23:19,480 --> 00:23:23,640 managing the size of this file, what helps here is to have a 348 00:23:23,920 --> 00:23:28,920 kind of references to other files like if you like need to 349 00:23:29,760 --> 00:23:35,040 add the video to my add a new video idea about like to my 350 00:23:35,040 --> 00:23:37,800 database, then like use this file. 351 00:23:38,280 --> 00:23:42,240 Here's the instructions. And it keeps it like very 352 00:23:42,760 --> 00:23:47,760 minimal and it doesn't kind of blow out the context. 353 00:23:48,080 --> 00:23:50,600 Yeah, like just in time instructions for a given task. 354 00:23:50,600 --> 00:23:54,000 Here's additional information I know for the system I'm building 355 00:23:54,040 --> 00:23:56,800 a box, one I've set up like a big mono repo, got a few 356 00:23:56,800 --> 00:23:59,680 different services inside. Every service has its own read 357 00:23:59,680 --> 00:24:03,080 me that gives instructions on the purpose, important aspects 358 00:24:03,080 --> 00:24:05,040 of of the of the app or the service. 359 00:24:05,360 --> 00:24:07,840 And then I have a root level read me that kind of directs it 360 00:24:07,840 --> 00:24:10,280 to those different things. So I can just say, hey, coding 361 00:24:10,280 --> 00:24:13,720 agent, here's your read me. Like use it as a map to explore 362 00:24:13,720 --> 00:24:16,240 the code base, find the relevant files, get the context you need 363 00:24:16,400 --> 00:24:20,120 and then execute the task. So I definitely find value in 364 00:24:20,120 --> 00:24:22,720 this. What was the phrase? 365 00:24:23,600 --> 00:24:26,760 Just like a a progressive loading of information into the 366 00:24:26,760 --> 00:24:28,760 context rather than just dumping everything all at once. 367 00:24:28,760 --> 00:24:32,000 Because one problem with MCP servers as an example is just 368 00:24:32,000 --> 00:24:35,120 the massive amount of tooling that introduced into the context 369 00:24:35,120 --> 00:24:36,440 could steer at the wrong direction. 370 00:24:37,400 --> 00:24:40,520 So do you have any other advice on helping a coding agent 371 00:24:40,600 --> 00:24:44,880 navigate through your Obsidian Vault to be able to pull up the 372 00:24:44,880 --> 00:24:46,720 proper files to get the proper context? 373 00:24:46,760 --> 00:24:50,800 Yeah, I I can't give my comment. I I was trying to design like a 374 00:24:51,800 --> 00:24:55,800 couple days ago a system where I'm going to be able to like 375 00:24:55,800 --> 00:25:00,000 prepare context for the different tasks switching to 376 00:25:00,000 --> 00:25:02,920 accomplish. I tried to design it, but then I 377 00:25:02,920 --> 00:25:07,920 realized that OK, if I'll just go to the new chart and ask 378 00:25:07,920 --> 00:25:11,520 Claude, OK, prepare context for me to continue job search. 379 00:25:11,600 --> 00:25:16,000 Actually in the minute you're going to get a great result and 380 00:25:16,000 --> 00:25:19,960 great start and it's going to get you 80% there without any 381 00:25:19,960 --> 00:25:25,280 additional information just by looking at your exploring your 382 00:25:26,000 --> 00:25:31,280 Obsidian with a genetic search using grip and then by exploring 383 00:25:31,280 --> 00:25:35,000 the the code base for kind of personal assistant use case in 384 00:25:35,000 --> 00:25:37,640 Obsidian. I think it's, it's less 385 00:25:37,640 --> 00:25:43,120 stringent of requirement to kind of properly manage the context 386 00:25:43,480 --> 00:25:47,800 if you don't get it right, but you get it like 80% right. 387 00:25:48,680 --> 00:25:51,760 It's it's very good. But I think for coding it's, 388 00:25:51,760 --> 00:25:56,760 it's much more stronger requirement to to get a proper 389 00:25:56,760 --> 00:25:59,200 context and proper understanding of the code base. 390 00:25:59,320 --> 00:26:00,920 Yeah. And also in terms of managing 391 00:26:00,920 --> 00:26:05,240 context, I think what really helps the problem which I faced 392 00:26:05,240 --> 00:26:12,160 is I have all of this goals and experiments which agent needs to 393 00:26:12,640 --> 00:26:15,560 read right understand OK, what's going on there. 394 00:26:16,640 --> 00:26:21,520 And it's, it becomes quickly unmanageable if you have if you 395 00:26:21,520 --> 00:26:25,280 need to read 10 files. So I, I was facing the issue 396 00:26:25,280 --> 00:26:30,520 where meet session, my context window would just yeah, go out. 397 00:26:30,520 --> 00:26:34,360 OK, you need to basically start a new session. 398 00:26:34,760 --> 00:26:40,160 Now the solution which I developed is have a template on 399 00:26:40,160 --> 00:26:44,800 the way you document your goals and logs. 400 00:26:45,280 --> 00:26:49,640 So we have like specific header in the markdown file and then 401 00:26:51,840 --> 00:26:55,000 it's all for all goals. It's the same. 402 00:26:55,200 --> 00:26:59,200 You document your logs in the same way. 403 00:26:59,520 --> 00:27:02,920 And now I build a parser which only parses the last three logs 404 00:27:02,920 --> 00:27:07,160 from this markdown file and it injects it into the context of 405 00:27:07,160 --> 00:27:10,240 cloud while this morning routine is happening. 406 00:27:10,400 --> 00:27:15,760 And also when you do this reflection, you need to update 407 00:27:15,760 --> 00:27:18,320 those logs. Now there is another script 408 00:27:18,640 --> 00:27:24,160 which it does updating the logs without reading the full file 409 00:27:24,200 --> 00:27:30,880 and updating it. So that's increases the speed of 410 00:27:31,560 --> 00:27:34,600 just working right. The code doesn't need to produce 411 00:27:34,600 --> 00:27:39,520 those tokens to generate a new file rather than just doing by 412 00:27:39,520 --> 00:27:43,000 script. That's something that's been 413 00:27:43,320 --> 00:27:47,920 really helpful. I also, yeah, I think it's 414 00:27:47,920 --> 00:27:52,760 something I discovered recently that all of your conversations, 415 00:27:53,120 --> 00:27:56,160 which you have with clouds, they're stored locally. 416 00:27:56,280 --> 00:27:59,320 You can access them, right? If you're using ChatGPT on the 417 00:27:59,320 --> 00:28:02,760 web, you have like no control over your data. 418 00:28:03,280 --> 00:28:06,920 So you need to like download, download it. 419 00:28:08,120 --> 00:28:12,280 And that's not the kind of dynamic, right? 420 00:28:13,160 --> 00:28:19,640 But here I can show I build a parser that enables cloud to 421 00:28:19,800 --> 00:28:23,360 kind of understand what kind of conversations have I had today. 422 00:28:23,880 --> 00:28:30,640 And also cloud can like extract the voice notes, which I kind of 423 00:28:31,560 --> 00:28:33,520 recorded today during the morning session. 424 00:28:34,440 --> 00:28:37,680 I think that's kind of very cool direction to explore. 425 00:28:38,120 --> 00:28:41,320 I think I'll just dictate the clot and I don't know how it's 426 00:28:41,320 --> 00:28:43,760 going to happen, but we'll improvise. 427 00:28:44,960 --> 00:28:50,680 Hey clot, can you please list all the sessions for today, 428 00:28:50,680 --> 00:28:55,880 which I had and extract the voice notes for my morning 429 00:28:55,880 --> 00:28:59,240 routine, which I did today and put it into my clipboard. 430 00:29:01,360 --> 00:29:06,120 Let's see if it if it would do it. 431 00:29:06,520 --> 00:29:07,840 What? How do you What do you do for 432 00:29:07,840 --> 00:29:10,600 voice notes? I use whisper flow yeah, I, I 433 00:29:10,640 --> 00:29:12,600 I've been big fan of super whisper. 434 00:29:12,880 --> 00:29:15,000 I've been a big fan of super whisper. 435 00:29:15,360 --> 00:29:19,880 But I think what really unique about whisper flow. 436 00:29:19,880 --> 00:29:23,360 I think they do some magic on on on back end that it's kind of 437 00:29:23,920 --> 00:29:27,800 instant and that's kind of deal breaker for me. 438 00:29:28,280 --> 00:29:31,920 Like if I need to wait for like a second to process my 439 00:29:31,920 --> 00:29:36,680 recording, I think it makes interaction like more like it 440 00:29:36,720 --> 00:29:40,160 puts some like more friction onto your interaction and kind 441 00:29:40,160 --> 00:29:42,760 of don't want to talk. But then it's if it's like 442 00:29:42,760 --> 00:29:45,000 instantly you kind of OK, let's do this. 443 00:29:45,760 --> 00:29:47,840 That's kind of cool. I've noticed the same thing if 444 00:29:47,960 --> 00:29:49,720 it's all about for me boot up time. 445 00:29:49,720 --> 00:29:52,400 Like I'm OK if it takes a little time to process at the end, but 446 00:29:52,400 --> 00:29:55,480 if I press the hot key to trigger my voice transcriber and 447 00:29:55,480 --> 00:29:58,560 it doesn't work right away and I have to wait, it just kills my 448 00:29:58,560 --> 00:29:59,960 flow. And it's funny how we're getting 449 00:29:59,960 --> 00:30:02,800 so like particular about this, but the whole purpose of voice 450 00:30:02,800 --> 00:30:04,320 transcriber is to increase bandwidth. 451 00:30:04,480 --> 00:30:07,680 Yeah, that's great. I think also the accuracy is 452 00:30:07,840 --> 00:30:10,000 another quick criteria, which is important. 453 00:30:11,080 --> 00:30:15,720 So I, I speak Russian language and I also, I can just mix now I 454 00:30:15,720 --> 00:30:18,040 can mix English and Russian and it's so cool. 455 00:30:18,040 --> 00:30:22,200 Like I couldn't do that two years ago. 456 00:30:22,640 --> 00:30:24,720 Now it's like very impressive, the accuracy. 457 00:30:25,560 --> 00:30:28,480 OK, but here's the workflow that I have the script. 458 00:30:28,560 --> 00:30:32,960 OK, what are the sessions which I had today and now here is a 459 00:30:32,960 --> 00:30:40,520 session ID for each of them plot code sessions and here is date. 460 00:30:41,080 --> 00:30:43,840 Now here is this number of messages. 461 00:30:44,120 --> 00:30:48,160 And I think that's important thing that it enables you to see 462 00:30:48,160 --> 00:30:50,320 what kind of flash command did you run? 463 00:30:50,480 --> 00:30:54,160 And and you're able to categorize conversations, right. 464 00:30:55,680 --> 00:30:57,800 For example, Oh, that's a reflection. 465 00:30:58,320 --> 00:31:01,520 And I can just talk about, oh, can you read this reflection and 466 00:31:01,520 --> 00:31:04,520 so on. And here is my evening routine. 467 00:31:04,600 --> 00:31:08,720 Here's my morning routine. And the next, I think what code 468 00:31:08,720 --> 00:31:15,320 does is OK, it, it copies the voice notes into my clipboard. 469 00:31:16,400 --> 00:31:20,840 So here it is, all of my voice notes from today. 470 00:31:21,720 --> 00:31:24,640 And yeah. Oh, sorry. 471 00:31:25,360 --> 00:31:28,120 OK, Yeah. And it's kind of all serves the 472 00:31:28,120 --> 00:31:31,080 context. Now I can ask So what kind of 473 00:31:31,080 --> 00:31:34,640 ideas how I had today and what kind of execute right away. 474 00:31:34,720 --> 00:31:38,600 And it's kind of just very interesting kind of use case 475 00:31:39,280 --> 00:31:45,120 that everything you do, like all the chats, it's not a waste, but 476 00:31:45,120 --> 00:31:49,200 it's like useful context on how you can like do what you can do 477 00:31:49,200 --> 00:31:50,920 right now. Yeah. 478 00:31:51,360 --> 00:31:54,680 So that's just amazing. That's super cool. 479 00:31:55,080 --> 00:31:57,480 I would love it if you could talk a little bit more about 480 00:31:57,480 --> 00:32:01,120 these scripts because one thing I preach on this show is to 481 00:32:01,120 --> 00:32:04,080 leverage deterministic code as much as possible and don't rely 482 00:32:04,080 --> 00:32:07,000 on the LMS for everything. And once you get a repeatable 483 00:32:07,000 --> 00:32:08,880 task, ask an LM to every single time. 484 00:32:08,880 --> 00:32:11,920 Is a lot of tokens wasted, a lot of money spent when you can just 485 00:32:11,920 --> 00:32:16,160 have a script that the that the coding assistant runs and then 486 00:32:16,160 --> 00:32:19,960 you get the predictable, fast, cheap output every single time. 487 00:32:19,960 --> 00:32:23,040 So what other scripts have you set up to help with your 488 00:32:23,040 --> 00:32:27,440 workflows? Yeah, I do extraction of the 489 00:32:28,760 --> 00:32:33,800 experiments because those are just the marked on files, files 490 00:32:33,800 --> 00:32:38,320 with the YAML front mother. And now like instead of like 491 00:32:38,320 --> 00:32:43,720 telling cloth OK, I list all all, all of my experiments which 492 00:32:43,720 --> 00:32:46,600 are active or list all the goals which are active. 493 00:32:46,640 --> 00:32:52,080 I I just build a script just OK, build like user script and all 494 00:32:52,080 --> 00:32:53,800 the time you get a producible output. 495 00:32:54,120 --> 00:33:01,800 And I think one cool thing about that is that when you have a 496 00:33:01,920 --> 00:33:06,480 custom flash command, when the cloud injects it, when cloud 497 00:33:06,480 --> 00:33:11,960 runs it, then what you have you have this like buck ticks, 498 00:33:12,000 --> 00:33:15,240 right? You can put the code in buck 499 00:33:15,240 --> 00:33:20,560 ticks and then it automatically executed executes it when 500 00:33:21,680 --> 00:33:26,920 command run, right? And then instead of you can what 501 00:33:26,920 --> 00:33:29,560 you can do is saying that, oh, here is the context or here you 502 00:33:29,560 --> 00:33:32,480 have a script. We just tell, oh, here are my 503 00:33:32,480 --> 00:33:35,440 active experiments. And then there is a code in buck 504 00:33:35,440 --> 00:33:39,000 ticks which you got get those experiments and once agent 505 00:33:39,000 --> 00:33:43,880 executes those it becomes a text which are actual experiments. 506 00:33:44,320 --> 00:33:46,880 Sorry, just just make sure I understand your slash commands 507 00:33:46,880 --> 00:33:50,040 have code in them which makes it a dynamic command, so it'll 508 00:33:50,040 --> 00:33:52,400 actually have different content every time you run it 509 00:33:52,480 --> 00:33:54,640 theoretically. Yes, exactly. 510 00:33:54,800 --> 00:33:56,600 Exactly. Very cool, yeah. 511 00:33:56,680 --> 00:34:00,440 So yeah, I can show how how it looks like in in practice. 512 00:34:01,000 --> 00:34:07,080 OK, I think main like evening. OK, let's do morning routine. 513 00:34:07,960 --> 00:34:13,120 Yes, I think that's example of just in time like code execution 514 00:34:13,120 --> 00:34:16,920 that here if you put in the buck ticks, that's going to be 515 00:34:17,320 --> 00:34:23,040 today's date plus time, right. And that's what you put in your 516 00:34:23,040 --> 00:34:25,440 context. It's time that H it understands 517 00:34:26,159 --> 00:34:29,400 what's happening what day of the week nowadays. 518 00:34:30,000 --> 00:34:36,159 And then I think I have those like custom flash commands, for 519 00:34:36,159 --> 00:34:41,679 example, for reviewing goals. Let's look at that review goals, 520 00:34:41,679 --> 00:34:44,239 I think yeah, I think it houses context. 521 00:34:44,239 --> 00:34:48,719 I put experiments and goals and then that just queries Python 522 00:34:48,719 --> 00:34:56,480 script to get last three like logs for active experiments and 523 00:34:56,679 --> 00:35:02,640 active goals and when cloud runs it, it becomes actual text 524 00:35:02,720 --> 00:35:07,040 rather than the datascript. So this kind of makes it 525 00:35:07,040 --> 00:35:10,720 reproducible and every time you get the kind of reliable 526 00:35:10,720 --> 00:35:12,120 results. That's really cool. 527 00:35:12,120 --> 00:35:15,640 I love having slash commands run other slash commands while 528 00:35:15,640 --> 00:35:19,280 simultaneously running code to get dynamic information. 529 00:35:19,320 --> 00:35:23,960 That's a really powerful system. That's kind of something that 530 00:35:24,680 --> 00:35:28,840 makes it reliable. I think it's big. 531 00:35:29,440 --> 00:35:32,560 Like I think that is kind of different use cases that you can 532 00:35:32,560 --> 00:35:38,280 tell agent to, OK, do this task like no supervision, like you do 533 00:35:38,280 --> 00:35:43,680 it at whatever cost. It's kind of 1 workflow to kind 534 00:35:43,680 --> 00:35:45,760 of explore, it's kind of open-ended questions. 535 00:35:46,200 --> 00:35:50,280 And then there is another workflows which are balancing 536 00:35:50,280 --> 00:35:54,600 the structure and the flexibility, right? 537 00:35:54,600 --> 00:35:58,480 Because during this more ink routines, you can go like 538 00:35:58,480 --> 00:36:02,440 different directions. You can, you can just change the 539 00:36:02,800 --> 00:36:04,680 direction of conversations the way you want. 540 00:36:06,360 --> 00:36:10,280 And I think that's kind of the power like having this balance 541 00:36:10,280 --> 00:36:15,400 of kind of how a structure, but at the same time have like full 542 00:36:15,400 --> 00:36:18,400 control of what's going on. You can ask at any time. 543 00:36:19,080 --> 00:36:21,480 OK, let's let's just change the workflow. 544 00:36:21,640 --> 00:36:24,720 I don't like that. Let's like update the template 545 00:36:24,720 --> 00:36:28,600 for the questions. Just open so much possibilities. 546 00:36:28,800 --> 00:36:31,000 And similar to the scripts, could you actually talk about 547 00:36:31,000 --> 00:36:34,360 some of the templates you have because I think giving these 548 00:36:34,600 --> 00:36:37,840 coding assistance structure that they can follow and they know 549 00:36:37,840 --> 00:36:40,240 what fields to look for if they're asking questions for an 550 00:36:40,240 --> 00:36:43,160 example are are very valuable. So, do you have any other 551 00:36:43,160 --> 00:36:45,360 templates that you would recommend to people? 552 00:36:45,360 --> 00:36:46,920 Yeah. Like those questions, they're 553 00:36:46,920 --> 00:36:50,720 just marked on files and you you can reference those. 554 00:36:50,880 --> 00:36:56,720 And if you reference them through at command, they're 555 00:36:56,760 --> 00:37:01,600 automatically kind of injects into the context without kind of 556 00:37:01,600 --> 00:37:06,240 feeling reading them. And this way kind of agent 557 00:37:06,240 --> 00:37:09,840 understands, OK, we have this template with the questions and 558 00:37:09,840 --> 00:37:14,720 we should follow that. That's kind of one way. 559 00:37:15,040 --> 00:37:18,480 I would say there's also some like mostly packages slash 560 00:37:18,480 --> 00:37:24,400 commands. I think kind of it's within the 561 00:37:24,520 --> 00:37:29,320 the custom slash commands like the you just reference those 562 00:37:29,320 --> 00:37:33,160 templates and the castle plus commands kind of create this 563 00:37:33,320 --> 00:37:36,880 structure on what is the target and interaction you want, what 564 00:37:36,880 --> 00:37:39,320 is what, what is that you want from the workflow. 565 00:37:40,040 --> 00:37:42,000 Yeah. So that's kind of all defined in 566 00:37:42,000 --> 00:37:44,200 the in the in the commands itself. 567 00:37:44,560 --> 00:37:45,520 Gotcha. OK. 568 00:37:46,480 --> 00:37:48,960 And you mentioned front matter. What? 569 00:37:49,200 --> 00:37:50,920 What do you use front matter for? 570 00:37:50,960 --> 00:37:53,040 Are you trying to be consistent across files? 571 00:37:53,040 --> 00:37:54,440 Do you have a parser for it? How? 572 00:37:54,480 --> 00:37:56,280 How does front matter help your system? 573 00:37:56,960 --> 00:38:00,280 Yeah, front matter is very is very important, important 574 00:38:00,280 --> 00:38:04,600 because it enables classification of information 575 00:38:04,680 --> 00:38:11,400 and if you have kind of classification you can create 576 00:38:11,400 --> 00:38:15,680 some structure out of that. And the main use of front matter 577 00:38:15,680 --> 00:38:21,480 is, is Obsidian basis. Is Obsidian basis enable you to 578 00:38:21,480 --> 00:38:28,120 render this front matter. And now what you can have is 579 00:38:28,120 --> 00:38:34,400 Notion like database, where you can have like full control of of 580 00:38:34,400 --> 00:38:37,440 your data and what goes into those files. 581 00:38:38,520 --> 00:38:46,160 And that's one use case such that you can filter out all of 582 00:38:46,160 --> 00:38:49,600 your notes by this front matter and display it in a structured 583 00:38:49,600 --> 00:38:52,680 way. For example, for the job search, 584 00:38:53,080 --> 00:38:56,760 like what I do, I, I track statuses like once I apply to a 585 00:38:56,760 --> 00:38:59,160 job, I, I change the status like in progress. 586 00:38:59,600 --> 00:39:04,400 Now it's something that I can like, understand and track. 587 00:39:04,680 --> 00:39:07,920 I think another case is just itself for the agents. 588 00:39:07,960 --> 00:39:11,600 Now it hasn't CML front matter. And then you can design the 589 00:39:11,600 --> 00:39:16,280 systems which enable filtering of your notes according to some 590 00:39:16,280 --> 00:39:20,280 criteria. And you can design those just 591 00:39:20,800 --> 00:39:26,720 simple parsers within like 5 minutes and get the the right 592 00:39:26,720 --> 00:39:32,000 result where agent can get like the target files which we need. 593 00:39:32,800 --> 00:39:35,080 And then it's all dynamic, right? 594 00:39:35,120 --> 00:39:38,880 Because those fields like the statuses are changing and now 595 00:39:38,880 --> 00:39:43,160 you're going to have different output like depending or you 596 00:39:43,160 --> 00:39:47,680 have this goal in progress. Now the context is different and 597 00:39:47,680 --> 00:39:50,760 this helps to kind of manage the cause of the context to get kind 598 00:39:50,760 --> 00:39:55,240 of the most updated information for your agent to kind of to 599 00:39:55,240 --> 00:39:58,360 help you to do your best work. I think that's kind of the main 600 00:39:58,480 --> 00:40:00,040 use cases. Nice. 601 00:40:00,080 --> 00:40:03,000 And actually pulling it back to your, your daily routine, which 602 00:40:03,000 --> 00:40:06,720 I think is just brilliant. When you go for your day and 603 00:40:06,720 --> 00:40:09,520 you're capturing different notes, are all your daily notes 604 00:40:09,520 --> 00:40:12,640 in one file and then that's the file that your morning routine 605 00:40:12,640 --> 00:40:15,360 parses? Or do you add front matter for 606 00:40:15,360 --> 00:40:19,400 the date and it's able to search and say between dates A&B, get 607 00:40:19,400 --> 00:40:21,680 all the files and then add that to the context? 608 00:40:22,000 --> 00:40:25,120 Yeah, it's a form for for my notes. 609 00:40:25,240 --> 00:40:31,360 I just have this Pandora timer. And I like that because it has a 610 00:40:31,360 --> 00:40:35,960 field where I can take like notes kind of like you have like 611 00:40:35,960 --> 00:40:38,520 25 minutes of your work, I don't know. 612 00:40:39,120 --> 00:40:44,000 And then at the end of the session you are given a window 613 00:40:44,000 --> 00:40:47,920 like text field where you can like just input your thought. 614 00:40:48,280 --> 00:40:50,720 And I just use it for like brain doubts. 615 00:40:50,920 --> 00:40:56,120 OK, what did they learn? What went well, what not went 616 00:40:56,120 --> 00:41:00,320 well and so on. And it just reduces friction, I 617 00:41:00,320 --> 00:41:04,240 think this coupling of timer plus taking notes. 618 00:41:04,760 --> 00:41:10,840 And then at the end of the day, I, I, I kind of parse this data. 619 00:41:10,840 --> 00:41:14,800 I just expose this data into a Jason file and it's stored on my 620 00:41:14,800 --> 00:41:17,160 computer. And then cloud just parses it 621 00:41:17,160 --> 00:41:20,400 according to today's date. What are the notes? 622 00:41:20,640 --> 00:41:22,800 What, how much time do they track today? 623 00:41:23,840 --> 00:41:25,840 What is the distribution of time and so on. 624 00:41:25,880 --> 00:41:31,880 We can do like very cool analysis there and it's not 625 00:41:32,160 --> 00:41:35,080 something that like it's an external app, but I believe you 626 00:41:35,080 --> 00:41:38,920 can do that. You can just right call it in a 627 00:41:40,000 --> 00:41:42,880 in a day or so. But what I do like to keep track 628 00:41:42,880 --> 00:41:46,640 of like kind of as I progress throughout the day, at the end 629 00:41:46,640 --> 00:41:51,240 of the morning routine, I kind of create a daily tasks file 630 00:41:51,560 --> 00:41:53,280 with all of my commitments for the day. 631 00:41:53,800 --> 00:41:58,360 And then as I progressed throughout the day, I kind of 632 00:41:58,360 --> 00:42:02,440 have very focusing sessions where of course, the plan didn't 633 00:42:02,440 --> 00:42:07,400 go as as as as planned. And now the context is 634 00:42:07,400 --> 00:42:10,080 different. And now I have like a chat with 635 00:42:10,080 --> 00:42:14,320 Clot saying, OK, let's here's my like daily commitments. 636 00:42:14,880 --> 00:42:20,520 And let's actually, I don't know, let's get refocused. 637 00:42:20,600 --> 00:42:25,080 Like like here I have like how much time left now let's work on 638 00:42:25,080 --> 00:42:27,200 something meaningful. Here's my energy levels. 639 00:42:28,080 --> 00:42:31,600 I don't know I feel like I feel like good energy. 640 00:42:31,720 --> 00:42:34,560 OK let's work on my thesis writing course something like 641 00:42:34,560 --> 00:42:38,520 that. So it's all dynamic like it's on 642 00:42:38,520 --> 00:42:41,000 demand. I think you have like very 643 00:42:41,000 --> 00:42:43,520 little structure just like 1 file, right. 644 00:42:43,520 --> 00:42:46,480 Just one file as simple as possible and then you reference 645 00:42:46,480 --> 00:42:49,960 it into the new chart. And then, OK, let's let's focus. 646 00:42:49,960 --> 00:42:53,160 That's understand how can we spend time in in efficient 647 00:42:53,160 --> 00:42:54,160 manner. Yeah. 648 00:42:54,160 --> 00:42:58,080 And actually I, I don't like take notes that don't like type 649 00:42:58,080 --> 00:43:03,120 text nowadays. Like it's all like managing like 650 00:43:03,120 --> 00:43:05,880 all the context is managed through the chat itself. 651 00:43:07,120 --> 00:43:13,040 You just like talk with kind of the new interaction which is 652 00:43:13,040 --> 00:43:14,960 emerging. It's so cool, I use voice all 653 00:43:14,960 --> 00:43:15,760 the time. Same thing. 654 00:43:15,760 --> 00:43:18,160 I feel it activates a different part of your brain. 655 00:43:18,520 --> 00:43:21,560 You're able to just get a stream of consciousness out rather than 656 00:43:21,560 --> 00:43:23,080 being meticulous with what you type. 657 00:43:24,080 --> 00:43:26,880 You've dropped a lot of great insight and advice here. 658 00:43:27,160 --> 00:43:30,480 Do you have any recommendations or a process for people who want 659 00:43:30,480 --> 00:43:31,680 to start implementing the systems? 660 00:43:31,680 --> 00:43:34,160 Like how do they get started? What do they look out for? 661 00:43:34,240 --> 00:43:37,080 What are some either tools, integrations, anything you 662 00:43:37,080 --> 00:43:38,600 recommend? How can someone go? 663 00:43:38,600 --> 00:43:42,560 From like brand new to Artem level automation. 664 00:43:42,680 --> 00:43:51,440 The best way to learn is to You learn by doing and you learn by 665 00:43:52,360 --> 00:43:57,320 making small steps size that you, you, you don't solve like 666 00:43:57,880 --> 00:44:01,200 big, big problems. Let me design a perfect system 667 00:44:01,520 --> 00:44:04,120 which is very challenging and you start designing and it's 668 00:44:04,120 --> 00:44:06,200 very demotivating, right? It's failing. 669 00:44:06,640 --> 00:44:13,800 But starting with some very simple steps, I think there is 670 00:44:14,320 --> 00:44:18,080 no way like no other way. There is no other way to learn 671 00:44:18,080 --> 00:44:23,920 it just by other than just by interacting with the EI agent 672 00:44:23,920 --> 00:44:28,000 itself, like understanding what are the boundaries, What can it 673 00:44:28,000 --> 00:44:31,080 do? Like can we do like this thing? 674 00:44:31,360 --> 00:44:34,840 OK, I think it's, it's not getting there, but that's a 675 00:44:34,840 --> 00:44:39,800 learning for me next time that I'm going to like understand the 676 00:44:39,800 --> 00:44:45,400 boundaries of what's possible and like constantly trying to 677 00:44:45,400 --> 00:44:52,880 like push it a bit. And yeah, I've kind of like, if 678 00:44:52,880 --> 00:44:56,680 you want to learn, you're just OK, well, let's open yeah, agent 679 00:44:56,680 --> 00:45:01,680 and start talking to that and let's like do something that's 680 00:45:02,240 --> 00:45:04,400 like, there is no, no, no, no other way. 681 00:45:04,720 --> 00:45:09,680 I think that planning is, is definitely changing. 682 00:45:09,800 --> 00:45:13,200 It's something that like, it's like now it's more dynamic, like 683 00:45:13,440 --> 00:45:15,280 it's kind of, I want to do something. 684 00:45:15,720 --> 00:45:18,960 OK, let's do it. It's not like I'm going to plan 685 00:45:19,320 --> 00:45:23,920 like I'm going to go for like like courses and study for that. 686 00:45:24,240 --> 00:45:27,360 Like I don't know, like I don't know, programming courses, 687 00:45:27,360 --> 00:45:29,520 whatever, whatever I want to learn. 688 00:45:29,520 --> 00:45:33,240 It's like you're just like, OK, I have a like agent right now. 689 00:45:33,360 --> 00:45:37,400 It can write any code and can study like I can study anything 690 00:45:37,400 --> 00:45:41,000 right now. That's kind of the mindset, just 691 00:45:41,000 --> 00:45:45,240 like learn by doing. I echo that statement. 692 00:45:45,240 --> 00:45:47,960 I think it's absolutely correct. Artem, you've, you've really 693 00:45:47,960 --> 00:45:50,400 inspired me to get my morning assistant morning routine going 694 00:45:50,400 --> 00:45:53,080 to try to help optimize my day. How can people keep up with you? 695 00:45:53,240 --> 00:45:58,640 I think if you find it useful, if you got some interesting 696 00:45:58,760 --> 00:46:02,480 ideas, if you got what is the one idea from this conversation 697 00:46:02,480 --> 00:46:09,040 that the success and I, I explore different use cases of 698 00:46:09,400 --> 00:46:11,960 AI according agents on my YouTube channel. 699 00:46:13,280 --> 00:46:16,880 Yeah. And I put some content. 700 00:46:16,880 --> 00:46:20,480 I think that's one main way, yeah. 701 00:46:20,760 --> 00:46:22,640 We'll we'll make sure to link it down below so everyone can find 702 00:46:22,640 --> 00:46:23,760 it. I highly recommend that you put 703 00:46:23,840 --> 00:46:26,200 together some great videos. Yeah, OK. 704 00:46:26,200 --> 00:46:29,240 Yeah, thanks. I actually I, I plan to like 705 00:46:30,000 --> 00:46:33,720 publish this feature regarding the like personal assistant for 706 00:46:33,720 --> 00:46:36,600 more encryption. So yeah, it's gonna be 707 00:46:36,600 --> 00:46:37,760 available. Perfect. 708 00:46:38,120 --> 00:46:40,000 Thank you so much for coming on. We'll we'll talk to you soon. 709 00:46:40,480 --> 00:46:41,400 All right. Thanks. 710 00:46:41,560 --> 00:46:42,760 Thanks, Mike. Great chat. 711 00:46:43,200 --> 00:46:45,040 Thank you for listening to my conversation with Artem. 712 00:46:45,520 --> 00:46:48,880 Artem and I met months ago and we're always talking about AI 713 00:46:48,880 --> 00:46:51,640 for productivity or how we optimize our Obsidian vaults. 714 00:46:51,920 --> 00:46:55,160 And we met through an in person event via AI tinkerers. 715 00:46:55,480 --> 00:46:58,120 And this week's call to action is, is just for people in 716 00:46:58,120 --> 00:47:00,400 Waterloo. I want you to start coming up to 717 00:47:00,400 --> 00:47:02,720 more events. We have a great community being 718 00:47:02,720 --> 00:47:05,160 built in Waterloo. There are so many strong 719 00:47:05,160 --> 00:47:07,480 engineers and ambitious founders, and we're trying to 720 00:47:07,480 --> 00:47:09,800 get them all together and build these relationships and with 721 00:47:09,800 --> 00:47:12,640 connections so we can teach each other, learn from each other, 722 00:47:12,640 --> 00:47:15,160 and help the ecosystem grow. So if you're located in 723 00:47:15,160 --> 00:47:17,280 Waterloo, please reach out. I'd love to hear from you, 724 00:47:17,440 --> 00:47:19,920 whether it's through the Discord or on social media. 725 00:47:20,160 --> 00:47:21,680 There are lots of ways that we can get in touch. 726 00:47:21,720 --> 00:47:23,680 And I want to let you know about the events we have planned. 727 00:47:23,680 --> 00:47:26,840 So whether it's AI tinkerers or Ravella Collective or maybe some 728 00:47:26,840 --> 00:47:29,360 other ones that we have in the works, we want to start building 729 00:47:29,360 --> 00:47:32,840 this ecosystem, bringing people together in real life so we can 730 00:47:32,840 --> 00:47:36,040 optimize the way that we learn and grow together for everyone 731 00:47:36,040 --> 00:47:37,320 else. I'll see you next week.