WEBVTT

00:00:00.000 --> 00:00:04.080
And I realized that there is so much manual work happening here.

00:00:04.080 --> 00:00:15.119
Everyone is running around and helping people at least get herding in doing wardrobe that is all the merch, conflicts and no one's sure what is shipped, what has not shipped etc. And I realized that this is a problem.

00:00:15.119 --> 00:00:15.919
Things aren't work like this.

00:00:19.600 --> 00:00:23.920
Hello and welcome to episode 40 of the Madagascar podcast.

00:00:23.920 --> 00:00:35.359
This is Ilja and me talking about our journey in Madagascar setting up the company and sometimes we have guests in our show and today we have three folks from

00:00:35.359 --> 00:00:39.119
tram line. They'll tell us in a little bit about what they work on.

00:00:39.119 --> 00:00:43.759
We have Pratul, Nivedita and Akshai from tram line today.

00:00:43.759 --> 00:00:45.679
We're going to hear about their journey.

00:00:45.679 --> 00:00:53.518
If folks have been listening to our episodes like diligently then they know that we talked about tram line a little bit in previous episodes.

00:00:53.518 --> 00:00:56.479
That's the CICD platform that we use.

00:00:56.479 --> 00:01:07.759
And I know Akshai and Nivedita from quite a few years ago when I worked with them for a few months at a dev agency called Nilensso in Bangalore.

00:01:08.399 --> 00:01:09.840
So yeah, here we go.

00:01:09.840 --> 00:01:12.959
Pratul, Akshai, Nivedita, welcome to the show.

00:01:12.959 --> 00:01:15.679
Do you want to introduce yourselves in tram line?

00:01:16.478 --> 00:01:17.519
Hey, so I'm Akshai.

00:01:17.519 --> 00:01:20.799
I've known Arna for quite a few years now.

00:01:20.799 --> 00:01:24.959
As Anna mentioned, we worked together for a bit at Nilensso.

00:01:24.959 --> 00:01:28.719
I think that was 2014 perhaps 15.

00:01:28.719 --> 00:01:37.039
And I think recently too, I just noticed on LinkedIn that you changed your job to tram line.

00:01:37.039 --> 00:01:39.679
And I messaged you on like, hey, what's tram line?

00:01:39.679 --> 00:01:40.478
And you explain it.

00:01:40.478 --> 00:01:47.439
And I was like, that's exactly what we need right now because that week I was struggling setting up CICD for our app.

00:01:47.439 --> 00:01:49.918
So that was like another set of.

00:01:49.918 --> 00:01:54.399
So before we get into tram line, how about you quickly introduce yourselves?

00:01:54.400 --> 00:01:56.879
Because I don't think we've heard all of you so far.

00:01:56.879 --> 00:01:58.480
That's basically it for me.

00:01:58.480 --> 00:02:07.040
So I mean, a little far back before I met you on a B-started Nilensso a year before that, then 13, Nivedita myself.

00:02:07.040 --> 00:02:11.120
And four other folks, I think originally kicked it off.

00:02:11.120 --> 00:02:22.319
I think you know most of them before that we also worked for another sort of very specialized Ruby on RealSish consultancy that was quite popular back in like a decade ago.

00:02:22.319 --> 00:02:25.039
That was what C42 or?

00:02:25.039 --> 00:02:26.639
It was called C42, yeah.

00:02:26.639 --> 00:02:37.280
Yeah, and I found out about those folks through various internet channels like the IRC, which is also where Pratalan I met in 2008.

00:02:37.280 --> 00:02:38.639
Yeah, that's right.

00:02:38.639 --> 00:02:43.280
I've basically been programming since and when moving across these different agencies.

00:02:43.280 --> 00:02:47.680
This is our first foray into doing a product for real.

00:02:47.680 --> 00:02:48.959
Like a full-fledged product.

00:02:48.960 --> 00:02:55.199
Yeah, not a fake sort of is this a product or this is a hobby project type of situation?

00:02:55.199 --> 00:02:56.560
Yeah, it's not a hobby project.

00:02:56.560 --> 00:02:57.520
That's the main thing.

00:02:58.639 --> 00:03:05.840
Thanks. I met Akshay at Nilensso before that C42.

00:03:05.840 --> 00:03:10.000
We both joined C42 around similar times like six months apart or something.

00:03:10.560 --> 00:03:16.960
And after C42 decided to close off its consulting thing, all of us at C42 decided to open Nilensso.

00:03:16.960 --> 00:03:19.120
That was how Nilensso was created.

00:03:19.120 --> 00:03:24.080
Basically, I worked and sort of ran Nilensso for the last few years for about nine years.

00:03:24.080 --> 00:03:27.520
Nilensso very recently celebrated its 10th anniversary.

00:03:27.520 --> 00:03:29.039
Wow, nice, yeah.

00:03:29.039 --> 00:03:30.400
Yeah, I'm surprised.

00:03:30.400 --> 00:03:33.280
I mean, like back when we started, we didn't think it would last this long.

00:03:33.280 --> 00:03:35.120
So, I mean, we wanted it to.

00:03:35.120 --> 00:03:36.400
We didn't think it would.

00:03:36.400 --> 00:03:40.560
But so we were quite happy of the fact that it has lasted long and it's going strong.

00:03:40.560 --> 00:03:43.120
Actually, to be honest, I'm really happy about that.

00:03:43.120 --> 00:03:51.759
The reason I said a real product and not like a hobby product is because at Nilensso, we tried like a few other products apart from the cool thing that Arnaugurgdaan.

00:03:51.759 --> 00:03:56.080
We tried some wiki thing, some reranting matamos.

00:03:56.080 --> 00:03:58.319
I think we tried like a few other products.

00:03:59.039 --> 00:04:02.560
Which we would treat as if it works out in the next three months.

00:04:02.560 --> 00:04:04.639
We will run this otherwise we'll kill it.

00:04:04.639 --> 00:04:08.960
So that was sort of like in our minds, hobby product or hobby project.

00:04:08.960 --> 00:04:11.759
You all were like big into dog fooding also, I think.

00:04:11.759 --> 00:04:16.158
Like everything that you built, you would use it internally and see if you'd like it or not.

00:04:16.158 --> 00:04:18.319
So that's a good way of developing things.

00:04:18.959 --> 00:04:25.519
Yeah, so, Tramline was all of ours first attempt into building a product as a business.

00:04:25.519 --> 00:04:26.879
Actually, second for me.

00:04:26.879 --> 00:04:27.839
I should call pause.

00:04:30.560 --> 00:04:32.639
Okay, let's hear from Pratul also.

00:04:32.639 --> 00:04:35.759
Yeah, you're the only person I don't think I've worked with, right?

00:04:35.759 --> 00:04:37.680
That's for you, because I was not at Nilensso.

00:04:37.680 --> 00:04:41.519
Although Nilensso is timeline and why time that intersects so many times.

00:04:41.519 --> 00:04:42.319
Oh, yeah, quickly.

00:04:42.319 --> 00:04:44.000
Hey, everyone, I'm Pratul.

00:04:44.000 --> 00:04:51.120
Between the three of us, between Akshay and Amedita and me, I'm the one who actually built a lot of mobile first stuff and built a lot of apps.

00:04:51.120 --> 00:04:56.319
I've been building Android applications in production since I think the first one was in 2010.

00:04:56.879 --> 00:04:58.560
Which was very, very early.

00:04:58.560 --> 00:05:01.199
Practically nobody had seen an Android phone.

00:05:01.199 --> 00:05:06.879
Because I remember for the longest time, a lot of people would ask what phone I have because they had never seen Android.

00:05:06.879 --> 00:05:14.158
And before that, I used to do a bunch of PXP and I used to do a bunch of open source work for Drupal.

00:05:14.158 --> 00:05:16.000
The content management platform.

00:05:16.000 --> 00:05:21.839
I did some of the code with Drupal, which is around the same timeline that Akshay and I met online on IRC.

00:05:21.839 --> 00:05:22.879
Through some of the code, right?

00:05:22.879 --> 00:05:24.718
I think it was a some of the code channel.

00:05:24.718 --> 00:05:25.439
That's right.

00:05:25.439 --> 00:05:31.120
Yeah. I mean, we had a shared interest because I was working at Gnome and you were working for Drupal, I think.

00:05:32.079 --> 00:05:36.079
So for people who are not familiar with this, what is some of the code?

00:05:36.079 --> 00:05:38.639
So some of the code is this really fun.

00:05:38.639 --> 00:05:44.478
And probably one of my favorite things that Google has ever done, which is a program for university students.

00:05:44.478 --> 00:05:53.120
So you have to be a student at a university, not in high school, where they get to work on an open source project.

00:05:53.120 --> 00:05:55.598
Like a specific part of an open source product.

00:05:55.598 --> 00:05:58.718
And Google pays them for it.

00:05:58.718 --> 00:06:01.120
So I think the timeline is something like three months.

00:06:01.120 --> 00:06:03.360
I think it's like the program is 10 or 12 weeks long.

00:06:03.360 --> 00:06:08.879
And you get paid, I don't actually have no idea how much money they get paid today.

00:06:08.879 --> 00:06:16.319
But in 2009, which is where I did summer of code, which now sounds like a lifetime ago, I think I got paid $4,500.

00:06:16.319 --> 00:06:17.519
If I remember correctly.

00:06:17.519 --> 00:06:18.639
Something that I'll do.

00:06:18.639 --> 00:06:20.639
Yeah. I think they have regional pricing now.

00:06:20.639 --> 00:06:23.680
Was it 4500 for the whole summer or per month?

00:06:23.680 --> 00:06:25.360
No, no, for the whole summer.

00:06:25.360 --> 00:06:26.879
It's probably still going on.

00:06:26.879 --> 00:06:30.959
But in the beginning, it was very hard to get into also, right?

00:06:30.959 --> 00:06:35.439
Like you would apply for it and then Google will go through like a selection process and all that.

00:06:35.439 --> 00:06:48.399
Yeah. And I distinctly remember this particular year, because the year that I did summer of code in 2009, I think is the first time they selected a hundred students from India.

00:06:48.399 --> 00:06:52.478
India was the second largest country in that year, after the US.

00:06:52.478 --> 00:06:58.639
And it was a hundred students, which is a quite a big deal because they didn't expect so many people from India to show.

00:06:58.639 --> 00:07:01.680
It was very, very nice. The program was very nice. My experience was great.

00:07:01.680 --> 00:07:03.839
It was very formative for me.

00:07:03.839 --> 00:07:06.800
And I'm still friends with pretty much everyone who I'm at at that point.

00:07:06.800 --> 00:07:10.879
And this whole lot of people have gone on to do all sorts of crazy things.

00:07:10.879 --> 00:07:12.639
How old were you when you did this?

00:07:12.639 --> 00:07:16.478
2019, 1920. So basically, like you were still a student.

00:07:16.478 --> 00:07:30.240
Cool. And I remember so these connections that you all created, because when I was working with you all at Nile Enso, there were a lot of other summer of code participants who showed up there.

00:07:30.240 --> 00:07:34.639
And these are like the best programmers in that university year.

00:07:34.639 --> 00:07:40.240
So you were getting the like cream of cream to show up for Nile Enso at that time.

00:07:40.240 --> 00:07:42.800
Yeah. I remember at Nile Enso, at least.

00:07:42.800 --> 00:07:46.079
Obviously worked a little bit differently, but at Nile Enso.

00:07:46.079 --> 00:07:47.199
Wait, what's obvious?

00:07:47.199 --> 00:07:51.360
Sorry, obviously the company had brought to go founded and worked at.

00:07:51.360 --> 00:08:03.600
Let me close out my chapter. Yeah. Basically, I ended up moving to Bangalore from Delhi and starting my career as an Android engineer in 2011, September 2011.

00:08:03.600 --> 00:08:10.480
And I worked on the very first app for this now very large medical software company called Prato.

00:08:10.480 --> 00:08:11.759
And I built their first app.

00:08:11.759 --> 00:08:14.079
I was one of the very early engineers there.

00:08:14.079 --> 00:08:17.360
And that was a fun experience, but I was very, very young.

00:08:17.360 --> 00:08:20.959
And so the founders, they're having the founders are only a year and a half older than me.

00:08:20.959 --> 00:08:23.199
I was 22, so they were 24.

00:08:23.199 --> 00:08:24.158
But you know what happened?

00:08:24.158 --> 00:08:28.879
You need to run a bunch of 22 and 24 year olds together and you asked them to build a business.

00:08:28.879 --> 00:08:31.279
So it was fun for a while and then I realized that he had to want to do this.

00:08:31.279 --> 00:08:33.678
So I want to do something else. I want to do something of my own.

00:08:33.678 --> 00:08:36.000
And basically after that, I never did a job.

00:08:36.000 --> 00:08:37.678
I only did consulting.

00:08:37.678 --> 00:08:40.158
I only did freelancing after that.

00:08:40.158 --> 00:08:48.960
And we and a very close friend from school, who I knew back in Delhi, both of us were in Bangalore and we did a freelance thing for a bit.

00:08:48.960 --> 00:08:53.200
We built a bunch of things and we also tried and had a lot of building a bunch of products.

00:08:53.200 --> 00:08:54.480
Actually, we built a game.

00:08:54.480 --> 00:08:56.080
We built a word game.

00:08:56.080 --> 00:09:00.559
We built a competitor to good reads back then.

00:09:00.559 --> 00:09:02.159
And a bunch of fun stuff.

00:09:02.159 --> 00:09:04.799
And we were kind of running out of money very quickly.

00:09:04.799 --> 00:09:07.679
And I got a chance.

00:09:07.679 --> 00:09:11.759
I think a bunch of people on Twitter were looking for an Android engineer.

00:09:11.759 --> 00:09:15.600
But rather, my former co-founder at Obvious Rahul Ghat Salvis.

00:09:15.600 --> 00:09:17.679
Rahul was looking for an Android engineer.

00:09:17.679 --> 00:09:20.879
And a bunch of people said, hey, if you're in Bangalore, you should talk to Prathal.

00:09:20.879 --> 00:09:23.438
So a bunch of different people tell him about me.

00:09:23.438 --> 00:09:26.239
And he's like, who is this guy again?

00:09:26.239 --> 00:09:30.078
So Rahul and I ended up working on one of the earliest apps at Flipkart.

00:09:30.078 --> 00:09:31.120
That Flipkart I would built.

00:09:31.120 --> 00:09:34.399
In fact, in fact, this was yours before they built a retail app.

00:09:34.399 --> 00:09:39.438
And Avers and eBooks platform and an MP3 streaming platform.

00:09:39.438 --> 00:09:40.879
That's what we worked on.

00:09:40.879 --> 00:09:43.120
Because we'll flight FLYTE.

00:09:43.120 --> 00:09:44.639
And that was fun.

00:09:44.639 --> 00:09:47.438
The most fun thing that came out of it is that Rahul and I became pretty close friends.

00:09:47.440 --> 00:09:48.480
And we decided, hey, you know what?

00:09:48.480 --> 00:09:50.240
We should do this consulting thing together.

00:09:50.240 --> 00:09:51.679
We shouldn't do this separately.

00:09:51.679 --> 00:09:53.360
And that's how Obvious happened.

00:09:53.360 --> 00:09:54.960
It wasn't initially called, obviously.

00:09:54.960 --> 00:09:57.200
It was initially called uncommon.

00:09:57.200 --> 00:10:00.960
But we started uncommon in Bangalore around the same time the Nelland source started.

00:10:00.960 --> 00:10:04.000
And we all knew each other all first pretty much.

00:10:04.000 --> 00:10:06.000
It was a very small community.

00:10:06.000 --> 00:10:10.320
And the next 9, 10 years overlap a lot for us.

00:10:10.320 --> 00:10:13.519
Because we had, yeah, we'd like to throw each other leads all the time.

00:10:13.519 --> 00:10:15.519
We've worked on a bunch of projects together.

00:10:15.519 --> 00:10:17.438
It helped that we weren't competing with each other.

00:10:17.438 --> 00:10:19.279
I think now that I look back, I think.

00:10:19.279 --> 00:10:23.679
Yeah, because Nelland so specialized in doing backend services.

00:10:23.679 --> 00:10:26.078
And like all this fun stuff on the backend.

00:10:26.078 --> 00:10:28.879
And what Obvious specialized in was actually frontend stuff.

00:10:28.879 --> 00:10:33.120
So we were doing design and apps or building apps.

00:10:33.120 --> 00:10:35.438
And so it was a good compliment to each other.

00:10:35.438 --> 00:10:40.000
Because every time we, every time someone asked us, I said, hey, do you guys know someone who can build this API for us?

00:10:40.000 --> 00:10:41.360
I'd be like, yeah, we know the best.

00:10:41.360 --> 00:10:43.600
We're actually, you should talk to these guys.

00:10:43.600 --> 00:10:48.240
Yeah. It lent itself well to being paired up together as well.

00:10:48.240 --> 00:10:50.799
So how did you all decide to start tram line?

00:10:50.799 --> 00:10:58.000
Is it like after 13 years of building Android apps, you finally got tired of automating the release process?

00:10:58.000 --> 00:11:00.480
That's, that's not very far off from the truth.

00:11:00.480 --> 00:11:01.919
Actually, that is the clear.

00:11:01.919 --> 00:11:10.480
So the story of tram line, it's funny because I have been mulling tram line or something like tram line in some shape or form for many years now.

00:11:10.480 --> 00:11:12.559
Many years before tram line even started actually.

00:11:12.559 --> 00:11:14.479
And before I even moved out of office.

00:11:14.479 --> 00:11:16.958
And it was the first people who work came and spoke to.

00:11:16.958 --> 00:11:19.359
And this was in 2018.

00:11:19.359 --> 00:11:27.039
So in 2018, at obvious, we were consulting for Ola Caps and Ola Caps and Uber at that front were fighting T-Hard.

00:11:27.039 --> 00:11:35.198
And so Ola got us in me and a couple of my colleagues we went in and we worked on performance stuff for their driver platform.

00:11:35.198 --> 00:11:40.318
So their driver, the app that their driver's used that was obviously running Android.

00:11:40.318 --> 00:11:41.919
And that platform was running Android.

00:11:41.919 --> 00:11:43.279
And it was built on top of Android.

00:11:43.279 --> 00:11:45.039
So we did a bunch of work for them.

00:11:45.039 --> 00:11:47.438
And I didn't actually write much code there.

00:11:47.438 --> 00:11:52.318
Because I had a couple of folks on my team at that point who were just doing this way faster than I was.

00:11:52.318 --> 00:11:57.679
And I was one of the senior most engineers on the team who had that kind of experience.

00:11:57.679 --> 00:12:01.198
And so my job became looking at the operational stuff of the team.

00:12:01.198 --> 00:12:02.399
And so this was a large team.

00:12:02.399 --> 00:12:09.318
This was a team of 20 engineers that was shipping one of the most used Android platforms daily in India.

00:12:09.320 --> 00:12:13.399
And I realized that there is so much manual work happening here.

00:12:13.399 --> 00:12:24.360
Everyone is running around, helping people are just cat-herding and doing war rooms and resolving merge conflicts and no one's sure what is shipped, what has not shipped, etc. And I realized that this is a problem.

00:12:24.360 --> 00:12:25.879
Things can't work like this.

00:12:25.879 --> 00:12:29.240
So I tried to help them out without building anything.

00:12:29.240 --> 00:12:37.000
Just as a process to kind of streamline their project management, streamline their Geras, streamline their merges and branching strategies and stuff.

00:12:37.000 --> 00:12:43.480
I kind of helped them with that. I actually did training on Git and branching such stuff for them.

00:12:43.480 --> 00:12:47.000
But that was this first part where I realized that this is a problem.

00:12:47.000 --> 00:12:49.799
I think I spent the next year, by the time I came to Nelland.

00:12:49.799 --> 00:12:54.279
So I spent a year looking up who has done something like this.

00:12:54.279 --> 00:13:03.799
And I discovered Facebook in typical Facebook style, had written a research paper very accurately titled Continuous Delivery of Mobile Applications at Facebook.

00:13:03.799 --> 00:13:04.840
It's very straightforward.

00:13:04.840 --> 00:13:07.720
And it's a 16 page log paper still available on the internet.

00:13:07.720 --> 00:13:09.879
Very, very well written, very well researched.

00:13:09.879 --> 00:13:11.320
It has folks like Kent Beck.

00:13:11.320 --> 00:13:14.360
I think Kent Beck is one of the authors on the paper version.

00:13:14.360 --> 00:13:30.120
And they talk about how they built this collection of tools and how they took the idea of a release train and how they took that build tooling around their project management system and their CI and their code to ship continuously or as continuously as they could.

00:13:30.120 --> 00:13:32.840
Because Facebook is one of the first very, very large apps on the iPhone.

00:13:32.840 --> 00:13:34.600
And it shipped on the first iPhone.

00:13:34.600 --> 00:13:36.840
And then it has always been one of the largest apps in the world.

00:13:36.840 --> 00:13:45.399
They ran into this problem before anyone else did that, which was that all the learnings that they had for continuous deployment on their back-end and front-end teams are also super large-scale.

00:13:45.399 --> 00:13:46.200
They all fell flat.

00:13:46.200 --> 00:13:50.200
They all went away because the app store or the Play Store just don't allow that in.

00:13:50.200 --> 00:13:51.399
So this is a very useful paper.

00:13:51.399 --> 00:13:53.720
And that paper was a landmark in my mind.

00:13:53.720 --> 00:13:55.399
I remember because I had it multiple times.

00:13:55.399 --> 00:13:56.840
I printed it out.

00:13:56.840 --> 00:13:58.840
I highlighted it and I was like, this is it.

00:13:58.840 --> 00:14:00.919
This has to exist somewhere.

00:14:00.919 --> 00:14:03.318
And I don't know what I did after that.

00:14:03.318 --> 00:14:06.679
I remember I did a whole bunch of very high-level thinking that this should happen.

00:14:06.679 --> 00:14:07.479
That's right.

00:14:07.479 --> 00:14:08.279
I took it to Nilan.

00:14:08.279 --> 00:14:11.000
So that, hey guys, this is really huge thing.

00:14:11.000 --> 00:14:13.399
I remember that thing was, oh, huge.

00:14:13.399 --> 00:14:14.839
It was so.

00:14:14.839 --> 00:14:17.399
It was a four-part vision.

00:14:17.399 --> 00:14:22.279
It was a multi-year vision into what he wanted this product to be.

00:14:22.279 --> 00:14:24.839
Yeah. And that was what I thought was version one.

00:14:24.839 --> 00:14:26.198
So you went to Nilan.

00:14:26.198 --> 00:14:29.958
So with this and Nilan, so not decide to work on it.

00:14:29.960 --> 00:14:32.840
How did you all fork out of like pretty much?

00:14:32.840 --> 00:14:37.000
I remember the scenes after there was a general disinterest.

00:14:37.000 --> 00:14:38.200
Let me put it that way.

00:14:38.200 --> 00:14:48.919
And I think a lot of the reason was not just because it was perhaps too bloated, but also because I think none of us had really closely worked in the mobile space that much.

00:14:48.919 --> 00:14:50.480
And none of the Nilan's are folks.

00:14:50.480 --> 00:14:54.120
I mean, we'd played around with the Closure script react natives and what have you.

00:14:54.120 --> 00:14:56.200
But not really released at large scale, maybe.

00:14:56.200 --> 00:14:59.480
Those teams were probably like four or five folks at max.

00:14:59.480 --> 00:15:01.960
So it didn't really hit us.

00:15:01.960 --> 00:15:09.320
I think if I remember correctly, it had a lot to do with a whole bunch of other stuff that hopefully trampling will incorporate in the future.

00:15:09.320 --> 00:15:12.679
But not enough to do with releases, per se.

00:15:12.679 --> 00:15:23.919
And that time, I think most of the other stuff, like the feature flaggings and the observabilities of the world were things that the back-end folks were just using.

00:15:23.919 --> 00:15:25.360
It was just a normal sea, right?

00:15:25.360 --> 00:15:27.360
Like the centuries, the data dogs.

00:15:27.360 --> 00:15:32.759
There was also a lack of empathy that all of us at Nilan so would have around this, right?

00:15:32.759 --> 00:15:35.759
Like back-end folks, they're like, this thing is simple.

00:15:35.759 --> 00:15:38.480
Why aren't you just using the standards that exist already?

00:15:38.480 --> 00:15:42.919
Why are you trying to recreate the wheel in some ways?

00:15:42.919 --> 00:15:46.480
That was the initial reaction a back-end team would have to this.

00:15:46.480 --> 00:16:00.519
And I think that I can totally understand that, I think, before starting with the mobile app building thing, because you do all of these things in the back-end, you're flexible because you can deploy smaller microservices independently and all that.

00:16:00.519 --> 00:16:03.198
It all works very seamlessly, I'd say.

00:16:03.198 --> 00:16:16.840
Whereas I think when I started building the iOS app and the Android app, if you just follow their app store guidelines or Android Play Store, independently, you can make it work.

00:16:16.840 --> 00:16:25.958
But just getting everything to work in automated, like, build and deploy, especially from one set-up code base because we use Flutter, right?

00:16:25.958 --> 00:16:28.719
We kind of build both apps from the same code base.

00:16:28.719 --> 00:16:30.799
That was insane.

00:16:30.799 --> 00:16:34.159
So I think I'm glad that something like that exists.

00:16:34.159 --> 00:16:37.198
Who are some of the incumbents in this space?

00:16:37.198 --> 00:16:40.198
There's BitRise, there's a few other places, right?

00:16:40.198 --> 00:16:45.000
So, Arjun, before we go, she can take a step back and maybe talk a bit about the customer problem here.

00:16:45.000 --> 00:16:47.719
What is the world without Tramline?

00:16:47.719 --> 00:17:05.200
Right. So the world without Tramline is effectively a part of your engineering team doing a bunch of coordination work and a bunch of hand holding across teams because you can't move fast enough, because you can't release fast enough on the app stores.

00:17:05.200 --> 00:17:06.160
So how do you release?

00:17:06.160 --> 00:17:08.880
What is the process if you don't use a tool like this?

00:17:08.880 --> 00:17:10.720
Then there are scripts to deploy stuff.

00:17:10.720 --> 00:17:11.519
That's there.

00:17:11.519 --> 00:17:23.519
There are tools that will dump a build into test flight, which fast lane, fast lane, for example, very popular open source project is really the style for open source stuff in mobile specifically, actually, for around mobile apps.

00:17:23.519 --> 00:17:26.959
So there are things like that, but there's scripts.

00:17:26.959 --> 00:17:39.119
And unfortunately, they cover a part of the release cycle and the problem comes into play when you're an organization that is trying to ship a product that you cannot ship fast enough.

00:17:39.119 --> 00:17:41.439
And therefore, you're artificially slowing down your release cycles.

00:17:41.439 --> 00:17:46.199
And if you're artificially slowing down your release cycles, the more you slow down, the more people stress.

00:17:46.199 --> 00:17:51.119
So there is only a couple of times in a month where a mobile first business is actually shipping an app.

00:17:51.119 --> 00:17:55.119
And therefore, everyone else in the app is now worried about those two, three days.

00:17:55.119 --> 00:18:09.719
Because they know me as a product manager or me as an engineering manager, where my team might be working on a feature, I know that if I don't finish this and I don't get it merged by say 11th of October, I will have to wait till 21st of October now.

00:18:09.719 --> 00:18:20.398
Because it'll take us 10 days to slowly roll out the build and that it's stable and it can go to 100% and we've monitored the users and crashes are fine, et cetera, it's a very, because things are slow.

00:18:20.400 --> 00:18:24.359
And things are slow because apps are not like on-premise software.

00:18:24.359 --> 00:18:28.839
Like apps get downloaded to our personal devices or our tablets and our phones.

00:18:28.839 --> 00:18:34.920
And the developers don't have any control about what happens to those apps once they're in the consumers' form.

00:18:34.920 --> 00:18:36.880
So you can choose to never update the app.

00:18:36.880 --> 00:18:38.160
You can choose to cancel the update.

00:18:38.160 --> 00:18:40.720
You can just not open the app entirely, et cetera.

00:18:40.720 --> 00:18:50.359
So it's a lot more complexity and that complexity is much more similar to on-premise software than it is to actually backend software, backend services or say web front-ends, that's not all.

00:18:50.359 --> 00:18:55.039
And Ilia, let me try to also add a bit of color from my perspective.

00:18:55.039 --> 00:19:04.519
When you say it's a script, let's say you have a team of like 15 developers and you're building an iOS app or an Android app or likely both at the same time.

00:19:04.519 --> 00:19:10.439
These scripts, you have to make them work exactly like fine-tune it for your app.

00:19:10.439 --> 00:19:15.839
But also somebody has to be in charge of coordinating all these releases, right?

00:19:15.839 --> 00:19:18.398
Because there's 15 people contributing code.

00:19:18.400 --> 00:19:21.160
You have to figure out which kind of feature is ready to go.

00:19:21.160 --> 00:19:24.440
Does it need to have feature toggling and all that stuff?

00:19:24.440 --> 00:19:28.039
And somebody needs to manually run those scripts.

00:19:28.039 --> 00:19:30.880
And you need to ensure that they're doing it correctly.

00:19:30.880 --> 00:19:34.839
And that's what I think all this process automation and tooling helps with.

00:19:34.839 --> 00:19:40.240
Is you take all of that out of like these 15 people, there's no need to coordinate anymore.

00:19:40.240 --> 00:19:51.359
You just, when you're ready, you ship your changes to or you get your code changes reviewed, merge it into a branch and then tram line will take it from there and figure out how to deploy it.

00:19:51.359 --> 00:19:54.119
A good analogy that I think we often like to use.

00:19:54.119 --> 00:20:01.319
It's a runbook of your perhaps manual release process, perhaps script-based process, but either way.

00:20:01.319 --> 00:20:05.519
It's a runbook that always executes the same way every single time you run it.

00:20:05.519 --> 00:20:10.920
And one of the cool things that have just emerged perhaps are now when yourself have seen it also.

00:20:10.920 --> 00:20:22.359
Now, because all this work is happening on tram line, when aren't there triggers something or earlier you trigger something, we have a full audit log of every single thing that a person did that pertains to her release.

00:20:22.359 --> 00:20:25.240
That is all captured as a part of release data.

00:20:25.240 --> 00:20:30.519
If you made a faulty decision perhaps or a decision that was unwanted.

00:20:30.519 --> 00:20:32.319
It lives on forever now.

00:20:32.319 --> 00:20:34.200
Thanks. Yeah, I live on.

00:20:34.200 --> 00:20:36.279
It's a tram line blame.

00:20:36.279 --> 00:20:41.279
Yeah. Yeah. I'm reading the Elon Musk book right now by Walter Azixon.

00:20:41.279 --> 00:20:53.638
So he says there that Musk will demand dates that next to every single thing that's being done whatever, like a part specification or a release, like for that matter, there would be a name.

00:20:53.638 --> 00:20:57.720
So that there is someone to blame for the things go wrong.

00:20:57.720 --> 00:20:59.279
That's very musky.

00:20:59.279 --> 00:21:00.599
That's one usage of it.

00:21:00.599 --> 00:21:04.480
Another use of it would be to learn, like, OK, this was the mistake we did.

00:21:04.480 --> 00:21:07.839
We can learn from it and not do the same mistake in the next release.

00:21:07.839 --> 00:21:09.599
But just that visibility, right?

00:21:09.599 --> 00:21:17.799
Like if you're running it using a script, let's say from my machine, you have no idea who ran the last release, who deployed it to Android.

00:21:17.799 --> 00:21:20.919
And if you have a question, you don't know who to go to ask.

00:21:20.919 --> 00:21:28.199
And on top of that, once the app is built, you don't know what commits got into it, what commits did not get into it.

00:21:28.199 --> 00:21:34.119
So somebody has to sit around and document all this, might as well be a process and a tool around it.

00:21:34.119 --> 00:21:35.839
Yeah, at the end of the day, it's a binary, right?

00:21:35.839 --> 00:21:38.079
We don't have the same sort of visibility.

00:21:38.079 --> 00:21:44.159
Because in backhand, you usually just like small chunks of work go, perhaps like two or three weeks of words going together.

00:21:44.159 --> 00:21:47.439
And there are times actually where release is run in parallel.

00:21:47.439 --> 00:22:02.720
Like if you're going back to Prattles Facebook paper that he mentioned, most releases, they actually run in parallel in big teams, where if a release has gone past the testing mode and is currently in sort of a release mode, they're released slowly, of course.

00:22:02.720 --> 00:22:08.720
There is another release already, which has gone into testing mode, while the upcoming release is in release mode.

00:22:08.720 --> 00:22:14.640
So there can be sometimes up to three releases, which are getting prepared simultaneously.

00:22:14.640 --> 00:22:17.279
So you don't have to just remember what's going on in this release.

00:22:17.279 --> 00:22:22.880
You have to remember or you have to know what is going on in all the three parallel releases that are getting prepped.

00:22:22.880 --> 00:22:31.119
And in most companies that we have talked to, there is usually one or two people who are like, I know exactly what to do in this release.

00:22:31.119 --> 00:22:34.200
If those people go away, the rest of the team has no idea.

00:22:34.200 --> 00:22:37.519
They're like, I don't know, I don't know how to release this app anymore.

00:22:37.519 --> 00:22:40.200
These are the two or three people who were responsible for it.

00:22:40.200 --> 00:22:44.039
So the best factor is just really, really low in most mobile teams.

00:22:44.039 --> 00:22:46.079
So Tramline plans to eliminate that.

00:22:46.079 --> 00:22:47.920
We have codified your release.

00:22:47.920 --> 00:22:50.240
Like, as Akshay said, this is a runbook.

00:22:50.240 --> 00:22:53.799
This is exactly the steps you need to follow to make this release.

00:22:53.799 --> 00:23:00.880
And even if the person responsible or the one person who knows it by heart is no longer there, anyone can take the runbook and just run with it.

00:23:00.880 --> 00:23:03.319
See, if I'm not there, Ilya can run it now.

00:23:03.319 --> 00:23:05.240
Yeah, because there's one button to click.

00:23:05.240 --> 00:23:06.519
It's guardrails.

00:23:06.519 --> 00:23:12.119
We don't even have a button to click anymore, because that's what I was telling Akshay, that I don't want buttons to click.

00:23:12.119 --> 00:23:16.359
I wanted to go out automatically on every night, yeah, which is great.

00:23:16.359 --> 00:23:20.039
There's a useful addendum here that is probably worth calling out.

00:23:20.039 --> 00:23:24.559
It isn't to say that this stuff doesn't happen on the back end.

00:23:24.559 --> 00:23:34.200
That would be unfair, because the designers and the compliance folks, the regulatory stuff, all the stuff that slows a release down is still there.

00:23:34.200 --> 00:23:35.480
That's not changing.

00:23:35.480 --> 00:23:46.680
The important distinction here to make, I think, is the level, the abstraction that you're working with in terms of the deployment of the software artifact is entirely different.

00:23:46.680 --> 00:23:49.920
I think that's where the stakeholders were a part of this process.

00:23:49.920 --> 00:24:02.440
They have a sense that there's sort of more scrutiny there, because on the web world, even though these folks are participating in this release process, this scrutiny is much less because A, you can deploy more frequently.

00:24:02.440 --> 00:24:04.960
So the unit of work is much smaller.

00:24:04.960 --> 00:24:07.400
And B, you can take it back if something goes wrong.

00:24:07.400 --> 00:24:10.119
Obviously, you don't want to keep rolling back also on the back end.

00:24:10.119 --> 00:24:12.000
That's a terrible waste of time.

00:24:12.000 --> 00:24:14.240
So you should still avoid doing that.

00:24:14.240 --> 00:24:25.039
But you have the optionality to do so is still there, which is why the process, although not entirely distinct from the other side, is more important on the mobile side.

00:24:25.039 --> 00:24:34.319
Yeah, I think like Pratul says, it's very much like you're shipping your code to be run in somebody else's computer, which because that is what it is.

00:24:34.319 --> 00:24:37.119
So it's hard to change after you've shipped it.

00:24:37.119 --> 00:24:39.839
You don't have any control over what's going to happen to it after.

00:24:39.839 --> 00:24:43.960
Yeah, it's shooting a football out in the air, type of situation.

00:24:43.960 --> 00:24:46.679
So who are the incumbents in this space?

00:24:46.679 --> 00:24:48.559
What do you do differently?

00:24:48.559 --> 00:24:53.759
I think one of the ways that I like to think about this is direct incumbents and indirect.

00:24:53.759 --> 00:24:55.960
Like direct competition and indirect competition.

00:24:55.960 --> 00:25:00.960
And direct competition is, of course, folks who are building products that overlap in many ways with transactions.

00:25:00.960 --> 00:25:03.599
So three examples that come to mind.

00:25:03.599 --> 00:25:08.039
Immediately are Microsoft App Center, Betrace, and Runway.

00:25:08.039 --> 00:25:11.759
And all of them do things a little bit, a little bit differently.

00:25:11.759 --> 00:25:14.519
Some of them prioritize a very wide variety of features.

00:25:14.519 --> 00:25:17.279
So App Center, for example, is very comprehensive.

00:25:17.279 --> 00:25:19.159
It has a CI pipeline.

00:25:19.159 --> 00:25:22.839
It has this internal beta build distribution.

00:25:22.839 --> 00:25:26.079
And it has stuff for React Native folks.

00:25:26.079 --> 00:25:29.359
It has over the air updates for React Native apps and stuff.

00:25:29.359 --> 00:25:32.439
Betrace is just CI CD.

00:25:32.440 --> 00:25:37.519
They were one of the first very well done CI platforms that focused on iOS and Android.

00:25:37.519 --> 00:25:38.160
That's their thing.

00:25:38.160 --> 00:25:47.960
Runway, I think, is the closest to what tram ride doesn't the sense that it is a nice, codified, release process, which gives you those guardrails that you can use.

00:25:47.960 --> 00:25:50.039
So there's a point about direct competition.

00:25:50.039 --> 00:25:53.640
And I think this probably is true for most of the market.

00:25:53.640 --> 00:25:57.000
Our fight is less towards direct competition and more towards indirect competition.

00:25:57.000 --> 00:26:02.000
And that is confluence and Google Sheeps and Notion.

00:26:02.000 --> 00:26:05.000
It's not possible that teams aren't solving this all gradually.

00:26:05.000 --> 00:26:06.920
So everyone needs a release process.

00:26:06.920 --> 00:26:08.039
No one just does this at all.

00:26:08.039 --> 00:26:11.759
If you're even marginally serious about your app, you have a release process.

00:26:11.759 --> 00:26:16.400
It's just that the first thing that they'll end up doing is just write it in a Google Doc.

00:26:16.400 --> 00:26:18.880
And at some point, it gets upgraded because someone's maintaining it.

00:26:18.880 --> 00:26:30.039
And then at bigger companies, we've seen five, six-page-wrong confluence documentation, which is maintained by a whole bunch of people that do this and do this and let this person this function for this part and so on.

00:26:30.039 --> 00:26:34.000
And that is really hard to get rid of because that is lured.

00:26:34.000 --> 00:26:35.440
It sounds like it's true.

00:26:35.440 --> 00:26:48.720
And I've often found in our customer conversations, and even in our research, which we've done, it was harder for us to convince people to give up their documentation and move to a system that can do the execution.

00:26:48.720 --> 00:26:51.720
That's an interesting thing to call out the direct and direct competition.

00:26:51.720 --> 00:26:53.079
Why is it hard for them?

00:26:53.079 --> 00:26:54.159
What stops them?

00:26:54.159 --> 00:26:56.240
I think because they're not used to a process at all.

00:26:56.240 --> 00:26:58.079
They are used to completely manual stuff.

00:26:58.079 --> 00:27:00.559
So they have bare-bones CI pipelines.

00:27:00.559 --> 00:27:02.439
It'll just make a remote built.

00:27:02.439 --> 00:27:06.000
Like all they want is a build on a CI server.

00:27:06.000 --> 00:27:07.279
But they don't do anything with it.

00:27:07.279 --> 00:27:08.000
They don't send that.

00:27:08.000 --> 00:27:13.559
They haven't scripted their pipeline to deposit the build into test flight, or to play store, or whatever.

00:27:13.559 --> 00:27:16.480
So what the pipeline does is it basically compiles the code.

00:27:16.480 --> 00:27:17.599
And then a person steps in.

00:27:17.599 --> 00:27:20.878
They download the binary files and it was like, or a 4.2, somewhere.

00:27:20.878 --> 00:27:22.398
It's very manually driven.

00:27:22.398 --> 00:27:24.720
It's a person's job to read that runbook.

00:27:24.720 --> 00:27:26.960
And then, of course, maintain that runbook.

00:27:26.960 --> 00:27:30.599
And they have to remember that this has to be updated because otherwise something will fail.

00:27:30.599 --> 00:27:36.920
What tends to happen with manual processes is you start to change things over time.

00:27:36.920 --> 00:27:39.799
You see, oh, there's a better way to do this small thing.

00:27:39.799 --> 00:27:41.960
And there's a different way to do this.

00:27:41.960 --> 00:27:43.480
And you change those things.

00:27:43.480 --> 00:27:50.039
And now every company who's doing this ends up with their own customized version of their own workflows.

00:27:50.039 --> 00:27:58.599
And you don't want to go to a tool because it maybe doesn't do five of the 25 things that you want, that you want to specifically control.

00:27:58.599 --> 00:28:07.079
This actually goes back to something that I was talking to Akshay maybe a few months back is how are you thinking about acquiring customers?

00:28:07.079 --> 00:28:24.200
Because established companies that have their own CIICD very, very specific document that this is what we do step after step will find it hard to move to something that is streamlined because it might not do a few of the things that they want

00:28:24.200 --> 00:28:28.759
versus maybe smaller places that don't have an established process.

00:28:28.759 --> 00:28:30.279
They're just looking to get started.

00:28:30.279 --> 00:28:33.440
Kind of like Ruby on Rails back when you started.

00:28:33.440 --> 00:28:34.759
It's very opinionated.

00:28:34.759 --> 00:28:36.680
But you know exactly what you're getting.

00:28:36.680 --> 00:28:38.319
And you don't have to think about it.

00:28:38.319 --> 00:28:50.240
I think one of the ways we are planning to, we think where we can work with this is we ask people, we model the release process in timeline as you would do it in your company.

00:28:50.240 --> 00:28:53.920
It's not, timeline is not opinionated in how you should run your release.

00:28:53.920 --> 00:28:56.720
It's not actually opinionated that way at all.

00:28:56.720 --> 00:29:00.880
What it is opinionated about is like whatever you do, you need to put that down.

00:29:00.880 --> 00:29:03.960
You need to put that down as a step in the release process.

00:29:03.960 --> 00:29:08.480
So that is I think where we differ from some of the incumbents as well.

00:29:08.480 --> 00:29:16.200
We will model your release process, whatever you follow because one of the other things is mobile doesn't have standards around this.

00:29:16.200 --> 00:29:21.440
Mobile teams do not have any kind of conventions or standards around how to run.

00:29:21.440 --> 00:29:22.720
I mean, I'm not saying any kind.

00:29:22.720 --> 00:29:27.640
There are some standards, but everyone has their own way of doing this, which is not true.

00:29:27.640 --> 00:29:32.799
And back in I have noticed there is a certain amount of the DevOps sort of guidelines that exist.

00:29:32.799 --> 00:29:36.079
Yeah, the types of deployments you can do canary, you can do blue green and all that.

00:29:36.079 --> 00:29:39.480
But like how to get to that is a very straightforward.

00:29:39.480 --> 00:29:40.480
It's very standard.

00:29:40.480 --> 00:29:48.759
So if you actually go back maybe eight to 10 years, there was a whole type of role called release engineers and release management.

00:29:48.759 --> 00:29:51.480
And so you would have your dev team who was building it.

00:29:51.480 --> 00:29:55.359
There's a support team, there's a DevOps team, and then there's a release team.

00:29:55.359 --> 00:30:04.079
All they do is figure out like what branches to merge, how to merge them, merge them, resolve the conflicts and go through these steps.

00:30:04.079 --> 00:30:06.680
And that today, that's gone, right?

00:30:06.680 --> 00:30:14.960
Like that role doesn't exist pretty much, except for maybe some very, very older companies who haven't changed their processes because it's all automated now.

00:30:14.960 --> 00:30:18.319
And that's what you're trying to do for the mobile world essentially.

00:30:18.319 --> 00:30:21.720
I mean, it helps to bear in mind that mobile is very, very new.

00:30:21.720 --> 00:30:27.039
Like the App Store 14 years, I think 13 or 14 years is the App Store's age.

00:30:27.039 --> 00:30:28.119
It's very new.

00:30:28.119 --> 00:30:36.119
And a lot of the very large mobile first companies that people associate, when people think of an app, some of the largest successful companies are very, very new.

00:30:36.119 --> 00:30:41.640
Say, Swicky, Go Jack. Or even like Uber, Facebook, they're not that old, compared.

00:30:41.640 --> 00:30:43.640
Yeah, Uber is I think 2012.

00:30:43.640 --> 00:30:45.599
I think it's like just over 10 years old.

00:30:45.599 --> 00:30:51.960
So it's not surprising that the first generation of companies that became very, very large and we've had done our research on this.

00:30:51.960 --> 00:31:00.079
It's not surprising that the Uber's and the lifts, you know, and the Spotify and Shopify and stuff, all of them built tools like Tramline internally.

00:31:00.079 --> 00:31:02.599
They faced the problem very, very fast.

00:31:02.599 --> 00:31:07.200
They were hitting huge scale on this app that they were shipping.

00:31:07.200 --> 00:31:20.039
And now that we're in the second generation, the second decade of the App Store, like it's kind of ridiculous to expect now that the next Uber that happens, or like the next large scale mobile first business that gets built, they will also have to solve the same problem internally.

00:31:20.039 --> 00:31:21.039
It's kind of ridiculous.

00:31:21.039 --> 00:31:25.398
It's time to democratize some of those ideas that we've understood that are good ideas.

00:31:25.398 --> 00:31:29.480
I'm kind of surprised that none of those companies open source something.

00:31:29.480 --> 00:31:32.799
And then AWS will just pick it up and do the service out of this.

00:31:35.200 --> 00:31:46.039
A few of them have, I believe, Shopify's ship it is open source and it's already written in a plug-in-based way where you can write one thing on top of it.

00:31:46.039 --> 00:31:49.240
You can write your own plugins to make your own process on it.

00:31:49.240 --> 00:31:51.720
But of course, writing that plugin is expensive.

00:31:51.720 --> 00:31:53.319
It's non-trivial to do.

00:31:53.319 --> 00:31:55.680
Yeah, no one open source their platform.

00:31:55.680 --> 00:31:57.638
People have open source parts of their tool.

00:31:57.638 --> 00:32:01.799
People have written about it extensively, even if they haven't open source it, there's a lot of writing.

00:32:01.799 --> 00:32:03.359
And we have learned a lot from that writing.

00:32:03.359 --> 00:32:08.039
We've in fact spoken to some of the people who've done that writing and understood what they were thinking and like how things were.

00:32:08.039 --> 00:32:14.359
We really hunted the internet for some of these videos around like five years ago, 10 years ago with people talking about these things.

00:32:14.359 --> 00:32:24.839
In fact, a lot of the UI that you see on Ramline is just directly lifted off of the few screenshots that you can find from the internal tools that these people have built it's based.

00:32:24.839 --> 00:32:28.240
So the stuff we just realized, this is great, they already figured this out.

00:32:28.240 --> 00:32:29.759
Has this to this?

00:32:29.759 --> 00:32:34.719
So talking about open source, you offer a Ramline, like it's fully open source also, right?

00:32:34.719 --> 00:32:39.279
So tell us like what led you to go down that path, how it's working out?

00:32:39.279 --> 00:32:46.000
I mean, when Pratil and I were speaking about this originally, which was when we were both in our previous jobs.

00:32:46.000 --> 00:32:53.000
And when we were speaking about this, I think it was very clear to us that this would have to be open source.

00:32:53.000 --> 00:32:58.079
There are reasons for it to be open source that make sort of longevity sense.

00:32:58.079 --> 00:33:06.839
And then there are reasons for it to be open source, which are derived from the fact that there is no reason for it to not be.

00:33:06.839 --> 00:33:08.839
So it's like that kind of lens as well.

00:33:08.839 --> 00:33:12.559
Of course, the second one is philosophical in nature.

00:33:12.559 --> 00:33:14.519
You have to buy into it, you have to believe in it.

00:33:14.519 --> 00:33:22.000
And I'm sure everyone knows the folks that I'm talking about here, started the open source evangelists of the world would say this.

00:33:22.000 --> 00:33:25.079
And I think we roughly fall into those camps as well.

00:33:25.079 --> 00:33:32.159
There was no reason for Ramline to not be open source in the sense that there was nothing much to lose here.

00:33:32.159 --> 00:33:41.440
Of course, when you're such in such an early stage, you can argue about it like what if the AWS is of the world coming and take your software and launch a service and all of that.

00:33:41.440 --> 00:33:43.720
I mean, we would be humbled to if they did so.

00:33:43.720 --> 00:33:48.000
Please take our software and launch our service if you're watching this.

00:33:48.000 --> 00:33:51.039
But it isn't really just about that.

00:33:51.039 --> 00:33:54.319
In a similar way, Fastlane has forever been open source.

00:33:54.319 --> 00:34:03.440
It makes sense for this kind of software, which is trying to build a standard to operate how things are done.

00:34:03.440 --> 00:34:07.480
It is essential for everyone to know what we're up to at all times.

00:34:07.480 --> 00:34:16.280
In a way, you're trying to get collaboration, but also with a community, you want to define the standards because there is an standard, right?

00:34:16.280 --> 00:34:19.400
And one way to do that is open source code.

00:34:19.400 --> 00:34:23.840
So if they don't like something, they can contribute a different way of doing it.

00:34:23.840 --> 00:34:34.199
Is it part of the calculus that also, if you have kind of critical mass, then you can also influence Apple and Google Play to modify their APIs, do stuff like that?

00:34:34.199 --> 00:34:35.159
Yeah, that would be great.

00:34:35.159 --> 00:34:42.920
Actually, there's a whole bunch of stuff that's missing as of today, which disallows us from giving you all a better experience, right?

00:34:42.920 --> 00:34:45.000
Like there's just APIs are lacking.

00:34:45.000 --> 00:34:49.760
Documentation is very often lacking around a lot of this stuff.

00:34:49.760 --> 00:34:51.719
Yeah, Erna is well aware.

00:34:51.719 --> 00:35:01.519
I don't think that's an active goal, but we hope that this does change some stuff because it's so visible that, hey, okay, these folks are trying to solve this problem here.

00:35:01.519 --> 00:35:05.400
It seems like we're not providing them enough information to make it better.

00:35:05.400 --> 00:35:06.960
We must do something about it.

00:35:06.960 --> 00:35:09.440
It's hopefully an emotion or...

00:35:09.440 --> 00:35:13.159
Enough of an influence to infancy big companies.

00:35:13.159 --> 00:35:14.480
Good luck.

00:35:14.480 --> 00:35:27.960
We have comments on Google Issue Tracker around their APIs, which all these companies that we mentioned, Shopify, Etsy, every one of those people who have built a platform like this, there's a comment there saying, please fix this.

00:35:27.960 --> 00:35:33.639
All the incumbents who have come have actually gone there and written a comment and we're like, okay, yeah, we see it.

00:35:33.639 --> 00:35:37.599
These are the people who are building these, or these are the people who are actually to platform here.

00:35:37.599 --> 00:35:43.880
Yeah, I'm surprised that Google hasn't done anything in this space because they've got a bunch of Android and iOS app.

00:35:43.880 --> 00:35:46.880
I don't know how many, probably like over 50 different apps.

00:35:46.880 --> 00:35:48.320
They have their own platform internally.

00:35:48.320 --> 00:35:49.239
We know this.

00:35:49.239 --> 00:35:52.760
Yeah, they probably have a really good platform internally.

00:35:52.760 --> 00:35:56.760
Exactly, yeah, but why don't they externalize it as a GCP service?

00:35:56.760 --> 00:36:00.440
And see, I think this is where one of those differences with Amazon would come in.

00:36:00.440 --> 00:36:09.000
If Amazon had produced 50 apps internally and had built a platform, I'm sure we would have seen like an AWS service about it already.

00:36:09.000 --> 00:36:15.039
Whereas Google probably likes to do excellent things, but it's not enough to get promoted.

00:36:15.039 --> 00:36:16.280
Right.

00:36:16.280 --> 00:36:16.800
Right.

00:36:16.800 --> 00:36:20.480
They haven't seen the opportunity to like make a thing about it yet.

00:36:20.480 --> 00:36:22.960
Or if they build it, they'll kill it after five years.

00:36:22.960 --> 00:36:23.559
One year.

00:36:23.559 --> 00:36:25.159
Yes, that too.

00:36:25.159 --> 00:36:34.440
But I feel like the folks are using the developer console on Google at the very least upload a binary and then roll it out.

00:36:34.440 --> 00:36:40.480
I think that solves most of the use cases for most of the people that platform.

00:36:40.480 --> 00:36:44.119
And I feel like that is enough in their heads, perhaps.

00:36:44.119 --> 00:36:45.559
I mean, this is all conjecture.

00:36:45.559 --> 00:36:48.320
It feels like this is good enough today.

00:36:48.320 --> 00:36:52.400
Of course, when we are talking about online, we're talking about the 90th percentile, right?

00:36:52.400 --> 00:36:57.639
Like we're talking about folks who are at the top of their game, essentially the top of the top mobile first companies.

00:36:57.639 --> 00:36:58.239
Like us.

00:36:58.239 --> 00:36:59.639
Yeah, you're pretty much here.

00:36:59.639 --> 00:37:00.639
Exactly.

00:37:00.639 --> 00:37:04.119
Or who is crucial, like whose business is mobile critical?

00:37:04.119 --> 00:37:07.759
Their business would stop if the mobile apps are not shipped on time.

00:37:07.759 --> 00:37:12.039
It's kind of interesting because you need some experience and expertise to actually even realize you have this problem.

00:37:12.039 --> 00:37:16.798
Because if you take like a student doing a pet project, it's not a big deal to upload something to the web console, right?

00:37:16.798 --> 00:37:18.079
They may not even think about it.

00:37:18.079 --> 00:37:22.318
But then what we are realizing now, we are a very small startup.

00:37:22.318 --> 00:37:28.798
And we save a lot of time, but also a lot of energy, but not having to do all the mental work.

00:37:28.800 --> 00:37:32.199
So actually startups probably get to benefit from this a lot.

00:37:32.199 --> 00:37:33.360
They just don't know.

00:37:33.360 --> 00:37:35.000
Maybe they don't think about this.

00:37:35.000 --> 00:37:40.599
I think you folks are definitely, I would use the word over-engineered in a slightly good sense.

00:37:40.599 --> 00:37:41.880
I mean, it's all good.

00:37:41.880 --> 00:37:42.880
I told you, Arnav.

00:37:42.880 --> 00:37:43.880
I told you.

00:37:43.880 --> 00:37:45.880
I told you.

00:37:45.880 --> 00:37:47.159
No, but you're absolutely right.

00:37:47.159 --> 00:38:02.840
Arnav, to your previous question, if there is like a Ruby on Rails version of tram line, this is definitely something we think about pretty much every week, breaking through the barriers of existing work that people have put in, and then not necessarily swapping it,

00:38:02.840 --> 00:38:11.199
but augmenting it with the more streamlined experience is initial work, which of course, we also had to spend a day together to do this.

00:38:11.199 --> 00:38:12.159
That's true.

00:38:12.159 --> 00:38:28.800
The slice that requires this to be a Ruby on Rails experience requires tram line to be a Ruby on Rails experience, which is basically the one-engineered framework, they want they like to call it, which essentially means it's a full stack framework, which means they do everything from top to bottom,

00:38:28.800 --> 00:38:33.800
you're vertically integrating all the sorts of stuff that you do in a release in one single place.

00:38:33.800 --> 00:38:39.880
And that's definitely something that's on the cards, but not a high priority at the moment.

00:38:39.880 --> 00:38:54.159
But yeah, it is, I think, valuable to both enterprises, just to draw this analogy out even further, Ruby on Rails is used by us, and Ruby on Rails is used by Shopify's, and the intercoms of the world also.

00:38:54.159 --> 00:38:55.519
It works for everyone.

00:38:55.519 --> 00:38:57.480
You just have to scale it differently.

00:38:57.480 --> 00:38:59.759
So it's been about a year now, right?

00:38:59.759 --> 00:39:07.000
And you're three people who does what, how are you like distributing, deciding who works on which sides and all that?

00:39:07.000 --> 00:39:17.838
Akshay and I take care of all of engineering, product, and engineering, related writing, support, in fact, some amount of sales as well, Pratulitex care of sales and product as well.

00:39:17.838 --> 00:39:25.360
So right now, I think we're such a small company that it doesn't need to have very clear divisions, like you do only this and you do only that.

00:39:25.360 --> 00:39:27.159
I was actually having this conversation with Akshay yesterday.

00:39:27.159 --> 00:39:32.480
It's sort of like this week or this next two weeks, needs to be completely focused on just this problem.

00:39:32.480 --> 00:39:35.480
So you go do that and why I take care of everything else.

00:39:35.480 --> 00:39:38.599
The other side is like, okay, this week, we don't have a lot of engineering work.

00:39:38.599 --> 00:39:42.199
So let's just, you also focus on sales, you also work focus on marketing.

00:39:42.199 --> 00:39:48.599
It is a bit of flexible roles right now, but yeah, Pratulitex, this is the kind of division we have right now is you.

00:39:48.599 --> 00:39:50.318
There are some baseline roles.

00:39:50.318 --> 00:39:51.838
That's what you need in a start.

00:39:51.838 --> 00:39:53.559
Yeah, that window is all the engineering.

00:39:53.559 --> 00:39:54.960
This window does no engineering.

00:39:54.960 --> 00:39:56.039
That's a big difference.

00:39:56.039 --> 00:40:01.000
But all three of you like code, all three of you do sales whenever needed, all three of you do.

00:40:01.000 --> 00:40:02.719
No, I barely written any code.

00:40:02.719 --> 00:40:04.239
I've done a bunch of UI work early on.

00:40:04.239 --> 00:40:05.639
I did a bunch of UI work.

00:40:05.639 --> 00:40:09.838
So there are some baseline roles, I would say, sort of initial roles.

00:40:09.838 --> 00:40:21.798
And then there is some minor overlap here and there because of from an engineering point of view, since both need and myself are there, it's slightly more engineering heavy happens to be engineering heavy at the moment.

00:40:21.798 --> 00:40:28.079
So we tend to balance out the whole equation of the sales marketing engineering support, the whole loop.

00:40:28.079 --> 00:40:35.719
It's possible that like sometimes the both of us spend more time on non-engineering work to balance out the work Pratulitex putting in.

00:40:35.719 --> 00:40:43.960
But yeah, we do have some baseline responsibilities and we are there weeks where like Pratulitex, you can get rid of sales, which we have with a couple of potential customers.

00:40:43.960 --> 00:40:46.239
And I am the one only doing engineering.

00:40:46.239 --> 00:40:48.199
I mean, right now I'm doing fundraising.

00:40:48.199 --> 00:40:52.400
And I've only been doing fundraising for three weeks now, I think.

00:40:52.400 --> 00:40:53.639
You look exhausted, man.

00:40:53.639 --> 00:40:59.559
Yeah, I don't think I've spoken to bigz many people in three weeks, F-Burge.

00:40:59.559 --> 00:41:01.000
I met so many new people.

00:41:01.000 --> 00:41:02.599
Tell us about that side of it.

00:41:02.599 --> 00:41:05.840
Like how's the money flowing in?

00:41:05.840 --> 00:41:08.159
How did you get your first few customers?

00:41:08.159 --> 00:41:09.480
How's that all going?

00:41:09.480 --> 00:41:12.679
What are you looking to do with fundraising and all that?

00:41:12.679 --> 00:41:15.079
So the first few customers, we just threatened all of them.

00:41:15.079 --> 00:41:17.878
Have you went and threatened all our clients?

00:41:17.878 --> 00:41:21.719
Effectively told them, hey, we are doing this thing and you have to listen to us.

00:41:21.719 --> 00:41:23.918
Clients from consulting time, OK?

00:41:23.918 --> 00:41:25.639
Yeah, clients from consulting.

00:41:25.639 --> 00:41:29.559
And all of them were like, yeah, I can do something.

00:41:29.559 --> 00:41:30.679
And we'll talk to you.

00:41:30.679 --> 00:41:32.440
I was a very, very slow person.

00:41:32.440 --> 00:41:41.759
I think personally from me, theoretically, and in all manner, understood that the early sales process is very, very slow.

00:41:41.760 --> 00:41:43.719
Like it takes a very long time.

00:41:43.719 --> 00:41:46.880
But I was still constantly surprised at how long it took, OK?

00:41:46.880 --> 00:41:48.280
I've heard it.

00:41:48.280 --> 00:41:49.719
It was such a drain.

00:41:49.719 --> 00:41:52.199
It was such a slog and just understand.

00:41:52.199 --> 00:41:54.519
At some point, I have to write a blog first about this.

00:41:54.519 --> 00:42:02.719
Like my personal experience of understanding the meaning of living through what the word positioning means.

00:42:02.719 --> 00:42:06.400
It's very easy to say, oh, your product positioning is not right.

00:42:06.400 --> 00:42:08.039
That doesn't mean anything to me.

00:42:08.039 --> 00:42:15.760
But to feel it, once you've spoken to 100 people, like 100 different companies, and then you realize, oh, they're just not getting it.

00:42:15.760 --> 00:42:17.119
Like, what am I saying wrongly?

00:42:17.119 --> 00:42:18.599
I'm not saying this the right way.

00:42:18.599 --> 00:42:20.360
So that it was a challenge, of course.

00:42:20.360 --> 00:42:21.599
But I thought it was very exciting.

00:42:21.599 --> 00:42:28.599
I get excited still when someone tells me about a thing from their personal background, which theoretically I understand.

00:42:28.599 --> 00:42:30.880
I guess you're retically no enterprise sales cycles are long.

00:42:30.880 --> 00:42:36.119
I sure, retically know that these things, I've never done it, but I sure, I technically know this is what's going to happen.

00:42:36.119 --> 00:42:42.639
But when someone tells me a person anecdotes about something from there, here, you're like, I meet someone and they'll tell me, yeah, 10 years ago, I did this.

00:42:42.639 --> 00:42:45.880
It's very fascinating to me that, wow, it's almost identical.

00:42:45.880 --> 00:42:47.840
There is no difference in this stuff at all.

00:42:47.840 --> 00:42:50.519
It's very first principles the way that this happens.

00:42:50.519 --> 00:42:54.519
So for us, our first users are all friends, like for everyone else.

00:42:54.519 --> 00:43:03.119
I've had a lot of friends who obviously have been mobile engineers, and our mobile engineers, they're building site projects, hobby projects.

00:43:03.119 --> 00:43:05.800
Some of them are building new businesses.

00:43:05.800 --> 00:43:07.920
Like you guys happen to be in that category.

00:43:07.920 --> 00:43:10.960
So those folks definitely became our earliest users.

00:43:10.960 --> 00:43:13.719
And some of those folks became early customers.

00:43:13.719 --> 00:43:15.400
They can work to customers.

00:43:15.400 --> 00:43:21.920
And correct me if I'm wrong, I think it took us seven months to get to the first user, right?

00:43:21.920 --> 00:43:23.280
Six, seven months.

00:43:23.280 --> 00:43:24.480
Yeah, I would say so.

00:43:24.480 --> 00:43:28.840
So is it seven months after we've already had the product, or is it seven months, including building the product?

00:43:28.840 --> 00:43:30.280
No, including building the product.

00:43:30.280 --> 00:43:35.920
Seven months of going from zero to, basically, zero to one where one is a production release.

00:43:35.920 --> 00:43:39.039
Or rather, someone made a production release to the app store.

00:43:39.039 --> 00:43:41.400
I think it was a place to actually be to the place or using traps.

00:43:41.400 --> 00:43:48.719
It was the place to, that was basically our benchmark because you can do all sorts of releases to test flights in the Firebase app distribution to the world.

00:43:48.719 --> 00:43:52.360
But the serious test of the platform is shipping it to the users.

00:43:52.360 --> 00:43:54.960
And so that's where we measured the benchmark.

00:43:54.960 --> 00:43:56.759
OK, this is how we counter-release.

00:43:56.759 --> 00:43:59.360
Everything else is sub-release.

00:43:59.360 --> 00:44:01.719
What's interesting is actually add to this.

00:44:01.719 --> 00:44:08.798
Is that from Jan, it took us six more months to get our first big enterprise customer.

00:44:08.800 --> 00:44:15.960
So it took us like a nearly a full year, even though we're in a market where we definitely, we're given that we're talking we're in Bangalore.

00:44:15.960 --> 00:44:20.400
And like the three of us have been done engineering in Bangalore for more than a decade.

00:44:20.400 --> 00:44:23.199
And we have access to so many of these companies, even then.

00:44:23.199 --> 00:44:24.840
And we did speak to a lot of these companies.

00:44:24.840 --> 00:44:31.400
But the value of land to love to get them to understand the value and for them to agree that, yes, we will try this.

00:44:31.400 --> 00:44:33.239
Yeah, a year of work.

00:44:33.239 --> 00:44:43.480
So if you were to say this on LinkedIn, you would say like you leveraged your robust network of previous connections cultivated during your consulting times.

00:44:43.480 --> 00:44:45.239
It created synergy.

00:44:45.239 --> 00:44:46.239
I will record it.

00:44:46.239 --> 00:44:47.119
Listen to this recording.

00:44:47.119 --> 00:44:49.079
And I will make that a positive.

00:44:49.079 --> 00:44:52.119
You could call this red flags or whatever you will, right?

00:44:52.119 --> 00:44:54.960
But this product is quite complicated to build.

00:44:54.960 --> 00:45:01.960
This is a non-trivial thing to ship in two months, which is like the general thumb rule of you ship three months or whatever to your first user.

00:45:01.960 --> 00:45:03.679
This was literally impossible.

00:45:03.679 --> 00:45:08.039
It would be basically Frankenstein project if we had shipped it like that.

00:45:08.039 --> 00:45:09.480
It would be dysfunctional.

00:45:09.480 --> 00:45:22.000
And so because it's such an integration heavy sort of thing, and it requires so much domain context to do, it doesn't make sense piecemeal until a whole bunch of things come together.

00:45:22.000 --> 00:45:29.798
There is obviously, I mean, looking back, perhaps there is some stuff we could have definitely left out, but it wouldn't have gone from like eight months to three months.

00:45:29.798 --> 00:45:32.278
It would have still been like five months or six months.

00:45:32.280 --> 00:45:37.360
Yeah, so you call it what you will, but I think that time elapsed was necessary.

00:45:37.360 --> 00:45:40.039
And of course, this is roughly the first time for us, right?

00:45:40.039 --> 00:45:41.639
Also trying to sell this.

00:45:41.639 --> 00:45:43.119
And so those cycles are also longer.

00:45:43.119 --> 00:45:48.159
And not just that, it's just this sort of stuff isn't out there in the wild.

00:45:48.159 --> 00:45:53.159
This isn't generated way, and this isn't a version control system, and this is into Jenkins.

00:45:53.159 --> 00:45:56.119
It's an entirely new subsystem.

00:45:56.119 --> 00:46:03.519
It sort of comes in the purview of wild DevOps, which has become sort of famous over the last five years, four years.

00:46:03.519 --> 00:46:10.119
But again, there was nothing to compare it to that this is like X of mobile engineering.

00:46:10.119 --> 00:46:14.119
There was no analogy we could draw when we were selling it to people.

00:46:14.119 --> 00:46:16.878
So we had to almost start from scratch.

00:46:16.878 --> 00:46:19.599
We would have to say, OK, this is how you do things now.

00:46:19.599 --> 00:46:21.599
And this is how you do things with tram line.

00:46:21.599 --> 00:46:26.559
And by the way, we have learned how to sell this by failing at it for so long.

00:46:26.559 --> 00:46:28.079
I wouldn't say we've learned it yet.

00:46:28.079 --> 00:46:29.838
I think we're starting to learn.

00:46:29.838 --> 00:46:31.920
We're still always moving.

00:46:31.920 --> 00:46:32.920
Yeah, I don't.

00:46:32.920 --> 00:46:36.039
I'm saying we've learned it in the sense that we've done one sale, big sale.

00:46:36.039 --> 00:46:38.960
So in that way, I'm going to give ourselves some credit.

00:46:38.960 --> 00:46:45.360
But I think this learning process is going to continue because none of us had actually sold a software.

00:46:45.360 --> 00:46:46.480
We were always on the other end.

00:46:46.480 --> 00:46:48.000
We were always the buyers.

00:46:48.000 --> 00:46:48.920
Actually, that's the point.

00:46:48.920 --> 00:46:57.159
Remember, we were discussing this today or yesterday that even as buyers, I don't remember ever paying $100,000 for a software.

00:46:57.159 --> 00:46:58.800
Not this bigger software, yeah.

00:46:58.800 --> 00:46:59.320
Exactly.

00:46:59.320 --> 00:47:05.159
So the three of us have also both of you, like you know, you win at AWS and Google.

00:47:05.159 --> 00:47:10.679
And you've actually had that experience of how large companies think of buying software and using it and deploying it.

00:47:10.679 --> 00:47:15.400
So you've probably seen six-figure contracts, seven-figure contracts, or your career.

00:47:15.400 --> 00:47:16.400
We've never done that.

00:47:16.400 --> 00:47:18.119
None of us have ever seen that happen.

00:47:18.119 --> 00:47:23.320
Or at least it's familiar to you in your vicinity if not in direct contact.

00:47:23.320 --> 00:47:25.760
It's a bit different, I think, in Amazon.

00:47:25.760 --> 00:47:29.280
There's a thing called NIH, not invented here.

00:47:29.280 --> 00:47:40.079
It's almost like a negative thing right now because Amazon would almost never go by some off-the-shelf thing or pay hundreds of thousands of dollars.

00:47:40.079 --> 00:47:45.440
They would instead like take two years to kind of figure it out and build it internally.

00:47:45.440 --> 00:47:48.679
And eventually they'll release it as a AWS product.

00:47:48.679 --> 00:47:50.760
But that's for like, infrastructure products, right?

00:47:50.760 --> 00:47:59.039
But things like the use exchange for Microsoft, the use Slack, oh, I'm pretty sure some, you know, conqueror for expenses.

00:47:59.039 --> 00:48:01.119
All that kind of non-core business stuff.

00:48:01.119 --> 00:48:05.480
And I'm pretty sure like this Slack contract is probably an emilians, given this scale of Amazon.

00:48:05.480 --> 00:48:12.880
I think Amazon is slacks if I remember the biggest installation because think about the number or employees Amazon has.

00:48:12.880 --> 00:48:14.440
I don't think there's any other.

00:48:14.440 --> 00:48:17.079
I'm pretty sure Amazon is a large, just imploring.

00:48:17.079 --> 00:48:18.360
Wouldn't be surprised, yeah.

00:48:18.360 --> 00:48:21.000
Well, Microsoft will come close, but they would use Teams.

00:48:21.000 --> 00:48:24.000
Yeah. I think it's about positioning, I think, is very interesting.

00:48:24.000 --> 00:48:29.199
My larger team at Google had this experience where they were selling Cloud Run, which is a container of the service.

00:48:29.199 --> 00:48:33.440
And they would come to customers and customers would be like, is it like AWS Lambda?

00:48:33.440 --> 00:48:35.119
Or is it like AWS Fargate?

00:48:35.119 --> 00:48:37.960
And the team would be like, it's neither.

00:48:37.960 --> 00:48:41.079
And then the customers would be like, it's just hard to explain.

00:48:41.079 --> 00:48:48.679
If there is a box in their architecture and just say, okay, so you just unplug that thing, plug our thing instead, it's just so much easier.

00:48:48.679 --> 00:48:54.079
But then if you say like, oh, you unplug half of that thing, one third of that thing, and also half of that thing.

00:48:54.079 --> 00:48:58.000
And then you like rewire the whole thing, it just becomes a much harder self.

00:48:58.000 --> 00:49:01.719
Too much changes for companies to take in all at once, yeah.

00:49:01.719 --> 00:49:08.199
I actually wouldn't be able to tell you the difference between Lambda and Fargate itself, even though I've used both of those.

00:49:08.199 --> 00:49:12.599
Because I think a lot of those AWS products and this is not disparaging, I think.

00:49:12.599 --> 00:49:16.920
They have, at the surface level, fairly subtle differences.

00:49:16.920 --> 00:49:20.159
You could lump them in roughly the same category.

00:49:20.159 --> 00:49:24.320
But like when you dig in, oh, okay, actually, this is a pass, but it's not localized.

00:49:24.320 --> 00:49:28.599
Or this is a pass, but it's not on Kubernetes or whatever, right, like that kind of thing.

00:49:28.599 --> 00:49:31.920
But it's still in the rough category of that, but it's slightly different.

00:49:31.920 --> 00:49:35.039
This is serverless, but still for deployment, really.

00:49:35.039 --> 00:49:40.519
It gets harder to remember the subtle changes that these products have.

00:49:40.519 --> 00:49:44.599
I feel like there's one more on AWS that does this thing.

00:49:44.599 --> 00:49:47.440
That's not Fargate and that's not Lambda.

00:49:47.440 --> 00:49:49.960
It's like Heroku, but on AWS.

00:49:49.960 --> 00:49:53.639
Oh, yeah, open chef.

00:49:53.639 --> 00:49:57.278
The team in Germany that ran it, oops, works.

00:49:57.278 --> 00:49:58.239
Oops, that's correct.

00:49:58.239 --> 00:50:01.759
Yeah, there's actually another one, which we don't need to get into.

00:50:01.759 --> 00:50:04.440
But I think there's a few of those out there.

00:50:04.440 --> 00:50:09.119
I think what tends to happen in AWS is also, teams are very independent.

00:50:09.119 --> 00:50:13.358
So initially Lambda and Fargate were very different products.

00:50:13.358 --> 00:50:20.878
But over the years, as they grow and get bigger, Lambda is introducing ways for you to bring your own containers and stuff.

00:50:20.880 --> 00:50:24.559
And Fargate is getting closer and closer to the serverless thing.

00:50:24.559 --> 00:50:29.800
So I think if you were to start today, there's like, yeah, they're almost very similar things.

00:50:29.800 --> 00:50:31.599
There are differences, but yeah.

00:50:31.599 --> 00:50:33.599
And Google is like in the typical Google factions.

00:50:33.599 --> 00:50:35.360
You all doing serverless wrong.

00:50:35.360 --> 00:50:36.199
Here's called run.

00:50:36.199 --> 00:50:37.039
So yeah.

00:50:37.039 --> 00:50:41.800
Yeah. This is the best way to run this.

00:50:41.800 --> 00:50:53.599
That's actually in one of our positioning conversations, which we may perhaps revive when our shot, we used to call ourselves like a Heroku for mobile, which doesn't really land that well.

00:50:53.599 --> 00:50:56.000
We call it a word cell of mobile.

00:50:56.000 --> 00:50:56.519
I'm sorry.

00:50:56.519 --> 00:50:57.320
That's what we used to call it.

00:50:57.320 --> 00:50:58.480
Similar things.

00:50:58.480 --> 00:51:00.679
My personality was circle siya of mobile.

00:51:00.679 --> 00:51:01.519
Yeah, that's correct.

00:51:01.519 --> 00:51:06.639
Yeah. So how did you like during the long build process, right?

00:51:06.639 --> 00:51:11.039
And you're starting to get your first enterprise customers now.

00:51:11.039 --> 00:51:12.920
How did you fund yourself?

00:51:12.920 --> 00:51:13.880
And where are you?

00:51:13.880 --> 00:51:16.199
What are you trying to do with raising funds?

00:51:16.199 --> 00:51:18.320
And what's the next step?

00:51:18.320 --> 00:51:22.440
So I raised right before I actually joined.

00:51:22.440 --> 00:51:25.039
I actually not I had a couple of months before that.

00:51:25.039 --> 00:51:28.519
I joined this accelerator program called on deck.

00:51:28.519 --> 00:51:31.360
They have a very cool founder fellowship.

00:51:31.360 --> 00:51:32.719
It's called on deck founder fellowship.

00:51:32.719 --> 00:51:36.800
It's like a eight week or 12 week long fellowship program for founders.

00:51:36.800 --> 00:51:44.199
They basically have programming around getting founders into groups like discussing stuff and like sharing their problems, et cetera, et cetera.

00:51:44.199 --> 00:51:48.880
It's almost like every month's group terrapizing each other, all these founders.

00:51:48.880 --> 00:51:54.759
And it is everyone who usually joins the on deck founder fellowship program, they're all very earned.

00:51:54.759 --> 00:51:57.559
So they're all usually at an idea stage.

00:51:57.559 --> 00:52:03.679
So that experience of me was super fun because I got to talk to all sorts of people who had all sorts of ideas.

00:52:03.679 --> 00:52:09.880
And they were all very excited about these ideas, but they had no idea what to do or like how to build this into a business.

00:52:09.880 --> 00:52:12.159
But they all were excited about this thing.

00:52:12.159 --> 00:52:14.798
And so that was very useful for me personally.

00:52:14.800 --> 00:52:23.760
And coincidentally, the on deck program also that year offered some founders the option to raise money from them.

00:52:23.760 --> 00:52:25.199
So that was that pre-seed round.

00:52:25.199 --> 00:52:26.760
So I did the program.

00:52:26.760 --> 00:52:31.239
I agreed to take on their pre-seed thing, which is $125,000.

00:52:31.239 --> 00:52:34.599
And that's the raise that in July last year.

00:52:34.599 --> 00:52:37.719
For what percentage of equity?

00:52:37.719 --> 00:52:41.559
It was standard 125K, some percent, pretty standard thing.

00:52:41.559 --> 00:52:45.519
OK, so like the Y-combinator or the standard deal thing?

00:52:45.519 --> 00:52:48.400
Yeah, like the older Y-combinator thing, basically.

00:52:48.400 --> 00:52:53.159
And right after that, actually, it's been taken to break for a bit and it came back.

00:52:53.159 --> 00:52:56.639
And he joined up full time as this thing.

00:52:56.639 --> 00:53:00.400
And then joined us in January, yeah, early January.

00:53:00.400 --> 00:53:10.519
So we're very careful about how we use the money, where aware that we have taken venture funding, even if it's low friction gap, it's accelerated money.

00:53:10.519 --> 00:53:12.159
So it's a little of friction.

00:53:12.159 --> 00:53:25.759
But we are aware of the fact that if we get on to the way that the valley likes to call it the VC train, then it kind of forces you to go in a certain direction at a certain pace in a certain time.

00:53:25.759 --> 00:53:27.280
Towards a certain goal?

00:53:27.280 --> 00:53:29.079
Yeah, exactly towards a certain goal.

00:53:29.079 --> 00:53:30.360
And both of you know this very well.

00:53:30.360 --> 00:53:33.159
You've been talking about the senior podcast over and over.

00:53:33.159 --> 00:53:36.880
And I don't think that venture capital is a bad idea.

00:53:36.880 --> 00:53:44.719
I think that the way Silicon Valley has done when you're capital over the past 10, 20 years or whatever, post 2008 perhaps, I don't know.

00:53:44.719 --> 00:53:52.159
That has taken a lot of what could have become sustainable businesses and made them become unfortunately unsustainable, right?

00:53:52.159 --> 00:54:00.079
Because once you've taken 10, 20 million dollars in funding, at that point, you have to become like a multi-hundred million dollar business.

00:54:00.079 --> 00:54:08.878
When so many of those businesses could have been very well run, 20 million dollar smaller businesses with a small team and they would already very happy.

00:54:08.880 --> 00:54:10.159
The founders would be happy.

00:54:10.159 --> 00:54:12.000
The early angels would be happy.

00:54:12.000 --> 00:54:13.000
The early investors.

00:54:13.000 --> 00:54:19.679
So I'm not against venture capital, but I think the slow and cheap capital, like slow VC mode is the way to do this.

00:54:19.679 --> 00:54:25.719
Some of those businesses would not have been able to actually reach that point of sustainability without the funding.

00:54:25.719 --> 00:54:27.719
But some of those could have.

00:54:27.719 --> 00:54:32.920
But they instead chose to take the money and then they basically shackled themselves into.

00:54:32.920 --> 00:54:39.278
Some of those the ones that could have ended up in the hype cycle anyway, where they could have avoided it, perhaps.

00:54:39.278 --> 00:54:41.440
So we're cautious about that, the three of us.

00:54:41.440 --> 00:54:44.119
Yeah, we want slow living, slow VC mode.

00:54:44.119 --> 00:54:45.559
What is slow VC?

00:54:45.559 --> 00:54:47.599
I mean, that is basically what I said.

00:54:47.599 --> 00:54:49.400
Like I'm not against the idea of venture capital.

00:54:49.400 --> 00:54:52.000
I don't think the three of us are against the idea of venture capital.

00:54:52.000 --> 00:55:00.119
It's just that be very, very, very mindful that you're taking somebody else's money, which means that the only reason they're giving you this money is because they want to make more money off.

00:55:00.119 --> 00:55:00.960
Then that's not right.

00:55:00.960 --> 00:55:01.480
Exactly.

00:55:01.480 --> 00:55:04.480
So you want to be very mindful of what that X is.

00:55:04.480 --> 00:55:11.360
If you end up taking 20 million dollars when you barely have anything, how are you going to return to 200 million dollars?

00:55:11.360 --> 00:55:13.639
Like you're going to make it somebody else's problem at some point.

00:55:13.639 --> 00:55:16.320
You're going to be like, oh, that's been six years doing this.

00:55:16.320 --> 00:55:17.519
I'm going to make somebody else see you.

00:55:17.519 --> 00:55:19.159
I'm going to leave figures.

00:55:19.159 --> 00:55:26.079
And we've seen this over and over again, every month, how can you somebody will write a story that this destroyed my business?

00:55:26.079 --> 00:55:27.719
I could have done this differently.

00:55:27.719 --> 00:55:37.199
Anyway, at the moment we're raising around, we like to think of it as a bridge, kind of like a middle ground between before we get to the point where we decide if we want to raise seed.

00:55:37.199 --> 00:55:43.679
We're very consciously avoiding venture capital, like basically avoiding VC funds in this round.

00:55:43.679 --> 00:55:46.318
And we're only raising from angels.

00:55:46.318 --> 00:55:49.719
So are you like looking for smaller angels?

00:55:49.719 --> 00:55:50.119
OK.

00:55:50.119 --> 00:56:00.358
Yes. Only from angels, engineering leaders, leaders who have experience in DevOps platforms, or people who've spent a lot of time at very large mobile first companies.

00:56:00.358 --> 00:56:04.838
So some of those, a lot of the angels right now, people who have experiences like that.

00:56:04.840 --> 00:56:07.079
And so of course, they're also looking for a return.

00:56:07.079 --> 00:56:09.079
I mean, I'm not saying they're not looking for money.

00:56:09.079 --> 00:56:11.599
But their individual capital is very limited.

00:56:11.599 --> 00:56:17.119
And the reason that they're investing in us is because they, either they really enjoy us as a team.

00:56:17.119 --> 00:56:21.639
So they know, as personally, and they just want to support someone who they know is doing something.

00:56:21.639 --> 00:56:24.199
Or they truly believe that this problem is real.

00:56:24.199 --> 00:56:26.559
And they want to try and help us.

00:56:26.559 --> 00:56:32.199
Or if some of our angels have been very, very proactive about offering support that closes round out.

00:56:32.199 --> 00:56:34.918
And then let's talk late October or November.

00:56:34.918 --> 00:56:39.519
And I want to understand how I can help you shape your US GTM, for example.

00:56:39.519 --> 00:56:40.438
And that helps.

00:56:40.438 --> 00:56:42.159
That's the kind of support that you want.

00:56:42.159 --> 00:56:43.000
It's very specific.

00:56:43.000 --> 00:56:45.159
It's very focused because these angels are unscended.

00:56:45.159 --> 00:56:46.798
I'll do this, this, this, this.

00:56:46.798 --> 00:56:49.318
I've done this for 10 years really well.

00:56:49.318 --> 00:56:51.239
And I can help you do this thing really well.

00:56:51.239 --> 00:56:52.559
And I really like what you do.

00:56:52.559 --> 00:56:53.798
It's nice.

00:56:53.798 --> 00:56:57.759
So how are you going about finding these angels?

00:56:57.759 --> 00:57:01.039
Is it the same robust, what did I say earlier?

00:57:01.039 --> 00:57:03.639
Like leveraging your robust network of?

00:57:03.639 --> 00:57:04.159
Correct.

00:57:04.159 --> 00:57:12.759
I'm leveraging by a robust network of professional connections and then asking them to leverage their more robust networks.

00:57:12.759 --> 00:57:16.400
So you're like directly reaching out to people one on one.

00:57:16.400 --> 00:57:20.000
And are you looking at angel networks and things like that?

00:57:20.000 --> 00:57:24.400
Or you're doing like literally one to one reaching out to people?

00:57:24.400 --> 00:57:27.480
I have looked at some engine networks where I knew an engine personally.

00:57:27.480 --> 00:57:28.679
So some of those have happened.

00:57:28.679 --> 00:57:33.398
The first set of like, I think 50 people, like 30 people that are each are two.

00:57:33.398 --> 00:57:35.440
I knew everyone personally.

00:57:35.440 --> 00:57:40.440
And then they, they're some of them who agreed and then some of them who didn't agree because of whatever reason.

00:57:40.440 --> 00:57:42.639
They ended up connecting us to other people.

00:57:42.639 --> 00:57:44.719
And now this happens on a daily basis.

00:57:44.719 --> 00:57:47.000
And daily basis, somebody will say, yes or no. And they're like, you know what?

00:57:47.000 --> 00:57:48.278
You should also talk to this person.

00:57:48.278 --> 00:57:50.599
And this person, this person is really good at this.

00:57:50.599 --> 00:57:52.960
What are the months I'm talking about this stage?

00:57:52.960 --> 00:57:54.039
Like third person.

00:57:54.039 --> 00:57:55.639
Par angel.

00:57:55.639 --> 00:58:08.960
It's like 10 to 50 K. It's usually the jacks I say 10 to 50 K. But you're also not just looking for that, but you're looking for people who are established in this space who can advise you on it.

00:58:08.960 --> 00:58:10.119
Yeah, some align me.

00:58:10.119 --> 00:58:10.960
Correct.

00:58:10.960 --> 00:58:11.798
I'm wrong.

00:58:11.798 --> 00:58:13.599
I don't think we're spoken to anyone like completely.

00:58:13.599 --> 00:58:17.838
Yeah, that's the, I guess, the value of going through the robust network.

00:58:17.838 --> 00:58:22.079
I mean, you'll end up finding folks who've kind of done this.

00:58:22.079 --> 00:58:32.918
And I think the folks who haven't generally just tend to kind of say, no, anyway, or like they're too far away from the problem, they'll be like, I can't form a thesis on this or whatever.

00:58:32.918 --> 00:58:35.199
I can perhaps connect you to folks who have.

00:58:35.199 --> 00:58:37.039
And then that's how the network grows.

00:58:37.039 --> 00:58:38.559
It kind of just end up it is.

00:58:38.559 --> 00:58:41.239
It ends up, it's not that we're actively looking out for the folks.

00:58:41.239 --> 00:58:44.599
It's just by design, it happens to be that way.

00:58:44.599 --> 00:58:47.159
How does structurally devol the paperwork?

00:58:47.159 --> 00:58:49.119
By the way, where are you guys incorporating this?

00:58:49.119 --> 00:58:49.639
At the beginning?

00:58:49.639 --> 00:58:51.958
Oh, it's Delaware. Where are Delaware's you call?

00:58:51.958 --> 00:58:54.639
And this is, this round is an angelist, RUV.

00:58:54.639 --> 00:58:58.278
It's a roller vehicle, which is a really fun product that angelist has.

00:58:58.278 --> 00:59:02.559
If you're not aware of it, RUV is still a safe note, like you're raising on a safe note.

00:59:02.559 --> 00:59:06.400
But what it does is angelist will create a special purpose vehicle.

00:59:06.400 --> 00:59:13.039
And everyone who invests money, they all become founders or whatever shareholders in that SPV.

00:59:13.039 --> 00:59:18.480
And then that SPV itself, that roller vehicle itself, is just one line item on your captivity.

00:59:18.480 --> 00:59:23.679
So it maintains a very clean, captivity instead of having all of these people who have little, little, little, little amounts.

00:59:23.679 --> 00:59:26.918
So investing in an RUV itself is also super easy.

00:59:26.918 --> 00:59:30.318
Like, angelist has really made the process butter smooth.

00:59:30.318 --> 00:59:33.639
And that's what we're raising using an angelist RUV.

00:59:33.639 --> 00:59:38.199
So basically, if you find the friend, then you just send them to angelist to put them on you there.

00:59:38.199 --> 00:59:39.639
Yes, yeah, we just send them a link.

00:59:39.639 --> 00:59:41.480
And angelist just guide them through the process.

00:59:41.480 --> 00:59:49.719
Angelist will give them all the details in it, because I've given them details of our previous round and all of that and are linked to the tech and like risks and this close and standard stuff.

00:59:49.719 --> 00:59:52.318
But it's a very neat platform.

00:59:52.320 --> 00:59:54.800
And how about like board seats and all that?

00:59:54.800 --> 00:59:56.400
None of that exists in an RUV.

00:59:56.400 --> 00:59:58.000
It's none of that matters.

00:59:58.000 --> 01:00:01.280
That's what happened when you end up taking a direct investment.

01:00:01.280 --> 01:00:02.760
Get to VC.

01:00:02.760 --> 01:00:10.320
Yeah, even a microphone which you'll want to cut like a 100k check, like a 200k check, they will start to make a little little noises about that.

01:00:10.320 --> 01:00:14.800
You know, like we want preferential shares or like we want to have what like, can we change this, amend this thing?

01:00:14.800 --> 01:00:21.079
When an RUV, when they're angels, it's literally a duplicate of the by-combinators they've document on by-combinator.com.

01:00:21.079 --> 01:00:22.960
They're like, I know that it doesn't matter.

01:00:22.960 --> 01:00:28.759
And it's at the same percentage, the same kind of deal percentage is based on the amount that they're putting in.

01:00:28.759 --> 01:00:31.759
Yes. And what are you planning to do?

01:00:31.759 --> 01:00:33.519
Like what's the future for a timeline?

01:00:33.519 --> 01:00:36.239
What are you planning to do with these funds?

01:00:36.239 --> 01:00:44.480
I mean, we have a whole bunch of experiments that lined up, some are experiments, some are where mostly convinced our features worth building.

01:00:44.480 --> 01:00:57.559
There is obviously the default catchup that Tramline has to play, which is to be open for as many people as possible, which is trying more integrations in on a consistent basis as people need them.

01:00:57.559 --> 01:01:04.039
So we have a certain lot today, but a few other client would come around tomorrow and they will need to certain other lot of integrations.

01:01:04.039 --> 01:01:06.480
So that process is forever ongoing.

01:01:06.480 --> 01:01:16.960
Obviously it'll reach point of closure when the most important ones have reached our system because there's only so much diversity in the integrations that we play with.

01:01:16.960 --> 01:01:22.639
So perhaps it's like a couple, and now it might become like six in the next year or so.

01:01:22.639 --> 01:01:24.559
That's about it, it'll probably stop there.

01:01:24.559 --> 01:01:38.639
This is sort of a thing that Tramline is inherently has as a platform, which is integrations, but there's of course a lot of other stuff that it can do to make it more Ruby on Railsesque if we wanna call it like that.

01:01:38.639 --> 01:01:42.960
There is of course the part where we build your apps as well.

01:01:42.960 --> 01:01:45.880
And I think now we've also spoken about this before.

01:01:45.880 --> 01:01:57.320
So to be clear right now when you use Tramline, it's basically the runbook for building and deploying and releasing your app, but the actual build is happening somewhere else.

01:01:57.320 --> 01:02:03.880
Like in GitHub or in our case, we use bitrises for actually building it in a container.

01:02:03.880 --> 01:02:16.079
So you want to provide like a mechanism which will make it even smoother, I think the UX, because as we were figuring out there's so many moving parts, certificates and all that to pass around.

01:02:16.079 --> 01:02:19.079
There is a level after which you can't really do anything.

01:02:19.079 --> 01:02:28.480
Again, the platform sort of is at the end of the day first shipping mobile apps to the stores from the Googles and the apples.

01:02:28.480 --> 01:02:32.759
So you have to abide by their rules and you have to abide by their APIs.

01:02:32.759 --> 01:02:45.318
So we're restricted by that, but definitely having a lot of those baked into the platform is a huge load of people's tests, like trying to integrate stuff in other places and then integrating Mac here.

01:02:45.318 --> 01:02:47.639
It's a much simpler experience overall.

01:02:47.639 --> 01:02:53.398
That's kind of like the distribution or the building part of things, the CI CD part of things, let's call it.

01:02:53.398 --> 01:02:55.119
Yeah, a bunch of stuff on sales.

01:02:55.119 --> 01:03:00.079
One of our big plans is also to actively start focusing on the US and Europe market.

01:03:00.079 --> 01:03:13.239
Right now it's a focus, obviously because of the geography we're based in, has been India, Southeast Asia, but also with this race, we're going to actively start looking at North America and Europe as well.

01:03:14.119 --> 01:03:28.480
And I think finally we'll try to wrap it up quickly, but it would be a crime to let you all go without talking about like the dev agency stuff because all three of you worked in some of the best boutique consulting dev agencies in India.

01:03:28.480 --> 01:03:31.960
Tell us a bit about how that goes.

01:03:31.960 --> 01:03:36.440
Where do you see startups looking to use their agencies?

01:03:36.440 --> 01:03:39.039
How do they go about selecting them and all that?

01:03:39.039 --> 01:03:54.400
This is really funny because I think once or once a week somebody asks me this, still it's been two and a half years after moving out of an agency business, I am still approached once a week by somebody that, hey, I have this idea and I want to build this app which will do this and that and that.

01:03:54.400 --> 01:03:55.480
So what should I do?

01:03:55.480 --> 01:03:56.800
Who should I talk to?

01:03:56.800 --> 01:04:03.480
And it's an issue because most people don't really have the kind of budgets to afford a good agency.

01:04:03.480 --> 01:04:08.519
And in a good agency in India, even in India, will cost you $60 in our minimum.

01:04:08.519 --> 01:04:11.599
And like, of course, going up to lip probably 100.

01:04:11.599 --> 01:04:16.480
And the vast majority of the people don't know how to even find these agencies.

01:04:16.480 --> 01:04:24.679
I think that's a very big challenge because these agencies are getting the work from word of mouth so they don't bother much advertising themselves anyway.

01:04:24.679 --> 01:04:38.559
So the bigger challenge that I see with startups is how do you sift through their $20 in our work or the $30 in our work, which is almost all of the work that you can call one of the kind of agencies that you see and figure out who to pick there.

01:04:38.559 --> 01:04:39.480
That is what it's like.

01:04:39.480 --> 01:04:45.280
I've actually helped a couple of folks who have met and like friends who are doing something new in helping them do this.

01:04:45.280 --> 01:04:59.280
And usually I tell them that if you like the leadership team, if you think that the founders or the team that is running, the team that you're working with, like the leads or whoever is running this team, if you like them and if you think they like your idea, at least that should be okay.

01:04:59.280 --> 01:05:03.960
But if you think that when you're talking to them and they're like, yeah, whatever, we'll build everything.

01:05:03.960 --> 01:05:05.679
You want to say, yeah, absolutely.

01:05:05.679 --> 01:05:08.679
That at that point, I see that as a very big red flag.

01:05:08.679 --> 01:05:13.878
Like you want a mass market agency at a low price point, you want them to care.

01:05:13.878 --> 01:05:17.599
And you know you're not going to get the best work and they know they don't can't produce best work.

01:05:17.599 --> 01:05:18.440
That's fine.

01:05:18.440 --> 01:05:19.278
Everyone already knows that.

01:05:19.278 --> 01:05:20.519
No one needs to speak that out loud.

01:05:20.519 --> 01:05:29.559
My advice to most people is that if you meet someone, if you meet an agency where you felt like this person I was talking to, this team lead, they cared about kind of cared about what I was building.

01:05:29.559 --> 01:05:30.599
I think that's good enough.

01:05:30.599 --> 01:05:31.440
Just stay.

01:05:31.440 --> 01:05:32.199
Go ahead.

01:05:32.199 --> 01:05:35.480
What kind of projects do you think it works really well in?

01:05:35.480 --> 01:05:38.320
Would you say this is for design?

01:05:38.320 --> 01:05:40.760
Essentially you're outsourcing some parts of it, right?

01:05:40.760 --> 01:05:44.000
Like how about developing your core application itself?

01:05:44.000 --> 01:05:45.400
Is that something?

01:05:45.400 --> 01:05:47.800
I mean, that is something that we have done.

01:05:47.800 --> 01:05:48.920
All three of us have done, right?

01:05:48.920 --> 01:05:54.079
Building someone else's core, whether that was backend or front end, core business application.

01:05:54.079 --> 01:05:58.880
And you get a consultancy usually or you get someone with an expertise.

01:05:58.880 --> 01:06:01.079
They don't just build this thing for you.

01:06:01.079 --> 01:06:02.719
That's how we have usually done.

01:06:02.719 --> 01:06:11.960
They'll teach people in your team and they'll mentor people in your team on how to build good software and how to build a scale, a software at this level.

01:06:11.960 --> 01:06:14.838
And that's what you wanna look for a little bit.

01:06:14.838 --> 01:06:23.639
Not just someone who will come, build this and just leave, but also someone who will come, mentor your team and who will build your team a little bit for you.

01:06:23.639 --> 01:06:25.599
Because yes, there won't be around forever.

01:06:25.599 --> 01:06:26.440
That's a thing.

01:06:26.440 --> 01:06:29.278
Both obviously in the lens, I did like one year, two year contracts.

01:06:29.278 --> 01:06:31.480
It was not a three months contract ever.

01:06:31.480 --> 01:06:32.798
They were all long term contracts.

01:06:32.800 --> 01:06:38.440
But what the most of the time spent there was not just building the product, but also building the team.

01:06:38.440 --> 01:06:52.360
I remember from early days at Gojek, the entire lens or team helped build their closure expertise, which was basically the central allocation service that did allocating of drivers to all their bookings.

01:06:52.360 --> 01:06:54.400
Like there was one central service that did that.

01:06:54.400 --> 01:06:58.960
That was written in closure and we didn't just build the service, but build the entire team around it.

01:06:58.960 --> 01:07:04.199
And now the team grew into like a 30% person team and like still going strong.

01:07:04.199 --> 01:07:06.719
So that is kind of what you would want to look for.

01:07:06.719 --> 01:07:08.840
It is not about solving one particular problem.

01:07:08.840 --> 01:07:12.639
Like you won't probably get someone to solve because you are the domain experts.

01:07:12.639 --> 01:07:15.639
You won't actually get someone to solve a particular domain problem.

01:07:15.639 --> 01:07:17.400
As a customer, you are the domain experts.

01:07:17.400 --> 01:07:21.239
You won't find like someone comes all this logistics problem for me.

01:07:21.239 --> 01:07:24.320
You have to gain your own expertise in that domain.

01:07:24.320 --> 01:07:32.679
What you would get, but is people who know how to build and scale software at the scale that you are at and help your team?

01:07:32.679 --> 01:07:37.920
Because most of these startups, most of these companies, even if they're not startups, they have a very young team.

01:07:37.920 --> 01:07:41.039
And it's hard for them to hire senior engineers.

01:07:41.039 --> 01:07:49.360
That's actually one of the big reasons why a lot of the times, at least Nilla and Sogot hired, just to get experience talent in play.

01:07:49.360 --> 01:07:51.360
Boots trapping their own companies.

01:07:51.360 --> 01:07:53.239
Boots trapping their own, yeah, pretty much.

01:07:53.239 --> 01:07:59.519
Because a lot of these companies kind of hire en masse and punch junior folks at the same time.

01:07:59.519 --> 01:08:00.599
Now what do you do with them?

01:08:00.599 --> 01:08:11.039
You don't have enough people to train them or not just train in sort of like a boot campy way, but like show them the ways of how a product is developed or like an engineering artifact is shipped.

01:08:11.039 --> 01:08:14.719
But again, I think the bare minimum qualities actually just track record.

01:08:14.719 --> 01:08:17.519
It's as simple as that, as with anything, right?

01:08:17.519 --> 01:08:20.880
If you've done this before, you're probably gonna be good.

01:08:20.880 --> 01:08:23.640
If you've done this before well, and that's not very hard to find out.

01:08:23.640 --> 01:08:37.439
Of course, as Prattal said, like we've never really marketed ourselves, because we've never needed to, because the demand has always been in surplus against what we can actually supply to the folks coming into us.

01:08:37.439 --> 01:08:39.880
A lot of the time it was about rejection and not.

01:08:39.880 --> 01:08:42.119
Yeah, it was about, they want to hire someone.

01:08:42.119 --> 01:08:44.239
Is there a team willing to get someone in?

01:08:44.239 --> 01:08:50.640
Is not just the CTO who's deciding that they need an expertise, but is the team actually willing to like make the change?

01:08:50.640 --> 01:08:59.960
Because one person deciding, or maybe even if it is a leader deciding that the engineering process or the engineering culture needs to change doesn't really affect it.

01:08:59.960 --> 01:09:01.840
Unless the team is involved.

01:09:01.840 --> 01:09:12.199
There is a very similar conversation that I was having with another friend of mine recently, and we were just talking about, I don't know if this was true a decade ago, roughly when we all started.

01:09:12.199 --> 01:09:28.800
It's just perhaps more so true before that, but what we've realized lately is that there is definitely a shortage of agencies lately who perform sort of very high level in areas that are hard to do.

01:09:28.800 --> 01:09:32.680
So a lot of sort of like this low latency, high throughput work.

01:09:32.680 --> 01:09:34.800
Those are hard computer science problems.

01:09:34.800 --> 01:09:35.680
Data pipelines.

01:09:35.680 --> 01:09:36.840
Data pipeline work.

01:09:36.840 --> 01:09:40.119
Large swaths of data handling, stuff like that.

01:09:40.119 --> 01:09:53.680
There's very few folks, at least from CarPurview, I might be wrong on this and I don't have enough data on this, but just looking back 10 years, the folks who are around looking at folks around now, I see a general lack of this.

01:09:53.680 --> 01:09:58.359
And perhaps that's because it is a talent that requires more skill in hands.

01:09:58.359 --> 01:10:07.880
It's harder to do, but I also think a lot of those folks who could have done this have just been swept up by the fangs of the world and the big companies of the world.

01:10:07.880 --> 01:10:09.599
Or they just get tired of this.

01:10:09.599 --> 01:10:11.159
Also that, yeah.

01:10:11.159 --> 01:10:12.439
Or they just retire.

01:10:12.439 --> 01:10:14.079
They also retire, yeah.

01:10:14.079 --> 01:10:17.519
I don't know if it's sad, but it's an opportunity if anything.

01:10:17.519 --> 01:10:24.439
But of course you have to buy into that sort of business building, which is kind of linear.

01:10:24.439 --> 01:10:25.759
And slow.

01:10:25.759 --> 01:10:27.079
Take time.

01:10:27.079 --> 01:10:33.439
Okay. So I think we're well over what we had initially told you will record for.

01:10:33.439 --> 01:10:35.600
So let's wrap this up.

01:10:35.600 --> 01:10:41.479
What's a book or a podcast that you're listening to recently or something you would recommend?

01:10:41.479 --> 01:10:43.880
Very weirdly, I just finished reading this.

01:10:43.880 --> 01:10:45.239
It's all top of mind.

01:10:45.239 --> 01:10:47.680
I have a terrible fear of flying.

01:10:47.680 --> 01:10:56.680
My fear of flying is so bad that I recently made a trip to Rajee and I fainted on the way down and then I had to take a train back.

01:10:56.680 --> 01:10:57.520
I was so bad.

01:10:57.520 --> 01:11:03.159
I remember because you and I were going to meet for something and then you said, I'm sorry I can't meet today.

01:11:03.159 --> 01:11:04.560
I was like, that's totally cool.

01:11:04.560 --> 01:11:10.680
And then later on, I'm talking to you like I fainted on the flight and I'm stuck in a ranch.

01:11:10.680 --> 01:11:11.520
It was not great.

01:11:11.520 --> 01:11:14.119
I mean, yeah, I've tried a bunch of things that doesn't work.

01:11:14.119 --> 01:11:19.319
It's been really not eye opening because I think these arguments that people make about flying.

01:11:19.319 --> 01:11:21.079
I know them all factually, right?

01:11:21.079 --> 01:11:22.760
Like it's all obvious.

01:11:22.760 --> 01:11:24.760
But it's just a lens in which was presented.

01:11:24.760 --> 01:11:32.479
This is a book called The Easy Way of Flying by the guy who wrote the book to quit smoking, which is Alan Carr.

01:11:32.479 --> 01:11:43.039
It's quite a popular book at this point, but I think the flying book is in that popular because I FOF isn't that big of an affliction as the grid smoking is.

01:11:43.039 --> 01:11:53.880
That book has a fantastic lens that as you're about to read it, feels like it's easily challengeable by the person who is already afraid of flying.

01:11:53.880 --> 01:11:57.199
But by the end of it, it's impossible to challenge it.

01:11:57.199 --> 01:12:00.239
So that lens shift was quite fascinating to me.

01:12:00.239 --> 01:12:02.159
And it helped, I think, quite a lot.

01:12:02.159 --> 01:12:04.000
When are you taking your next flight?

01:12:04.000 --> 01:12:05.640
I'm taking it very soon.

01:12:05.640 --> 01:12:06.760
And I'm all ready for it.

01:12:06.760 --> 01:12:09.760
So I get afraid like weeks in advance, right?

01:12:09.760 --> 01:12:11.359
And not this time.

01:12:11.359 --> 01:12:14.239
Good luck to that next flight, yeah.

01:12:15.279 --> 01:12:17.680
Yeah, need Pratulia, go ahead.

01:12:17.680 --> 01:12:19.279
I have actually not read anything.

01:12:19.279 --> 01:12:24.199
You know, why like what I was reading last was the memory police by forget her name.

01:12:24.199 --> 01:12:26.319
Yoko Okaza, I think.

01:12:26.319 --> 01:12:30.239
Yeah, the famous, I mean, I want to read some Japanese authors.

01:12:30.239 --> 01:12:33.960
And I like sci-fi, so I was reading memory police.

01:12:33.960 --> 01:12:39.319
And I really enjoyed the very almost poetic way of the stories written.

01:12:39.319 --> 01:12:40.960
I really enjoyed that kind.

01:12:40.960 --> 01:12:45.399
It's a very, I'm not going to say Murakami-esque, but it sort of touches that.

01:12:45.399 --> 01:12:49.079
It's not as dark, but yeah, that is what I was reading last.

01:12:49.079 --> 01:12:50.479
And I really enjoyed it.

01:12:50.479 --> 01:12:54.759
And you have been learning Japanese, or both of you have been learning Japanese for a while.

01:12:54.759 --> 01:12:58.159
Well, you follow me on Doolingos, and you know it happens very often.

01:12:58.159 --> 01:13:01.439
Yeah. Well, I don't know what language you do.

01:13:01.439 --> 01:13:04.359
I just see progress updates and all, yeah.

01:13:04.359 --> 01:13:08.000
I mean, we haven't officially cleared the N5.

01:13:08.000 --> 01:13:10.359
There's like a leveling system in Japanese.

01:13:10.359 --> 01:13:12.918
But I think we're roughly around that level.

01:13:12.918 --> 01:13:18.000
You'll be like ready to fly to Japan, and no Japanese at the same time.

01:13:18.000 --> 01:13:23.279
I think we can buy bread and milk pretty easily, and rent a flat out here.

01:13:23.279 --> 01:13:23.960
I mean, you're done.

01:13:23.960 --> 01:13:25.560
That's all we need.

01:13:25.560 --> 01:13:27.119
House and bread and milk.

01:13:27.119 --> 01:13:28.880
And your computer, yeah.

01:13:28.880 --> 01:13:30.800
And internet, of course.

01:13:30.800 --> 01:13:32.560
And yeah, Pratul.

01:13:32.560 --> 01:13:42.119
I've actually been reading this fantastic fiction series called The Locked Tomb by this author called Townsend Murge.

01:13:42.119 --> 01:13:49.599
It's a trilogy, and you know, I mean, I've read a lot of science fiction and fantasy, but this is unlike anything else I've ever read.

01:13:49.599 --> 01:13:51.159
It's incredible.

01:13:51.159 --> 01:13:52.798
It's the front page of the book.

01:13:52.798 --> 01:13:56.719
The blurb just says, let's be in necromancers in space.

01:13:56.719 --> 01:13:57.960
That's it.

01:13:57.960 --> 01:14:00.719
And the book is so incredibly well-drained.

01:14:00.719 --> 01:14:02.759
Like, it is nothing.

01:14:02.759 --> 01:14:08.559
I think this is one of those books that is going to definitely go down as, if you enjoy fantasy, you have to do this.

01:14:08.559 --> 01:14:10.559
It's super, super fun to do.

01:14:10.559 --> 01:14:13.119
I mean, what's finishing the tradition?

01:14:13.119 --> 01:14:16.000
And podcasts, we listen to Barakast.

01:14:16.000 --> 01:14:17.479
Chris, yeah.

01:14:17.479 --> 01:14:18.720
Yeah, actually, that's true.

01:14:18.720 --> 01:14:23.840
I have actually every once in a while on LinkedIn, it'll pop up and I'll go, I have also been listening, yeah.

01:14:23.840 --> 01:14:29.680
I know this is a super popular thing, but I did finally give the Hoobeman Lab a shot.

01:14:29.680 --> 01:14:35.000
And I kind of got it and crossed into it for a while, for many months, actually.

01:14:35.000 --> 01:14:40.239
And I would like, listen through the whole, they're really long and really like almost tiring, right?

01:14:40.239 --> 01:14:42.439
Because it's just, it's just log area, right?

01:14:42.439 --> 01:14:47.880
Like, it's just bunch of words being thrown at you, constantly for four hours.

01:14:47.880 --> 01:14:49.039
It was a bit tiring.

01:14:49.039 --> 01:14:51.640
Also, what's it, no, no, it's important.

01:14:51.640 --> 01:14:53.119
Most of the words you don't know.

01:14:53.119 --> 01:14:55.920
So it's, it's very dense.

01:14:55.920 --> 01:15:08.600
I did read a bunch of criticisms on his techniques in which he parses, because a lot of it is him parsing papers and sort of making them accessible.

01:15:08.600 --> 01:15:15.600
It's basically just a giant, like, I will read 20 white papers this week and I will condense them down into a four hour podcast.

01:15:15.600 --> 01:15:17.720
That's essentially what I think he does.

01:15:17.720 --> 01:15:20.000
It's like papers we love in that case.

01:15:20.000 --> 01:15:21.880
It's paper, paper, we love in podcasts.

01:15:21.880 --> 01:15:23.439
I'm a single person.

01:15:23.439 --> 01:15:34.680
But I've been reading a lot of criticism about how he parses them and there are some discrepancies in the outcomes derived from it.

01:15:34.680 --> 01:15:40.399
So like, I started to hold back a little bit because of those, not that most of what he's doing is that.

01:15:40.399 --> 01:15:43.319
I think there are some holes here and there, which is expected.

01:15:43.319 --> 01:15:48.239
I mean, you can't read a thousand papers in a few months and expect not to have any errors.

01:15:48.239 --> 01:15:52.639
I was consuming that quite intensely for many months, like a lot of it.

01:15:52.639 --> 01:15:53.719
Blue Mibreins out.

01:15:53.719 --> 01:15:57.479
I've only tried one of his episodes where he talks about stuff.

01:15:57.479 --> 01:15:59.639
I think it was something about dopamine.

01:15:59.639 --> 01:16:02.319
After 20 minutes, I'm like, I don't understand.

01:16:02.319 --> 01:16:03.759
I'm just losing track of it.

01:16:03.759 --> 01:16:04.960
It's like just to dense.

01:16:04.960 --> 01:16:06.639
But his interview is actually pretty good.

01:16:06.639 --> 01:16:10.000
Like, his interview with Mark Andreessen was really, really good.

01:16:10.000 --> 01:16:15.479
But Mark Andreessen also, he like, his picks at like, I don't know, I know what the normal rate of species he speaks three times, right?

01:16:15.479 --> 01:16:17.039
It's impossible to parse him.

01:16:17.039 --> 01:16:21.000
I recently just downloaded a book by another person he interviewed.

01:16:21.000 --> 01:16:24.000
His name is Peter R. T. He's like, I think he's a doctor.

01:16:24.000 --> 01:16:28.680
Who just kind of generally talks about, like, muscle building and health type stuff.

01:16:28.680 --> 01:16:31.880
And that interview I found was quite interesting.

01:16:31.880 --> 01:16:39.079
It had a lot of weird correlations that he drew from it, which you wouldn't really draw naturally.

01:16:39.079 --> 01:16:44.800
There is a very strong correlation, for example, between grip strength and longevity.

01:16:44.800 --> 01:16:45.880
It doesn't compute, right?

01:16:45.880 --> 01:16:49.000
When you first hear about it, but it's like good data to back it up.

01:16:49.000 --> 01:16:51.559
So yeah, this stuff like that's interesting.

01:16:51.559 --> 01:16:52.680
Right.

01:16:52.680 --> 01:17:00.199
OK, it was wonderful to have you all finally, like tell us where people can find you and where they can find tram line.

01:17:00.199 --> 01:17:03.680
Twitter and link it and tramline.com.

01:17:03.680 --> 01:17:06.760
What are your handles on Twitter and LinkedIn?

01:17:06.760 --> 01:17:10.119
My handle on Twitter is PRXTL.

01:17:10.119 --> 01:17:11.199
And I'm LinkedIn.

01:17:11.199 --> 01:17:12.000
I'm just fine.

01:17:12.000 --> 01:17:12.800
You can find me back.

01:17:12.800 --> 01:17:13.840
I've already got it.

01:17:13.840 --> 01:17:16.560
Shabnay is actually tramline HQ on Twitter.

01:17:16.560 --> 01:17:18.680
Yeah, I'm mid 90 everywhere.

01:17:18.680 --> 01:17:19.479
I am.

01:17:19.479 --> 01:17:20.960
It's a little hard to pronounce.

01:17:20.960 --> 01:17:22.600
I guess this settle sit now, right?

01:17:22.600 --> 01:17:24.920
My nickname is pronounced as Catalis.

01:17:24.920 --> 01:17:27.840
It's not Catalis or something else.

01:17:27.840 --> 01:17:31.520
It's Catalis. It's K-I-T-A-W-L-L-I-S.

01:17:31.520 --> 01:17:33.880
I'm pretty much that everywhere on the internet.

01:17:33.880 --> 01:17:35.840
What's the origin of that nickname?

01:17:35.840 --> 01:17:37.880
Oh, that's a long, that's another podcast.

01:17:37.880 --> 01:17:39.640
Yeah, it's a podcast episode.

01:17:42.640 --> 01:17:43.279
It's not great.

01:17:43.279 --> 01:17:47.239
It's like 80% cringe and 20% interesting, I think.

01:17:47.239 --> 01:17:51.039
You'll have to take it in 30 seconds.

01:17:51.039 --> 01:17:53.119
We can't live here.

01:17:53.119 --> 01:18:01.119
This opens us up to another, like, an episode hopefully in the future where we start off with this.

01:18:01.119 --> 01:18:02.800
Origin story.

01:18:02.800 --> 01:18:03.640
Great.

01:18:03.640 --> 01:18:05.600
Yeah. It was awesome having you.

01:18:05.600 --> 01:18:06.439
Thanks, folks.