In short
Podcast Episode Summary: Replit CEO Amjad Masad on 1 Billion Developers: A Better End State than AGI?
Episode Overview In this episode, Replit CEO Amjad Masad discusses his vision of empowering one billion software creators and how the rise of AI technologies, particularly large language models (LLMs), is making this vision more attainable. Hosted by David Cahn and Sonya Huang from Sequoia Capital, the episode explores implications for the economy, society, and the nature of work in a future where coding becomes accessible to all.
Key Themes and Discussions
Vision for One Billion Developers
- Dream of Empowerment: Masad's long-held ambition is to enable one billion individuals globally to become software developers.
- Democratization of Coding: He asserts that with the right tools and technologies, coding will no longer be the domain of experts, but accessible to everyone, from young learners to knowledge workers.
The Impact of AI on Development
- AI as a Tool for Creativity: Masad believes that AI will not replace human developers but will augment their capabilities, allowing more people to solve complex problems through software.
- Shift in Workforce Dynamics: As more people become capable developers, traditional organizational structures may evolve from silos to more integrated, collaborative environments where employees can independently solve problems.
Replit's Role in Shaping the Future
- Simplifying Complexity: Replit aims to reduce the barriers to coding, making it easier for non-technical users to create software.
- User-Centric Development: The platform has effectively shifted from a focus on students to professionals, with a growing user base that includes engineers from prominent companies like Netflix.
Broader Economic Implications
- Techification of Industries: Many traditional sectors (e.g., healthcare, education) have yet to be fully integrated with technology. Mass coding abilities can lead to transformative innovation in these areas.
- Wealth Distribution: Masad posits that enabling more developers can lead to a more equitable distribution of wealth, particularly in developing regions.
Management Philosophy
- Hands-On Leadership Style: Masad describes his leadership approach as being involved yet trusting. He maintains high expectations and actively engages with team members to track progress.
- Recruitment for Raw Talent: Emphasizing the importance of diversity and unconventional backgrounds, Masad highlights the value of recruiting individuals with unique perspectives and skills.
Personal Journey
- Background and Motivation: Masad shares his journey from growing up in Jordan to becoming a successful entrepreneur in Silicon Valley, emphasizing the influence of his family and his passion for technology.
- Balancing Work and Personal Life: He discusses the challenges of working with his spouse, highlighting both the benefits and difficulties of intertwining personal and professional relationships.
Key Takeaways
- Empowering Individuals: The vision of one billion developers signifies a shift towards a more inclusive tech landscape where everyone can contribute.
- AI and Human Collaboration: The roles of AI and human creativity will be complementary in the future of software development.
- Cultural Transformation: As coding becomes mainstream, there will be a cultural shift in how organizations operate and innovate.
- Resilience in Leadership: Navigating challenges, both personal and professional, is crucial for sustained success in the tech industry.
Mentioned Works
- On the Naturalness of Software: 2012 paper discussing applying NLP techniques to code.
- Attention Is All You Need: Seminal 2017 paper on the transformer model.
- I Am a Strange Loop: 2007 follow-up to Douglas Hofstadter’s work exploring the nature of consciousness.
- On Lisp: Paul Graham’s 1993 book on the original programming language of AI.
---
This summary encapsulates the significant discussions from the podcast episode, providing insights into the transformative potential of coding and AI as articulated by Amjad Masad, while also reflecting on his personal journey and management philosophy.
Written by AI. May contain mistakes. Listen to the episode to check what was said.
Transcript
Automatic transcript. May contain errors.0:00you know, what is special about humans and what's replicable in the machines and at least in the in the near term. My view is that AI is going to get really good at sort of two things, things that are highly represented in the data and things that you can construct a very good RLN environment for. So what can you construct a great RL environment for? Like obviously with alpha zero games, right? Games are famous for you can you can have these self -play sort of algorithms that develop over time Now with reasoning models You know math is an environment that especially with lean like a code Almost like an expression of math that can be executed that's like a great, you know, RL environment, I think code execution as well, so running the code and then, you know, doing your reinforcement learning on that.
1:05And things that are already represented on GitHub and things like that. But there's a lot of other domains where we actually still don't know how we're gonna make them better. Like new fundamental and new ideas, new knowledge. It's not entirely clear how we're gonna get there, Can you use RL for these more software things? Perhaps you create a world model, you can approximate these things, but I feel like the ideas and the creativity and the sense of coming up with really novel things and understanding the world and very complicated, intractable way. And coming up with an idea that could fundamentally change how things work or change the world, I think will still have to be the domain of the human.
2:11Hello and welcome to Training Data. I'm David Khan and I'll be the guest host on today's episode interviewing Amjad Masad, the founder and CEO of Repplet. But I'm John's vision of the future is a world in which a billion people on the internet become developers. And in today's episode, we imagine how these billion developers will reshape the economy, society, culture, and more. A lot of people talk about AGI as a utopian vision of the future where people aren't working and there's universal basic income. But what if there's a different vision of the future? What if people are working? They're working as developers and they radically change segments of the economy that we never thought we could revolutionize.
2:48Things like healthcare, education, industrials, and more. That's the topic of today's episode. Enjoy. I'm Chad. Welcome. Thanks for coming on the podcast. Thank you, my pleasure. You and I have known each other I think five years now, and I had the chance to invest in you four years ago at Co2, so I've been able to see the journey. One thing that's been true for you since the first day I met you, and I think for maybe a decade even before I met you, is you've been talking about this idea of a billion developers coming on the internet, which is a bold idea. Maybe it's gotten more consensus as AI has come around.
3:21Maybe tell us a little bit about that idea. When did that intuition first hit you? And how has that journey evolved? Forgot to that. I remember, I actually remember the first time we met, it was in our Bryant office, which is actually kind of a home, a loft we're in the basement, sitting downstairs. and so we worked slash lived in this like really small place in San Francisco. And in terms of the billion developers, it's just like, you know, ever since I was a kid, I started programming really early on. Like my first experience with computers was when I was six years old. And like by seven I was trying to make things with it.
4:00The first program I made was for my younger brother to learn math. And I've done such a good job at it that he works at a replete today. So, it just always felt like making software is the natural thing to do on a computer. And I was actually surprised that this is the domain of the expert, as opposed to this, I think that anyone can do. And, you know, through thinking about why is that the case, it just felt like a lot of tools were complicated. it. Actually, they were getting more complicated over time. So if you think when I was a teenager kind of building a business, it was visual basic. And I can like, you know, make an app and visual basic with database and everything kind of shrink wrap everything into an exe and sell it.
4:47And then the web came along and it just felt like a lot more complicated. It was more powerful. We can deliver things over the internet. And then the complexity didn't and stop, like if you think about a JavaScript application today, there's a lot of things you need to do. You need to spend perhaps hours. If you're new, you might spend days kind of setting up the development environment and learning all these esteric things like, you know, what is webpack and what is transpilation, compilation and all that. And it just felt kind of force than when I started. And there was kind of no reason. and I didn't feel like there was an intrinsic reason for that.
5:29There's all these perhaps social phenomena that made it so that programming is a lot more complex. And one is this decentralized nature of open source. When open source took over and it was in Microsoft product managers designing how programming should look like. But I felt like even then you can have the open source ecosystem being this decentralized innovation machine. But you can create experiences on top of that by mixing the best of the open source to create amazing experiences. In the old language of open source hackers, there's the cathedral and the Bazaar. And the idea of the Bazaar is this complicated mess and this is where open source software lives and the cathedral is like something like Apple or Microsoft where you're designing it, top down.
6:21But I was like, well, that's a kind of a false economy. We can build a feed rules from Bazaars. And that's been kind of the driving motivation for RAPLIT. And I felt like, okay, if you make programming something about more people can do by removing this complexity, a lot more people would want to use it. And the nature of computing changes, because no longer is there's this big divide between what it means to be a developer or in what it means to be a user of applications, which was the original vision for computing. So this was the drive behind that. And it's just, you know, also the opportunities presented by being a programmer is kind of amazing.
7:04And I'm sure we'll get into my story, but like the fact that I was able to make all this money when I was a kid, I was able to get a no one visa, I get to the US. And I felt that opportunity could be a lot more accessible to people. Maybe take us just to start, like take us 10 years into the future, or I don't know, you tell me how many years from now it is, when there are a billion developers, what does the world look like? How does the economy look? I mean, I think you have this sort of imagination about all the ways that we're gonna build software and the ways that businesses are gonna be built are different.
7:34And to me, it's somewhat of a utopian vision of the future. And tell us a little bit about what that looks like. Yeah, I try not to be too utopian. But a few things on that. One is the nature of, if essentially anyone can program, and most knowledge workers would want to develop or make applications or solve problems using software, NAI, the nature of what it means to be a company kind of changes. Because if you think about companies today, we have these roles and we have these silos, and kind of the way companies are structured, are based on the factory pipeline from the industrial revolution.
8:17Actually, if you look at society today, a lot of it hasn't been updated since the industrial revolution. The main collaboration slash work innovation from that era is the pipeline. It's the idea, you do this one thing and then you pass whatever you're making to the next person. eventually there's a car or toy whatever at the end of the end of factory chain. And you know, society is sort of designed, but that's like the main design principle that we have. And so you look at the school for example, you started like kindergarten, you go to first grade, second grade, and it's like everything is kind of created like that.
8:56And even companies, it's like, oh, you have the product manager creating a PRD and then goes to the designer. and then it goes to an engineer, and then it goes to a release engineer, and then the product is out there, goes to marketers, goes to UX researchers, and then, and so, always the silos and the pipeline model. If you have journalists that can make, that can make increasingly more complicated things, and can use computing to its true court, into solve problems, I think you're, you're gonna have people in the organization that can solve problem across the board. So if you're someone in sales and you want to, you want to, you have an idea to drive more sales, you might spin up sort of like an SDR agent that does this one specific thing that's based on an idea that you have.
9:52There's no, there's no this separation. Oh, well, I need to go to my boss to, to go kind of, hire someone to do the SDR. You can actually spend an up an agent that does that exact thing that you want to do. perhaps maybe you're on a customer call and a customer's asking, how can I do this X, Y, and Z with your product, and perhaps your API or SDK? Now, traditionally, you have to go back to engineering and you have to ask them, how to do that, and you have to kind of... But in this world, you can spend up something like Replet agent, and you can say, well, yeah, prototype this thing for me and show the customer in real time.
10:30By the way, all the stories that I'm saying are real things from our customers. And so you can think about it as just a company is a set of Generalist problem solvers. So and you see that in startups, right? We see that in startups, but I think that's going to be the case at scale. The other thing is The way we construct software, I think will change. So if you think about how we construct software where, again, within one company, you see this sort of factory pipeline, but also when you look at the economy in general, you also see the same sort of separation between different companies and how the products get made, for example, the supply chain, right?
11:17In software, we have some sort of supply chain where you have a database company and then you have infrastructure hosting company and then you have, you know, whatever front end company that's delivering actually goods and services. I think going from the industrial age to the network, I think the way we construct things will become more like a network. You can imagine the way software is constructed is if we have something like crypto, Bitcoin, stablecoins, things that are able to, let's people to transact without having to know each other, trust each other, you can imagine software being constructed where I am sitting in front of software agents and I'm going to say, okay, well I need to create this product and the agent is going to be like, oh well I'm going to go grab this database from this area, this you know thing that sends SMS or email from this area and by the way they're going to cost this much and as an agent I actually have a wall that I'm going to be able to pay for them and when I'm going to publish my software my software is monetize and whenever there's like a dollar that comes in it kind of flows through the entire network and so there's this ambience services that my software agent is able to compose without necessarily having any sort of centralized system and all these services are operated by hackers and people that are making money on their nuts.
12:49And so I think the nature of software itself and the nature of companies and perhaps the nature of economy would change when everyone can be a generalist software and AI agent creator. Maybe taking that last point on the economy to its larger look stream, macro economics itself changes in a world where everyone's a developer. You have all these stories. A lot of your users are abroad. there in other countries, you have users in how many countries do you have gas that users in now? Every country, China is harder, but we have some some users there, but basically every other country. How do you think like the global economy changes, the way the economy works today, the people you're empowering, how does this change how these economies work?
13:30So I think one concrete thing, I think Piotr Tiel talked about this paradox of the internet, where the internet was supposed to be the grade equalizer, yet it centralized all the wealth in Silicon Valley and this one area. And so why is the case like this thing that is purely virtual, could have been and perhaps should have been much more decentralized? And there are all these things you can see about network effects and things like that. But you know, ultimately I think that's part of the problem is yes, we think about the technology as accessible, but it's not as accessible as we think it is.
14:14For example, there's a university student in India that was living in some rural area, but he was going to school to study computer science and didn't have a computer or laptop. He had an Android phone at home and he would go and wrap it and start programming and learning how to code on his phone because we have a mobile app. And then he started picking up tasks from our bounties, but platforms, so bounties is the ability for people on our platform to provide services to others. Thinking behind it is like we have a lot of people with time and then we have a lot of people with money and no time.
15:00So a lot of people with time and money and it's like obvious trade. So a lot of people learn to go on platform and they want to earn, so we want to present opportunities for them. And so we had an entrepreneur here in the US build actually a technical recruiter building a recruiting app, but he was running into problems and he was able to go on our down to his platform, hire this kid and for this kid to kind of fix some of those problems. And it was entrepreneurial to be able to ship his applications. So, and that could make money, made more money than his entire family would make for our entire year.
15:35And so, yes, the option of use will get distributed. Obviously, this is more providing labor services, but you can imagine it actually creating a company, creating something that could be scalable on that way, perhaps, that this massive wealth generation machine that that we call the internet will be accessible to more people in the world. Yeah, that's amazing. When I think about your vision, I think it's fundamentally this empowering economic vision. I think it's a vision of wealth, it's a vision of prosperity, it's a vision of giving opportunity to people like, and we'll talk about your story, but people like you and your kid.
16:11I'm curious to question to you, like what do you think is the macro because you're more than finance, brain, like what do you think the macro implications of everything that we just talk about? I think that if we go down this route of having a billion developers, The question is, what are all the sectors of the economy today? They're not techified, if you will. They're getting techified. And so you think about healthcare, you think about education, you think about these enormous percentages of GDP that fundamentally have not been touched by Silicon Valley and touched by Silicon Valley technology.
16:38And the thing that I think about is, well, the barrier to entry was high for the industries. And so in order to build some of these industries, you had to go sell to them, it was difficult, it was tricky, and so what were the lowest barriers to entry? consumer, you and I can go download Facebook on our phone and e -commerce. We want to buy things and it's pretty easy to make money buying things. So you think about social and e -commerce to sort of the initial engines that kind of got going as the economy was terrified. And this is where the, you think about the wage rate for a software engineer is being a proxy for how valuable software engineers are.
17:11And so the wage rate is continued to go up. It's sort of one of these surprising things. You would think that as the more supply of software engineers came into the market, the wage rate would go down. And what that tells you is the value that's offered in Gears Drive is actually higher than the wage rate. And so I think companies like Repplet, and as you see this next wave of developers come, you're gonna have this incredible prosperity from the value that they're gonna go create. And so the thing that excites me is, what are all the sectors of the economy where we can go create this value such that the kid in India who's using Repplet is gonna extract some of that value and create prosperity for his family.
17:46but also such that the consumer at the end of that experience, call it a healthcare experience, what, call it a government experience, whatever it might be, is also a crewing value. And so we've seen that value creation, but to the extent that there's 100 million people I think have created GitHub accounts today, and there's going to be a billion. And so you have this incredible increase. I think there's a lot more to come. There's also like a cultural impact, right? Like where Silicon Valley, as much as we have this global view of the world, and we can, because we have so many immigrants, we can actually relate to a lot of those people.
18:21But there's limits to that. I remember when I was working at Facebook, we were redesigning a photo as an experience on desktop. And we designed this amazing vertical scrolling experience where everything was scrolling after the iPhone came out. And everyone was excited about it. and then we went and did a Navy test in all the metrics tanked. It's like, what is this? Did we create some copy product that didn't work? And then the UX researchers did some tests and then nothing came back as not working. Everyone was happy about the product. Then one product manager actually looked and dug into the metric and found that most, like the majority of Facebook desktop users use it on the on the netbooks or like those laptops where it's like wire screen and they don't have a lot of vertical space and that was mind -blowing to me.
19:19Where everyone in Silicon Valley have these like amazing sort of MacBooks and and so they're there limit to how much we can relate and I think they the products that we build is often not as suitable to these culture and creates this flattening of the world, whereas when you have innovation decentralized, I think they're going to be able to create applications that are more local that can benefit their communities. I think there's less of that today. You've architected your product this way. Maybe this is one of the secrets of Replet that people don't fully understand is how do you make a product, how do you make a coding product that's actually good at mobile?
19:59Is people think of this landscape? There's a lot of hard work that goes into that. How do you make it work on all these devices? maybe talk to us a little bit how you've done that. Yeah. Well, initially, I mean, the main breakthrough of the open source project that we've come wrapped up with the company was that I was the first to compile a bunch of programming languages to JavaScript to run in the browser. So this technology becomes wasm later on, but I was on the Grand Floor. It was like a research project by Mozilla. I was called and script and me and my friend were able to compile C Python to JavaScript using this technology.
20:39We contributed a lot to it. We had to create sort of a unique simulation layer in the browser. It was like a very complicated project. But it captures people's imagination. We put it up on hack and news and went to the trial and people got really excited about it. I remember one highlight at the time was Brendan Eich, the inventor of JavaScript, tweeting about it. It's like, wow, you know, we're like kids in Jordan, like building a thing and people got people, you know, very important people got excited about it. And at the time, I thought that was like the best thing. The problem is when I tried to load it on phones, they would crash, especially though, and like Android phones.
21:21And I even wanted to work on like these Nokia SIMB and phones at at the time. And it's because we were downloading tens of megabytes of JavaScript. So it worked for a lot of people, people excited about it. But the problem with client side execution is that a lot of people's machines aren't just not very good. And so when we went to, when I went to work at Code Academy, and maybe I was giving it a little bit in our story, we, again, we wanted more and more people in the world to learn how to code, and we started having users in Africa and other places like that, and the computers would not handle tens of megabytes of JavaScript to download.
22:04And then so I started building the sort of back -end execution environment such that when you're using it in your form, it's really a thin client, and any code you're typing is just going to the server, executing, and coming back to the client. And then you make it to that, you hyper -optimize the JavaScript application such that it's very small, it doesn't criminal loading. All that stuff with React right now is really easy, but back in 2011, it was actually quite hard to do. We had to invent a lot of kind of web technologies to kind of make it make it work. And you know, still to this day, like if you go to the app store and download the Rafflet app, it's actually one of the smaller apps on the app store.
22:46It's less than 100 megabytes, I think, whereas most apps are on the off -gabites. What do you think that is? The IDE market is one of the, I think, the last markets to move to the cloud. You talk to a lot of Silicon Valley developers today. They still want the local thing on their laptop. You cannot make me run this thing in the cloud. Whereas every other piece of software we've used, people have eventually given in, and Google Sheets and Figma and all these amazing cloud -made companies, why do you think developers have been kind of the last last market to move to the cloud? What is the saying where like the shoemaker is walking around barefoot or something like that?
23:25There's a at least an Arabic there's the saying where you know people who make things for other people are often not satisfied their own needs. I think there's some about and I think there's some cultural aspect like you know you can't really you're I can't pinpoint a real sort of technical problem that can't be solved, that can't be mitigated, that prevents people from coding in the cloud. I think a lot of it is cultural, there's this sense of control over the stuff on my machine. Anyway, there's this old kind of joke in programming where progress in programming happens one generation at a time.
24:03So you need the whole generation to retire or some of the new generation. By the way, all the folks that are learned to code on Rapplin, Code Academy, and things like that, I think they're coming into the market now. They have no problem with the inner coding on Cloud products. I love that. Another question. Back to the origin of the company. Did you foresee that we're going to have LLMs and, you know, Sonnet and all these amazing models to actually transform coding back when you started the company originally? So when I was working on at Code Academy and they went to work at Facebook and before that on the open source, what I was doing is wrangling code.
24:43So I was writing compilers, transpilers, parsers. And those things are very fiddly and very complicated programs. And it just felt like, you know, it just felt like this This laborious thing that machines should be better at. It was like parsing this character and putting it in a node and trying to understand the structure of the program. I read this paper in 2012, which I think is an underrated paper that should be a legendary on the order, maybe not on the order, but similar to the intentions that all you need. It's called on the naturalness of software. and this group, they're making the argument that NLP can be applied to code.
25:32And they make a statistical argument about how code is statistically like natural language. There isn't a lot of daylight between them. And so they build an ingram model and they use the ingram model to do completion. And by the way, you can scale Ingram, Ingram models, like Ingram models were the original language models, and famously Google did this trillion parameter Ingram model that was pretty good at translating. They're very, very simple things that's trying to predict the next character based on frequency. So they constructed that thing, and then it was performing well, it wasn't at performing as well as IDE completions, but then they used static methods like IDE completions to rank their completions from the language model.
26:28And the result was superior and program was rated as superior and it actually did more completions than this static methods on their own or the classical kind of algorithmic methods. So at that point it just felt like, okay, that's the future. or like, you know, deep learning and things like that. We're coming on the scene and your networks. And if this very simple thing is able to have such results, I'm sure we're gonna have better things. And so try to do something like that, but it didn't work really well at the time. But actually when I pitched, you know, I think the seed deck is out there on the internet.
27:10But one slide in it, I tried to do like the Elon Musk master plan, which everyone does these days, but basically, there's like, you know, the Elon Musk master pouch. Really amazing. It's like, oh, we're going to build the roadsters, going to be expensive. We're going to use some money to fund the next generation and that'll create economies of scale and so on. And they did it. Basically, it was like, we're going to create this website for hobbyist learners and teachers and we're going to grow it that way. And that way we're going to get a lot of data about how people use and learn programming.
27:46Then we're able to train machine learning models. It's going to be this AI -powered tool. And then that would be a tool that's more powerful than traditional software tools. And therefore, people come to the side learn how to code, make things in deploy them. And that was in 2015. And so every year I would try to do something with machine learning. And the first time that I got a glimpse of something working with GPT2, and there's a lot of experiments at the time, a lot of the early community around GPT kind of had the feeling that, okay, this is working because you saw GPT1 you saw GPT2, it's scale even GPT2, there was like two sets of weights, one more parameters, you could tell that scaling is working.
28:37And so when GPT -3 came, it was amazing. It was like, you know, groundbreaking event. For a lot of us, it was the chat GPT moment. Because chat GPT was not, it was like a UI, innovation, perhaps some fine tuning. But it was really clear that it was here and it was coming and I started orienting the company to take advantage of that. Do you want to talk to us a bit about Repplet Agent? I mean, that feels like a transformative moment in this company and almost like the whole company, You got these millions of users. You had this community and almost like the whole company was built for this moment.
Read the full transcript
29:10Talk to us a bit about Repplet Agent. Yeah, so every year, we implemented a co -pilot like features. We're actually the first startup to train code models outside of Microsoft and OpenAI. We also have some of them for a small time. There were soda models. There were three billion parameters. and that was really exciting, but the thing that I thought would be transformative is agents. I actually had a thread that went viral at the time in 2022 about how soft operations will change programming and perhaps the economy. And so every year we tried it, I remember we tried it with the GPG3. The context window wrangling that we had to do was insane.
29:56like we had to, every time we generate a class or a function or whatever, we'd have to like summarize it into one sentence and put it back into context to be able to kind of iterate. So that didn't work. 2023, you had auto GPT and things like that come out and you could tell the models getting better at like being coherent a little longer, but it wasn't working very well. October 2023, I gave a talk at TED Talk and I talked about how in the future people make software. In it, I talked about agents. I kind of predicted test times scaling as well where I was saying, there's going to be a trade -off between costs, speed and accuracy.
30:47Sometimes you want to like pour more compute or time into a task. And you're gonna have these plans and the agent will iterate on these plans and build a software and you're gonna be human in the loop where you're that's sort of the creative engine. It was the plan, it was the roadmap for where we're gonna build. And 24, I think around the time for Oak him out, it felt like we're almost there. And so I essentially put the entire company on that. And in fact, we actually did a layoff in May 2024, partly to kind of cut burn and focus. But the other part is like, I knew in my bones that there was the way to go and we were doing a lot of other random things that were unimportant.
31:31So between March, the first time I got a demo from someone on the AI team, Zen on our team, he showed me something and I could immediately feel like we're there. It was like almost like a baby, a baby kind of agent. So we spent seven, eight months working on it. And then it just felt like we were on this treadmill fixing one bug after the other, you know, trying to make it go here. And the transformative thing that happened as like June 24 when Sonnet 3 .5 came out and Sonnet 3 .5 had two important properties. Actually, the main property that people don't treat you talk about all that much is Sonnet was able to generate like thousands of tokens.
32:28I think up to 32 ,000 tokens of code, coherence code. So you almost. Whereas with GPT -40, when you're doing agents, you're writing one function at a time and then testing. If you remember, had they caught ignition demo, as I go, they write one thing, they go to the browser, they write one thing, they go to a browser, and that was like, that was intractable. That was very, very expensive. And we thought that's not going to work. And the thing that Sonnetbro, though, at the time, is like writing high quality code and not being lazy about it. Because the problem with OpenAI's products were lazy.
33:04There's a real the Paul of laziness, where it's a, it like yasset to do something and it's, and at one point, it adds a comment and says the rest of the code here. Bro, I asked you to make that program. Why are you asking me? Slash. It's for the... Get a quick, a human. Yeah.
33:24And so, Susanne, it was this huge unlock and we felt like we're going to be able to ship soon. And there's always this tension, the quality and windio and ship. And so we set that line for my birthday September 5th. And it was so contentious. Actually, at least one person in the team kind of quit because they thought we're not ready. And he was partially right. And we launched an agent. And there was a lot of excitement because it really is the first software agent that works on the market. the very first and people got really excited because, oh, you can try this thing and you can get a glimpse of the future or this thing can bring it in a database and like provision it for you.
34:07It can run a migration, it can like deploy my app. But then as it escaped the kind of early adopters, it was, you know, a lot of people were disappointed because it was actually kind of crappy. And so we sprinted between September and then, December, we had something we were really proud of and we exited the beta. And although we're growing well, then we grew really fast from there and people got a lot of value out of it. Now we have Virgin 2 coming and it's rolled out to some beta users and we've done AB tests and it is anywhere depending on the metric we're looking at between 50 and 500 percent better.
34:51Wow, so it created a 50 % better data retention, a 50 % conversion, a 50 % better engagement. But the metric that was really great was, new users are twice more likely to deploy an app that they made with agents. And power users are five, six times more likely to deploy an app that they made. And deployment of a Repplet is very, very important because that's one of what makes Repplet great. It's that you can go from an idea to a deploy thing and we see people who deploy are 10 times more likely to retain on a Repplet. So that metric we track very well. So now I look at V1, I'm like this crappy thing.
35:36We got to ship V2 as soon as possible and like on the team and so we're starting to roll it out now and it's really good. Can you give us some of the intuition for how you've gotten it so much better? Because I imagine it still saw it 3 .5. That still seems like the Southern model that everyone likes right now under the hood. Maybe it was to be had a scene for how the agent actually works and how you've gotten it to be so much better when the base models are very similar. Yeah, so at the 3 .5 era, we had to build this fairly complicated multi -agent system. and we were talking about LandGraph earlier where there was a state machine component to it.
36:17And there was a lot of non -AI state transitions that we're having to make so that the more you put into the eye, the worst decisions it often makes and less go here and it is. So a context window was still very important because there are actually studies showing that although these models are advertising a million tokens, actually after something like 32 ,000 tokens, reasoning in a lot of benchmarks, just like tank, like crazy, right? And so there's a lot of context window wrangling, and so we had a manager, and it had different contacts than the editor, than the debugger, because we had to kind of make sure they're isolated and they have their different memories and things like that.
37:11And the tooling between all these things had to be different. We built our own protocol for the agent to call tools because actually tool calling was not very reliable at the time. It would like hallucinate tools or hallucinate arguments. So there was a lot of engineering behind it to make it work. When computer use from Floppy came out, so that was 3 .5 V2. The moment we laid our eyes on it, we felt that there's something important that wasn't getting marketed, that was a start of a transition, which is, it looks like it actually fine -tuned it for long horizon reasoning. Because if you want something to do computer use, you're You're going to have all these images in context, and it's going to have to kind of continuously like click on things, reason, think about what to do next, click on the other thing.
38:07And so you can actually roll out a long chain of tool calls without that big of a degradation and reasoning. And so we started re -architecting the model of the agent to be, let's call it, less multi -agent and more single -frighted because the models are getting good at it. And that's like a much bigger simplification. It added other challenges, but it's a much bigger simplification over the existing model. And so kind of the lesson to learn is that you have to constantly rewrite the systems because you want to make use of the Next version of the and you want to be able to predict what's coming down the line when 3 .7 came out You know cursor had a big problem with integrating it everyone hated it on cursor I think just they just recently fixed it and the reason is because again 3 .7 is more agentic And so when you try to use it and that it's a composer style request response, it is not very good at that.
39:17It's actually worse at that because it's trying to kind of make decisions that you're not giving it the space to kind of do this looping. And so there's a really kind of tough lesson for engineering and product teams. If you over optimize for the present capabilities, you're going to enter a local maxima that is quite hard to move. There's an innovator's dilemma problem on the order of months. The innovator's dilemma used to be an order of decades where a company has an innovation which is a certain height of success based on a product that they made that people really love. but then there's a disruptive technology and they don't make use of it because it might be destructive for the current business where it cannibalizes their business and so they tend to not pay attention to it and fight it the classic example is like Kodak had a digital camera product, but they didn't actually launch it because I was gonna cannibalize their film business which was the thing that's making the money actually and this kind of thing is happening on the lower ones which is really harder up your head or at.
40:31And so the move fast break thing is actually very, very important today, right? More than ever. And you have to be okay with your, with sometimes like delivering crap experiences. You mentioned cursor. What do you make of the entire lens? It feels like the landscape of coding tools has just exploded in the last six months. And, you know, developers are reaching for new IDs. You know, many more people who didn't consider themselves developers before entering the market. What's your view of the market landscape? And how do you think of as the ideal person that chooses replettes versus one of these other tools?
41:07Yeah, so I think there are incremental innovations and there are more disruptive, clean slate innovations. And I would put replant in the latter category. So So you take VS Code and you build an amazing AI experience on top of it. Really cursors like a fantastic experience. A lot of people on our team use it. The thing is it is by definition, Kermel, you took a business software that Microsoft says we've been building for over a decade and you added this, you're much better experience on top of it, but you're still kind of, it is still literally this additional layer with the ROTLOT agent, we actually took a clean slate approach to that.
41:57And I was like, okay, what do we need to make it that people aren't coding at all? Like, you know, we want to kind of drive towards this vision of no coding, not only no coding, no DevOps, no IT. Like, we don't want you to set up a database. We don't want you to write migrations. Like, writing migrations is the worst thing ever. Like, you know, if people don't talk about this, But one of the worst things about building software is being able to keep your version control, your database schema, and your deployment settings and configuration in constant and lock step. And most actually most outages when you read postmortems from Google Cloud or AWS, it's like a configuration error and usually it's outdated configuration.
42:42The software changes, but they forget an environment firewall configuration. And so when you have an agent to actually do these things, this is actually much better at doing that. And so the system that we built for the agent is this sort of transactional lock -step system that does these transformation one at a time. When you hit Reverts and Replet, it actually reverts the code, but also reverts the database changes. And other environmental things, and environment variables, things like that. So there's all these things that we thought about where you as a developer coming to our outlet, the thing you have to worry about the most is your ideas.
43:29You know, you don't have to worry about where do I get object storage and how do I configure my buckets, right? Whereas when you're sitting in cursor, There's either so many in your company, a back in engineering worrying about these things, and you're basically hooking into these APIs, or you're having to build them from scratch. And it would help you hit those APIs, but you still have to architect the larger system. So I think there's like a fundamental category difference between these things. These products are hooking into existing systems and require a lot of existing support around these systems, Whereas, a replet is trying to be the final tool you have to adopt in order to build a piece of software.
44:14One thing I've heard from users when I talked to them about Replet agent and deploying on Replet. One of the things that people love is that you can go straight to deployment and that Replet does the whole thing. You start from nothing and you end up with a fully deployed system. Can you talk a little about that? How do you think the deployment space plays into this? You guys in some ways are not comparable to a lot of these other companies in the sense that you can go all the way on Replet. But how do you think about that last mile? Who cares about that and how does that play into the long conversion?
44:41Yeah. So, in the same way that I can say that cursor helps you with coding, doesn't help you with the other stuff for cell, helps you with hosting, doesn't help you with the other stuff, right? And again, it's like this back to the cathedral and the bizarre, sort of like a bizarre, or you need to kind of find all these tools and configure them and figure out, whereas sort of, wrap it. I mean, another sushi analogy, there's ala card and there's al macasse, a wraplet is al macasse, we're going to make, we think we have great taste, or we're going to make the design choices for you. And it's not for a lot of people.
45:14If you want to make all these choices, don't come to a wraplet. I mean, there's a lot of other products out there. So in terms of like the deployment system, the if you want to reach a billion people, eventually like making software. At priority most of them will not know how to set up a deployment environment and therefore the replica product needs to have deployment environment. Basically that's how we approach product in general you know. In the early days of Repplet there was always this narrative of it's students, it's young people, it's people learning how to code. It feels like in recent years that's really changed in maybe AI's enabled that.
45:54I was talking to a Netflix engineer who's telling me about He's using Repplet. Paul Graham has obviously always been a big advocate of Repplet and one of the early believers in the company. How do you think the user persona has changed and how will it continue to evolve over time? How amazing of a visionary is Paul? Like how can you look at a crappy Toy -like Repplet and just see that oh that this one day could could be really big or the idea that people are leaving You know are sleeping on mattresses and other people's homes. That's gonna be like a hundred million dollar company It's incredible.
46:26Yeah, it is fascinating. He's also incredibly good at human. He's been very supportive during very difficult times in the company when all those were weren't. It was frustrating for a long time that like, oh, replete as a toy, hobby toy, students, kids, teenagers. On the one hand, I was excited by it because we had a group of users that are willing to experiment, that are willing to kind of try to find a future of software, the future what we just talked about of being able to have an economy built into the software infrastructure. And we tried a lot of that and I think it's going to work. We still have, like the main missing thing was the agent, but all these things are going to work.
47:10And there's this call of illusion that happened with these users that was very important. The other thing that that perception was important because sort of competitors were paying attention. They looked at replacements like, oh, that's a toy thing. Well, I would have paid attention to it. A very close friend of mine and someone who's looked up to in the end industry, visitors the other day, and visit a lot of our friends. And he was selling him, he was using replic to kind of post -op ideas for a new company. And everyone was like, well, isn't that like the toy thing that I'm just working on?
47:48was like, well, no, it's very useful for me. And that's how I'm able to rate on these ideas very quickly. So now, yeah, the perception is changing. And partly look, I mean, we took explicit decisions to make the product more premium. Actually, what's fascinating now is the product, a replica is the most expensive product in the market, with the cursor composer, I think one request is four cents, with a replica one request is 25 cents. in the reason we did that is like we just really want to build an agent. We don't want to build co -gen tool. And if you want to build an agent, it's going to be expensive.
48:26It's going to iterate and it's going to call a bunch of tools with every request. And so it did eliminate some users. That partly also shifted the perception and kind of more professionals, got them bored. But if we're going to reach a billion people, we need to go down market again. But I think we started in one end and now we're starting in another end. We'll meet in the middle, I guess at some point. But I guess that replete is the more roaster now. And as we drive costs down by perhaps using more open -source models and things like that it's going to become more and more acceptable to people.
49:12What do you think of vibes coding? I don't really like the term. I think you shouldn't fight it because I actually didn't like Jenny. I either. It's just I don't know. Same. Yeah. I just like cheapens the possibilities. Yeah. It's like, oh, this thing that generates things. Well, actually, you can build agents and not just generate things. we can actually reason. In vibe coding is make sense if you're sort of a starting form position of coder and your Andre Carpathy and you don't want to kind of worry too much about the code and you keep heading into whatever. But if you're starting with Rocklet, you're actually not starting for a position of code.
49:59You're starting from an idea, you're starting and then you go in and the agent is unfolding this code in front of you. Actually, when you're using Rapplet agent, you don't have the luxury to look at the code. So we have another protocol assistant, and assistant is for more advanced people. And that you can do more by coding there, because it's like a request response, and you kind of like kind of refute the code and do all that. But if I were to explain a replica, it's just vibe. Like don't call it vibe. And not vibe coding, just vibe. You've always been a bit of a contrarian. One idea that's very popular now in Silicon Valley is EGI.
50:45There's this idea that there's gonna be no software engineers. And you sort of have the opposite view. There's gonna be a billion software engineers. Talk to, how do you think about EGI? What is EGI in your view? And what would you say to all the people who say, I talked to a lot of software engineers and they're like, well, I'm not gonna have a job. I'm worried about not having a job. when we're worried about no one's gonna have a job. We're all just gonna be on universal basic income and all this stuff. Replytics in some ways, the opposite vision, right? Of like, we're actually all gonna have jobs.
51:10They're just gonna be very powerful and we're gonna be able to do all these amazing things. I think it's like a fundamental, it's philosophical difference.
51:22What is special about humans and what's replicable in the machines and at least in the near term? My view is that AI is going to get really good at sort of two things. Things that are highly represented in the data and things that you can construct a very good RLN environment for. So what can you construct a great RLN environment for? Like obviously with Alpha Zero games, right? Games are famous for, you can have these self -play sort of algorithms that of time. Now with reasoning models, you know, math is an environment that especially with lean, it's like a code, almost like an expression of math that can be executed.
52:14That's like a great, you know, RL environment, I think code execution as well. So running the code and then, you know, doing your reinforcement learning on that. And things that are already represented that don't get hub and things like that. But there's a lot of other domains where we actually still don't know what we're how we're gonna make them better. Like new fundamental and new ideas, new knowledge. It's not entirely clear how we're gonna get there. Can you use RL for these more software things? Perhaps you create a reward model, you can approximate these things, but I feel like the sort of the ideas is in the creativity and the sense of like coming up with really novel things and understanding the world and very complicated, intractable way and you know coming up with an idea that could fundamentally change how things work or change the world.
53:12I think we'll still have be the domain of the human. And AGI will have AGI but it would be a functional AGI meaning it would do the jobs that a lot of humans are doing today by virtue of the training data being available and by virtue of some of these jobs having like ground truth that you can train on. And the reason I call it functional AGI is because it's fundamentally not general in that you can throw it in a super novel environment and for it to efficiently learn things especially when they're, you know, when there's not explicit feedback and be able to be successful in that environment, which you have the definition of the universal AI, which doesn't feel like we're trending that way, but I do think that you can reach something.
54:08So the definition of a AI at a lot of these companies is doing economically useful activities in front of a computer, right? I mean, But if I have a remote worker, I'm going to create a hundred more workers and implement all my ideas. And still, it's a tool. It's useful for me. Is it going to replace me? Well, if I am like a code monkey, it's going to replace me. But if I see my place in the world as someone who can generate ideas and create products and services, because I understand what people want and how the economy works and all of that. I think that's still irreplaceable. I want to talk to you a little bit about your life story.
54:52You touched on coming to the US, the ONV's growing up in Jordan. Maybe you started the beginning for people who don't know your story, because it's a really inspiring story. And in some ways, your whole life has built up to a repilate. It's not just a company. I mean, your wife works at the company. Your cousin works at the... Like, this is like your whole life and your whole mission. All in. Bring us to the beginning. Like, how did this all come together? How did you get to the US? How did you get into Silicon Valley? Yeah, yeah, so it might one of my first memories Just as a child. I don't know if you remember your first memory, but I remember very vividly that my father Kind of getting this this machine and like opening this this box and like putting it together And I was fascinated by it even before I knew what it does and I walk walk over him and I kind of look over this shoulder were him sitting at the keyboard and sort of finger sort of typing.
55:50He had like a big manual like you know you throw it at someone who could really hurt them. And he would he was reading into it but one by one he was like finger typing, CD, MKD IR you know these docks commands. And remember, feeling that it's just, wow, this is a machine that you can talk to. What is a DOS? It is like a Rappl. This is where the Rapplit name comes from, ReadYval print loop. You can essentially have a conversation with this machine. So my father would like go in like attend classes to learn computer computers. And he would like, you know, every night he would come in with all these notebooks.
56:39He's like such a such a big nerd. Apple doesn't fall far from the tree. I'm different than my father. My father's a Palestinian refugee crew up with like this intense focus on education. Like if we're gonna make it, we're gonna have to be like the best educated, we're gonna have to be better than anyone else We're gonna so there's like a a students and working really hard My mom is sort of the the opposite my mom is like a sort of a free spirit She was a Interpol tree she taught me a lot of poetry When I was kid and I was actually able to So it was like there's an art to telling an Arabic poetry.
57:30And so I was just a mix of two things because I can be very intuitive. I can be, I can go on purely an intuition and take a lot of risk based on some kind of idea or vision or something that I feel good about. And I also have this very analytical mind and I can sit and be such a You know pin in the butt about about being so rigorous about certain things and that's that's really my father's inspiration and and so You know, you know one day my father comes home and I'm sitting in front of the computer and he was he was mad He put all the savings into this machine and and I was like, you know, opened a computer apart, took the parts out, put them back in, and I was like, you know, doing it in an angry, I know exactly how to use it, I know exactly how it works, and I showed him how to use it.
58:27I showed him essentially how to create things, how to open applications that he's been studying the whole time, and I was like, okay, this is fascinating, you know. All right, it's yours. And the first program that I wrote, I think I mentioned earlier, was to teach my younger brother math and I thought, okay, I can use this thing, this conversational machine, which I still think about it that way. Obviously with AI, that really happened. Yeah. And this idea that you consider front of it, learn something, play games, do something fun. And so that was the first program that I built. And then when I was a teenager, I was really obsessed and Counter -Strike, so I would go to these Internet and Land Gaming cafes, and I would like, you know, Whatever money scraps of money I have, I would like Put it into that and just play a lot of Counter -Strike And strategy games and things like that.
59:25I got very good at them. To the point that it was like a source of income. I was actually winning tournaments and things like that. It's good to go to eSports early on. So that's another bench of my life. But one of the things I noticed about those businesses, is they were running on a pen and paper, I'm like, you have all these computers. You can just write software for it. So I did write this client server software that did accounting, that get people accounts and username and password and manage their time on the system and they're also did security so that people can't format the computers or do install malware and start selling that and it made a lot of money on that.
1:00:12I mean, I sold it to a lot of businesses in Jordan. By the time I got to college, I had this idea that AI is going to get so good, we're not going to have to write software. It just felt like software is this like pedestrian thing that you do. It's like not that interesting. It's just like you just do it to like make things. And at the time like these wizards of code generations were coming out from Microsoft. So when I went to school, I actually studied more on the electrocure engineering side, especially because my father thought that computer science was not a real field, because the engineering association of Jordan would not admit you into that as an engineer, if you don't have like you know electric going gearing and by the way my father is the vice president of the so organization.
1:01:04I didn't know that. I learned so. He really loves that engineering organization. But throughout my college experience I got really into program languages. I started reading programs, started reading hack and news, program wrote a lot on on list. He actually has a book called OnList and programs view of program languages is more of an art rather than science. Like these artifacts are aesthetic artifacts and not just functional artifacts. And that also played into the reason to create Repplin because I wanted to try all these program of languages. And it wasn't a place I learned to intern at to be able to try all these program of languages.
1:01:48And after I created Repplin, had that breakthrough that I talked about earlier, it went viral in the US, a bunch of attack companies started adopting it. If you remember 2010 -11, there was the MOOC kind of hype. We have AI hype now. There's a blip period where there's the massive online courses. Audacity came out of that period. Coursera came out, code academy. And I got a bunch of, they all started using Repplet by the way. And I got a bunch of offers. I eventually decided to come to the US, got an O1 visa, because a lot of my work was published in the news and everywhere else. and so it was possible to go know when Visa landed in New York early 2011.
1:02:33The only money that I had was taking from me at the airport. And the reason is in the airport in a month, I had like perhaps $700 dollars. There's the money that I'm going to the US with. And the folks at the airport did not know what an all -one visa is. I apparently like no one in Jordan had ever gotten no one visa to get to the US. And they didn't think it was like a resident visa. They thought it was like a visitor visa and that I needed a ticket back. And I was like, no, it's like I can go there, I can work, it's a work visa. And they didn't believe me. I was like, go look it up there. They didn't believe me.
1:03:14And they made me buy a ticket back. And that was something like 500, 600 ,000 dollars. So I arrived there with like about a hundred bucks. And my salary was $80 ,000, $70 ,000 or $80 ,000 in New York City. That's pretty big. Yeah. Well, not in New York City. When your rent is like $2 ,000. I think at some point you had someone offered to buy the company for a lot of money. How did you decide to turn that down? That seems like that was a pretty big decision. Coming from this background, you grew up, you made it to the US, you got this job, then you have an offer by your company for life changing amount of money.
1:03:46In seeing amount of money, we were like six people at the time. And you know, the numbers that were thrown around is between 500 million to a billion dollars or six people. And so it would have made me insanely rich, right? So And it was a tough time. I Wasn't really happy about the culture then like we grew to six seven people or something like that from from the three that are our families essentially and And we hired people that I didn't like very much and the culture was changing and I kind of wanted to do a reset. And at the same time, my mom was diagnosed with cancer back in Jordan and I had to go back.
1:04:33They entirely had to go back, which is half the team. Well, to spend time with my mother and it was a very stressful time. and the thing that made me, which is like the absolute rational thing to do, is to stick the money to home and live, I guess, happily ever after or something. But I felt two things. One is my dreams, right? I've had the dream of being in Silicon Valley for so long. like the first time I knew about Silicon Valley is through a low -budget movie called The Pirates of Silicon Valley, where it's the dramatized fight between Steve Jobs and Bill Gates. And I was like, wow, this is Silicon Valley places.
1:05:26There must be flying cars and really mass advanced technology. Of course, you come here. It's like the suburbs. But I always wanted to be here. I thought the innovation was really I was reading about all these entrepreneurs. I felt like this is the most important thing in those people are heroes. And I felt like the weight of Silicon Valley also on my shoulders because Paul Graham, you know, Mark and Dreson, and other people that I really respect invested in the company. And like they all have like very high hopes for it. And they're all really excited about it. And I felt like I don't want to let people down.
1:06:11And I felt like if I sold the company, it wouldn't be, I wouldn't have achieved the potential of it. And maybe I would regret it in the future. And it's like, okay, being rich is good. I think money is actually great and improves your lives in many ways. It allows you to focus on the things you love. But, you know, what are you gonna be? You're gonna be another, you know, rich Silicon Valley dude, and there's a lot of them. You know, gonna like write and invest, do angel investing is like your life has gone a little boring and you never kind of want to take the pain again unless you're a Elon Musk to kind of like go start a, start another company and put your life's force and energy into it.
1:07:00And so for all these reasons, we decided to turn it down. Now you have 40 million users? Yes, and we achieved evaluation over what we got sold for. And I think the company is actually underpriced now. It's a lot of grit to get here from six people. I want to talk a bit about your management style. You have a unique management style. I remember seeing one time on the internet. You said, like, I'm now the VP of engineering of Repilit. I feel like over the years, there's always been your hands -on leader. Your leadership style maybe has become more popular. even it wasn't popular six, seven years ago and you were doing this, like, how did you develop your leadership style?
1:07:37What advice do you have for founders as they think about running their companies? In some way it's a deficiency. Jensen now talks talks a lot about him not being sort of a great manager and him having all these reports and only talking to everyone in these big meetings and being, you know, giving feedback publicly, not really doing performance reviews in the traditional way and all of that. And in some way, I would say it is a perhaps lack of skill in terms of like how to do traditional management. The management styles that I have is similar to like how I would like lead an open source project or how I would lead a sports team back home.
1:08:22I've always been a leader and I've always been sort of a hands -on leader where it is this duality of micromanaging and trusting people. It is actually not at odds to do these things. The most inspiring leaders both can go dig into the details and give very precise direction. But then really trust people to deliver on those things. Also trust people have their own innovation, their own ideas. The way I managed the company from the start is I had a text file inside Rapplet, I use it as a set of a notebook, and the text file had everyone's names, and the one thing that I think they should be working on, or the one thing that I expect them to deliver on, and every week when I meet everyone we would go around the table, and I would tell them, did you do this thing?
1:09:15And it's either yes or no, or something, they don't go right or something like that, and then the other question, what are you going to do next week? And so it's like, okay, they did that last week or they didn't do it. Why did they fail? What happened? And here's what you do, what they're going to do the next week. By the way, my execs still write that everyone in the company, every week on Friday, they write, he's what I got done this week. Here's what I'm planning to do next week. And so I can still keep in my head what most so the company can do or is working on. Like I can walk around and tell you this, this guy's working on this, this person's working on this.
1:09:59So partly is I can keep a lot of complexity in my head and I can like really be able to kind of make these, these, you know, very deep decision about how, like a sort of one -button should work inside the product or how certain marketing ideas we should run, and so I can go between all these different departments and be able to go all in into the details and then kind of zoom back out. And also, just having really high expectations. If someone, if we go over week, that person who said they were gonna get that thing done and they couldn't, it's like an obvious reason to let them go. It's like not that complicated.
1:10:46And so, Replet has, and then high attrition rate, especially in the first few months of people joining, 23 % of people are going to either leave or get let go because they're not able to keep pace of the environment or they get confused about how to work in that kind of environment. The other thing I think is unique about your culture. I remember I attended some all -teamed internet and all -you -can -eat barbecue restaurant. I don't know if you remember this. And there's all these young people around the table and some of them didn't even go to college graduate college I mean you seem to recruit for raw talent.
1:11:21Yes, and that's something that a lot of people talk about doing They want to do but it's hard to do. How do you do that? How do you filter people? How do you find these people? How do you give them leeway? How do you train them talk to us a little bit about how that how that happens? Yeah first of all I am You need to be able to work with weirdos and misfits And I was able to do that, whether it's instinctively or whether I relate to them being sort of myself or we're doing misfit. And I can see talents, certain people, like even back in my college years, like finding those people that have hidden talents and being able to harness it somehow.
1:12:02I have this feeling of like, if someone has a talent that is not being put to good use, I feel like a sense of waste. I'm like, you know, this needs to be harnessed somehow. And I think that's sort of a good management skill. But in terms of, so first of all, you shouldn't have allergy to or see people. I remember my wife and co -founder, when we hired Mason, he was like 18 year old kid. He was, you know, a joke that he's a runaway kid from Santa Cruz, which is partly true. He lost Santa Cruz in high school. He wasn't happy. He was happy with his family, with his school. He went up to the city.
1:12:46He went to one of those boot camps. Those boot camps were using, we're using replet all of them. And one of them was sending me bugger parts. I'm like, look, I don't have a lot of people who work on this. Why don't you send me your best engineers? It's like, look, I'm going to send you the sketch. He's really awkward, but he's one of our best. So he came in and I remember high one day, I was like, oh, this kid doesn't keep the door open behind him. He like, a little bit of slams the door on me. He's like, well, he's not really thinking about you. He's like thinking about code as he's walking around, right?
1:13:20So, and still to the state, I see people doing that. But the first thing is, most people, I think, just project these people out right when they can't communicate with them or they can't relate to them. And then the other thing, you know, they're gonna spike on certain things and then they're gonna be not great at some other things, right? And so, but, you know, you can construct a team where it all fits together, where the peaks of someone is the valleys of someone else, right? Someone is really good at, that's shipping thousands of lines of code. And someone else is really good at testing it at a very methodical about code reviews.
1:14:07And if you have one who's like a cowboy slinging code and others like a little more careful, and like meticulous and rigorous, and perhaps a little annoying of how meticulous they are, put these two things together. There's a lot of tension, but then they get a good product. So you want to balance the team in a way. And you want to go to higher from places that other people aren't going to. And that gives you an advantage because everyone's competing over the existing talents on the market. So for us, a lot of it was going to Rapplet. A lot of it was running hackathons, running surprises on Rapplet.
1:14:51and some kids win and we fly them out to us, to work with us. And we've had anywhere from 16, 17, 18, 21 years old join the team and even on the older side, people who haven't had traditional jobs before or were ND game hackers that joined the team. So yeah, I mean, it's sort of a diversity of sources. If I am starting a company today, I would try to find niche communities. This is where you'll find some really underrated talent, whether it's an niche group community around a niche crypto project or a niche program language. That's where I would look first. You mentioned your wife, Haya, a couple of times.
1:15:42What's it been like building a company with your wife? It depends on the day.
1:15:51We've worked together. We met at work back in Jordan. We were working at this company where we recruited actually a foreigner, Kimner Jordan, as part of a job from Belgium. He decided that he loved Jordan a lot. He loved the desert. He wanted to build a company there. So I was the first employee there and I was the second chosen designer. I was an engineer and he pitched us on this idea. We're going to do consulting and then we're going to build a product on the on the side and then we're going to become a product company. By the way, every company that has this idea never becomes a product company.
1:16:27I'm sure you've seen some of them. And so the company was very dysfunctional. He was non -present and so it was like the inmates were running this island. So I and I ended up working a lot of projects together just for fun. And then we started dating, which dating in Jordan is not real dating. Like God for a cup of coffee, she had like a 7 p .m. curfew. And so, and then by the time I started working on the open source, Replet, she actually contributed the logo and a few other designs. She helped with a few other things. And then when I got the VZ to come to US, we got married and we were very young.
1:17:14I was like 24 at the time. And then she joined me in the US. We continued working on projects the whole time. We worked on art projects, working on games, all these other things. And then when the time came to to start the company, I was kind of like looking for co -founders because I'm like, oh yeah, YC says that you need to have co -founders and I guess it's like best to have co -founders and I was like going in these co -founder dates and trying to meet people and all of that. And then she was like, well, I can start the company with you. I was like, it's gonna be really painful. Like it's really, really painful.
1:17:54Like I assure you wanna go through that. And she's like, yeah, yeah, of course. like I saw you, you know, with Code Academy. I can do that three or four months later. She's like, I understand how hard this thing is. But she obviously lived up to the challenge. And I think overall it strengthened our relationship. Because when I was at Code Academy, and I was working you know, 12 hour, 14 hour days, she doesn't really relate. Like what kind of job requires that kind of commitment. And then with Repplet, we were both doing that. So it's not like, you know, your partner is going off in the morning, not returning until midnight.
1:18:38On the weekend, they're wasted and they can't really do anything fun. And so you don't really have this great relationship with them. If you have a startup founder and you have a regular job. But if you're both founders, you're actually going through this together. And I think that ends up being good. And at the time, it was actually working against us because venture capitalists do not like husband, wife, founder. It wasn't a lot of examples at the time. Obviously, the most famous example is Paul Graham and Jessica. But then now there's like they get canvass founders that a bunch of other Companies that that made it work, but there are challenges, too like You know right now we're fully sort of fully committed to the company, but also we have kids And so how do you how do you manage how do you manage this that that's quite a bit of stress and pressure on us?
1:19:38And then the other thing is when something is going wrong in the company Like a lot of people can go home, I can disconnect because they find comforts and talking to their spouse about other things. But when high -end I go home, we're talking about the problems and the problems kind of percolate. And they end up seeming bigger and worse. And so you start to have, you start to need rules around when do you actually talk about work and you're constantly breaking into those rules obviously because you're thinking about something. So I think it is a challenge and I think it is at the same time there's something very Very unique and good about it.
1:20:19Yeah, well, it's impressive. How well you made it worked and you guys have a really great dynamic Mm -hmm. Thank you. All right lightning round. We have some linear on questions. Are scaling a lot is gonna hold Yes, it Scaling different things we're just gonna keep finding things to scale What is the best piece of advice you've gotten? Paul Graham asked me this question. I was stressed at the time and he told me, is this your life's work? Are you going to be working on this 10, 20 years from now? I said, yes. He said, well, why are you worrying too much about the daily tribulations? If they just sell into the fact that even if things are not great today, you're going to be able to fix them and you're going to be able to turn things around.
1:21:07Honestly, as long as you're not dying. And that's why Paul is talking about not dying. It's surviving as a company. What is your favorite new AI app? I'm kind of a lot of died because I make a lot of things myself and I use a replete to make them. I use the basics like, you know, chatroom tea perplexity, but then I spend a piece of software every day to use. I guess Manus is an interesting demo. It's actually pushing on this idea that we talked about of like how long can models work while saying coherence. I think they showed that they can go for an hour with some coherence. Since you brought up Repplet apps, what's a cool Repplet app that you've seen recently?
1:21:55There are a lot of business things that are fascinating. One cool thing that I went to New York. I was meeting a few investors and customers and I met with Sears Home Services. This is a century old company. I didn't know it still existed but I found that the Home Services Department still existed. I met this very cool trendy team. They kind of easily the work I was starting up, they're working at Sears and they told me that six months ago they finished the cobalt migration. And it took them six months. And then I started asking him what kind of other tools to use. He used any SaaS software and they didn't have any ERP software or any of these modern SaaS software.
1:22:42and they leaf -frogged an entire generation of software to start using Rapplet to create agents to manage their business. That's really cool. Yeah, so they have these field workers that every morning they wake up and they're like, oh, how do I optimize my routes to kind of earn the modes and service the most customers? So they build like an AI tool that actually gives them the most optimal route that they He was every day, for example. Yeah. By the way, that team is non technical. They're all operations. Wow. It's insane that you go from cold vault to replet and you skip everything in between.
1:23:22It does, we're talking about this in the beginning of the conversation, but it gives you a sense of the sector to the economy that are going to get transformed by this technology. Favorite book? I am a strange loop. Douglas Hofstadter. I actually disagree with the conclusion slash premise, perhaps, of the book, but it's still one of the best books exploring concepts like AGI, concepts like consciousness and the soul and what it means to be a human, what it means to be a machine intelligence. What is the foundation model that you're, you like most are most impressed by? The Edie -Iman Claude is the best, I mean 3 .7 is really the best at doing agent stuff.
1:24:04Person who's influenced your life. I think my mom had this supernatural belief in me. Like she would talk about all the great things that I was going to do even when I was a very small kid. She gave me this again unwarranted at times confidence in myself. Recommended reading on the eye.
1:24:35I think it's really awesome. I think it got degraded recently, but there's so many papers that you find on Twitter or so many snippets of information, just like go read those papers, skim them, and I think you'll learn about what's coming down the line by just reading the literature. Last question. Who is the most underrated person in AI? I think, Mike Heligatosta, head of AI now, present at a replica. I don't think he's very public, but he was one of the early pioneers of LM's for code. And he's a great leader as well and visionary around where AI for code is how to. Super impressive guy. I love every conversation I have with him.
1:25:24All right, well, thank you for coming on the podcast. I really appreciate our friendship. Thank you for your time. Thank you. I mean, I appreciate your belief in us. And I think you saw something special real long time ago. And like all these things that you notice about with special about Replet, and I really appreciate that. Thank you. We're still 4 % there, 40 million users. We got 960 million to go. Yeah. Exciting times ahead. Thanks, I've done. Thank you.
1:25:57Hmm.
1:26:11Hmm. Hmm. Hmm. Hmm. Hmm. Hmm. Hmm.
From the publisher
Amjad Masad set out more than a decade ago to pursue the dream of unleashing 1B software creators around the world. With millions of Replit users pre-ChatGPT, that vision was already becoming a reality. Turbocharged by LLMs, the vision of enabling anyone to code—from 12-year-olds in India to knowledge workers in the U.S.—seems less and less radical. In this episode, Amjad explains how an explosion in the developer population could change the economy, society and more. He also discusses his early days programming in Jordan, his unique management approach and what AI will mean for the global economy.
Hosted by David Cahn and Sonya Huang, Sequoia Capital
Mentioned in this episode:
On the Naturalness of Software: 2012 paper on applying NLP to code
Attention Is All You Need: Seminal 2017 paper on transformers
I Am a Strange Loop: 2007 follow up to Douglas Hofstadter’s 1979 classic Gödel, Escher, Bach that explores how self-referential systems can describe minds
On Lisp: Paul Graham’s 1993 book on the original programming language of AI




