Meeting Title: ABC Roadmap and Allocations Final Check-In Date: 2026-03-18 Meeting participants: Brylle Girang, Pranav Narahari, Samuel Roberts, Uttam Kumaran
WEBVTT
1 00:02:32.370 ⇒ 00:02:33.350 Pranav Narahari: Hey, B.
2 00:02:39.150 ⇒ 00:02:40.410 Brylle Girang: Hello?
3 00:02:42.400 ⇒ 00:02:47.460 Pranav Narahari: Hey, I just noticed that this meeting’s only 15, so… Probably…
4 00:02:47.640 ⇒ 00:02:52.690 Pranav Narahari: Just kind of want to talk to you about, like, how do you kind of just want to go about presenting this?
5 00:02:52.820 ⇒ 00:02:55.220 Pranav Narahari: I tried to share my screen, go over the…
6 00:02:55.410 ⇒ 00:02:57.890 Pranav Narahari: the docs, it should be pretty straightforward, but…
7 00:02:58.070 ⇒ 00:03:00.650 Pranav Narahari: Just want to make sure we make best use of time.
8 00:03:01.170 ⇒ 00:03:06.829 Brylle Girang: Yeah, we just need, like, the final confirmation of, like, the roadmap.
9 00:03:07.050 ⇒ 00:03:18.670 Brylle Girang: when are we going to finish the proposals? When are we planning to do those proposals? And then, like, the allocations. Mainly, Otam wants to know, like.
10 00:03:18.820 ⇒ 00:03:27.100 Brylle Girang: How many hours will the engineers and the people working on this project I’ll be dedicating to
11 00:03:28.200 ⇒ 00:03:37.690 Brylle Girang: to ABC moving forward. So, OTAM has been really aggressive with the confirmation needed, because we want to make sure that we
12 00:03:37.890 ⇒ 00:03:41.950 Brylle Girang: We allocate people accordingly, especially since we’re moving faster.
13 00:03:42.240 ⇒ 00:03:43.899 Brylle Girang: For the next few weeks.
14 00:03:44.170 ⇒ 00:03:50.969 Brylle Girang: So, this is really important, because without the allocations, then we won’t be able to, like, plan really effectively.
15 00:03:53.090 ⇒ 00:03:54.390 Pranav Narahari: Yeah, totally.
16 00:03:55.470 ⇒ 00:04:01.229 Brylle Girang: So, I guess you can start with the allocations. Oh, no, sorry.
17 00:04:01.960 ⇒ 00:04:08.180 Brylle Girang: You can start with the best roadmap, with the best option, and then share the allocations or the hours needed.
18 00:04:11.010 ⇒ 00:04:12.290 Pranav Narahari: Yeah, sounds good.
19 00:04:12.840 ⇒ 00:04:13.670 Uttam Kumaran: Hey, guys.
20 00:04:13.840 ⇒ 00:04:16.080 Uttam Kumaran: Okay, let’s go for it.
21 00:04:16.760 ⇒ 00:04:19.750 Pranav Narahari: Yep, just gonna share my screen real quick to…
22 00:04:19.750 ⇒ 00:04:20.339 Uttam Kumaran: Okay.
23 00:04:22.310 ⇒ 00:04:24.429 Pranav Narahari: So I can just share the… the doc.
24 00:04:39.260 ⇒ 00:04:41.659 Pranav Narahari: Started using Arc this week, so…
25 00:04:41.930 ⇒ 00:04:46.919 Pranav Narahari: Nice. Always just an extra 5 seconds to do everything until I get used to it.
26 00:04:48.220 ⇒ 00:04:48.870 Pranav Narahari: Alright.
27 00:04:49.830 ⇒ 00:04:52.720 Pranav Narahari: Yeah, so…
28 00:04:52.970 ⇒ 00:05:08.799 Pranav Narahari: three things, Tom, we kind of already talked about it, we can maybe talk about it in further detail if you want, but on Monday, we kind of talked about the three different things. And so I kind of outlined 3 different options for how we can go, and I have a preference, of course, but I think…
29 00:05:09.100 ⇒ 00:05:15.330 Pranav Narahari: there’s pros and cons to everything, 6-week, 8-week, and 10-week. And…
30 00:05:16.410 ⇒ 00:05:29.339 Pranav Narahari: with 8-week, I feel like we’re just able to not run the risk of, like, certain things, like having a blocker, and it stops the progress on everything else. And it just requires, like, ends up just being more of a…
31 00:05:29.790 ⇒ 00:05:36.340 Pranav Narahari: just being a lot harder to manage is my… is my worry there. I think 8-week makes the most sense, and…
32 00:05:36.700 ⇒ 00:05:46.549 Pranav Narahari: Yeah, basically what I think of in terms of allocation is we just need, like, 20 hours per week if we do things right, from Mustafa and Casey, so 10-10.
33 00:05:46.620 ⇒ 00:05:57.339 Pranav Narahari: And then I would be 10 to kind of help out a little bit if needed, and then for Sam is a little bit of a wild card. I’m kind of… it’s kind of difficult for me to understand exactly…
34 00:05:57.380 ⇒ 00:06:09.320 Pranav Narahari: where Sam is gonna fit in, and how many hours he would need. But maybe that’s something we can talk about here. But yeah, for Mustafa and Casey specifically, I feel like they just need 10 hours each.
35 00:06:11.340 ⇒ 00:06:11.940 Uttam Kumaran: Okay.
36 00:06:12.070 ⇒ 00:06:13.439 Uttam Kumaran: I mean, hearing that
37 00:06:14.450 ⇒ 00:06:25.200 Uttam Kumaran: makes me happy. That feels like we haven’t been… we’ve been spending much more time than that, so reconcile that with me, like, I feel like Casey is spending…
38 00:06:25.610 ⇒ 00:06:28.499 Uttam Kumaran: Most of his day there.
39 00:06:28.750 ⇒ 00:06:33.420 Uttam Kumaran: I know, I know, I understand your time going down, so I guess we talked about this morning.
40 00:06:33.630 ⇒ 00:06:37.529 Uttam Kumaran: But, like, talk to me about Casey’s time, like, it seems like he’s spending…
41 00:06:38.040 ⇒ 00:06:40.759 Uttam Kumaran: I mean, there’s only… he’s only working on that, so…
42 00:06:41.020 ⇒ 00:06:43.819 Uttam Kumaran: Maybe talk to me about that, and then I… yeah.
43 00:06:44.500 ⇒ 00:06:47.140 Pranav Narahari: what I’ve just noticed with migration is just, like.
44 00:06:47.260 ⇒ 00:06:53.020 Pranav Narahari: things have just, like, extended. I don’t think there was any clear deliverables, and, like, the timeline was just, like…
45 00:06:53.340 ⇒ 00:07:01.859 Pranav Narahari: just kept on getting pushed. I think Casey and Mustafa just, like, didn’t really have, like, the direction on, like, what to work on. Okay.
46 00:07:02.360 ⇒ 00:07:06.710 Pranav Narahari: I feel, though, like, with these things, like, that we’re building, we’re not, like…
47 00:07:06.820 ⇒ 00:07:15.239 Pranav Narahari: we’re not doing something super technically complex, and I think the way that I’ve mapped it out, it’s like, they should… they’re gonna have, like, so much direction on just, like…
48 00:07:15.240 ⇒ 00:07:15.760 Uttam Kumaran: Okay.
49 00:07:16.100 ⇒ 00:07:27.589 Pranav Narahari: just taking things from, like, cursor, like, when we assign it to, like, a linear ticket to Cursor, and then just basically just tying a bow on it, and then just shipping a PR, so…
50 00:07:28.070 ⇒ 00:07:31.280 Pranav Narahari: Yeah, I don’t know, I feel pretty good about that.
51 00:07:31.280 ⇒ 00:07:43.979 Uttam Kumaran: Okay. I mean, I… yeah, I feel if you’re confident, then I agree with you in that there hasn’t, like, there are some things that still require, like, because we’re from an old system, but…
52 00:07:44.190 ⇒ 00:07:55.400 Uttam Kumaran: everything from the Google Workspace stuff is all accessible via CLI, everything’s in Master now, real, you can entirely do via AI, so I’m also, like…
53 00:07:55.660 ⇒ 00:08:04.469 Uttam Kumaran: One thing that I want to help you do is identify… is, through this process, help you identify tickets that could get handed off to AI.
54 00:08:04.470 ⇒ 00:08:15.860 Uttam Kumaran: And maybe that’s… that’s sort of how the platform team supports you, because you’re gonna be one of… you’re… I want you to be really aggressive with that goal, because I really feel confident that
55 00:08:16.020 ⇒ 00:08:27.079 Uttam Kumaran: I would rather you take extra time to call Janice and Yvette and just get more roadmap items and deliver, because I feel like a lot of the development work we can start to hand off.
56 00:08:27.760 ⇒ 00:08:28.340 Pranav Narahari: Yeah.
57 00:08:28.590 ⇒ 00:08:30.539 Uttam Kumaran: So, this, this makes sense to me.
58 00:08:31.500 ⇒ 00:08:33.130 Pranav Narahari: Okay, that sounds great. Yeah, I mean…
59 00:08:33.130 ⇒ 00:08:35.309 Uttam Kumaran: So, yeah, yeah, go ahead, yeah, yeah.
60 00:08:35.409 ⇒ 00:08:36.380 Uttam Kumaran: Go, go, go ahead.
61 00:08:37.270 ⇒ 00:08:53.729 Pranav Narahari: I was just gonna say, yeah, with delivery items, like, I can even see, like, future scopes as well, like, I have a few other ideas, for… and I need to touch up on them again, like, I was just so focused on these ones, like, I don’t have that much detail on other ones, but…
62 00:08:53.770 ⇒ 00:08:57.470 Pranav Narahari: Yeah, I agree, like, with 2 months here, like, we need to start, like, scoping…
63 00:08:58.270 ⇒ 00:09:17.770 Pranav Narahari: what’s next? You know, it’s not even 2 months, it’s only gonna be, like, 8 weeks, so, like, by the end of May, we’re going to be ready to, like, start working on other stuff again. Another thing here is, too, is, like, if things do go as planned, right, like, I will have some time to do, like, additional development on here, too. So, like, we’ll be working at a faster than…
64 00:09:17.900 ⇒ 00:09:22.590 Pranav Narahari: 20 hour per week pace will be, like, more so, like, on a 25.
65 00:09:22.890 ⇒ 00:09:28.300 Pranav Narahari: Hours per week pays. And then that’s not even including Sam’s time onto the project.
66 00:09:28.300 ⇒ 00:09:28.920 Uttam Kumaran: Yeah.
67 00:09:29.170 ⇒ 00:09:38.809 Pranav Narahari: we could move even faster, and then… so yeah, I will be cognizant of just, like, keeping up with Janice and Yvette, and just, like, so we don’t end this project, and we’re just like, what… what’s next? Cool.
68 00:09:39.320 ⇒ 00:09:41.980 Uttam Kumaran: Okay, so, yeah, yeah, go ahead.
69 00:09:42.360 ⇒ 00:09:45.910 Pranav Narahari: this, project, like, the contract ends on May 31st.
70 00:09:47.050 ⇒ 00:09:48.060 Uttam Kumaran: Okay, cool.
71 00:09:48.300 ⇒ 00:09:49.879 Uttam Kumaran: So I think,
72 00:09:50.390 ⇒ 00:09:55.359 Uttam Kumaran: Two things. So, remind me again, you recommended that we go with the 8-week? Okay, yeah.
73 00:09:55.790 ⇒ 00:09:56.390 Pranav Narahari: Yo.
74 00:09:56.710 ⇒ 00:10:01.130 Uttam Kumaran: So this… does this take us into… this takes us to May 31st, basically?
75 00:10:01.480 ⇒ 00:10:04.190 Pranav Narahari: A couple weeks, a week before, yeah.
76 00:10:04.570 ⇒ 00:10:11.749 Uttam Kumaran: Okay, okay, cool. Okay, great. So let me just do a quick… let me just say some of these items back to you.
77 00:10:11.890 ⇒ 00:10:16.359 Uttam Kumaran: So report discovery, Okay, that makes sense.
78 00:10:18.680 ⇒ 00:10:21.049 Uttam Kumaran: Demo architecture…
79 00:10:23.630 ⇒ 00:10:36.999 Pranav Narahari: kind of how I had things set up is just, like, we can deliver on things weekly, and so there’s not gonna be, like, a demo weekly, but, like, we’ll have… we also have reports as a big part of this, right? So, like, additional dashboards we’re gonna build.
80 00:10:37.060 ⇒ 00:10:55.800 Pranav Narahari: Like, we kind of showed on Monday, like, how a lot of, like, real stuff is, like, it’s there, but it’s just kind of, like, broken. And so part of this, too, is, like, I kind of scoped this out as if, like, they’re not even there, so it could just be literally just, like, an hour of development just to get a whole deliverable for a dashboard up. So…
81 00:10:55.800 ⇒ 00:10:56.380 Uttam Kumaran: Okay.
82 00:10:56.690 ⇒ 00:11:03.599 Pranav Narahari: what I’m scoping here, too, like, is a little bit of an overestimate, but at the same time, you know, things break, so… I think 8 weeks makes sense.
83 00:11:04.260 ⇒ 00:11:11.899 Uttam Kumaran: Okay. And then, so, for these tickets, are they… these are already created.
84 00:11:12.070 ⇒ 00:11:15.020 Pranav Narahari: I haven’t shipped, like, I haven’t made them in linear yet, but they’re just, like…
85 00:11:15.020 ⇒ 00:11:15.410 Uttam Kumaran: Okay.
86 00:11:15.550 ⇒ 00:11:16.879 Pranav Narahari: bumped away, I guess.
87 00:11:17.250 ⇒ 00:11:17.850 Uttam Kumaran: Okay.
88 00:11:19.270 ⇒ 00:11:26.220 Uttam Kumaran: So my suggestion, in terms of just feedback on this, is, one.
89 00:11:26.480 ⇒ 00:11:35.010 Uttam Kumaran: I’ll try… if I could see if… I feel fine with option B, I think that takes us right to the end of this contract. So, I think…
90 00:11:35.120 ⇒ 00:11:36.639 Uttam Kumaran: You’re good to just, like.
91 00:11:37.350 ⇒ 00:11:52.680 Uttam Kumaran: delete the other options, that’s fine. One thing that I would like to see as part of option B is, like, how this maps to linear projects and linear initiatives. It seems like you have initiatives around reporting, seems like you have initiatives around, like.
92 00:11:55.410 ⇒ 00:12:07.899 Uttam Kumaran: like, is… I feel like, yeah, I just want to see, sort of, like, what the core initiatives are, and then mapping pro… mapping these to projects, and then mapping the tickets to the projects. There is a lot in,
93 00:12:08.020 ⇒ 00:12:10.840 Uttam Kumaran: the platform now about how to do that process.
94 00:12:10.960 ⇒ 00:12:14.869 Uttam Kumaran: So, if you have questions, like, I’m totally happy to answer, but that’s probably the only
95 00:12:15.020 ⇒ 00:12:17.629 Uttam Kumaran: thing I would like to see.
96 00:12:17.870 ⇒ 00:12:23.790 Uttam Kumaran: And then once we do that, I can go… I can go through the tickets with you and help you,
97 00:12:24.340 ⇒ 00:12:29.710 Uttam Kumaran: Give you some clarity on, like, what else we can scope, because looking at this, I feel like…
98 00:12:30.100 ⇒ 00:12:33.850 Uttam Kumaran: Your hunch is right. Like, a lot of the,
99 00:12:34.720 ⇒ 00:12:40.209 Uttam Kumaran: I mean, a lot of the… the dashboarding work, I feel like, can get done quicker.
100 00:12:41.150 ⇒ 00:12:41.650 Pranav Narahari: Yeah.
101 00:12:41.650 ⇒ 00:12:46.849 Uttam Kumaran: But I just wanna… I wanna… I don’t wanna just say that, like, I wanna kinda see the tickets and go through that with you.
102 00:12:48.910 ⇒ 00:12:57.999 Pranav Narahari: And are you… did you take a look at the PRDs, too? Because, like, I have some questions there that I feel like could map pretty well to initiatives, and just milestones.
103 00:12:58.120 ⇒ 00:13:00.550 Pranav Narahari: Yeah, which one should…
104 00:13:00.550 ⇒ 00:13:02.040 Uttam Kumaran: I look at the… yeah.
105 00:13:02.040 ⇒ 00:13:05.720 Pranav Narahari: Let’s look at Document Update. Maybe that’s just the one I have in front of me.
106 00:13:07.240 ⇒ 00:13:08.410 Pranav Narahari: 2041.
107 00:13:08.710 ⇒ 00:13:10.979 Uttam Kumaran: Yeah, Integrated Document Update Copilot.
108 00:13:14.320 ⇒ 00:13:21.710 Pranav Narahari: Yeah, this is, like, for the… yeah. And so, in this… if you scroll down to the Sprint Catalog, I feel like that maps pretty well to, like, linear milestones.
109 00:13:25.590 ⇒ 00:13:27.809 Uttam Kumaran: The script catalog, yeah, yeah.
110 00:13:28.490 ⇒ 00:13:30.169 Pranav Narahari: script catalog, yeah.
111 00:13:36.510 ⇒ 00:13:37.200 Uttam Kumaran: Okay.
112 00:13:39.000 ⇒ 00:13:40.859 Pranav Narahari: If I’m thinking about that right.
113 00:13:40.860 ⇒ 00:13:43.549 Uttam Kumaran: Yeah, I feel… I feel good about this.
114 00:13:43.780 ⇒ 00:13:50.400 Uttam Kumaran: But this isn’t, like… so is this… is this… this is also mapped in that… in your…
115 00:13:52.140 ⇒ 00:13:53.990 Uttam Kumaran: Roadmap options?
116 00:13:55.400 ⇒ 00:13:59.180 Pranav Narahari: I combined all 3 of these things into, like, the roadmap.
117 00:13:59.670 ⇒ 00:14:05.809 Pranav Narahari: So the document update, the real, the real, like.
118 00:14:06.210 ⇒ 00:14:12.940 Pranav Narahari: additional views, and then also the transcript-driven adoption one. So, 2037.
119 00:14:14.280 ⇒ 00:14:23.859 Uttam Kumaran: Okay, so one thing that could be… yeah, so let’s just move forward with option B. I think what would be helpful for me is…
120 00:14:24.090 ⇒ 00:14:27.420 Uttam Kumaran: I’m happy with the hours, I’m happy with…
121 00:14:27.590 ⇒ 00:14:42.930 Uttam Kumaran: I think you have sort of 3 core areas, which is the sort of document update, transcript analysis, and adoption, and, like, the general reporting. I think that’s great.
122 00:14:43.150 ⇒ 00:14:46.550 Uttam Kumaran: What I would like to see is a mapping of…
123 00:14:46.760 ⇒ 00:14:50.780 Uttam Kumaran: I mean, I would say eat 3 of… those 3 are your initiatives.
124 00:14:51.490 ⇒ 00:14:52.280 Pranav Narahari: Oh, okay.
125 00:14:52.830 ⇒ 00:14:55.359 Uttam Kumaran: I think those 3 are great initiatives.
126 00:14:55.470 ⇒ 00:15:00.859 Uttam Kumaran: I think you map the projects underneath them to those initiatives.
127 00:15:00.990 ⇒ 00:15:04.910 Uttam Kumaran: And then I think you map the tickets to those projects.
128 00:15:05.050 ⇒ 00:15:10.910 Uttam Kumaran: I think what I would like to… Also, scope out is,
129 00:15:11.210 ⇒ 00:15:14.790 Uttam Kumaran: A couple of tickets around performance improvements.
130 00:15:15.290 ⇒ 00:15:18.669 Uttam Kumaran: Like, I would like us to do… I would like us to…
131 00:15:19.270 ⇒ 00:15:23.110 Uttam Kumaran: see how we… like, two things. I would like us to see how we can bring the,
132 00:15:24.330 ⇒ 00:15:26.920 Uttam Kumaran: Response times even lower.
133 00:15:27.380 ⇒ 00:15:31.140 Uttam Kumaran: And so for that, we’re gonna need the… we’re gonna need the reporting, right?
134 00:15:31.710 ⇒ 00:15:32.230 Uttam Kumaran: I was…
135 00:15:32.240 ⇒ 00:15:39.329 Pranav Narahari: I was talking to Yvette about that on Monday, and then, you know, because the last metric she got was, like.
136 00:15:39.740 ⇒ 00:15:49.210 Pranav Narahari: I think, like, 7 seconds, and she’s like, yeah, you know, like, when we first talked to Utam about Andy, like, they were promising, like, 3 seconds, right? And so I think…
137 00:15:49.320 ⇒ 00:16:06.699 Pranav Narahari: they’re… they’re not really, I think, they understand that this is a work in progress, too, like, they’re not expecting, like, 3 seconds, like, in 2 months. But what Casey just showed us, like, and he just showed this in, I think, the channel yesterday night or this morning, was that, it’s, like, 4.5 seconds now, with the new logic.
138 00:16:07.260 ⇒ 00:16:12.959 Uttam Kumaran: Well, that’s what I just, like… what I’m… what I’m more asking for is, I think I have some ways for you to get there.
139 00:16:13.160 ⇒ 00:16:19.069 Uttam Kumaran: In, like, probably, like, 2 hours. So, like, what I… what I… what I would like us to do is just have…
140 00:16:19.290 ⇒ 00:16:24.610 Uttam Kumaran: a project, created around… Like, speed improvements?
141 00:16:25.130 ⇒ 00:16:25.670 Pranav Narahari: Okay.
142 00:16:25.670 ⇒ 00:16:27.780 Uttam Kumaran: And there are some that, like.
143 00:16:27.900 ⇒ 00:16:39.520 Uttam Kumaran: I don’t… I don’t want us to just, like, hand this to Casey and be like, make it faster. Me and you, and Sam, I have some architecture decisions to propose that will make it faster, and then you hand it to them to execute.
144 00:16:40.080 ⇒ 00:16:40.520 Pranav Narahari: That sounds fine.
145 00:16:40.530 ⇒ 00:16:47.300 Uttam Kumaran: I think everybody on the crew should always be trying to find optimizations, but I just want to, like.
146 00:16:47.460 ⇒ 00:16:56.460 Uttam Kumaran: like, there are some great ways that we can just use some different models and speed this up, I’m suspecting. And so, that’s probably the only other
147 00:16:56.900 ⇒ 00:17:00.630 Uttam Kumaran: I would… I would like to create a project around,
148 00:17:02.530 ⇒ 00:17:08.420 Uttam Kumaran: Yeah, I mean, I would like to create one initiative just around, speed.
149 00:17:09.380 ⇒ 00:17:11.799 Uttam Kumaran: And you can just have one project into that.
150 00:17:11.990 ⇒ 00:17:16.740 Uttam Kumaran: And then, I don’t know if you want to create anything else around, like, broader maintenance?
151 00:17:16.950 ⇒ 00:17:21.190 Uttam Kumaran: Like, if there is any recurring maintenance that has to happen, I would…
152 00:17:21.420 ⇒ 00:17:25.439 Uttam Kumaran: I would just create those, but otherwise, I see four initiatives.
153 00:17:26.040 ⇒ 00:17:32.020 Uttam Kumaran: And then, ideally, like, once you get all of those in place.
154 00:17:32.620 ⇒ 00:17:45.869 Uttam Kumaran: I think before assign… the reason why I wanted to meet quicker is before assigning it out, I want to work with you to kind of give you a framework of, like, how you can… you can do some of these yourself, you can assign this to Kershaw, or you can assign this to the team.
155 00:17:46.020 ⇒ 00:17:54.619 Uttam Kumaran: If you assign it to the team, they’re gonna work on it in any way they feel, so I want you to sort of see, like, I’m fairly confident
156 00:17:54.950 ⇒ 00:17:55.920 Uttam Kumaran: you could…
157 00:17:56.070 ⇒ 00:18:03.300 Uttam Kumaran: probably vibe code the entire analysis thing yourself in, like, 2 hours. So I want to just show you some of these things.
158 00:18:03.460 ⇒ 00:18:05.419 Uttam Kumaran: So that you get a sense
159 00:18:05.610 ⇒ 00:18:10.360 Uttam Kumaran: It’s gonna be helpful for you to get a sense of expectation for how long something’s gonna take.
160 00:18:10.810 ⇒ 00:18:17.980 Uttam Kumaran: So that when things end up taking 8, 10 hours, you have some options for, like, what did we try, right?
161 00:18:18.150 ⇒ 00:18:21.829 Uttam Kumaran: So, if one thing I could ask for today is.
162 00:18:22.110 ⇒ 00:18:28.870 Uttam Kumaran: and maybe, B, you could work with the team on it, is, like, I want to see the initiatives, I want to see the projects, and I want to see the
163 00:18:29.010 ⇒ 00:18:32.179 Uttam Kumaran: All the tickets underneath them, in linear.
164 00:18:32.690 ⇒ 00:18:34.710 Uttam Kumaran: With dates.
165 00:18:35.430 ⇒ 00:18:38.549 Uttam Kumaran: I think if I can see that, then I can go…
166 00:18:39.020 ⇒ 00:18:52.539 Uttam Kumaran: to some… I can go review some tickets, and then I want to work… I want to actually show you the process of leveraging, like, how I’m starting to do some agent-driven development on some of these, especially when it comes to some of the data ones.
167 00:18:52.700 ⇒ 00:18:55.450 Uttam Kumaran: And then I think we’re… we’re free to…
168 00:18:56.090 ⇒ 00:18:57.800 Uttam Kumaran: Kind of just execute the plan.
169 00:18:59.000 ⇒ 00:19:00.089 Pranav Narahari: Cool. Sounds good.
170 00:19:00.090 ⇒ 00:19:01.270 Uttam Kumaran: Does that make sense? Okay.
171 00:19:02.370 ⇒ 00:19:17.540 Uttam Kumaran: Yeah, and again, I think on the speed things, like, I hear you in that, like, I’m not saying that they have a necessary rush. I think there are some simple architecture changes that we can make to leverage that, that I want to share.
172 00:19:17.670 ⇒ 00:19:21.060 Uttam Kumaran: But again, like, I want us to…
173 00:19:21.440 ⇒ 00:19:34.939 Uttam Kumaran: and this is something that I’ll… it’ll kind of get a little bit clearer next quarter, is, like, I want you to have the clarity on, like, what we’re working on, what the expectations are for your team, so that then you can hold people accountable, versus it being more, like.
174 00:19:35.480 ⇒ 00:19:41.430 Uttam Kumaran: more like everybody’s on the same page. I think if you come to the table with, like, these are the tickets, these are the hours.
175 00:19:41.710 ⇒ 00:19:48.249 Uttam Kumaran: We’ve looked through everything, and we are comfortable with the fact that this can get done with the time allotted per week.
176 00:19:48.370 ⇒ 00:19:55.969 Uttam Kumaran: people will get it done in that timeline, you know? And so I don’t want this to be, like, we created all the tickets, and then we’re back into just, like.
177 00:19:56.160 ⇒ 00:20:07.639 Uttam Kumaran: Linear just never gets updated. I really want this phase to get… be like, okay, Linear’s in a sick place, comfortable with every single ticket. I’m not comfortable with the team picking things off.
178 00:20:07.790 ⇒ 00:20:23.180 Uttam Kumaran: And I have… every week, I can look at a clear view in linear and see how far off we are, right? I’m very, very confident we’re there. It’s just gonna require us to spend, like, a little bit more time in this planning phase for me and you to be on the same page.
179 00:20:23.710 ⇒ 00:20:26.250 Uttam Kumaran: Across all these tickets and initiatives.
180 00:20:27.700 ⇒ 00:20:29.769 Uttam Kumaran: And then, yeah, I think we’ll be good.
181 00:20:30.610 ⇒ 00:20:34.889 Pranav Narahari: Okay, do you have, like, a couple more minutes? I know we only scheduled 15.
182 00:20:34.890 ⇒ 00:20:35.780 Uttam Kumaran: Yeah, yeah.
183 00:20:36.350 ⇒ 00:20:46.420 Pranav Narahari: Okay, yeah, I was just gonna ask, like, how does, like, Sam fit in here? I was thinking with, like, the PRs, like, that’s where, that makes a lot of sense for him to kind of take a look, kind of.
184 00:20:46.960 ⇒ 00:21:02.640 Pranav Narahari: on just, like, everything, every ticket that’s shipped, like, we talked a little bit yesterday with, like, okay, with the speed we’re moving, like, we don’t want a PR generator for every single thing, because that’s gonna really slow us down. It’s gonna be a bottleneck if we just have, like, 20 tickets with 20 different PRs, so…
185 00:21:03.040 ⇒ 00:21:03.970 Pranav Narahari: kind of…
186 00:21:04.220 ⇒ 00:21:11.730 Pranav Narahari: constructing some type of thing where we are grouping similar tickets into a consolidated PR that’s maybe, like, 15.
187 00:21:11.730 ⇒ 00:21:17.409 Uttam Kumaran: Yeah, there’s, like, let me tell you how I’m thinking about this, because I’m dealing with this on the platform team,
188 00:21:17.610 ⇒ 00:21:21.350 Uttam Kumaran: is… One, I think…
189 00:21:22.120 ⇒ 00:21:39.529 Uttam Kumaran: I’m fairly confident that if you just set up BugBot, it’ll prevent probably, like, 50% of the issues. So, if you can just make sure that BugBot is set up on that repo, and that’s working, I think, like, that’s one hack. Second, I think you can be the reviewer on
190 00:21:39.660 ⇒ 00:21:44.989 Uttam Kumaran: a fair bit of these, and then I think you should pass some of the more difficult ones to Sam.
191 00:21:45.140 ⇒ 00:21:48.880 Uttam Kumaran: I think that would… that’s, like, a good way. If you find, like.
192 00:21:49.390 ⇒ 00:21:52.319 Uttam Kumaran: I actually don’t mind there being smaller…
193 00:21:52.600 ⇒ 00:22:07.030 Uttam Kumaran: PRs, because the limiting factor isn’t the PR size, it’s actually just, like, the time to review. And so, I want to spread it out, like, I want you to see that BugBot, like, this is what I’m going to share with you. The cleaner the ticket is.
194 00:22:07.100 ⇒ 00:22:14.529 Uttam Kumaran: the… and the fact that they used that ticket branch to then build, BugBot will actually give a sick review.
195 00:22:14.580 ⇒ 00:22:17.569 Uttam Kumaran: So, it all cascades from…
196 00:22:17.610 ⇒ 00:22:35.740 Uttam Kumaran: a really clean ticket to people using that branch, and so it’s actually going to be more important for you to enforce the fact that people are linking out their… like, they’re using that branch, so it’s linked to the ticket, that the tickets are really high quality, and that nothing needs to go to your review until it passes BugBot.
197 00:22:36.110 ⇒ 00:22:51.210 Uttam Kumaran: So that’s what I’m finding, is that it’s not worth a human review until the AI says it’s good, and then I think if you can have BugBot and you as, like, a… as a reviewer, as a code owner, I think that would be great. And then I think past things to Sam that require
198 00:22:51.590 ⇒ 00:22:56.180 Uttam Kumaran: larger oversight, and I think that can be ad hoc, is what I would recommend. Okay.
199 00:22:56.660 ⇒ 00:23:10.659 Uttam Kumaran: I think that’s… that gives you control over the pace. I think… I want to put the constraint on you to lean on that AI reviewer, so that you can give us feedback on the platform side on, like, the AI reviewer’s, like, not…
200 00:23:10.990 ⇒ 00:23:11.840 Uttam Kumaran: Effective enough.
201 00:23:12.430 ⇒ 00:23:12.850 Uttam Kumaran: So…
202 00:23:12.850 ⇒ 00:23:13.530 Pranav Narahari: Yeah.
203 00:23:14.150 ⇒ 00:23:15.419 Pranav Narahari: And that’s sort of habit.
204 00:23:15.420 ⇒ 00:23:16.010 Uttam Kumaran: Yeah.
205 00:23:16.230 ⇒ 00:23:16.810 Uttam Kumaran: There we go.
206 00:23:16.810 ⇒ 00:23:23.199 Pranav Narahari: a little bit too fast there, too, because with what we’re doing right now, we’re not, like, updating Andy where it’s going to, like.
207 00:23:23.590 ⇒ 00:23:26.370 Pranav Narahari: screw up the responses. Yeah, that’s why…
208 00:23:26.370 ⇒ 00:23:34.650 Uttam Kumaran: like, I think that’s… that’s why I don’t want you out of the loop, because ultimately, if your team ships something on a Friday, then it’s, like, your ass, so…
209 00:23:34.790 ⇒ 00:23:45.200 Uttam Kumaran: just, like, I want you to still see that, but again, like, I’m telling you, the better quality the tickets, the easier it’s gonna be for you to review, and then…
210 00:23:45.380 ⇒ 00:23:52.620 Uttam Kumaran: if you find that, hey, I’m not able to review, then the team… you have to go be like, you guys need to add unit tests, we need to have better CI, like.
211 00:23:52.620 ⇒ 00:23:53.170 Pranav Narahari: Yo.
212 00:23:53.380 ⇒ 00:24:12.010 Uttam Kumaran: that’s the natural flow. Like, to tell you how I overcame that problem is I’m doing, like, 20 or 30 PRs a day. I rely super, super heavily on BugBot and Codex to give me a review, and I rely super, super heavily on CI. I’m adding, like, unit tests, integration tests, deployment tests, like.
213 00:24:12.050 ⇒ 00:24:31.440 Uttam Kumaran: out the ass, because I’m like a… it’s like, I’m, like, sort of solo driving, and I’m going… and so, when I think about applying… taking what I’ve learned and applying it to the team, it’s continuing to lean on those tools, and actually leaning on what we always know as software developers, is just, like, builds really, really great unit tests.
214 00:24:31.630 ⇒ 00:24:38.460 Uttam Kumaran: So that’s why I don’t… I don’t necessarily want to attack, like, the PR shape, because.
215 00:24:38.460 ⇒ 00:24:39.200 Pranav Narahari: Okay.
216 00:24:39.200 ⇒ 00:24:52.949 Uttam Kumaran: where this is going is that you’ll be able to… you’ll start handing off tasks to AI, and it will create a PR per ticket. And so if the PR is too… if the PR is too small, then I would say the ticket is too small, right?
217 00:24:53.210 ⇒ 00:24:58.059 Uttam Kumaran: So, the reason why is it always gives you the ability to craft the outcome.
218 00:24:58.170 ⇒ 00:25:05.810 Uttam Kumaran: like, I want to take less… I want to take things off the engineers to have to think about, like, is this PR too big, small? It’s like…
219 00:25:06.250 ⇒ 00:25:13.319 Uttam Kumaran: we are comfortable with this atomic ticket. If the atomic ticket was, like, a one-liner, then we should have looped it in with something else.
220 00:25:13.460 ⇒ 00:25:17.930 Uttam Kumaran: And we’ll learn. We’ll learn, like, what’s big, what’s small, things like that, you know?
221 00:25:18.810 ⇒ 00:25:24.229 Pranav Narahari: So one thing I did with the tickets here is, like, I made them 2-4 hours, like, estimates. Okay.
222 00:25:24.230 ⇒ 00:25:24.580 Uttam Kumaran: Cool.
223 00:25:24.580 ⇒ 00:25:31.959 Pranav Narahari: I did that purposely because I just felt like there were so many tickets in Linear right now that were just there from so long ago, and not.
224 00:25:31.960 ⇒ 00:25:37.299 Uttam Kumaran: Well, that’s also one thing that I’m doing today, is, like, I’m going and cleaning and consolidating, so if you want me to…
225 00:25:37.640 ⇒ 00:25:46.189 Uttam Kumaran: clean house on your stuff, I will do it. Like, if you’re not married to any of the stuff. Meaning, like, I’m not deleting, I’m just gonna, like, consolidate
226 00:25:46.330 ⇒ 00:25:52.390 Uttam Kumaran: archive, like, You will end up with fewer tickets, the tickets will be richer with all the context.
227 00:25:52.700 ⇒ 00:25:58.190 Uttam Kumaran: And I’m doing that across our entire linear, like, instance.
228 00:25:58.320 ⇒ 00:26:01.559 Uttam Kumaran: So if there is stuff in the pa-.
229 00:26:01.560 ⇒ 00:26:02.930 Pranav Narahari: The cursor skills for that?
230 00:26:03.510 ⇒ 00:26:12.800 Uttam Kumaran: Yeah, yeah, yeah, and I’m building all the skills for it. So, I can… I can… I’m, like, doing that across my clients, and I have skills that basically go look at
231 00:26:13.070 ⇒ 00:26:21.860 Uttam Kumaran: as matching the SOW to the projects, naming conventions, ensuring that tickets have descriptions, assignments, projects.
232 00:26:22.000 ⇒ 00:26:24.420 Uttam Kumaran: Like, things like that. Yeah.
233 00:26:25.060 ⇒ 00:26:40.580 Uttam Kumaran: I can… I can rip that, or I can just give you the sort of… yeah, okay, okay, cool. So let me just do that. That way, like, nothing that’s in flight is gonna move statuses or anything, but if anything, things should just get a lot clearer, and then you at least have a blank slate.
234 00:26:41.980 ⇒ 00:26:53.540 Uttam Kumaran: And I think… yeah, I think… and I think, B, maybe one thing that I could use your help on is trying to adhere the work that this team did, in these documents to our, like, linear phasing
235 00:26:53.680 ⇒ 00:27:01.129 Uttam Kumaran: Sort of stuff. Ultimately, I want one document to live as an extension… one document to basically show, like.
236 00:27:01.720 ⇒ 00:27:05.139 Uttam Kumaran: This team’s perspective on the initiatives?
237 00:27:05.210 ⇒ 00:27:09.370 Uttam Kumaran: Like, why they’re important, how much time it should take to accomplish that goal.
238 00:27:09.440 ⇒ 00:27:29.329 Uttam Kumaran: the breakdown of those into projects, and then the… and I don’t need to see every ticket in this plan, but, like, yeah, I just… I’m mainly interested in the initiatives, the milestones, and the projects, and you can see I’m… I’m using the same terminology as linear on purpose. There is instructions in the platform on, like, on, like, how to write these.
239 00:27:29.400 ⇒ 00:27:35.780 Uttam Kumaran: So I think you can just have AI just… just redo it a little bit. If you can leave with one document that sort of gives that.
240 00:27:36.200 ⇒ 00:27:47.269 Uttam Kumaran: And then gives the hour estimates, we’re, like, we’re in a great shape. Because ultimately what we will do is, as the time goes on, we will… we’re gonna build some skills that compare where we are.
241 00:27:47.440 ⇒ 00:27:59.990 Uttam Kumaran: to that dock. And so it’ll easily flag to you where things have shifted. So I want as much to align to that dock, so we, like, have, like, a version of that. So then as things shift, we can start to
242 00:28:00.210 ⇒ 00:28:01.999 Uttam Kumaran: understand Drift a little bit.
243 00:28:03.040 ⇒ 00:28:03.960 Pranav Narahari: Okay, yeah.
244 00:28:03.960 ⇒ 00:28:14.600 Uttam Kumaran: So, like, I would say try at your best to lean on the platform for, like, naming conventions and things like that, and there is documents already on, like, how to break up a project plan into linear phasing.
245 00:28:14.730 ⇒ 00:28:17.950 Uttam Kumaran: And then there are skills into linear phasing to tickets.
246 00:28:18.360 ⇒ 00:28:21.989 Uttam Kumaran: Yeah, and so I think you should be good.
247 00:28:22.860 ⇒ 00:28:24.369 Pranav Narahari: Perfect. Yeah, I can do that.
248 00:28:25.150 ⇒ 00:28:34.429 Uttam Kumaran: Okay, sick. So, yeah, if I could have you guys do that, I think… I also, Sam, want to get your feedback today before you’re out on the Eden AI piece.
249 00:28:34.550 ⇒ 00:28:36.560 Uttam Kumaran: So, I think you heard a little bit of my…
250 00:28:36.670 ⇒ 00:28:44.200 Uttam Kumaran: Perfect. I think you heard a little bit of, like, how I’m looking at these, so really, I feel like what would be helpful is, like.
251 00:28:45.090 ⇒ 00:28:51.259 Uttam Kumaran: Is commentary or, like, How we should phase this out, technologies.
252 00:28:51.260 ⇒ 00:28:51.640 Samuel Roberts: to you.
253 00:28:51.640 ⇒ 00:28:58.430 Uttam Kumaran: And, like, level of effort. I think I’ll let Pran… if Pranav can then work on, like.
254 00:28:58.560 ⇒ 00:29:02.189 Uttam Kumaran: What are the milestones, and how to… when do we communicate different things?
255 00:29:02.310 ⇒ 00:29:04.090 Uttam Kumaran: I kind of want that.
256 00:29:04.410 ⇒ 00:29:11.439 Uttam Kumaran: that type of separation, and, like, getting into linear tickets and everything, I think Pranav, you can handle. So I think the most essential part is, like.
257 00:29:11.840 ⇒ 00:29:16.939 Uttam Kumaran: what are the technologies being used? Like, what are some of the risks, depending on the technology?
258 00:29:17.350 ⇒ 00:29:23.149 Uttam Kumaran: What are some estimates on the larger initiatives on, like, what’s hard, what’s easy, what to consider?
259 00:29:23.300 ⇒ 00:29:31.039 Uttam Kumaran: just that commentary, I think, will go a long way. And then this week, I think me, B, and Pranav, we can work on
260 00:29:31.530 ⇒ 00:29:34.450 Uttam Kumaran: Putting exactly a similar document to this together.
261 00:29:34.660 ⇒ 00:29:37.890 Uttam Kumaran: And I… I think we’re… I think we’re rolling, you know?
262 00:29:39.400 ⇒ 00:29:45.780 Uttam Kumaran: Cool, cool. And then it looks like… it looks like, given on the timing, it looks like you have more than enough resources on…
263 00:29:46.120 ⇒ 00:29:53.609 Uttam Kumaran: to execute that second project as well. Maybe it’s… continues to just be you and Casey. And then…
264 00:29:53.780 ⇒ 00:30:05.370 Uttam Kumaran: what I’m doing on my side this week is I’m gonna start to understand, like, what resourcing the platform team needs. The client stuff comes first, but it’s clear that, like, I think you can run ABC Leaner.
265 00:30:05.550 ⇒ 00:30:11.259 Uttam Kumaran: I also want to get a sense for what resources are needed on the Eden project.
266 00:30:12.010 ⇒ 00:30:12.530 Pranav Narahari: Yep.
267 00:30:12.530 ⇒ 00:30:16.089 Uttam Kumaran: And that’ll help me inform what I need on the platform side.
268 00:30:16.270 ⇒ 00:30:21.430 Uttam Kumaran: And then also, we are recruiting for more folks on the AI team, so that would be helpful.
269 00:30:22.370 ⇒ 00:30:23.660 Pranav Narahari: Sure, yeah, cool.
270 00:30:23.970 ⇒ 00:30:28.989 Brylle Girang: Speaking of Eden, before I forget, schedule it for later, 4.30pm Eastern.
271 00:30:29.390 ⇒ 00:30:38.339 Brylle Girang: Well, we didn’t have… we don’t have any other time. Sam, what am I? I need your help in pushing back the final interview sketch that you have.
272 00:30:38.340 ⇒ 00:30:41.160 Uttam Kumaran: Well, I don’t need… I don’t need to be on this call.
273 00:30:41.690 ⇒ 00:30:42.200 Uttam Kumaran: Like…
274 00:30:42.460 ⇒ 00:30:43.110 Samuel Roberts: What is this?
275 00:30:43.110 ⇒ 00:30:46.199 Uttam Kumaran: I want to review a doc like we reviewed today.
276 00:30:46.640 ⇒ 00:30:57.479 Uttam Kumaran: Right? So, Pranav has a clear understanding of, like, what we’re building for them. I think Sam can provide the technical background on, like, how we should build, or where the risks are.
277 00:30:57.740 ⇒ 00:31:07.779 Uttam Kumaran: And then, I would like for… for… I would like, yeah, if you could… by tomorrow, I would like to see a similar document to, like, the updated document you’re working on for ABC.
278 00:31:08.030 ⇒ 00:31:13.140 Uttam Kumaran: And then Friday, we can just… we’ll confirm tickets for both, and we’ll… we’ll rock next week, you know?
279 00:31:13.730 ⇒ 00:31:16.849 Uttam Kumaran: So I don’t need to be on it until, like, something’s ready for review.
280 00:31:20.370 ⇒ 00:31:21.520 Brylle Girang: Gotcha. Okay.
281 00:31:21.830 ⇒ 00:31:22.370 Uttam Kumaran: Okay.
282 00:31:22.370 ⇒ 00:31:24.699 Brylle Girang: Is that enough time for you to review?
283 00:31:25.400 ⇒ 00:31:26.609 Brylle Girang: the Eden plan?
284 00:31:27.150 ⇒ 00:31:27.630 Samuel Roberts: Sorry?
285 00:31:27.630 ⇒ 00:31:30.310 Brylle Girang: Is that enough time for you to review the Eden plan?
286 00:31:31.110 ⇒ 00:31:36.419 Samuel Roberts: Yeah, I was just fixing up some of the platform URLs and stuff, and then I was jumping into that next, so… Okay.
287 00:31:37.930 ⇒ 00:31:38.550 Brylle Girang: Thank you.
288 00:31:39.940 ⇒ 00:31:40.530 Uttam Kumaran: Okay.
289 00:31:40.690 ⇒ 00:31:42.400 Uttam Kumaran: Perfect. Alright guys, I gotta jump.
290 00:31:43.840 ⇒ 00:31:45.120 Brylle Girang: Thanks, everyone. Bye-bye.
291 00:31:45.120 ⇒ 00:31:45.830 Uttam Kumaran: Thank you.