WEBVTT

1
00:00:00.000 --> 00:00:04.400
All right, looks like we're live.

2
00:00:04.400 --> 00:00:08.840
So if you guys are watching this for the first time, we are going to start streaming to Facebook.

3
00:00:08.840 --> 00:00:14.600
We normally don't stream to Facebook, but normally all of our streams are on YouTube

4
00:00:14.600 --> 00:00:16.280
and X.

5
00:00:16.280 --> 00:00:22.080
And so we have a development agency that we've been going since 2010.

6
00:00:22.080 --> 00:00:27.600
And just recently we've been dealing and experimenting with a lot of AI, as you can imagine.

7
00:00:27.600 --> 00:00:31.280
Someone recently asked me, like, oh, aren't you super scared about how AI is changing

8
00:00:31.280 --> 00:00:32.280
code?

9
00:00:32.280 --> 00:00:36.440
I was like, no, this is the best time to be alive as a developer.

10
00:00:36.440 --> 00:00:37.840
We were able to improve our process.

11
00:00:37.840 --> 00:00:42.800
We spent a lot of time the last 12 months kind of working on our process as far as getting

12
00:00:42.800 --> 00:00:48.040
really, really smart about shaping and framing projects really well, breadboarding things,

13
00:00:48.040 --> 00:00:51.320
and helping do kind of the thinking side of it first.

14
00:00:51.320 --> 00:00:56.420
And then eventually moving that into then leveraging the AI to go execute on all this

15
00:00:56.420 --> 00:00:57.420
as well.

16
00:00:58.240 --> 00:01:00.580
So we're building some new tools every single week.

17
00:01:00.580 --> 00:01:06.020
And so rather than me try to build some playbooks for our team, we're just hopping on once a

18
00:01:06.020 --> 00:01:11.060
week and just talking for an hour and kind of showing what I'm doing as far as process

19
00:01:11.060 --> 00:01:12.700
goes, what some of our team are doing.

20
00:01:12.700 --> 00:01:15.500
So if you think that's cool, follow along.

21
00:01:15.500 --> 00:01:18.420
We'll try to keep these coming each week.

22
00:01:18.420 --> 00:01:21.500
And if you're interested, we actually have a whole course now.

23
00:01:21.500 --> 00:01:24.140
So if you're looking at the description, you can jump on that course.

24
00:01:24.140 --> 00:01:26.500
And we have all this kind of broken into a course.

25
00:01:26.580 --> 00:01:29.980
And you can check out our workflow and some of our best practices.

26
00:01:29.980 --> 00:01:36.740
And I think we even have like all of our long sessions we had with Ryan Singer are all in

27
00:01:36.740 --> 00:01:37.780
that course as well.

28
00:01:37.780 --> 00:01:39.860
So check that out.

29
00:01:39.860 --> 00:01:44.540
So I'm going to jump over and like talk a little bit about our process as it stands

30
00:01:44.540 --> 00:01:45.540
today.

31
00:01:45.540 --> 00:01:47.460
I've got my team around here as well.

32
00:01:47.460 --> 00:01:52.060
So we may jump on if they have questions or you guys want to comment on anything, just

33
00:01:52.060 --> 00:01:53.540
message me there.

34
00:01:54.540 --> 00:02:00.100
So one thing I thought would be helpful would be like to go through like a reactive task.

35
00:02:00.100 --> 00:02:05.820
So typically we have like project work, which we've talked a little bit about previously

36
00:02:05.820 --> 00:02:15.300
where we may have like a bunch of tasks where we like break things into task grid or something

37
00:02:15.300 --> 00:02:16.700
where we frame it.

38
00:02:16.700 --> 00:02:21.500
Last week, we went through and actually a little bit of a project within a project here.

39
00:02:21.500 --> 00:02:27.980
So we took our dashboard and we just framed a project.

40
00:02:27.980 --> 00:02:29.660
So we kind of figure out what the problem is.

41
00:02:29.660 --> 00:02:32.580
We figure out what the outcome is, what's out of bounds, what the appetite is.

42
00:02:32.580 --> 00:02:36.740
So this is typically what a document looks like when it comes into our system.

43
00:02:36.740 --> 00:02:41.740
So when you're starting any new project here, this is sort of the flow is to get a framed

44
00:02:41.740 --> 00:02:42.740
project.

45
00:02:42.740 --> 00:02:45.220
There's a whole process for doing that.

46
00:02:45.220 --> 00:02:49.460
We drop it in here into our dashboard and we can present it to the client and then we'll

47
00:02:49.460 --> 00:02:54.540
actually get a signature or sign off from them to move this out.

48
00:02:54.540 --> 00:02:56.380
And this kind of becomes our contract.

49
00:02:56.380 --> 00:02:58.020
It's not solutions based.

50
00:02:58.020 --> 00:03:02.060
It's very much like here's the problem and here's what we want the outcome to be.

51
00:03:02.060 --> 00:03:04.860
There may be a bunch of solutions that help us get to this outcome.

52
00:03:04.860 --> 00:03:07.700
So it gives a little bit of flexibility to that.

53
00:03:07.700 --> 00:03:09.700
And then we get very specific about what we're not doing.

54
00:03:09.700 --> 00:03:13.660
And this typically creates a much more precision around sort of the frame of where does this

55
00:03:13.660 --> 00:03:16.300
project start and end.

56
00:03:16.300 --> 00:03:20.820
Once we do that, we move it into get really specific and we create a task grid.

57
00:03:20.820 --> 00:03:29.940
And so I show these to you here because we have like some MCP tools and a CLI agent now

58
00:03:29.940 --> 00:03:33.780
that we're using that will help you organize these.

59
00:03:33.780 --> 00:03:38.300
And you can actually sign in like from the terminal or you could use Cloud or you can

60
00:03:38.300 --> 00:03:46.380
use chat GPT and connect by MCP to the dashboard and have it write all these tasks up for you

61
00:03:46.380 --> 00:03:47.380
very quickly.

62
00:03:47.380 --> 00:03:52.420
These are all super awesome tools to help get things out quickly.

63
00:03:52.420 --> 00:03:57.020
And then recently we've also added this task piece, which is actually connecting to Notion

64
00:03:57.020 --> 00:03:58.020
now.

65
00:03:58.020 --> 00:04:01.900
So we can kind of have a task grid, which is like go build a new feature, slice it up

66
00:04:01.900 --> 00:04:03.460
into different verticals.

67
00:04:03.460 --> 00:04:06.460
And then task is kind of like reactive work.

68
00:04:06.460 --> 00:04:12.980
So I'm just going to show you like the workflow I used for a reactive task yesterday, kind

69
00:04:12.980 --> 00:04:18.899
of how that flow went from, you know, from getting the message to like how we framed

70
00:04:18.899 --> 00:04:24.300
it up and then how we used Cloud to like basically write up a plan for it.

71
00:04:24.300 --> 00:04:27.940
We wrote the plan back into Notion and then we went and executed there.

72
00:04:27.940 --> 00:04:30.940
So I'll just sort of talk about the process here.

73
00:04:30.940 --> 00:04:34.820
So a client typically like comes in here, they give us a new Slack, I mean, a new task.

74
00:04:34.820 --> 00:04:36.660
This could be like in Slack.

75
00:04:36.660 --> 00:04:41.980
Yesterday it was actually in a text message, which is like my favorite way to get reactive

76
00:04:41.980 --> 00:04:43.060
work.

77
00:04:43.060 --> 00:04:48.180
But Slack, maybe it's coming through an email, something comes in the door here.

78
00:04:48.180 --> 00:04:53.820
So typically what we do is we would actually start this by essentially kicking off like

79
00:04:53.820 --> 00:04:59.940
a new thing here, which would be just to like, I would say just the planning.

80
00:05:00.000 --> 00:05:06.080
piece. So we take everything we know here and have your, and I'm just going to, I'm going to use

81
00:05:06.080 --> 00:05:10.800
Cloud or AI kind of interchangeably. I'm using Cloud for everything. I know some people using

82
00:05:11.360 --> 00:05:17.360
Codex or using other LLMs, but I'll use AI and Cloud interchangeably, you'll see.

83
00:05:17.920 --> 00:05:27.600
So we'll say AI, basically like discover the project and then also go and basically write a

84
00:05:27.600 --> 00:05:33.120
plan. And this will be written into Notion. So I'll just go ahead and try to do this for you

85
00:05:33.120 --> 00:05:41.600
guys live. So we have a project here. I'm going to open up terminal and then let's just get this

86
00:05:42.560 --> 00:05:51.120
cleared out here. Make it nice and big. Oops. There we go. Sorry. It's a little bit weird

87
00:05:51.120 --> 00:05:55.520
with the screen share here. Okay. So we'll go ahead and kick off Cloud here and I'm going to go

88
00:05:56.240 --> 00:06:05.360
and grab a task. So let's, let's go into Slack. So we actually have a task here where

89
00:06:05.360 --> 00:06:12.880
one of our friends, Steven, sent us a task to notify groups. So luckily, nicely,

90
00:06:13.760 --> 00:06:21.440
he did here for us was to actually give us a video. And the best thing about video is a transcript.

91
00:06:21.440 --> 00:06:26.800
So I'm going to just take all that. We've exported that. I'm going to just save it to

92
00:06:26.800 --> 00:06:33.280
like feature idea here. And I can now bring this into my chat. So I can do this obviously in the

93
00:06:33.280 --> 00:06:38.720
terminal. I'm also going to like show you guys, like you could use Cloud directly to do this.

94
00:06:38.720 --> 00:06:44.000
If you want to use the desktop app, I've been using them together quite a bit. So it doesn't

95
00:06:44.000 --> 00:06:50.960
have to be quite as technical as using the, using this here. So what I'll do to speed things up is

96
00:06:50.960 --> 00:06:59.360
to grab that file real quick. I'm just going to paste it in. I'm not going to, I know Lucien's

97
00:06:59.360 --> 00:07:05.200
probably paranoid. We're going to blow some tokens real quick. So I'm like, help me like

98
00:07:05.200 --> 00:07:14.960
frame this project up for, it would be like tribe social reactive, like for March and make like,

99
00:07:14.960 --> 00:07:25.600
so I'll just say like planet. And then, and this feature, actually this particular one is in a,

100
00:07:25.600 --> 00:07:28.720
in a different, let's just do this real quick. I'm going to switch it to this.

101
00:07:31.520 --> 00:07:36.720
Okay. I just have them in two separate projects right now. So let's go over here, help us frame

102
00:07:36.720 --> 00:07:44.800
this up. And I'll go back to my text here, planet, and then like make a task in Notion

103
00:07:47.280 --> 00:07:56.400
using Lenovo CP and set to like dev ready. So now I'm going to just paste the transcript here

104
00:07:56.960 --> 00:08:02.560
and let it go and turn. So we're in plan mode. I'm going to kill this. And I do this in the project

105
00:08:02.560 --> 00:08:07.920
because then it can go and actually use the context of the project itself. So it's going to

106
00:08:07.920 --> 00:08:11.920
give it a second there and what's going to happen, we're going to see this happen here sort of in

107
00:08:11.920 --> 00:08:21.040
real time is go over to Notion and I'm going to go to our tribe reactive. So come on, where's my

108
00:08:21.040 --> 00:08:33.840
shortcuts? Okay. Reactive. Oops. Sorry, my keyboard just seems to be not liking the screen share.

109
00:08:35.440 --> 00:08:44.240
March 26. So this is how we track little tasks of bugs that pop up. So yesterday, while that's

110
00:08:44.240 --> 00:08:50.560
churning behind here, I took a bunch of new features that were happening in like our chat DM.

111
00:08:50.560 --> 00:08:57.600
And this is kind of what it did. Like I wrote the plan up and then it came in to Notion

112
00:08:57.600 --> 00:09:03.600
with a full plan. And I just liked it in here because it helped me track where it was in like

113
00:09:03.600 --> 00:09:08.800
sort of my interface back to the company. I'll show you as well, something that we're starting

114
00:09:08.800 --> 00:09:14.400
to draw a little bit more as a team here as we're kind of thinking of like this is like we've built

115
00:09:14.400 --> 00:09:19.440
this sort of centralized hub of knowledge using the MCP and the CLI. And you can like, there's

116
00:09:19.440 --> 00:09:26.240
some API stuff here. And the dashboard, which you saw over here is like one layer to that. We have

117
00:09:26.240 --> 00:09:31.920
a client dashboard of a team dashboard. It's all kind of in one, it's sort of our default UI layer.

118
00:09:32.480 --> 00:09:38.400
But I can also sit here, like some of our team members can sit there. We use Notion as a tool,

119
00:09:38.400 --> 00:09:42.240
but I'm just using Notion. Notion's just reading what's going on in here. And my MCP is just

120
00:09:42.240 --> 00:09:46.560
talking to what's going on in here. Notion happens to be like a nice way to view all that,

121
00:09:46.640 --> 00:09:52.800
that has statuses and tracks it. And I can just see it in like a familiar view. But what happened

122
00:09:52.800 --> 00:09:56.640
is a new task came in here and then we pulled the task down, we worked on it. And then you can see

123
00:09:57.840 --> 00:09:59.840
Claude made notes in the comments here.

124
00:10:00.000 --> 00:10:02.160
so I could track what it was doing.

125
00:10:02.160 --> 00:10:04.360
And then I can always assign this to a different team

126
00:10:04.360 --> 00:10:05.160
member if I wanted.

127
00:10:05.160 --> 00:10:06.660
I can change, obviously, the status.

128
00:10:06.660 --> 00:10:10.120
I can move them around from there.

129
00:10:10.120 --> 00:10:13.560
And so let me see where we're at right here.

130
00:10:13.560 --> 00:10:15.040
I have a pretty good this.

131
00:10:15.040 --> 00:10:18.320
And I have not framed this beforehand.

132
00:10:18.320 --> 00:10:19.720
I'm just doing this all live.

133
00:10:19.720 --> 00:10:22.600
So we'll see how great or not great it is.

134
00:10:22.600 --> 00:10:25.960
And perfect, it says there's no MCP.

135
00:10:25.960 --> 00:10:29.880
So this is going to be a great, very fun demo.

136
00:10:29.880 --> 00:10:32.760
Even though it does have MCP, so let's just teach it

137
00:10:32.760 --> 00:10:33.800
something real quick here.

138
00:10:33.800 --> 00:10:34.300
We do.

139
00:10:37.400 --> 00:10:40.440
It's probably running.

140
00:10:40.440 --> 00:10:42.640
Great, great example.

141
00:10:42.640 --> 00:10:47.120
So I will stop sharing for just a second.

142
00:10:47.120 --> 00:10:50.000
Get CP to back up.

143
00:10:50.000 --> 00:10:51.080
Let's see here.

144
00:10:51.080 --> 00:10:54.680
I think I'm not going to be able to do it without you guys seeing it.

145
00:10:54.680 --> 00:10:56.760
Demo-linus.

146
00:10:56.800 --> 00:11:00.280
Yes, this is a real demo.

147
00:11:00.280 --> 00:11:03.200
So we'll go through this and just see frame up.

148
00:11:03.200 --> 00:11:06.400
So what you could do is show you, like,

149
00:11:06.400 --> 00:11:08.160
I haven't even watched the video yet.

150
00:11:08.160 --> 00:11:10.480
Now, I did watch the video.

151
00:11:10.480 --> 00:11:13.160
Steven, if you're watching this, I watched the video.

152
00:11:13.160 --> 00:11:15.840
But I'm just, this is how fast.

153
00:11:15.840 --> 00:11:17.720
I don't have to watch the video.

154
00:11:17.720 --> 00:11:20.280
I'm taking the transcript and I'm shoving it in here.

155
00:11:20.280 --> 00:11:24.600
And it's basically asking for, it's

156
00:11:24.600 --> 00:11:27.480
starting to put a plan together that then we can just

157
00:11:27.480 --> 00:11:30.760
create the task and then hand this off to a developer.

158
00:11:30.760 --> 00:11:34.360
Or if you want to go work on it yourself, you can too.

159
00:11:34.360 --> 00:11:37.280
So it's kind of getting hung up on this MCP stuff.

160
00:11:37.280 --> 00:11:41.000
It's probably because I moved this directory right

161
00:11:41.000 --> 00:11:41.880
before the call.

162
00:11:41.880 --> 00:11:45.280
I had tried to be fancy and organize some things.

163
00:11:45.280 --> 00:11:52.000
Let's just do this as like a, we'll just, yeah,

164
00:11:52.000 --> 00:11:53.720
we'll just go ahead and have it.

165
00:11:53.720 --> 00:11:56.080
Sorry, go through this here.

166
00:11:56.080 --> 00:11:58.360
So we'll skip the Notion piece.

167
00:11:58.360 --> 00:12:01.080
You can, with one prompt, basically

168
00:12:01.080 --> 00:12:03.280
have it write it all to Notion, make the new task, which

169
00:12:03.280 --> 00:12:05.320
is kind of a magic trick here.

170
00:12:05.320 --> 00:12:06.960
And so now it's kind of written up this.

171
00:12:06.960 --> 00:12:09.720
Now, this would be like now for a developer.

172
00:12:09.720 --> 00:12:11.680
So the reason I wanted to break it into Notion

173
00:12:11.680 --> 00:12:13.480
is that if you were just capturing

174
00:12:13.480 --> 00:12:16.000
this task from a client, we could just write this back.

175
00:12:16.000 --> 00:12:17.840
You don't even have to know what any of this

176
00:12:17.840 --> 00:12:20.880
is, but you can kind of write this in so that it kind of comes

177
00:12:20.880 --> 00:12:23.440
in with a very specific.

178
00:12:23.520 --> 00:12:26.120
I used the word frame, and so it got a little carried away

179
00:12:26.120 --> 00:12:28.760
and framed the task, which is kind of like a little mini

180
00:12:28.760 --> 00:12:31.320
project, I guess.

181
00:12:31.320 --> 00:12:33.600
But we can kind of read this now in a much better way,

182
00:12:33.600 --> 00:12:37.120
because when it comes in through Slack, it's a video.

183
00:12:37.120 --> 00:12:38.920
So I'm going to have to watch the video.

184
00:12:38.920 --> 00:12:39.800
It's two minutes.

185
00:12:39.800 --> 00:12:42.760
We have to kind of understand what they're wanting to do.

186
00:12:42.760 --> 00:12:45.040
What screen does this actually connect to?

187
00:12:45.040 --> 00:12:50.000
What other problems might this cause if we added this?

188
00:12:50.000 --> 00:12:51.680
But this helps us just kind of put it

189
00:12:51.680 --> 00:12:55.120
in a much easier-to-read format.

190
00:12:55.120 --> 00:12:56.580
So they're saying like, hey, there's

191
00:12:56.580 --> 00:12:59.600
admins who manage multiple communities on Tribe,

192
00:12:59.600 --> 00:13:01.000
and they send the same notification

193
00:13:01.000 --> 00:13:02.440
to several groups at once.

194
00:13:02.440 --> 00:13:04.720
Today, the flow is that you open the notification form,

195
00:13:04.720 --> 00:13:07.240
you select one group, fill in title, you hit Send,

196
00:13:07.240 --> 00:13:08.980
and then you repeat steps one through four

197
00:13:08.980 --> 00:13:10.360
for every single group.

198
00:13:10.360 --> 00:13:14.080
Steven, misspelled, and it just guessed it,

199
00:13:14.080 --> 00:13:16.880
like made up a company that it's not connected to,

200
00:13:16.880 --> 00:13:18.720
reports doing this four times per session,

201
00:13:18.720 --> 00:13:20.400
and it's kind of a pain.

202
00:13:20.400 --> 00:13:24.520
And so the solution would be to have some sort of multi-select

203
00:13:24.520 --> 00:13:25.120
groups.

204
00:13:25.120 --> 00:13:29.680
So admin can pick two groups, and they only have one API

205
00:13:29.680 --> 00:13:31.340
call, and it does a bunch of stuff here.

206
00:13:31.340 --> 00:13:33.960
So the front end, so now, see, I've got very specific now.

207
00:13:33.960 --> 00:13:35.960
Like, hey, we're going to replace a single group

208
00:13:35.960 --> 00:13:39.080
dropdown, the multi-select dropdown.

209
00:13:39.080 --> 00:13:41.640
Back end needs to accept these different group IDs,

210
00:13:41.640 --> 00:13:44.200
and then deduplicate a bunch of stuff.

211
00:13:44.200 --> 00:13:45.440
Firebase is storing that.

212
00:13:45.440 --> 00:13:46.320
OK, blah, blah, blah.

213
00:13:46.320 --> 00:13:49.920
So it's kind of got into the weeds of it here.

214
00:13:49.920 --> 00:13:53.760
It's using definitely an older training here

215
00:13:53.760 --> 00:13:54.800
on what framing is.

216
00:13:54.800 --> 00:13:57.440
I'm not sure where it got these no-gos and rabbit holes.

217
00:13:57.440 --> 00:14:00.400
We don't use that so much anymore.

218
00:14:00.400 --> 00:14:02.160
But it's got a little notification

219
00:14:02.160 --> 00:14:03.240
into implementation plans.

220
00:14:03.240 --> 00:14:05.240
This could kind of help get the task in,

221
00:14:05.240 --> 00:14:07.080
and we could sort of dump that into Notion,

222
00:14:07.080 --> 00:14:08.700
and then we could assign it to someone.

223
00:14:08.700 --> 00:14:10.440
So this is a great little pre-step

224
00:14:10.440 --> 00:14:12.920
to getting the project in.

225
00:14:12.920 --> 00:14:14.960
Now, it would be good to read through this,

226
00:14:14.960 --> 00:14:16.920
make changes to the plan, but then you

227
00:14:16.920 --> 00:14:18.880
could use the MCP to pull the task down,

228
00:14:18.880 --> 00:14:22.320
and then work on it, and kind of work your way through that

229
00:14:22.320 --> 00:14:22.800
as well.

230
00:14:22.800 --> 00:14:26.400
So the main thing here would be to show you

231
00:14:26.400 --> 00:14:28.440
how it writes to Notion and comes back,

232
00:14:28.440 --> 00:14:31.440
and then how you can pull tasks down from Notion as well.

233
00:14:31.440 --> 00:14:34.280
So maybe I'll take a second and get that,

234
00:14:34.280 --> 00:14:38.360
or maybe just be better prepared next time for this demo.

235
00:14:38.360 --> 00:14:42.760
But that's sort of how we would go about pulling this in.

236
00:14:42.760 --> 00:14:45.960
Let me go back to my little diagram here.

237
00:14:45.960 --> 00:14:48.600
We'd pull this in, we'd plan it here.

238
00:14:49.200 --> 00:14:50.760
And then this would send it to Notion.

239
00:14:50.760 --> 00:14:53.960
This would actually do the planning piece.

240
00:14:53.960 --> 00:14:55.760
And then I'll put this under the human part,

241
00:14:55.760 --> 00:14:58.120
but it would essentially, like, right here,

242
00:14:58.120 --> 00:15:00.960
we'll actually write to Notion.

243
00:15:00.000 --> 00:15:04.240
and write up a plan and a task in Notion here,

244
00:15:04.240 --> 00:15:06.680
which we can review and comment on and do things there.

245
00:15:06.680 --> 00:15:09.660
So it kind of makes it a little more accessible again.

246
00:15:09.660 --> 00:15:11.640
And then anyone on the team could actually

247
00:15:11.640 --> 00:15:16.120
pull that task, kick off, basically,

248
00:15:16.120 --> 00:15:18.160
start a work session.

249
00:15:18.160 --> 00:15:20.480
And we can kick it back over to AI

250
00:15:20.480 --> 00:15:23.640
to go ahead and do that task.

251
00:15:23.640 --> 00:15:27.320
Once it's finished, then it kicks back to review.

252
00:15:27.320 --> 00:15:29.560
We're talking about one day having it run local tests.

253
00:15:30.360 --> 00:15:33.080
But say it would run it, and it would comment here

254
00:15:33.080 --> 00:15:37.280
and give us a PR link, essentially, to finish that off.

255
00:15:37.280 --> 00:15:40.880
And so what we're doing is we're still using the human layer

256
00:15:40.880 --> 00:15:42.480
to do the planning.

257
00:15:42.480 --> 00:15:44.760
We're still using the human of when to start it.

258
00:15:44.760 --> 00:15:46.720
And it has to review the plan and make sure

259
00:15:46.720 --> 00:15:49.240
that it actually looks like a solid solution.

260
00:15:49.240 --> 00:15:51.880
But a lot of the time as well, we're

261
00:15:51.880 --> 00:15:53.840
talking even about simplifying this.

262
00:15:53.840 --> 00:15:59.200
Once it plans it, don't worry about this is sort of the,

263
00:15:59.200 --> 00:16:00.680
I'll put this in a different color.

264
00:16:00.680 --> 00:16:05.760
But this is very much like a safety net right now.

265
00:16:05.760 --> 00:16:09.280
In future versions, why would you not just do this?

266
00:16:09.280 --> 00:16:12.160
Why would you just take these two things out?

267
00:16:12.160 --> 00:16:15.640
Plan it, finish it, and then just comment back.

268
00:16:15.640 --> 00:16:18.720
Because coding is so cheap and tokens are so cheap,

269
00:16:18.720 --> 00:16:21.360
why would we just not let it just take a stab at it?

270
00:16:21.360 --> 00:16:24.000
And this is actually what I've been doing recently,

271
00:16:24.000 --> 00:16:25.960
going into the planning, reviewing it, and just

272
00:16:25.960 --> 00:16:28.000
executing on it, and letting it go right back

273
00:16:28.000 --> 00:16:30.840
into the first time I look at it,

274
00:16:30.840 --> 00:16:33.760
again, is when it's in review mode.

275
00:16:33.760 --> 00:16:39.200
And this starts to get into what I'm referring to now

276
00:16:39.200 --> 00:16:42.520
as somewhat of a code factory, a small version of this, where

277
00:16:42.520 --> 00:16:45.080
you basically have tasks being built up here.

278
00:16:45.080 --> 00:16:46.480
And then you can kind of see what

279
00:16:46.480 --> 00:16:48.120
the AI is working on in the in progress.

280
00:16:48.120 --> 00:16:49.700
And then it's being moved to in review.

281
00:16:49.700 --> 00:16:52.360
And then a human is coming back into the in review piece

282
00:16:52.360 --> 00:16:54.720
and moving them into completed.

283
00:16:54.720 --> 00:16:57.960
Or you can basically click in here.

284
00:16:57.960 --> 00:16:59.080
This is a bad example.

285
00:16:59.080 --> 00:17:03.640
But if this was an AI task like this one,

286
00:17:03.640 --> 00:17:07.680
I can select this, go into Cloud, and say, hey, work on,

287
00:17:07.680 --> 00:17:09.119
and then paste title.

288
00:17:09.119 --> 00:17:12.400
And it will just go and find that task somewhere in Notion.

289
00:17:12.400 --> 00:17:14.880
It'll pull everything in the plan

290
00:17:14.880 --> 00:17:17.480
here, which you can see is quite extensive,

291
00:17:17.480 --> 00:17:19.480
plus all of the comments it's made,

292
00:17:19.480 --> 00:17:21.079
so the incremental updates.

293
00:17:21.079 --> 00:17:24.200
It kind of uses it as memory bank.

294
00:17:24.200 --> 00:17:25.700
And then you can keep working on it.

295
00:17:25.700 --> 00:17:28.380
So this happened as well, where it went into review.

296
00:17:28.380 --> 00:17:29.980
And I was like, great, this is perfect.

297
00:17:29.980 --> 00:17:31.020
I mark it as completed.

298
00:17:31.020 --> 00:17:32.660
And then I go into something else.

299
00:17:32.660 --> 00:17:35.020
And then I find out there's actually a bug that happened.

300
00:17:35.020 --> 00:17:36.340
So I basically bring it back out.

301
00:17:36.340 --> 00:17:37.180
We work on it again.

302
00:17:37.180 --> 00:17:39.420
And so you can see there's kind of some different work

303
00:17:39.420 --> 00:17:42.660
sessions here where we went back and forth on that.

304
00:17:42.660 --> 00:17:44.380
And I did all this in a separate branch.

305
00:17:44.380 --> 00:17:46.900
And then we just did one PR that moved all four or five

306
00:17:46.900 --> 00:17:49.660
of these somewhat related upgrades

307
00:17:49.660 --> 00:17:54.180
to this one chat component, all in one move.

308
00:17:54.180 --> 00:17:58.740
So that was kind of the flow yesterday.

309
00:17:58.740 --> 00:18:00.340
I basically took these two steps out

310
00:18:00.340 --> 00:18:04.500
and just went straight from planning directly

311
00:18:04.500 --> 00:18:06.500
into do the work.

312
00:18:06.500 --> 00:18:08.380
And then what I was doing is just sort

313
00:18:08.380 --> 00:18:10.220
of monitoring it in real time.

314
00:18:10.220 --> 00:18:12.700
And so maybe there's some overlap here,

315
00:18:12.700 --> 00:18:16.740
where it was probably just an observer.

316
00:18:16.740 --> 00:18:21.380
Because this is a mobile app, so we kind of have to test it.

317
00:18:21.380 --> 00:18:23.740
It's just easier to test on my physical device.

318
00:18:23.740 --> 00:18:25.700
I did all that, marked everything as completed,

319
00:18:25.700 --> 00:18:27.540
pushed it all to web, sent it off

320
00:18:27.540 --> 00:18:31.500
to the production for the web.

321
00:18:31.500 --> 00:18:33.340
And I was like, I'll just set up the iPhone.

322
00:18:33.340 --> 00:18:35.300
And I pulled up the iPhone, and half the things

323
00:18:35.300 --> 00:18:38.020
didn't work once I switched to a real iPhone device.

324
00:18:38.020 --> 00:18:39.660
So then I had to go back into it.

325
00:18:39.660 --> 00:18:41.700
And it was pretty easy at that point

326
00:18:41.700 --> 00:18:46.060
to just prompt it a few more times to fix the iOS version.

327
00:18:46.060 --> 00:18:49.460
So that's kind of like our flow.

328
00:18:49.460 --> 00:18:52.380
Hopefully that's helpful to some of you.

329
00:18:52.380 --> 00:18:53.740
I'll pull this up as well.

330
00:18:53.740 --> 00:18:56.820
We did add this AI course I mentioned at the beginning.

331
00:18:56.820 --> 00:18:59.060
So this course, our team has gone through this.

332
00:18:59.060 --> 00:19:01.860
You can see this little free about how we frame, shape,

333
00:19:01.860 --> 00:19:03.460
and ship projects.

334
00:19:03.460 --> 00:19:06.420
And you can see all the framing stuff we talked about,

335
00:19:06.420 --> 00:19:09.180
how we're building, how we're communicating with clients,

336
00:19:09.180 --> 00:19:09.860
doing AI stuff.

337
00:19:09.860 --> 00:19:11.740
So we're looking to build our team this year.

338
00:19:11.740 --> 00:19:13.380
So if this stuff is interesting to you,

339
00:19:13.380 --> 00:19:16.060
and you'd like to nerd out about it, dive into the course.

340
00:19:16.060 --> 00:19:20.260
And then definitely connect with us, and we'd love to chat.

341
00:19:20.260 --> 00:19:21.940
So I'll probably end the stream there,

342
00:19:21.980 --> 00:19:23.540
and then we'll hang out with the team,

343
00:19:23.540 --> 00:19:26.580
and we'll do some more conversation.

344
00:19:26.580 --> 00:19:28.620
So thanks, guys.