Meeting Title: Zoom-Meeting Date: 2024-03-08 Meeting participants: Ryan Luke Daque, Uttam Kumaran
WEBVTT
1 00:00:19.320 ⇒ 00:00:20.110 Ryan Luke Daque: Hello!
2 00:00:24.650 ⇒ 00:00:25.500 Uttam Kumaran: Hey!
3 00:00:25.730 ⇒ 00:00:29.970 Ryan Luke Daque: Hey, Othan! How’s it going? How are you doing? Great!
4 00:00:31.170 ⇒ 00:00:33.920 Uttam Kumaran: What’s a how’s the week been?
5 00:00:35.120 ⇒ 00:00:45.300 Ryan Luke Daque: It’s been pretty fine. yeah, nothing to weird or anything.
6 00:00:45.320 ⇒ 00:00:51.410 Ryan Luke Daque: pretty much a normal week or something. Actually.
7 00:00:51.840 ⇒ 00:00:52.999 Ryan Luke Daque: we call that
8 00:00:53.120 ⇒ 00:00:54.330 Uttam Kumaran: nice. Okay.
9 00:00:54.580 ⇒ 00:01:05.340 Uttam Kumaran: how about you looks like you’ve been like, busy the whole week. Yeah, I this has been the best week we’ve had in the company. I will say.
10 00:01:05.980 ⇒ 00:01:15.080 Uttam Kumaran: it’s funny, like I I’d be interested to hear from your perspective what you think after, because now we’ve been working for a while, but I go through like ups and downs.
11 00:01:15.130 ⇒ 00:01:27.570 Uttam Kumaran: But II try to I don’t know, especially when I’m talking to a team or talking to clients. I try to be pretty even keel, but there’s just so much that needs to happen to kind of like push the business forward
12 00:01:27.590 ⇒ 00:01:34.209 Uttam Kumaran: some days. I really find myself kind of paralyzed, because.
13 00:01:34.450 ⇒ 00:01:38.129 Uttam Kumaran: you know, there’s not only engineering work. There’s like sales work.
14 00:01:38.420 ⇒ 00:01:49.009 Uttam Kumaran: Yeah, there’s so much to do like. So there’s like taxes and bookkeeping. And then, like again, I have to eat. I have to like shower. I gotta like.
15 00:01:49.070 ⇒ 00:01:54.130 Uttam Kumaran: see my like. So for for probably like 6 months there.
16 00:01:54.180 ⇒ 00:01:55.780 Uttam Kumaran: I basically like.
17 00:01:56.260 ⇒ 00:02:08.460 Uttam Kumaran: I basically get up work and I go to bed, and I try to go to gym, and you know but it it’s just became became very tough. So now I’m very, very happy, because, you know, we have a really really solid team.
18 00:02:08.940 ⇒ 00:02:12.869 Uttam Kumaran: As you can see, a lot of this, you know, we wanted to try to do.
19 00:02:13.520 ⇒ 00:02:15.760 Uttam Kumaran: We’re able to now, and
20 00:02:15.820 ⇒ 00:02:23.950 Uttam Kumaran: That’s make me really excited for the clients we have now, where we’re really over exceeding expectations and delivering a ton of stuff.
21 00:02:24.070 ⇒ 00:02:25.510 Uttam Kumaran: But where we get
22 00:02:26.010 ⇒ 00:02:40.220 Uttam Kumaran: where we get locked up is like a lot of stuff still is relying on me right? Like, for for example, on your side. it’s like, Okay, what tasks do I work on? Okay? Then I need to do that from your perspective. You’re like, Hey, why doesn’t he just give me stuff to do
23 00:02:40.260 ⇒ 00:02:51.550 Uttam Kumaran: from my perspective. That’s like one of like 50 things. And it’s not priority ranking. It’s actually just all of them are so important.
24 00:02:51.760 ⇒ 00:03:01.640 Ryan Luke Daque: I can, I can see like comparing like the first month we were working together and like, now you’re like, so you seem to be like
25 00:03:01.770 ⇒ 00:03:07.460 Ryan Luke Daque: so much in thought of the a lot of stuff. So especially with, like the
26 00:03:07.860 ⇒ 00:03:20.949 Ryan Luke Daque: yeah new customers, new people also like new tasks to do pipelines and like the dashboards and everything. So yeah, like you mentioned even payroll. I mean, like tax and stuff like.
27 00:03:21.250 ⇒ 00:03:32.139 Ryan Luke Daque: I wouldn’t like. I wouldn’t think that’s your expertise and stuff like that. So yeah, that’s gonna be taxing on you. It’s like high airport for you, I guess. So. Yeah.
28 00:03:32.300 ⇒ 00:03:36.039 Uttam Kumaran: And no. And I. And again, I really appreciate.
29 00:03:37.300 ⇒ 00:03:49.670 Uttam Kumaran: I really appreciate, like you saying that. And again, a lot of these things were in my brain and I knew I wanted to do them. It’s just now’s the time. But the other thing I really need to be diligent about is, how do I give you guys the tools
30 00:03:49.770 ⇒ 00:03:59.840 Uttam Kumaran: to kind of understand and make these decisions. For example. if if you have contacts on each of the different clients, and what’s the highest priority.
31 00:03:59.950 ⇒ 00:04:24.289 Uttam Kumaran: you could go ahead and say, Hey, I made like 5 different tickets. Can you just check what the tickets are and like good to go right? And so we’ll get there. And you know, I think as I get these processes a little bit better down, and everybody has contacts about the work they’re doing, and it becomes more of like a hey? I looked. You guys can look ahead and say, Hey, I noticed this thing. I wanna work on it, are you good? And then it doesn’t require
32 00:04:24.300 ⇒ 00:04:30.720 Uttam Kumaran: kind of like us to rehash everything. And so that’s just a necessary task, right? I think the last 2 weeks
33 00:04:30.770 ⇒ 00:04:40.799 Uttam Kumaran: we want again, I would say, compared to other companies where it takes people like a month to get onboarded like Patrick. And these guys on board in like a week
34 00:04:41.000 ⇒ 00:04:59.759 Uttam Kumaran: about that, because I’ve I think I’ve gotten amazing people, and like the work is speaks for itself. And so there’s no complicated things. I basically let people run free. The next thing we need to do is about like process. So everything, from day to day to the week to the month.
35 00:04:59.890 ⇒ 00:05:08.950 Uttam Kumaran: why are opportunities for you guys to say, like, I’m owning this area, I’m gonna go run towards it. And then me, I can come in and and look across.
36 00:05:09.080 ⇒ 00:05:33.309 Uttam Kumaran: And the the vantage point I have is, I’m sitting above everything. So I can see all the things that everybody’s working on. And you should collaborate here, or actually what someone else is doing is more important or like, we’re missing this area right? And that’s that’s the benefit like. Ultimately, II don’t think that like manager and things like that, and like a hierarchy I think about is like, there’s just a different role.
37 00:05:33.630 ⇒ 00:05:55.310 Uttam Kumaran: right like there’s a role when you are in an individual engineer. And then there’s a role when you are a manager, and the manager’s job is not to engineer and the engineers job, like the manager just under manage. It’s actually the the manager job is to take there the benefit they get of the engineering happening to look above everything, to look above and to look forward to look behind.
38 00:05:55.450 ⇒ 00:06:12.269 Uttam Kumaran: The engineer has to just look, probably at the week level, right, maybe few days, and then execute. And so my my goal is like, you guys can come into work every day and be like, have everything I need. I can run. And my job is to say, do they have it? Do they have everything they need?
39 00:06:12.450 ⇒ 00:06:36.910 Uttam Kumaran: And then what’s coming up next? And what’s what have we done before? And then, hopefully, now, I can give you guys the tools to say, actually, I’m good. I can. I know exactly what I can do next. right? And we kind of have, like we go from planning out just the week to planning out with the month. And so a lot again, a lot of these are happening in parallel, and for me to do that I needed more money. So then we had to deliver for some signs, and they wait for the money. And then so there’s all these like
40 00:06:37.420 ⇒ 00:06:46.579 Uttam Kumaran: domino effect. But we’re in a really good spot right now. And so again, I think we’re just some like growing pains, and it’ll be totally fine. I’m not worried at all. So
41 00:06:47.190 ⇒ 00:06:49.870 Ryan Luke Daque: nice. Yeah.
42 00:06:51.700 ⇒ 00:06:55.600 okay, cool. So I mainly wanted to talk about
43 00:06:56.890 ⇒ 00:07:05.929 Uttam Kumaran: modeling things. And maybe this would be most helpful if you want to take some notes. What I’m gonna ask for you to do is actually
44 00:07:05.980 ⇒ 00:07:18.340 Uttam Kumaran: ticket some of these out and start to spend some time doing that in a new project folder and the new projects thing. So I’m gonna send you that
45 00:07:18.660 ⇒ 00:07:27.350 Uttam Kumaran: at Github. But you don’t have to do this now. Maybe this we could just have a discussion I wanted to talk about.
46 00:07:27.440 ⇒ 00:07:30.050 Uttam Kumaran: You know honestly the clients that we have
47 00:07:30.290 ⇒ 00:07:36.250 Uttam Kumaran: the clients that we have today.
48 00:07:36.740 ⇒ 00:07:38.300 Uttam Kumaran: And
49 00:08:07.760 ⇒ 00:08:15.290 Uttam Kumaran: so mainly just, I think the focus right now is, gonna be
50 00:08:16.650 ⇒ 00:08:17.790 Uttam Kumaran: on
51 00:08:17.920 ⇒ 00:08:31.479 Uttam Kumaran: Let’s talk about the 2 clients where there’s there’s actually been like data modeling work first. So on pool part side, there’s a couple let’s talk about infrastructure related
52 00:08:31.660 ⇒ 00:08:43.550 Uttam Kumaran: projects. So infrastructure. I want to Ca categorize as things like testing as things like the repo structure. Things like naming conventions of tables.
53 00:08:44.670 ⇒ 00:08:46.980 So maybe that’s one thing where?
54 00:08:47.430 ⇒ 00:08:53.009 Uttam Kumaran: We can kind of note down a couple of projects. So one I definitely want to have
55 00:08:53.160 ⇒ 00:08:58.050 Uttam Kumaran: testing. As you mentioned. so we can create maybe a
56 00:08:58.180 ⇒ 00:09:01.250 Uttam Kumaran: like a wish list for Tess.
57 00:09:02.000 ⇒ 00:09:04.500 Uttam Kumaran: and then have some tickets around that.
58 00:09:04.690 ⇒ 00:09:10.830 Uttam Kumaran: So those are the main ones are like, I wanna make sure that sums are good around, like across tables.
59 00:09:10.910 ⇒ 00:09:13.380 Uttam Kumaran: There’s well defined primary keys
60 00:09:13.890 ⇒ 00:09:15.789 Uttam Kumaran: and just make sure that
61 00:09:15.950 ⇒ 00:09:20.750 Uttam Kumaran: every that every model that every core reporting model has tests associated with it.
62 00:09:21.370 ⇒ 00:09:22.750 Ryan Luke Daque: Yeah, that makes sense.
63 00:09:23.960 ⇒ 00:09:31.599 Uttam Kumaran: So I think that’s that’s pretty. Basically on the testing side. I think another infrastructure project that I want to do is
64 00:09:31.690 ⇒ 00:09:34.750 Uttam Kumaran: I wanna modify the repo structure.
65 00:09:35.030 ⇒ 00:09:45.769 Uttam Kumaran: So Pat and Jack have some ideas. I just want to basically crowdsource from the team. What we believe the repo structure should be.
66 00:09:45.780 ⇒ 00:09:48.099 Uttam Kumaran: which is, how are the models organized?
67 00:09:48.310 ⇒ 00:09:49.210 Ryan Luke Daque: Right?
68 00:09:49.410 ⇒ 00:09:55.630 Uttam Kumaran: So that’s something that it would be great again. Maybe it would take 2 days to get feedback on everything.
69 00:09:55.670 ⇒ 00:10:04.369 Uttam Kumaran: understand what changes he’s doing, may execute the changes better reviewed. So that’s one thing I think would be great for you to own is like, what is that?
70 00:10:04.430 ⇒ 00:10:07.850 Uttam Kumaran: How do we actually implement those? Yeah.
71 00:10:09.020 ⇒ 00:10:14.260 Ryan Luke Daque: sure, yeah, we can. We can. That’s what I was also thinking about, like
72 00:10:14.400 ⇒ 00:10:18.509 Ryan Luke Daque: like for pool pipes, for example, like our models, are some somewhat like
73 00:10:19.180 ⇒ 00:10:23.390 Ryan Luke Daque: not really as as structured as as we
74 00:10:23.790 ⇒ 00:10:34.320 Ryan Luke Daque: wanted to be like. Maybe try to organize it better, like reporting would be like one folder and and what whatnot and like staging models would be different and stuff like that. So yeah.
75 00:10:34.370 ⇒ 00:10:38.630 Ryan Luke Daque: maybe I don’t know. Should should I guess we can discuss it with
76 00:10:39.060 ⇒ 00:10:45.850 Ryan Luke Daque: Pat and I was seen, or whoever else maybe the 3 of us 4 of us, I guess.
77 00:10:46.150 ⇒ 00:10:48.950 Uttam Kumaran: Yeah, exactly. Yeah. We can like.
78 00:10:49.230 ⇒ 00:10:52.569 Ryan Luke Daque: decide like what structure we would want to have.
79 00:10:52.880 ⇒ 00:11:00.130 Ryan Luke Daque: make it like a template for all clients that we have report and all repos.
80 00:11:01.280 ⇒ 00:11:08.459 Uttam Kumaran: Yeah, that’s that’s that’s honestly exactly like what I would hope for. So we can make that change there and then
81 00:11:08.610 ⇒ 00:11:15.090 Uttam Kumaran: we could. Then the other thing I want to do there is have a documentation for how we structure repos.
82 00:11:19.260 ⇒ 00:11:21.119 Uttam Kumaran: which would be awesome. Also.
83 00:11:21.530 ⇒ 00:11:24.860 Ryan Luke Daque: I can draft one like, maybe
84 00:11:25.360 ⇒ 00:11:27.930 Ryan Luke Daque: like, based on what I
85 00:11:28.640 ⇒ 00:11:43.369 Ryan Luke Daque: been doing in my previous, like clients like how I organize my models and stuff like that. I can create a draft, and like, we can discuss it. Yeah, let’s do that. So it would be great if can you create that document and then also schedule a meeting
86 00:11:43.740 ⇒ 00:11:50.199 Uttam Kumaran: me, you and maybe between me, you and Patrick.
87 00:11:50.560 ⇒ 00:11:51.350 Ryan Luke Daque: Hmm.
88 00:11:51.550 ⇒ 00:11:54.609 Uttam Kumaran: and then let’s just let’s just
89 00:11:55.790 ⇒ 00:12:00.370 Uttam Kumaran: Yeah, let’s just finalize it right there. So maybe we could schedule that for Monday.
90 00:12:00.610 ⇒ 00:12:08.410 Ryan Luke Daque: Yeah, sure, yeah, I can. I can work on that documentation today, I guess. And yeah, we can discuss about it.
91 00:12:08.490 ⇒ 00:12:14.329 Ryan Luke Daque: See what else we could change. The last point on that is, there’s a refo that’s called. Everybody eats
92 00:12:14.600 ⇒ 00:12:19.970 Ryan Luke Daque: the name of that. But basically, I want to. Just.
93 00:12:20.040 ⇒ 00:12:21.819 Uttam Kumaran: I want to start to save
94 00:12:22.270 ⇒ 00:12:29.269 Uttam Kumaran: like, okay, so there’s actually. So there’s actually 2 things that I wanna do is one
95 00:12:32.490 ⇒ 00:12:35.880 Uttam Kumaran: I wanna actually create like a template repo.
96 00:12:37.430 ⇒ 00:12:42.740 Ryan Luke Daque: So that’s not that repo. But let’s create another one. That’s just like
97 00:12:43.090 ⇒ 00:12:50.720 Uttam Kumaran: Brainforge template repository for any new project. I want to be able to leverage that
98 00:12:51.180 ⇒ 00:12:52.670 Uttam Kumaran: template repository.
99 00:12:52.970 ⇒ 00:13:07.230 Ryan Luke Daque: So I guess, like, what do you have here like? Maybe, Macros, that we would be using over and over again, and stuff like that, right? Everybody eats. One is like, I wanted to publish some stuff publicly. But
100 00:13:07.310 ⇒ 00:13:09.450 Uttam Kumaran: let’s create one. That’s just internally.
101 00:13:09.740 ⇒ 00:13:10.649 Uttam Kumaran: yeah, or.
102 00:13:13.900 ⇒ 00:13:17.010 Uttam Kumaran: yeah, let’s just create one that’s internal. For now.
103 00:13:19.100 ⇒ 00:13:25.300 Uttam Kumaran: okay, yeah. And and like, we, I, we can add onto those like Macros, whatever.
104 00:13:25.450 ⇒ 00:13:26.670 Uttam Kumaran: yeah.
105 00:13:27.560 ⇒ 00:13:33.250 Ryan Luke Daque: we can maybe even make it a DVD package, or just private package as well
106 00:13:33.410 ⇒ 00:13:38.759 Uttam Kumaran: like. So we can just call it to other clients.
107 00:13:41.020 ⇒ 00:13:45.489 Okay, so that’s probably the big things on the infrastructure side.
108 00:13:45.880 ⇒ 00:13:50.240 Uttam Kumaran: the other stuff that I want to
109 00:13:50.520 ⇒ 00:13:53.649 Uttam Kumaran: work on on the pool part side.
110 00:13:53.830 ⇒ 00:14:07.860 Uttam Kumaran: so the main things are like, we basically have all like everything modeled as of now. The only thing that I have been suggesting to Jack and Patrick
111 00:14:07.910 ⇒ 00:14:20.459 Uttam Kumaran: is that they are gonna have model changes that they request like a weekly basis based on their analysis. So I basically said that you’re gonna be leading
112 00:14:20.570 ⇒ 00:14:27.729 Uttam Kumaran: like model changes. So this isn’t like an exact like, Hey, we need to go make this change now.
113 00:14:27.870 ⇒ 00:14:40.869 Uttam Kumaran: But basically it would be great if you could just kind of like W work directly with them. and as they need changes very similar to the customer id stuff that Jack was talking about.
114 00:14:40.940 ⇒ 00:14:43.050 Uttam Kumaran: they’re gonna make changes they want.
115 00:14:43.210 ⇒ 00:14:47.699 Uttam Kumaran: And so the one thing that I would like to get into a cadence of
116 00:14:47.740 ⇒ 00:15:01.059 Uttam Kumaran: is planning out basically what model changes, because for for them, let’s say, their work is going to take a day or 2, your work 3 or 4 days. So there’s definitely like a lead problem where I want them to understand
117 00:15:01.450 ⇒ 00:15:06.829 Uttam Kumaran: that they should be telling you ahead of time what model changes you need, so they can get the timing right
118 00:15:07.010 ⇒ 00:15:08.240 Ryan Luke Daque: right?
119 00:15:08.900 ⇒ 00:15:13.780 Uttam Kumaran: So that this this would be a great meeting honestly for you and
120 00:15:13.910 ⇒ 00:15:21.830 Uttam Kumaran: Jack and Pat to kind of lead. And again, this can happen on Mondays. But basically just getting a sense of like, okay, what are the
121 00:15:22.160 ⇒ 00:15:31.770 Uttam Kumaran: What are the modeling tasks that are necessary for client work this week? Because we basically have done all the stuff we needed.
122 00:15:32.010 ⇒ 00:15:39.930 Uttam Kumaran: So I think that kind of the 3 main areas are one, the test 2, the repo structure
123 00:15:40.080 ⇒ 00:15:45.919 Uttam Kumaran: and 3 just basically being on call for model updates for them.
124 00:15:46.440 ⇒ 00:15:55.170 Uttam Kumaran: which there there are there. There are going to be some that come out so so that’s I think, all for the pool parts. Client.
125 00:15:56.080 ⇒ 00:15:58.930 Ryan Luke Daque: Yeah. that sounds good.
126 00:15:59.590 ⇒ 00:16:03.959 Uttam Kumaran: I think the other thing is for the asset link client. I think.
127 00:16:04.000 ⇒ 00:16:13.739 Uttam Kumaran: Similarly, gonna maybe we can apply the repo structure when we get there. and when we have that, and then, second
128 00:16:14.250 ⇒ 00:16:23.019 Uttam Kumaran: there are some like web related events and things like that that they’re asking for. They haven’t asked for it yet, so I don’t have the tickets yet.
129 00:16:23.360 ⇒ 00:16:24.120 Uttam Kumaran: But
130 00:16:24.300 ⇒ 00:16:26.720 Uttam Kumaran: basically
131 00:16:26.960 ⇒ 00:16:39.980 Uttam Kumaran: I’m just working with them to kind of figure out what the next steps are. Right now. I actually may get your help on a couple of data asks that they have regarding like some data cleaning
132 00:16:40.330 ⇒ 00:16:42.490 Uttam Kumaran: and some
133 00:16:43.800 ⇒ 00:16:46.859 Uttam Kumaran: some data cleaning and some dashboarding.
134 00:16:47.080 ⇒ 00:16:52.079 Uttam Kumaran: but I haven’t gotten the word back from them yet on what those are.
135 00:16:52.260 ⇒ 00:16:55.970 Ryan Luke Daque: This is asset link, Greg, asset link
136 00:16:56.250 ⇒ 00:16:57.079 Ryan Luke Daque: got the check.
137 00:16:57.980 ⇒ 00:17:00.960 Uttam Kumaran: So let’s just we can just pause there for now.
138 00:17:01.430 ⇒ 00:17:04.700 Ryan Luke Daque: Sure. I just one question, though, for the
139 00:17:05.010 ⇒ 00:17:10.449 Ryan Luke Daque: repo, like, if we decide on a repo structure, are we gonna like
140 00:17:11.220 ⇒ 00:17:15.479 Ryan Luke Daque: redo like pullparts and asset link to follow that structure?
141 00:17:15.650 ⇒ 00:17:19.400 Uttam Kumaran: Yeah. So I mean, hopefully, that’s just moving files. Right?
142 00:17:20.410 ⇒ 00:17:22.560 Ryan Luke Daque: Yeah. Okay?
143 00:17:24.130 ⇒ 00:17:27.570 Uttam Kumaran: So the so couple things in that document one.
144 00:17:28.020 ⇒ 00:17:36.319 Ryan Luke Daque: the folder structure to the the file, naming convention, naming convention. Note down that we want to do both of those.
145 00:17:36.710 ⇒ 00:17:45.169 Uttam Kumaran: And then I want to do one big Pr that like renames everything. Basically the the thing that’s going to be tough is I don’t know how that’s gonna work with light dash.
146 00:17:46.580 ⇒ 00:17:49.180 Ryan Luke Daque: All right. Cause that’s yeah. That’s gonna
147 00:17:49.650 ⇒ 00:17:52.150 Ryan Luke Daque: that’s gonna break all the
148 00:17:52.280 ⇒ 00:17:59.959 Ryan Luke Daque: I mean that we. We try that right when we then never mind. But never mind for the documentation. Let’s keep
149 00:18:00.290 ⇒ 00:18:05.140 Uttam Kumaran: naming conventions. But okay, yeah, I don’t even wanna deal with that?
150 00:18:05.310 ⇒ 00:18:14.719 Ryan Luke Daque: Yeah, maybe moving forward, we can use that. But like for the existing one supplied Dash, I mean a full parts and asset link, we can just leave them
151 00:18:14.880 ⇒ 00:18:18.820 Ryan Luke Daque: unless it’s not that big of a change. Right?
152 00:18:20.550 ⇒ 00:18:21.320 Ryan Luke Daque: Yeah.
153 00:18:22.740 ⇒ 00:18:23.490 Ryan Luke Daque: cool.
154 00:18:28.290 ⇒ 00:18:37.189 Uttam Kumaran: So I think that’s a big stuff. So it’d be great, Ryan, if you can come up with a couple of tickets for these and put them into that project.
155 00:18:37.310 ⇒ 00:18:45.459 Uttam Kumaran: Yeah. II think you can generally follow what we’ve done for the ticket templates. which is usually like.
156 00:18:45.790 ⇒ 00:18:51.089 Uttam Kumaran: it’s usually like a goal. And then the acceptance criteria, basically.
157 00:18:51.570 ⇒ 00:18:53.000 Ryan Luke Daque: Yeah.
158 00:18:53.700 ⇒ 00:18:56.999 Uttam Kumaran: I don’t know how to create an a template in
159 00:18:58.140 ⇒ 00:19:02.650 Ryan Luke Daque: project. Cracker.
160 00:19:06.710 ⇒ 00:19:08.470 Ryan Luke Daque: Oh, and
161 00:19:09.830 ⇒ 00:19:11.160 Ryan Luke Daque: sentence.
162 00:19:13.480 ⇒ 00:19:17.909 Ryan Luke Daque: where do I put the repo? Though? Because this is like for everything, I guess.
163 00:19:18.660 ⇒ 00:19:22.080 Ryan Luke Daque: Well, I can just put it. No. So there, there is a thing called internal.
164 00:19:22.440 ⇒ 00:19:26.399 Uttam Kumaran: There’s a client called Brainforge Brain Forge.
165 00:19:26.610 ⇒ 00:19:27.760 Ryan Luke Daque: That makes sense.
166 00:19:30.610 ⇒ 00:19:33.159 Uttam Kumaran: Yeah, I don’t really know
167 00:19:46.380 ⇒ 00:19:47.050 one.
168 00:19:47.850 ⇒ 00:19:50.989 Uttam Kumaran: I don’t really know how to create like an individual template.
169 00:20:39.750 ⇒ 00:20:43.639 Ryan Luke Daque: I guess this would be back end right or like maybe
170 00:20:45.060 ⇒ 00:20:49.069 Ryan Luke Daque: just data model. I guess the task type for this one
171 00:20:49.350 ⇒ 00:20:50.400 Uttam Kumaran: Umhm.
172 00:20:54.950 ⇒ 00:21:00.839 Uttam Kumaran: So is the flow. Are you supposed to be creating issues first and then creating items
173 00:21:02.730 ⇒ 00:21:05.639 Ryan Luke Daque: like for for Github projects. I mean, yeah.
174 00:21:06.810 ⇒ 00:21:08.359 Ryan Luke Daque: I’m not sure. I saw
175 00:21:09.660 ⇒ 00:21:17.150 Ryan Luke Daque: like what we’ve been doing the opposite way, right like we’re creating items and then converting it to issue. And it’s been working.
176 00:21:17.260 ⇒ 00:21:19.690 Ryan Luke Daque: Yeah, that’s no fun.
177 00:21:30.160 ⇒ 00:21:31.090 Uttam Kumaran: I don’t know.
178 00:21:57.470 ⇒ 00:22:07.950 Uttam Kumaran: Okay, whatever we can figure that out later. But yeah, if you just want to put everything into that into that project that I sent you, and then you could tag internal stuff you could tag with Brainforge.
179 00:22:10.010 ⇒ 00:22:22.549 Uttam Kumaran: And then so yeah, if you don’t like creating those testing tickets, the the repo structure and the repa structure, the Docs tickets.
180 00:22:23.170 ⇒ 00:22:28.420 Uttam Kumaran: And then you just want to send me those you could just send me those in internal engineering, and I’ll just take a look.
181 00:22:29.230 ⇒ 00:22:29.960 Ryan Luke Daque: Sure.
182 00:22:31.550 ⇒ 00:22:32.510 Ryan Luke Daque: Sounds good.
183 00:22:35.190 ⇒ 00:22:41.719 Uttam Kumaran: Okay, that’s probably all I had. I think we may chat again as a team later today. But I’ll let you know.
184 00:22:42.300 ⇒ 00:22:47.500 Ryan Luke Daque: Okay, sounds good. Thanks, Utah. Have a nice rest of your day.
185 00:22:47.580 ⇒ 00:22:48.659 Uttam Kumaran: Bye, bye.