Podcasts about YC

Acquired co-hosts Ben and David are BACK to discuss the state of the VC market and YC shutting down its Continuity Fund (6:20) before diving into industries that benefitted from ZIRP (26:35). They also break down which social apps they want to own and why (45:29). Then, Ben and Jason wrap up the show by discussing the future of Amazon and Starfish Space, a new space startup (1:11:48) (0:00) Nick tees up today's topics (1:36) David's time at Stanford (6:20) Ben's private market snapshot (8:49) Microsoft for Startups Founders Hub - Apply in 5 minutes for six figures in discounts at http://aka.ms/thisweekinstartups (10:19) David's private market snapshot (16:19) Reacting to YC closing down its Continuity Fund (25:35) QuickNode - Go to http://quicknode.com/ and use the code TWIST for a free month on their feature-packed Build Plan (26:35) Industries that benefitted from ZIRP (35:08) House of Macadamias - Get 20% off at https://houseofmacadamias.com/twist by using code TWIST20 (36:36) How compelling is AI?  (45:29) Owning either Instagram, Linked In, or YouTube (48:15) Rational and Wildcard: Who is likely to acquire TikTok?  (53:44) Twitter product development (1:00:51) Reclaiming lost time  (1:11:48) The future of Amazon  (1:19:57) Apple to spend $1B on producing theatrical releases + Project Titan (1:25:21) SOTD: Keeping satellites on course with Starfish Space   FOLLOW Ben: https://twitter.com/gilbert FOLLOW David: https://twitter.com/djrosent FOLLOW Jason: https://linktr.ee/calacanis Subscribe to our YouTube to watch all full episodes: https://www.youtube.com/channel/UCkkhmBWfS7pILYIk0izkc3A?sub_confirmation=1 FOUNDERS! Subscribe to the Founder University podcast: https://podcasts.apple.com/au/podcast/founder-university/id1648407190

Try Acres for free: https://www.acres.co/Tule Technologies: https://tule.ag/CropX: Today's episode features Tom Shapland of Tule Technologies and John Gates of CropX. We have a great episode for you talking about Tule's technology, Tom's entrepreneurial journey, The decision on both sides for Cropx to acquire Tule, M&A in agtech and integration lesson, and the future of artificial intelligence in agtech. Tom is the co-founder and CEO of Tule Technologies, which is now part of CropX. As a graduate student at UC Davis, Tom developed the underlying technology that Tule commercialized which is a way to measure water use of crop plants over a broad area. Specifically they measure actual crop evapotranspiration or ET and he'll talk a lot more about that. He founded Tule in 2013 after finishing his PhD work in this area. He went out and started talking to customers and getting sales early, which you'll find is an important part of his entrepreneurial journey. Him and his co-founder Jeff LaBarge went the Y Combinator program, which is our second episode this month with a YC alum. Joining us from CropX is senior vice president and global head of product John Gates. John also has a background in academia. He was a professor of Hydrology at University of Nebraska. He evenutally joined CropMetrics as their Chief Scientist and stayed on with CropX after they acquired CropMetrics a few years ago. You'll hear from Tom first about Tule's technology and trajectory, and then we'll invite John in to talk about the acquisition and much much more.

Trill Withers Tries to Throw 10 Yards in an NFL Game in The Trill Withers Show Best of The Week!!! Join Trill Withers, Coley Mick, YC and Scoob as they debate the question going around Tik Tok this week of whether or not an average person can throw for 10 yards in an NFL Pro Bowl. Other topics include Dream's face reveal, March Madness NCAA Tournament, Dan Orlovsky's 30 Day Towel and the Giant Seaweed blob coming to kill us all. Don't forget to like and subscribe!!! FULL VIDEO EPISODE: https://youtu.be/IzxvIs8Xogs

(0:00) Bestie intro! (1:35) Recapping the events of the past week (5:39) Understanding the banking crisis (32:55) Solving the global debt problem, righting the ship (54:20) VC market update: Founders Fund splits its eighth fund in two, Sequoia's reported returns, YC cuts its growth-stage team (1:08:36) Science corner: Superconductors (1:24:56) DeSantis update, Ukraine spending run rate, bestie wrap! Follow the besties: https://twitter.com/chamath https://linktr.ee/calacanis https://twitter.com/DavidSacks https://twitter.com/friedberg Follow the pod: https://twitter.com/theallinpod https://linktr.ee/allinpodcast Intro Music Credit: https://rb.gy/tppkzl https://twitter.com/yung_spielburg Intro Video Credit: https://twitter.com/TheZachEffect Referenced in the show: https://seekingalpha.com/article/4565388-svb-financial-blow-up-risk https://www.wsj.com/articles/easy-loans-great-service-why-silicon-valley-loved-silicon-valley-bank-6b3f203e https://www.wsj.com/articles/the-silicon-valley-bank-bailout-chorus-yellen-treasury-fed-fdic-deposit-limit-dodd-frank-run-cc80761e https://www.bloomberg.com/news/articles/2023-03-16/credit-suisse-got-its-lifeline-now-it-needs-to-win-back-clients https://www.bloomberg.com/news/articles/2023-03-15/credit-suisse-top-shareholder-rules-out-more-assistance-to-bank-lf9gfhbr https://www.nytimes.com/live/2023/03/16/world/france-pension-vote#france-pension-vote https://www.politico.eu/article/police-fire-dutch-farmer-protest-nitrogen-emission-cut https://www.bbc.com/news/uk-england-london-64968795 https://www.treasurydirect.gov https://www.axios.com/2023/03/03/founders-fund-slashes-vc-peter-thiel https://www.axios.com/2023/03/15/stripe-50-billion https://www.businessinsider.com/sequoia-capital-venture-capital-returns-university-of-california-2023-3 https://www.wsj.com/articles/tiger-global-writes-down-venture-funds-bets-by-33-in-2022-3f9f6ade https://techcrunch.com/2023/03/13/y-combinator-cuts-nearly-20-of-staff-scales-back-growth-stage-investments https://twitter.com/Jason/status/1633570102326202368 https://www.nature.com/articles/s41586-023-05742-0 https://youtu.be/4lE8QWtrEvQ https://www.theatlantic.com/ideas/archive/2023/03/desantis-ukraine-pro-russia-position-gop-presidential-nomination/673392

Join Trill Withers, Coley Mick, YC, and Scoob as they watched the 7ET/6CT slate of March Madness games! Auburn takes on Iowa, Duke tries to stay hot against Oral Roberts, Colgate looks to upset Texas, and Boise State battles Northwestern! LIKE AND SUBSCRIBE ON YOUTUBE: https://youtube.com/live/A2a2Y9KxUUc?feature=share Go to HelloFresh.com/withers65, and use code withers65, for 65% off plus free shipping! You can grow thicker, healthier hair AND support our show by going to Nutrafol.com/men, and entering the promo code TRILL to save fifteen dollars off your first month's subscription – this is their best offer anywhere and it's only available to US customers for a limited time.

Stop! Turn! Take a look around, at all of the lights and sounds we emit as we Album Spotlight Yellowcard's 2006 release "Lights and Sounds." YC is coming back this year with a world tour and we cannot wait. Join us for a track by track discussion where we chat about the follow up to the global smash Ocean Avenue. Be sure to follow us on all social media @HSNEpod and visit http://www.hsnepod.com for official merchandise and more! Join in the conversation on our official Discord https://discord.gg/b3AdrAYURm  High School Never Ends is a part of the Dragon Wagon Radio independent podcast network.  www.dragonwagonradio.com

Trill Withers FIXES Halftime Entertainment in this episode of the Trill Withers Show Best of The Week. Join Trill Withers, Coley Mick, Scoob, YC and Jam Packard as they grow tired of NBA Halftime Legends like Red Panda and fix Halftime Shows with a genius idea of their own!!! Also included is Scoob's plans to die a tragic death once he wins Underdog Fantasy's Small Ball tournament, the show's plan on how to stop the bullfrog infestation in Utah, Scoob's impression of Scott Foster's technical and a conspiracy theory involving pandas never existing. Finally Jam tells us about his courtside conversation with Taylor Rooks that went viral. Please be sure to leave a like and subscribe!!!! FULL VIDEO EPISODE: https://youtu.be/gfI-8js-g5U

Michele Veldsman is Director of Neuroscience R&D at Cambridge Cognition and Founder and CEO of Playroom, an invitation-only secure social network for families. Victoria talks to Michele about the premise of Playroom and its goal of giving parents a network, a safe social community where parents are able to know and easily communicate with people associated with their children and also provide specific options to maintain boundaries when it comes to their privacy and safety, the challenges families face in raising kids and maintaining a career, and new features she wants the app to include, such as finding nearby restrooms while out and about. Playroom (https://www.playroom-app.com/) Follow Playroom on LinkedIn (https://www.linkedin.com/company/playroom-app/) or Twitter (https://twitter.com/playroom_app). Follow Michele Veldsman on LinkedIn (https://www.linkedin.com/in/micheleveldsman/). Follow thoughtbot on Twitter (https://twitter.com/thoughtbot) or LinkedIn (https://www.linkedin.com/company/150727/). Become a Sponsor (https://thoughtbot.com/sponsorship) of Giant Robots! Transcript: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido. And with me today is Michele Veldsman, Director of Neuroscience R&D at Cambridge Cognition and Founder and CEO of playroom, an invitation-only secure social network for your family. Michele, thank you for joining me. MICHELE: Thank you for having me. VICTORIA: Tell me a little bit about your journey. How did all of this get started? MICHELE: I had some kids, and I realized quite quickly that raising children is really difficult. I don't have family close by to support me. They are a couple of hours away. But trying to manage being a professional working in a fairly intense job, looking after my kids, making sure they have everything that they need and that they can socialize, and that I have a support network around me turned out to be really difficult. And so I wanted to find a way to solve that essentially. VICTORIA: Right. So you identified a problem from your own life in trying to manage your career, and you're raising your children without that close, immediate support. MICHELE: Yeah, exactly, yeah. And I realized this is a problem for a lot of people that increasingly, we don't live in these sort of small communities where we're surrounded by friends and family. Increasingly, people are moving to different cities, different countries. And that support network isn't there, but there are still all of the challenges of raising kids and trying to have a career at the same time. VICTORIA: Right. And like we were talking before we recorded, I just got back from visiting my family in Virginia, and I live in California now. So I'm familiar with some of the challenges my brother and sister-in-law are facing with childcare. Can you tell us some of the things that specifically you found really difficult in this situation? MICHELE: A lot of the time in my working life, I found there were loads and loads of tech to kind of try and make things easier to organize things. There's just a lot out there just for my working life but not much to support my family life, of which there are actually many, many more challenges because I'm kind of trying to juggle. I'm making sure that my kids their healthcare is all right, that they're getting their vaccinations on time, that I'm applying to school places on time, that I'm making sure that they're meeting other kids their age, and they're having play dates, and organizing birthday parties, all of those things. And then to try and fit that all into the wider day-to-day life, I found this really difficult. I spoke to other parents, and they also found it really difficult. In fact, I did some research with over 120 parents, and 70% of them found parenting really difficult or extremely difficult. VICTORIA: That's a lot of cognitive load on a person to manage all of these different things like school, and medical, and all the things you need to buy, [laughs] and what brands are the best. MICHELE: [laughs] Yeah, exactly. And actually, just trying to build this community around yourself is more difficult than you anticipate. So, for example, my kids went to nursery. And this is the time that they're starting to socialize and making these important connections that are really important to their development. And so as a parent, you're hearing from your three-year-old, oh, they've got this new best friend, but you have no idea how to connect to the parents of that child. And the nurseries daycare can't give out that information because, of course, there are privacy issues. So it's really difficult to make connections to other parents to be able to do these things like play dates. Organizing a birthday party, I found what you have to do is just take an invitation, give it to the nursery or the daycare center. Hopefully, they put it in the bags of the children that are friends with your kids, and then you kind of hope that they've got it and the right people are coming. You don't know who's coming to your kid's birthday party. And this just all seemed like there could be easy solutions to solve this to really build communities that center around your children. VICTORIA: And I love that the purpose of playroom is to really build that community of social support that you need for parents. You mentioned you started to do some research on what that would look like. And I'm wondering if there was anything that surprised you as a result of that research. MICHELE: Yes, I was quite surprised by...I suppose in some ways, it's reassuring actually as well that a lot of parents are going through similar struggles, struggling to connect to other families and not sort of in that way of, like, as you're...it's kind of a strange thing when you have kids because when they're very young, you can still socialize with your friends and people that you meet, maybe work colleagues. But as they get older, the focus becomes a little more around them and their friends, so making those connections are a little bit more difficult. So a lot of people struggle with that. A lot of people struggled with just keeping on top of everything. As you're saying, that cognitive load is very large; just trying to remember organizing dentist appointments, doctor's appointments, all of those things. It's a large cognitive load. And we've got enough tech now that we shouldn't have to...we should be able to put that load on to technology that can support us. VICTORIA: And so you feel like it was reassuring almost that this was a common problem [laughs], and it wasn't just you. MICHELE: Yeah, it's reassuring. It's always reassuring when you connect with other people to realize that they're going through similar things. It's not just you that's, you know, somehow not able to manage it all. But the other thing I found interesting is that there's a very large spectrum of how people feel about images and media associated with their children. So you've got a really wide spectrum of people who...some parents are very happy to share a lot about their children's lives, and their photos, and things that they're proud of on the major social media platforms. And other parents are a lot more guarded, and they don't want to share those pictures or have other people share them on platforms. So there's a massive spectrum of how people feel about the use of images and media associated with their children and also related to that of data associated with their children. VICTORIA: Yes, and I wanted to ask you about how privacy played into your planning on how you built the application. MICHELE: This was important to me because I had both that experience, and also, I started to become more aware of the darker sides of the major platforms where there's perhaps not as much protection for children and that, of course, children can't consent. So I found...having spoken to all of these parents, the spectrum was very wide on what people were willing to share, and how much they knew about how their data was used, and how much privacy they had on these platforms. I really wanted to ensure that that spectrum was reflected. In playroom, within the app, it's built so that you have control over how much privacy, how openly your images, for example, of your child, can be shared. So it can be from having any images to be shared with anybody. You know, maybe we're at a birthday party, and there are a lot of children there. So there are lots of pictures where your child is in there; some people are very happy for those to be shared. Others are not wanting that shared anywhere. So within the app, you have control over how far those sorts of pictures can be shared and with whom. But the premise of playroom is that you're essentially in a network, a community where you know everybody associated with your children. So it's not that sort of massively open network. It's very much closed and associated with just the people you know are surrounding your children. VICTORIA: That's great, and it's very relevant for me. I just got a new camera, and I offered to take pictures for my niece's birthday party last weekend. And now I have all these photos that, I'm not sure how to share them with the parents and in a way that would be secure and provide those options. So I can understand the value of what you've built here. MICHELE: Within playroom, there are bubbles. So if your child, for example, goes to nursery or daycare, they usually are in a room with children of a similar age, a playroom, that forms a bubble. So the nursery gives you a secure code that connects you to the other parents in that playroom. So that forms this bubble of parents associated with your children. So if you're taking photos at an event, so let's say you have a birthday party, you take photos. There are lots of other children in those photos. You can share those photos with the people in that bubble and in that bubble alone. And then, you can set your own personal media sharing settings so that you can make it clear to other parents that I don't want you to share this to wider social media. Watermark everything, very strongly watermarked or not downloadable. Or I'm happy for you to share it within playroom itself with other people that I know. So those settings are sort of adjustable depending on your preferences. VICTORIA: Were there any obstacles that you faced from maybe a technology or a process perspective with implementing or building the app? MICHELE: Yeah, so there are a couple of challenges. The biggest one is data and privacy. So, of course, security is a huge priority. That's going to be the center of priorities, really, so that everything is very, very secure. Parents, of course, are conscious of security surrounding their children. To be honest, as I was saying before, with sharing of media, it's quite on the spectrum, but either way, the priority is security and then privacy. So the use of data is an interesting one because a lot of traditional social networks, social media rely on the monetization of data. And again, this works on a spectrum where some parents flat out don't want any data associated with their children used or monetized in any way. Others are a lot more liberal about that. My personal view and from having spoken to a lot of parents, I think there's a good middle ground in which data is used in a responsible way for the purposes of actually benefiting parents in some way. So maybe it's the use of data rather than constant targeted ads, the use of data for the provision of services. Maybe within an area, you've got a high proportion of children there, and there needs to be better childcare provisions or play activity provisions. VICTORIA: That makes sense. So make the data more relevant in the way that it's used to provide better services to parents, right? MICHELE: Exactly, yeah, rather than that strict sort of targeted advertising. VICTORIA: That makes sense. And so you've had to adjust your plan for monetization based on the needs of your users regarding privacy and security, and we love to hear that founders really care about privacy and security at thoughtbot, so... MICHELE: Yes, exactly. Yeah, I think it's really, really important, and even more so now. There's really this acknowledgment of the very large open networks that they were never really built around children, of course. I mean, why would they be? But there's been a lot of controversy recently over parents having images and their children featured in videos and things online. The child accounts run by parents have millions of followers and videos, images, and things get saved thousands of times and commented in ways that are a little uncomfortable. So there is this sort of growing feeling that these large open networks...mostly parents just don't really know. And they do...when you become a parent, you're really excited, and you're proud, and you want to share these things with the world. And you perhaps don't think about those kinds of darker sides of things. That's really coming into the forefront now. So I think a sort of more closed community-based network is important. VICTORIA: I agree. I've spent some time volunteering for organizations that work with children and privacy and human trafficking situations. And when you start to understand really how dark it can get for children, maybe too dark for this podcast, but security and privacy becomes the penultimate goal. MID-ROLL AD: thoughtbot is thrilled to announce our own incubator launching this year. If you are a non-technical founding team with a business idea that involves a web or mobile app, we encourage you to apply for our eight-week program. We'll help you move forward with confidence in your team, your product vision, and a roadmap for getting you there. Learn more and apply at tbot.io/incubator. That's tbot.io/incubator. VICTORIA: You mentioned learning all of this as part of your journey on building the app. I'm curious what you brought from your background in neuroscience into the creation of the app and maybe how that played into how you built certain behaviors and things into the features. MICHELE: Yeah, it's kind of interesting. So my neuroscience background, I guess, has really informed how I think about child development and brain development and the importance of the developmental stages of socializing with children. It was always at the front of my mind, and one of the things that really spurred me on to create this is really knowing that as children are developing, they are learning these really important social skills, and I just wanted to foster that as much as possible. And I thought, you know, it's actually really difficult to foster that social side of things if you don't have a community naturally around you. So I guess that's the main way that it's fed into my thinking about playroom. Other than that, I'm not too sure, actually. I think it's early stages, but I think it will probably influence some of the UX decisions, which is a big part of what I do in my day job, not the UX itself but the kind of psychology and neuroscience behind certain behaviors and how we interact with technology. VICTORIA: I love to see founders and people who find their way into technology roles that usually come from a wide variety of backgrounds. And for me, neuroscience makes a lot of sense when you're doing these studies. Because you really are even, you know, from a scientific perspective, setting up a study and experiment to see how people will react to it. And you're proving your theory of is this how people will actually relate and connect inside the application? MICHELE: Yes, absolutely, yeah. A lot of my job is data science. So I'm really excited to just get data in that I can really make decisions based on. I'm very much a kind of evidence-based person from my science background definitely. VICTORIA: Yes, excellent. And maybe you could tell me more about a decision you had to make maybe early on in the development of the app that was challenging for you or you had to put a lot of time and thought into. MICHELE: One of the things I found tricky, I suppose, is kind of being a solo founder, actually. Early on, I spent a lot of time trying to find a co-founder, and I really wanted somebody like a technical co-founder that could kind of fill the gap that I have. I don't have any formal experience in app development or anything like that, although a lot of my job involves coding and the data science side of things. Yeah, I spent a lot of time trying to find a technical co-founder and just really struggled to find somebody that had interest, and passion, and vision that would work for playroom. And so, after a while and after speaking to a couple of mentors, I decided to save that energy of trying to find somebody and just go at it alone for now. So, you know, open to finding somebody who has a similar vision for it, but yeah, that was really a difficult thing; it always is being a solo founder. But I just am really passionate about it and kind of filled the gaps with mentors and with advisors who can help me along the way. VICTORIA: That's so interesting. I think deciding about who you're going to bring into your inner circle when you're passionate about an idea sounds like a very difficult decision. MICHELE: Yeah, it is, yeah, and it's a strange sort of space as well because by no means does it need somebody who has children or has an interest there. But I think it does help with the passion because it's a really specific problem. And yeah, I just haven't found anyone yet. VICTORIA: But you have found several mentors. That sounds like it's meeting your needs in that way for now. How did you go about finding the right people to give you advice in that way? MICHELE: A combination really of just kind of stalking through LinkedIn and connecting to people, and just chatting to people, and then also through networks of other founders, and going through accelerators, things like that where I'm kind of formally introduced to mentors. They've maybe given me warm introductions, amazing women's network where people have either given warm introductions or volunteered themselves to give advice. That's been really, really great. You sort of feel like you've got a community there already. VICTORIA: That's great. And did you focus on local groups in the UK, or did you go just online virtual groups? Which was easier for you? MICHELE: A combination. So I went through an accelerator that was based in London, and so that introduced me to a few people more locally and quite a wide network, actually. I also joined a women of color network called Founderland, and they're based in Berlin. And they are a really amazing support network that has quite a wide international reach but really gives you a lot of support and guidance and is completely free and just really feels like a nice, supportive community. VICTORIA: Sounds like building a community of founders is as important as building a community for people raising children, right? [laughs] MICHELE: Yeah, definitely. [laughs] Yeah, I think so. I think any aspect of your life that is difficult benefits from a community really because, in almost all areas, there are people who have gone through something before that want to make it easy for you or who are going through something at the same time and want somebody to talk to or to support each other. VICTORIA: The most important thing we can be doing is building community. You have your full-time position, and then you also have your children that you're raising, and you are founding this company. How do you make time for yourself and for your own peace of mind in the week? [laughter] MICHELE: With great difficulty, yeah, [laughter] and a very supportive partner. It's a real struggle, and things sometimes have to be slower than I would like. I've got an amazing team of app developers who are absolutely brilliant and are usually chasing me rather than me chasing them, which is always really great. Again, a fantastic support network, a big community of other parent founders who know how difficult it all is. And then it's just like a lot of working evenings, taking a day off to focus on things. VICTORIA: Yes, we're learning a technique at thoughtbot with energy coaching and coaching people on when to take breaks and how to make sure you have time for lunch and take vacations, and all of that, which I think is important for your long-term ability to maintain your momentum. MICHELE: Yes, definitely. VICTORIA: But I've heard from many founders, you know, the support network is one of the most important things to be able to balance everything. MICHELE: Yes, it really is, yeah. I am susceptible to burnout, and I know it now. And I should know better because I know the kind of neuroscience of it as well. And so I do have to be really careful. I don't push myself too much. One of the good things actually, you know, my kids are school age now. So they have these half-term breaks. They have regular breaks from school, and then summer holidays, of course, Christmas, all of that, and that sort of forces a time for you to break and then spend really quality time with the kids. So it's really, really good in that way. VICTORIA: I appreciate kind of enforced time off. [laughs] MICHELE: Yeah, I know. [laughs] VICTORIA: And really committing to it. It makes sense, yeah. [laughter] MICHELE: I just realized that. VICTORIA: UK people are better at that than I think in the U.S. generally, but it's certainly something I strive for. Sometimes even just going to a place where there's no internet access, [laughs] so good luck trying to reach me. MICHELE: Oh yes, yeah. VICTORIA: Well, tell me more about your interaction with your developers' team. And you mentioned how wonderful they are. What is your communication patterns with them? Do you have regular meetings set up, or what is that like? MICHELE: So it's a company that I met through YC summer school program, got sort of chatting to them. They're really, really great with communication. So we communicate on Slack every day, get updates, have little videos of updates, and work through any issues, and then kind of weekly meetings. And yeah, it's been a really, really positive experience. I also have recently...on top of working full-time, and doing this, and having two kids I recently had...my husband was very ill and in hospital for two months just over Christmas. And then he came out of hospital for three days over Christmas, but then I was ill and in hospital for a month. So it's been absolutely crazy just trying to look after the kids and get work going, all of this. And they've been really consistent throughout. They've just kept everything ticking away. So that's been really, really great to have that, knowing that that continues on when I've had lots of life things going on. VICTORIA: That ability for the team to manage themselves and be proactive in their communication is something I would always advise founders to look for in a development partner. You want to see that activity on a daily basis and see the product fairly often as well. You don't want to be surprised three months later with what they built and have it not be correct, what you're looking for. MICHELE: Yeah, it's literally been back and forth of details that need ironing out. There's always a list that I can get to in my time, and there's the acknowledgment that I'm kind of working around a full-time job. VICTORIA: Well, what are you most excited about in your features roadmap that you could share with us? MICHELE: I'm so excited by all of it. I have two things that I'm really excited about. The first is the bubble, so that's just the ability to immediately connect to parents in different contexts. So I can immediately connect to all the parents in my child's nursery. It makes it really easy to organize birthday parties, play dates in other contexts as well. Say, for example, my daughter started a gymnastics course. We pay for the whole gymnastics course. She then didn't really want to do it because she didn't know anybody there. And so I think we managed about two lessons before she just really didn't want to do it anymore. And, again, I had this sort of feeling that if we were able to talk to the other parents and encourage some friendships and things, that would be really helpful for her. And just as things go along, the kids do become friends, and it's nice to be able to connect to the other parents in those contexts as well. Same thing for summer camps, any kind of setting where your kids are making new friends. And you want to get to know the parents of those friends and be able to connect to other families. And then the other feature that I'm really excited about is just being able to with one click find things nearby, toilets, cafes, supermarkets really easily. Usually, you have, one, holding a baby, pushing a pram, toddler has to suddenly use the toilet, no idea where to find one. So just being able to one click of a button find that really near me, I think, will be really, really useful. So I'm really excited about that feature and just seeing it working nicely. VICTORIA: Great. And then you'll get to use it in real life. [laughs] MICHELE: Yeah, exactly. VICTORIA: Build the change you want to see in the world. I love it. And then, if you could go back in time and give yourself some advice when this all started now that you have this hindsight, what would you tell yourself? MICHELE: I probably would tell myself to just keep at it. Maybe don't waste time trying to fill perceived gaps in your own abilities because I can learn stuff, and I can find support, and advisors, and mentors. So probably, that's what I would focus on. I spent a lot of time and energy trying to find a co-founder that would fill these gaps that I felt like I had. I'd come from an academic and a neuroscience background, less commercial experience, so I worried about needing somebody who would have that business side, needing somebody to have that technical side. But, in fact, I've got a lot of those skills from my career and from my jobs anyway. I can learn a lot. I managed to get myself a Ph.D. in neuroscience from Cambridge University, so I can probably pick things up. [laughs] And I also can fill in any gaps with really great mentors and advisors. VICTORIA: I love that. And I love that this problem that you had drove you to find the solution and to push forward even if you didn't know all the answers. MICHELE: Yeah. Exactly, yeah. VICTORIA: Wonderful. What does success look like for playroom in the next six months or five years? MICHELE: Six months is having the app in some of the nurseries that we've been working with so out with parents and making those communities. In five years, it's having hundreds of thousands of parents in communities and having them supported, connected to other parents, feeling like they have a safe space for themselves and their kids. VICTORIA: I love it. And maybe you can mention even more about what the impact that can have on a parent who might be struggling to keep it all together. MICHELE: Oh, a huge impact. So I know this personally because my husband was ill, and then I was ill. So we had three months, you know, a five-year-old and a two-year-old, each of us solo parenting and each of us with quite serious illnesses. And it was incredibly difficult. I was lucky enough that my next-door neighbor her kids are the same age and go to the same school. And actually, that's when I met them. So even though we were neighbors, we hadn't even met. But when she found out that my husband was unwell and I was looking after the kids on my own, really stepped up and helped look after my daughter, take some of the burden off of doing all the parenting on my own, plus visiting my husband in the hospital. And then reached out to a wider community within the area, like her friends that she knows from the school, and these parents really stepped up and helped me so much, like bringing food around and being that community that everybody wants and needs. And I feel like a lot of it came about sort of accidentally because I was in this really difficult situation, but it helped me so much. I can't even describe how much. And I just think if I can do that for lots of other parents, it will make a huge impact because it is really difficult for some people, for a lot of people. VICTORIA: I think the impact can't be underestimated enough. I know recently I signed up for Big Sisters and Big Brothers San Diego, so it's mentorship for children in the local county. And taking some of the training courses, they say in the U.S. alone, there are 3 million children who are just neglected or abused every year. Neglect could come from not having that social support network and not being able to look after your kids or not having other ways to connect with parents to get the support you need. So I think it's a really amazing product that you're building. MICHELE: Oh, thank you. Yeah, I completely agree that there are so many ways that it can help and actually in just bringing together communities just, sort of locally centered around your children. And yeah, as you're saying, that neglect when there are situations where people actually...parents can't cope or need help and won't reach out. It's a sort of more natural way to have a community around you. VICTORIA: Are there any other final takeaways you'd like to leave for listeners? MICHELE: Well, I guess for the parents, parenting is hard, and it can be lonely, and that's okay. Just try and reach out to people as much as you can and go join playroom. VICTORIA: Wonderful. Thank you so much, Michele. You can subscribe to the show and find notes along with a complete transcript for this episode at giantrobots.fm. If you have questions or comments, email us at hosts@giantrobots.fm. And you can find me on Twitter @victori_ousg. This podcast is brought to you by thoughtbot and produced and edited by Mandy Moore. Thank you for listening. See you next time. ANNOUNCER: This podcast is brought to you by thoughtbot, your expert strategy, design, development, and product management partner. We bring digital products from idea to success and teach you how because we care. Learn more at thoughtbot.com. Special Guest: Michele Veldsman.

Meet Jonah Hanig, Founder and CEO of Rove — a premium portfolio of luxury Airbnbs designed for discerning travelers. Jonah grew up in the Chicago suburbs and always had a knack for tinkering with business ideas. After going to school in New York, Jonah decided to pursue his dream of becoming an entrepreneur and was fortunate enough to get accepted to Y Combinator — the most prestigious of start-up accelerators in the world.  Fun fact — Airbnb is a YC company! Soon after being accepted to YC covid hit…and, well, Jonah's startup wasn't immune to the disruption that all of us felt in those early days. But it wasn't long before Jonah had another idea…and that idea was to offer a Ritz-Carlton-like experience within the context of a collection of highly-curated short-term rentals. Tune in to hear the story of: Where the idea for Rove came from  How Rove is building the Ritz-Carlton of STRs Why Rove is also building a Zillow for STR investors  How Rove has thought about differentiation in an increasingly-crowded marketplace This episode is brought to you by our friends at Guesty for Hosts... Will you send them a quick message thanking them for being a sponsor?  You can email them here or DM them on social media here! While there are many property management softwares on the market, I always encourage our listeners to check out Guesty For Hosts.  Guesty's channel manager centralizes reservations across Airbnb, Vrbo and Booking.com to stay on top of your listings without having to hop back and forth between channels. Guesty's automation tools enable you to connect with guests in a meaningful, creative, and instant fashion. Guesty's new and improved Website Builder allows you to create your own branded booking website in just minutes…allowing you to grow your brand and increase your direct bookings.  And finally, Guesty is positioned well to grow with you. As your business grows, you can grow with Guesty For Pros, unlocking new features and offerings designed for larger portfolios. So here's the deal.  If you're an. STR host without a PMS system or a host looking at exploring a new one, I've got a treat for you. The team at Guesty is giving Behind the Stays listeners and Sponstayneous subscribers $20 off an annual or monthly plan of Guesty For Hosts when they use the discount code “SPONSTAYNEOUS” when signing up for a free 14 day trial - no credit card, set up fee, or commitment required  — and cancel anytime if you don't love it.   Guesty For Hosts — they're the bestie of top-rated STR super hosts!  About the Show Behind the Stays is brought to you twice a week by Sponstayneous — a free, biweekly newsletter that brings subscribers the best last-minute deals and upcoming steals on Airbnb.     You can subscribe, for free, at www.sponstayneous.com.  Behind the Stays is hosted by Zach Busekrus, co-founder of Sponstayneous, you can connect with him on Twitter at @zboozee.

Trill Withers and Tom Brady Do Standup in this edition of the Trill Withers Show Best of The Week. Laugh along with Trill Withers, Coley Mick, Scoob and YC as they tag along with the 6x Super Bowl Champion Tom Brady on his latest endeavor to conquer the Stand Up Comedy Industry!! Also included is Scoob's theory that Goofy had hoes and an infamous stand up comedy hack that could take the world by storm. The gang then reacts to Louisville's shitty year....literally, celebrate Snuffy's 1 year anniversary of getting the 'rona at a Chuggy concert before diving into some conspiracies surrounding the Mexican President seeign an elf and the impending doom scientists are unaware of with the sun. To round things out Trill gives an unexpected movie review, the gang celebrates the return of the double down sandwich and the Mick Man stands next to Bryce Young, which obviously isn't good for the short man's brand.    FULL VIDEO EPISODE: https://youtu.be/_GOyWjvIWiY

Brought to you by Linear—The new standard for modern software development. | Eppo—Run reliable, impactful experiments. | Pando—Always-on employee progression.—Gustaf Alströmer is a Group Partner at Y Combinator, where he's worked with over 600 startups in his 6.5 years there. He's also a fellow Airbnb alumnus and even started the original Airbnb growth team. In today's podcast, Gustaf discusses common reasons startups fail and how he helps coach founders on avoiding these mistakes. He explains the attributes that the best founders tend to have, and signs that a company has potential. We also cover the growing space of climate tech, for which Gustaf has a huge passion and where he's already had an incredible impact. He shares some key areas of innovation and investment in climate tech, some notable companies he's helped fund, and where he sees potential going forward.Find the full transcript here: https://www.lennyspodcast.com/lessons-from-working-with-600-yc-startups-gustaf-alstromer-y-combinator-airbnb/#transcriptWhere to find Gustaf Alströmer:• Twitter: https://twitter.com/gustaf• LinkedIn: https://www.linkedin.com/in/gustafalstromer/Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• Twitter: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/Referenced:• Airbnb tweet: https://twitter.com/gustaf/status/1580330162725347330• Startups Are an Act of Desperation: https://blog.eladgil.com/p/startups-are-an-act-of-desperation• The 18 Mistakes That Kill Startups: http://www.paulgraham.com/startupmistakes.html• Do Things That Don't Scale: http://paulgraham.com/ds.html• Marc Andreessen: https://a16z.com/author/marc-andreessen/• How to Talk to Users: https://youtu.be/z1iF1c8w5Lg• How to Get Your First Customers: https://youtu.be/hyYCn_kAngI• Pachama: https://pachama.com/• Request for Startups: Climate Tech: https://www.ycombinator.com/blog/rfs-climatetech• Climate Draft: https://www.climatedraft.org/• Seabound: https://www.seabound.co/• Fleetzero: https://www.fleetzero.com/• Unravel Carbon: https://www.unravelcarbon.com/• CarbonChain: https://www.carbonchain.com/• Sinai: https://www.sinaitechnologies.com/• Enode: https://enode.com/• Statiq: https://www.statiq.in/• Heart Aerospace: https://heartaerospace.com/• The 100% Solution: A Plan for Solving Climate Change: https://www.amazon.com/100-Solution-Solving-Climate-Change/dp/1612198384• Without a Doubt: How to Go from Underrated to Unbeatable: https://www.amazon.com/exec/obidos/ASIN/1982147903?tag=simonsayscom• Emily in Paris on Netflix: https://www.netflix.com/title/81037371• Everything Everywhere All at Once on Showtime: https://www.sho.com/titles/3493875/everything-everywhere-all-at-once• How to Apply and Succeed at Y Combinator, by Dalton Caldwell: https://www.youtube.com/watch?v=8yiOcCPvyNE• Y Combinator on YouTube: https://www.youtube.com/c/ycombinatorIn this episode, we cover:(00:00) Gustaf's background(04:15) What made Airbnb so special(07:21) How culture interviews and hiring founders contributed to Airbnb's success(10:31) Motivations for starting companies(13:17) Why Gustaf helps founders understand their motivations(14:13) Reasons you should not start a company(16:03) The magic that happens at YC office hours(20:45) Why founders in coworking spaces should schedule time to talk (21:36) Questions Gustaf asks founders(22:26) Common reasons startups fail(26:23) Getting over the fear of rejection (27:57) The importance of solving for pain points and why you should watch users(34:21) The value of having a technical co-founder(37:42) How founders without technical expertise have succeeded(40:46) Attributes of the most successful founders(44:57) Why it's hard to predict success and how YC advises against failures(46:59) Indications of potential for success(50:03) Speed vs. quality(51:11) Confidence vs. humility(52:48) Execution and tactics vs. strategy(54:36) Autocratic vs. collaborative-driven founders(56:27) Why you should focus on product first(59:03) The economic incentive for investing in climate tech(1:02:16) The clean-tech bubble of 2008(1:04:59) Why you don't need to be super-scientific to work in climate tech(1:06:51) Areas of climate tech and promising companies(1:12:27) What's going well in the climate-change space(1:16:49) Lightning roundProduction and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

119. Welcome to the Alfalfa Podcast

Are you tired of losing potential customers because of your mobile paywall? In this video, we'll go over some tips and tricks for optimizing your paywall for a better user experience and increasing your in-app subscriptions. We'll cover topics such as placement, design, and overall usability to help you increase conversions and boost your revenue. By following these strategies, you can make the most of your mobile paywall and keep your customers coming back for more. Jake Mor is Co-Founder & CEO at Superwall. Previously he built and grew FitnessAI to 5M in revenue over 4 years. Went through YC for both FitnessAI and Superwall, and raised a seed round for each. Learn more: http://jakemor.com/ App Audits: https://play.google.com/store/apps/details?id=com.kalantos.shakelight https://apps.apple.com/us/app/bells-by-iron-revival/id1554919084 You can watch this video: https://youtube.com/live/h_9dyOe3ufA Work with us to grow your apps faster & cheaper: http://www.appmasters.com/ SPONSORS Growing your app beyond a certain point by yourself is almost impossible as the your beloved baby must mature and transform into a company. Bluethrone's new partnership model is better than a VC Investment: It gives you cash in hand, your life back and the right to see your app adopted by millions, and making millions. Got an app idea that you think will be the next unicorn? But you don't know what to do next? With more than 15 years of experience creating software, B7dev.com can help you out. Schedule a free 1-hour call by going to B7Dev.com and let them know that Steve sent you. Tired of overpaying for App Store Optimization? Get unlimited ASO and app marketing support to increase your keyword rankings, downloads, and revenue. Learn more at ASO Masters. *************** Follow us: YouTube: AppMasters.com/YouTube Instagram: @stevepyoung Twitter: @stevepyoung TikTok: @stevepyoung Facebook: App Masters *************** --- Send in a voice message: https://anchor.fm/app-marketing-podcast/message

YC's Kat Mañalac wants to change the way you think about launching. In her talk, she shares the multitude of ways to launch and get attention for your product, with tangible strategies and examples from companies like Airbnb. Apply to Y Combinator: https://www.ycombinator.com/apply/

James Mikrut is Founder of Payload CMS, the React & TypeScript headless CMS. Their open source project, payload, has over 9K stars on Github and provides a Headless CMS and Application Framework built with TypeScript, Node.js, React, and MongoDB. Payload has raised over $5M from investors including Gradient Ventures and YC. In this episode, we discuss Payload's early guerilla marketing tactics, listening to your community to inform your monetization model, what developer-first really means & more!

HAVE YOU SUBSCRIBED TO "Before the Bell?" https://www.youtube.com/channel/UCFmyKJKseEMQp1d14AjvMUw (2/22/23) The long-awaited market correction has arrived, begging the question of whether markets can firm-up and hold levels here. Look at correction as an opportunity for portfolio rebalancing; St. Louis Fed Pres. James Bullard says interest rates need to exceed 5% to battle inflation; markets have rallied on the notion earnings have troughed, and that the worst is behind us. Bullard admits the economy is stronger than first thought, per economic data. The problem is economic data is very "laggy," and is often revised after the fact: Not a good metric for investors. The level of liquidity in markets is still high; what do the Yield Curves say? YC-reinversion is key. The Roberts' Family saga of Thump-thump the Bunny; men vs women w advanced degrees; credit score dating, and holiday rankings; market response to Bullard commentary; Walmart & Home Depot reports: consumption is decreasing; Bed Bath & Bodyworks; Jim Cramer's Six Things that Need to Happen before the sell-off can end; why buy bonds? Pay off your mortgage with your 401-k? No. How to get better yields on cash. SEG-1: Correction Day has Come SEG-2: When the Economy is Stronger Than First Thought SEG-3: Thump-thump the Bunny; James Bullard commentary SEG-4: Pre-market Commentary; Jim Cramer's Six Things SEG-4B: Why Invest in Bonds Now? Hosted by RIA Advisors Chief Investment Strategist Lance Roberts, CIO, w Senior Advisor, Danny Ratliff, CFP Produced by Brent Clanton, Executive Producer -------- Watch today's show on our YouTube channel:   https://www.youtube.com/watch?v=v21rwpoHehE&list=PLVT8LcWPeAugpcGzM8hHyEP11lE87RYPe&index=1&t=2852s -------- The latest installment of our new feature, Before the Bell | "Don't Chase Stocks Quite Yet" is here: https://www.youtube.com/watch?v=oxcyo-tqt4I&list=PLwNgo56zE4RAbkqxgdj-8GOvjZTp9_Zlz&index=1   --------  Our previous show is here: "Is Sticky Inflation Entrenched in Economy?" https://www.youtube.com/watch?v=ucqByxZmSPs&list=PLVT8LcWPeAugpcGzM8hHyEP11lE87RYPe&index=1&t=7s -------- Articles mentioned in this podcast: "Gold Investors Are Betting on the Fed" https://realinvestmentadvice.com/gold-investors-are-betting-on-the-fed --------- Register for the next Lunch & Learn on Raising Money Smart Kids (2/23/23): https://us06web.zoom.us/webinar/register/8516736369321/WN_u6P-EAklT0iIgAXc1ChgrA -------- Get more info & commentary:  https://realinvestmentadvice.com/newsletter/ -------- SUBSCRIBE to The Real Investment Show here: http://www.youtube.com/c/TheRealInvestmentShow -------- Visit our Site: www.realinvestmentadvice.com Contact Us: 1-855-RIA-PLAN -------- Subscribe to SimpleVisor: https://www.simplevisor.com/register-new -------- Connect with us on social: https://twitter.com/RealInvAdvice https://twitter.com/LanceRoberts https://www.facebook.com/RealInvestmentAdvice/ https://www.linkedin.com/in/realinvestmentadvice/ #InvestingAdvice #InterestRates #MarketCorrection #FederalReserve #Inflation #StickyInflation #Recession #Markets #Money #Investing  

HAVE YOU SUBSCRIBED TO "Before the Bell?" https://www.youtube.com/channel/UCFmyKJKseEMQp1d14AjvMUw (2/22/23) The long-awaited market correction has arrived, begging the question of whether markets can firm-up and hold levels here. Look at correction as an opportunity for portfolio rebalancing; St. Louis Fed Pres. James Bullard says interest rates need to exceed 5% to battle inflation; markets have rallied on the notion earnings have troughed, and that the worst is behind us. Bullard admits the economy is stronger than first thought, per economic data. The problem is economic data is very "laggy," and is often revised after the fact: Not a good metric for investors. The level of liquidity in markets is still high; what do the Yield Curves say? YC-reinversion is key. The Roberts' Family saga of Thump-thump the Bunny; men vs women w advanced degrees; credit score dating, and holiday rankings; market response to Bullard commentary; Walmart & Home Depot reports: consumption is decreasing; Bed Bath & Bodyworks; Jim Cramer's Six Things that Need to Happen before the sell-off can end; why buy bonds? Pay off your mortgage with your 401-k? No. How to get better yields on cash. SEG-1: Correction Day has Come SEG-2: When the Economy is Stronger Than First Thought SEG-3: Thump-thump the Bunny; James Bullard commentary SEG-4: Pre-market Commentary; Jim Cramer's Six Things SEG-4B: Why Invest in Bonds Now? Hosted by RIA Advisors Chief Investment Strategist Lance Roberts, CIO, w Senior Advisor, Danny Ratliff, CFP Produced by Brent Clanton, Executive Producer -------- Watch today's show on our YouTube channel: https://www.youtube.com/watch?v=v21rwpoHehE&list=PLVT8LcWPeAugpcGzM8hHyEP11lE87RYPe&index=1&t=2852s -------- The latest installment of our new feature, Before the Bell | "Don't Chase Stocks Quite Yet" is here: https://www.youtube.com/watch?v=oxcyo-tqt4I&list=PLwNgo56zE4RAbkqxgdj-8GOvjZTp9_Zlz&index=1 -------- Our previous show is here: "Is Sticky Inflation Entrenched in Economy?" https://www.youtube.com/watch?v=ucqByxZmSPs&list=PLVT8LcWPeAugpcGzM8hHyEP11lE87RYPe&index=1&t=7s -------- Articles mentioned in this podcast: "Gold Investors Are Betting on the Fed" https://realinvestmentadvice.com/gold-investors-are-betting-on-the-fed --------- Register for the next Lunch & Learn on Raising Money Smart Kids (2/23/23): https://us06web.zoom.us/webinar/register/8516736369321/WN_u6P-EAklT0iIgAXc1ChgrA -------- Get more info & commentary: https://realinvestmentadvice.com/newsletter/ -------- SUBSCRIBE to The Real Investment Show here: http://www.youtube.com/c/TheRealInvestmentShow -------- Visit our Site: www.realinvestmentadvice.com Contact Us: 1-855-RIA-PLAN -------- Subscribe to SimpleVisor: https://www.simplevisor.com/register-new -------- Connect with us on social: https://twitter.com/RealInvAdvice https://twitter.com/LanceRoberts https://www.facebook.com/RealInvestmentAdvice/ https://www.linkedin.com/in/realinvestmentadvice/ #InvestingAdvice #InterestRates #MarketCorrection #FederalReserve #Inflation #StickyInflation #Recession #Markets #Money #Investing

Michael Ma is the founder & CEO of CreatorDAO, a decentralized community that accelerates creators with capital & technology. He is also a VC and founded Liquid 2 Ventures alongside legendary football player Joe Montana after helping First Round Capital launch Dorm Room Fund in Boston. Prior to venture capital, Michael got his MBA at Harvard Business School and before that sold his startup TalkBin to Google 7 months after cofounding the company with Qasar Younis. In this conversation we discuss: How Michael started & sold TalkBin to Google in 7 months Choosing to sell vs. scale your startup How he met Joe Montana (and started a VC firm with him) What he got out of his time at Harvard Business School The value of an MBA degree YC vs. Harvard Business School What he looks for as an investor What is CreatorDAO And much more

This week our host Brandi Starr is joined by Brendan Dell, Messaging Expert & Tech Executive at Brendan Dell. A positioning and messaging expert to top technology brands, Brendan's clients include Expedia, ADP, HP, YC and 99 Start Ups portfolio companies, and many others. His book the 12 Immutable Laws of High-Impact Messaging shares rules for standing out in crowded markets. Brendan's new course, $1B Pitch, examines the 8 elements of $1B pitches. His podcast Billion Dollar Tech reaches founders, executives, Venture Capitalists and Private Equity investors globally. In this week's episode of Revenue Rehab, on the couch, Brandi and Brendan tackle the critical issue of Brand Positioning: Achieving Growth, Even with Non-Mission Critical Offerings. Links: Get in touch with Brendan Dell on: LinkedIn Instagram Brendan Dell Billion Dollar Tech Podcast Subscribe, listen, and rate/review Revenue Rehab Podcast on Apple Podcasts, Spotify, Google Podcasts , Amazon Music, or iHeart Radio and find more episodes on our website RevenueRehab.live

Mike Duboe is a Partner @ Greylock where he sits on the board of Builder, Inventa, Novi, Pepper, Postscript. Prior to entering the world of venture, Mike was the first in-house growth hire at Stitch Fix, where he built and led the Growth organization helping take the company through to their IPO. Before Stitchfix, Mike was the first growth hire at Tilt, where he built and oversaw multiple teams, including analytics, marketing, community, and growth product. He also served on YC's growth advisory council and was a growth lecturer at Reforge. In Today's Episode with Mike Duboe We Discuss: 1.) Entry into the World of Growth: How Mike made his way from consulting at Bain to leading the growth team for Stitchfix? What did Mike believe about growth 5 years ago that he no longer believes? What does Mike know now that he wishes he had known when he entered the world of growth? 2.) When and Who To Hire: How does Mike define the term "growth team"? What is their core role and responsibility? Should the first growth hire be a senior growth lead or a more junior analytical lead? What data foundations should founders have in place prior to their growth hire joining? What are the most common ways founders fail to prepare for their first growth hires joining? When does Mike believe is the right and crucial time for growth hires to be made? Should these growth hires join existing teams or be put in standalone "growth teams"? 3.) The Hiring Process: How to Detect and Win the Best: How should founders structure the interview process for their first growth hires? What are the best questions to ask to reveal the quality of a potential growth hire? What are the right case studies and tests to do to assertain their quality? What are the different levels of comp package for different growth execs? What are the single biggest mistakes founders make in the hiring process? 4.) Mastering Paid Marketing: Lessons from Stitchfix: Why is CAC/LTV a BS metric? What should be used instead? When is the right time to start really engaging with paid marketing? How should marketing and growth teams determine budget on a per channel basis? How much is the right mix between paid vs organic? What are Mike's biggest lessons from making paid work so well at Stitchfix? What are the single biggest mistakes Mike sees founders make today with paid marketing?  

Trill Withers EXPOSES Groundhog Day in this edition of Best of The Week!!! Punxsutawney Phil might have had his big day capped off by an induction into the Meteorologist Hall of Fame, but Trill Withers, Coley Mick, Scoob, Jam and YC are here to put an end to the propaganda he spreads every year! They also react to some of the best ad reads of all time and the story of Pat O'Dea The Kangaroo Kicker, before putting Jam up to his newest food challenge, The Perpetual Stew. Coley Mick tells the story of when his daughter exposed the US Military for being secret pirates and the gang answers the question of whether or not stolen valor should be accepted by your wife. Finally, the gang sits down with CBS executives and Tony Romo for an intervention before reacting to a terrifying invisible fire and a "failed" Satchel Paige gimmick. With another hilarious week in the books be sure to like and subscribe for more Trill Withers Show content.   FULL VIDEO EPISODE: https://youtu.be/cvunkwKbrcA Like, Subscribe AND Watch LIVE on YouTube M-F 12-3ET to chat along with us and check out the clips for our best moments so far! Give @UnderdogFantasy a follow as well for more from our buds! CUT TO IT WITH STEVE SMITH SR. AND COLEY MICK: Cut To It - YouTube COLEY AND KLEW'S START/SIT SHOW SUNDAY 12-1ET: Underdog Fantasy - YouTube

On this episode of The Tech Trek, host Amir Bormand speaks with Tony Dong, the Senior Director of Engineering at Rippling. Tony is a major advocate for maintaining a startup mindset regardless of your team's size. He and Amir also discuss strategies for effectively scaling a team. Notes 04:29 - Tony explains why he prefers to maintain a startup mindset even as his teams grow. 09:03 - How can engineering leaders stay connected with their teams as companies start to scale? 12:41 - Tony shares his experiences dealing with changing team structures. 16:34 - Best practices for engineering leaders who are scaling their teams for the first time. 18:21 - What are the best ways to preserve quality and culture as a company grows? About the guest: Tony Dong is a Senior Director of Engineering at Rippling, leading Platform and Core HR Products. Prior to Rippling was the co-founder and CTO of a YC-backed startup. https://www.linkedin.com/in/tonydong3/ https://twitter.com/TonyDong3 ___ Thank you so much for checking out this episode of The Tech Trek, and we would appreciate it if you would take a minute to rate and review us on your favorite podcast player. Want to learn more about us? Head over at https://www.elevano.com Have questions or want to cover specific topics with our future guests? Please message me at https://www.linkedin.com/in/amirbormand (Amir Bormand)

Anh-Tho Chuong is Co-Founder & CEO of Lago, the open source metering and usage-based billing platform. Lago's underlying project, also called Lago, has 2K stars on GitHub and a Slack community with hundreds of members. Lago is a YC company from the S21 batch. In this episode, we discuss the state of billing today and why a hybrid and open approach makes sense for many companies, positioning as an "open source alternative to...", deciding what content is worth creating (ie. if your users ask the same question 5x, then blog about it), going through YC as an open source company & more!

Trill Withers SAVES The M&M Spokescandies in this HEROIC Best of The Week!!! Join Trill Withers, Coley Mick, Scoob, Jam Packard and YC for this best moments of the Trill Withers Show mash up!! They open the show with the devastating news that M&Ms have been cancelled, launching a mission to save the Spokescandies and Rooty The Root Bear. Following that they head all over the map, first to Venezula to see Ronald Acuña's spectacular home run trot then to the Domincan to see Framber Valdez and his tank of loud sounds and then back to America to marvel at our totally necessary defense vehicles and vests. Once finally back in the comfort of the quad box they react to Marlon Humphrey's DISGUSTING take on pizza, some incredibly entertaining street games of skill and Jerry Rice's obnoxiously ugly neck piece. Finally, we wrap up this conglomeration of clips with a look at the Trill Withers Night Show where the gang told some old stories of their college days.  FULL VIDEO EPISODE: https://youtu.be/FZcALMvV0hk Like, Subscribe AND Watch LIVE on YouTube M-F 12-3ET to chat along with us and check out the clips for our best moments so far! Give @UnderdogFantasy a follow as well for more from our buds! CUT TO IT WITH STEVE SMITH SR. AND COLEY MICK: Cut To It - YouTube COLEY AND KLEW'S START/SIT SHOW SUNDAY 12-1ET: Underdog Fantasy - YouTube

How do you find a co-founder and build a great partnership? YC's Catheryn Li (who also built our Co-Founder Matching tool) and Visiting Partner Divya Bhat cover the importance of having co-founders, how to get & vet one, and the ways to build a successful working relationship with them. Apply to Y Combinator: https://www.ycombinator.com/apply Looking for a co-founder? Sign up for Co-Founder Matching: https://www.ycombinator.com/cofounder-matching

Trill Withers FAILS at Wheel of Fortune in this hilarious Best of The Week!! Join Trill Withers, Coley Mick, Scoob, Jam Packard and YC in this compilation of the best moments of the Trill Withers Show!! They kick off the show reacting to the hilarious viral clip of an Indiana University student failing at Wheel of Fortune. They then watch some young AAU players break the basketball code as they showboat their way across the court and remember Coach Longshirt pinning his own players layup. Scoob then presents his questionable theory on history and the gang criticizes Bob Meyers podcasting skills during his episode with Steph Curry. Finally, your favorite quad box rips off some rapid fire segments with Who you crappin, stories of Velour, Bill Simmons hot takes and Coley's unfortunate realization that he did not win the lottery. Please consider liking and subscribing to help grow the show!!!!   FULL VIDEO EPISODE: https://youtu.be/TxBlv2T3BVY Like, Subscribe AND Watch LIVE on YouTube M-F 12-3ET to chat along with us and check out the clips for our best moments so far! Give @UnderdogFantasy a follow as well for more from our buds! CUT TO IT WITH STEVE SMITH SR. AND COLEY MICK: Cut To It - YouTube COLEY AND KLEW'S START/SIT SHOW SUNDAY 12-1ET: Underdog Fantasy - YouTube

Hoy nos acompaña @AnamarOrihuela, Psicoterapeuta, conferencista, escritora. Fundadora de la clínica HERA y creadora del método HERA y hablamos de"Las heridas de la infancia" . Las heridas de la infancia tienen un peso muy importante en las distintas etapas de la vida. Cuando creces empiezas a cargar con heridas, y tus comportamientos son las reacciones de esas heridas de rechazo, de abandono, humillación, traición, también dichos como los vacíos interiores. ¿por qué ocurren las heridas de la infancia, qué son?, ¿Cuáles son las heridas de la infancia y qué efectos tienen en la vida? Y ¿Cómo sanar las heridas de la infancia?. ¿Cuáles son las 5 heridas de la infancia?. Vamos a revisar con detalle estas y otras preguntas. No te pierdas este episodio. anamar.orihuela #AnamarOrihuela #HeridasDeLaInfancia #MétodoHera #SanandoHeridas #PsicoterapiaLaMontana

Trill Withers Catches A WILD Snow Leopard in this WILD Best of The Week!!!! Join Trill Withers, Coley Mick, Scoob, Jam Packard and YC head to the Dallas Zoo to catch a Snow Leopard that ESCAPED! In the process they discuss some coyotes and look back on the horrifying murder of Mary The Elephant. They then examine some food products like the infamous Chip Butty, New Sprite, and a man with a suitcase of meat. To follow that up the gang finds out the rat czar needs to use a musket trap before ripping through some quick hitters on Joel Embiid's NFT Project, Michael Bay's Pigeon Murder, Cookies, Dasani Water and Vladdy Jr Hitting ABSOLUTE NUKES! 

Trill Withers Joins The Fat Man's Club of NYC in this hilarious Best of The Week!!!! Join Trill Withers, Coley Mick, Scoob, Jam Packard and YC as they join the most exclusive club in New York City. They also get to the bottom of Scoob's Streamer Hairline and the man who somehow gets robbed every single day of his life, before revealing how the iconic Bad News Barnes got his nickname. Finally, the gang tells some horror stories about moving, turn their nose at YC's questionable McDonald's order and catch up with old friend Jose Canseco as he challenges Aaron Judge to a home run derby. Lastly, Trill enjoyed some cinema over the break so catch his honest review of Glass Onion: Knives Out!!! Like, Subscribe AND Watch LIVE on YouTube M-F 12-3ET to chat along with us and check out the clips for our best moments so far! Give @UnderdogFantasy a follow as well for more from our buds! CUT TO IT WITH STEVE SMITH SR. AND COLEY MICK: Cut To It - YouTube COLEY AND KLEW'S START/SIT SHOW SUNDAY 12-1ET: Underdog Fantasy - YouTube

Pour l'épisode de cette semaine, je reçois Tom Nguyen, le cofondateur et CEO de Café. Café c'est une solution qui aide les entreprises à gérer le modèle hybride et à créer du lien entre les collaborateurs. Au cours de cet épisode, nous avons parlé des débuts de Café, de comment son frère et lui ont eu l'idée et l'ont développé en plein confinement, de leur passage par YC, des décisions produit et de leur réorientation vers les grands comptes. Vous pouvez suivre Tom sur LinkedIn. Bonne écoute ! _____ Pour soutenir SaaS Connection en 1 minute⏱ (et 2 secondes) : Abonnez-vous à SaaS Connection sur votre plateforme préférée pour ne rater aucun épisode

Victor is a software consultant in Tokyo who describes himself as a yak shaver. He writes on his blog at vadosware and curates Awesome F/OSS, a mailing list of open source products. He's also a contributor to the Open Core Ventures blog. Before our conversation Victor wrote a structured summary of how he works on projects. I recommend checking that out in addition to the episode. Topics covered: Most people should use Dokku or CapRover But he uses Kubernetes anyways Hosting a Database in Kubernetes Learning technology You don't really know a thing until something goes wrong History of Frontend Development Context from lower layers of the stack and historical projects Good project pages have comparisons to other products Choosing technologies Language choice affects maintainability Knowing an ecosystem Victor's preferred stack Technology bake offs Posting findings means you get free corrections Why people use medium instead of personal sites Victor VADOSWARE - Blog How Victor works on Projects - Companion post for this episode Awesome FOSS - Curated list of OSS projects NimbusWS - Hosted OSS built on top of budget cloud providers Unvalidated Ideas - Startup ideas for side project inspiration PodcastSaver - Podcast index that allows you to choose Postgres or MeiliSearch and compare performance and results of each Victor's preferred stack Docker - Containers Kubernetes - Container provisioning (Though at the beginning of the episode he suggests Dokku for single server or CapRover for multiple) TypeScript - JavaScript with syntax for types. Victor's default choice. Rust - Language he uses if doing embedded work, performance is critical, or more correctness is desired Haskell - Language he uses if correctness and type system is the most important for the project Postgresql - General purpose database that's good enough for most use cases including full text search. KeyDB - Redis compatible database for caching. Acquired by Snap and then made open source. Victor uses it over Redis because it is multi threaded and supports flash storage without a Redis Enterprise license. Pulumi - Provision infrastructure with the languages you're already using instead of a specialized one or YAML Svelte and SvelteKit - Preferred frontend stack. Previously used Nuxt. Search engines Postgres Full Text Search vs the rest Optimizing Postgres Text Search with Trigrams OpenSearch - Amazon's fork of Elasticsearch typesense meilisearch sonic Quickwit JavaScript build tools Babel SWC Webpack esbuild parcel Vite Turbopack JavaScript frameworks React Vue Svelte Ember Frameworks built on top of frameworks Next - React Nuxt - Vue SvelteKit - Svelte Astro - Multiple Historical JavaScript tools and frameworks Underscore jQuery MooTools Backbone AngularJS Knockout Aurelia GWT Bower - Frontend package manager Grunt - Task runner Gulp - Task runner Related Links Dokku - Open source single-host alternative to Heroku Cloud Native Buildpacks - Buildpacks created by Heroku and Pivotal and used by Dokku CapRover - An open source PaaS-like abstraction built on top of Docker Swarm Kelsey Hightower's tweet about being cautious about running databases on Kubernetes Settling the Myth of Transparent HugePages for Databases Kubernetes Container Storage Interface (CSI) Kubernetes Local Persistent Volumes Longhorn - Distributed block storage for Kubernetes Postgres docs Postgres TOAST Everything I've seen on optimizing Postgres on ZFS Kubernetes Workload Resources Kubernetes Network Plugins Kubernetes Ingress Traefik Kubernetes the Hard Way (Setting up a cluster in a way that optimizes for learning) How does TLS work Let's Encrypt Cert manager for Kubernetes Choose Boring Technology A Linux user's guide to Logical Volume Management Docker networking overview Kubernetes Scheduler Tauri - Build desktop applications with web technology and Rust ripgrep - CLI tool to recursively search directory for a regex pattern (Meant to be a rust replacement for grep) angle-grinder / ag - CLI tool to parse and process log files written in rust Object.observe ECMAScript Proposal to be Withdrawn Ruby on Rails - Ruby web framework Django - Python web framework Laravel - PHP web framework Adonis - JavaScript NestJS - JavaScript What is a NullPointerException, and how do I fix it? Mastodon Clap - CLI argument parser for Rust AWS CDK - Provision AWS infrastructure using programming languages Terraform - Provision infrastructure with terraform language URL canonicalization of duplicate pages and the use of the canonical tag - Used by dev.to to send google traffic to the original blogpost instead of dev.to Transcript You can help edit this transcript on GitHub. [00:00:00] Jeremy: This episode, I talk to Victor Adossi who describes himself as a yak shaver. Someone who likes trying a whole bunch of different technologies, seeing the different options. We talk about what he uses, the evolution of front end development, and his various projects. Talking to just different people it's always good to get where they're coming from because something that works for Google at their scale is going to be different than what you're doing with one of your smaller projects. [00:00:31] Victor: Yeah, the context. Of course in direct conflict with that statement, I definitely use Google technology despite not needing to at all right? Like, you know, 99% of people who are doing like people like to call it indiehacking or building small products could probably get by with just Dokku. If you know Dokku or like CapRover. Are two projects that'll be like, Oh, you can just push your code here, we'll build it up like a little mini Heroku PaaS thing and just go on one big server, right? Like 99% of the people could just use that. But of course I'm not doing that. So I'm a bit of a hypocrite in that sense. I know what I should be doing, but I'm not doing that. I am writing a Kubernetes cluster with like five nodes for no reason. Uh, yeah, I dunno, people don't normally count the controllers. [00:01:24] Jeremy: Dokku and CapRover, I think those are where it's supposed to create a heroku like experience I think it's based off of the heroku buildpacks right? At least Dokku is? [00:01:36] Victor: Yeah Buildpacks has actually been spun out into like a community thing so like pivotal and heroku, it's like buildpacks.io, they're trying to build a wider standard around it so that more people can get involved. And buildpacks are actually obviously fantastic as a technology and as a a process piece. There's not much else like them and you know, that's obvious from like Heroku's success and everything. I know Dokku uses that. I don't know that Caprover does, but I haven't, I haven't really run Caprover that much. They, they probably do. Like at this point if you're going to support building from code, it seems silly to try and build your own buildpacks. Cause that's what you will do, eventually. So you might as well use what's there. Anyway, this is like just getting to like my personal opinions at this point, but like, if you think containers are a bad idea in 2022, You're wrong, you should, you should stop. Like you should, you should stop. Think about it. I mean, obviously there's not, um, I got a really great question at an interview once, which is, where are containers a bad idea? That's probably one of the best like recent interview questions I've ever gotten cause I was like, Oh yeah, I mean, like, you can't, it can't be perfect everywhere, right? Nothing's perfect everywhere. So it's like, where is it? Uh, and of course the answer was networking, right? (unintelligible) So if you need absolute performance, but like for just about everything else. Containers are kind of it at this point. Like, time has born it out, I think. So yeah, I always just like bias at taking containers at this point. So I'm probably more of a CapRover person than a Dokku person, even though I have not used, I don't use CapRover. [00:03:09] Jeremy: Well, like something that I've heard with containers, and maybe it's changed recently, but, but something that was kind of holdout was when people would host a database sometimes they would oh we just don't wanna put this in a container and I wonder if like that matches with your thinking or if things have changed. [00:03:27] Victor: I am not a database administrator right like I read postgres docs and I read the, uh, the Postgres documentation, and I think I know a bit about postgres but I don't commit right like so and I also haven't, like, oh, managed X terabytes on one server that you are making sure never goes down kind of deal. But the stickiness for me, at least from when I've run, So I've done a lot of tests with like ZFS and Postgres and like, um, and also like just trying to figure out, and I run Postgres in Kubernetes of course, like on my cluster and a lot of the stuff I found around is, is like fiddly kernel things like sort of base kernel settings that you need to have set. Like, you know, stuff like should you be using transparent huge pages, like stuff like that. But once you have that settled. Containers are just processes with name spacing and resource control, right? Like, that's it. there are some other ins and outs, but for the most part, if you're fine running a process, so people ran processes, right? And they were just completely like unprotected. Then people made users for the processes and they limited the users and ran the processes, right? Then the next step is now you can run a process and then do the limiting the name spaces in cgroups dynamically. Like there, there's, there's sort of not a humongous difference, unless you're hitting something very specific. Uh, but yeah, databases have been a point of contention, but I think, Kelsey Hightower had that tweet yeah. That was like, um, don't run databases in Kubernetes. And I think he called it back. [00:04:56] Victor: I don't know, but I, I know that was uh, was one of those things that people were really unsure about at first, but then after people sort of like felt it out, they were like, Oh, it's actually fine. Yeah. [00:05:06] Jeremy: Yeah I vaguely remember one of the concerns having to do with persistent storage. Like there were challenges with Kubernetes and needing to keep that storage around and I don't know if that's changed yeah or if that's still a concern. [00:05:18] Victor: Uh, I'd say that definitely has changed. Uh, and it was, it was a concern, depending on where you were. Mostly people who are running AKS or EKS or you know, all those other managed Kubernetes, they're just using EBS or like whatever storage provider is like offering for storage. Most of those people don't actually have that much of a problem with, storage in general. Now, high performance storage is obviously different, right? So like, so you'll, you're gonna have to start doing manual, like local volume management and stuff like that. it was a problem, because obviously CSI (Kubernetes Container Storage Interface) didn't exist for some period of time, and like there was, it was hard to know what to do for if you were just running a Kubernetes cluster. I think a lot of people were just using local, first of all, local didn't even exist for a bit. Um, they were just using host path, right? And just like, Oh, it's on the disk somewhere. Where do we, we have to go get it right? Or we have to like, sort of manage that. So that was something most people weren't ready for, especially if you were just, if you weren't like sort of a, a, a traditional sysadmin and used to doing that stuff. And then of course local volumes came out, but I think they still had to be, um, pre-provisioned. So that's sysadmin stuff that most people, you know, maybe aren't, aren't necessarily ready for. Uh, and then most of the general solutions were slow. So like, I used Longhorn (https://longhorn.io) for a long time and Longhorn, Longhorn's great. And super easy to set up, but it can be slower and you can have some, like, delays in mount time. it wasn't ideal for, for most people. So yeah, I, overall it's true. Databases, Databases in Kubernetes were kind of fraught with peril for a while, but it wasn't for the reason that, it wasn't for the fundamental reason that Kubernetes was just wrong or like, it wasn't the reason most people think of, which is just like, Oh, you're gonna break your database. It's more like, running a database is hard and Kubernetes hasn't solved all the hard problems. Like, cuz that's what Kubernetes does. It basically solves a lot of problems in a very generic way. Right. So it just hadn't solved all those problems yet at this point. I think it's got decent answers on a lot of them. So I, I mean, I don't know. I I do it. Don't, don't take what I'm saying to your, you know, PM meeting or your standup meeting, uh, anyone who's listening. But it's more like if you could solve the problems with databases in the sense before. You could probably solve 'em on Kubernetes now with a good understanding of Kubernetes. Cause at the end of the day, it's all the same stuff. Just Kubernetes makes it a little easier to, uh, do it dynamically. [00:07:50] Jeremy: It sounds like you could do it before, but some of the, I guess the tools or the ways of doing persistent storage were not quite there yet, or they were difficult to use. And so that was why people at the start were like, Okay, maybe it's not a good idea, but, now maybe there's some established practices for how you should run a database in Kubernetes. And I, I suppose the other aspect too is that, like you were saying, Kubernetes is its own thing. You gotta learn Kubernetes and all its intricacies. And then running a database is also its own challenge. So if you stack the two of them together and, and the path was not really clear then maybe at the start it wasn't the best idea. Um, uh, if somebody was going to try it out now, was there like a specific resource you looked at or a specific path to where like okay this is is how I'm going to do it. [00:08:55] Victor: I'll just say what I normally recommend to everybody. Cause it depends on which path you wanna go right? If you wanna go down like running a database path first and figure that out, fill out that skill tree. Like go read the Postgres docs. Well, first of all, use Postgres. That's the first tip there. But like, read those documents. And obviously you don't have to understand everything. You won't understand everything. But knowing the big pieces and sort of letting your brain see the mention of like a whole bunch of things, like what is toast? Oh, you can do compression on columns. Like, you can do some, some things concurrently. Um, you know, what ALTER TABLE looks like. You get all that stuff kind of in your head. Um, and then I personally really believe in sort of learning by building and just like iterating. you won't get it right the first time. It's just like, it's not gonna happen. You're get, you can, you can get better the first time, right? By being really prepared and like, and leave yourself lots of outs, but you kind of have to like, get it out there. Do do your best to make sure that you can't fail, uh, catastrophically, right? So this is like, goes back to that decision to like use ZFS as the bottom of this I'm just like, All right, well, I, I'm not a file systems expert, but if I. I could delegate some of that, you know, some of that, I can get some of that knowledge from someone else. Um, and I can make it easier for me to not fail catastrophically. For the database side, actually read documentation on Postgres or the whatever database you're going to use, make sure you at least understand that. Then start running it like locally or whatever. Again, Docker use, use Docker locally. It's, it's, it's fine. and then, you know, sort of graduate to running sort of more progressively, more complicated versions. what I would say for the Kubernetes side is actually similar. the Kubernetes docs are really good. they're very large. but they're good. So you can actually go through and know all the, like, workload, workload resources, know, like what a config map is, what a secret is, right? Like what etcd is doing in this whole situation. you know, what a kublet is versus an API server, right? Like the, the general stuff, like if you go through all that, you should have like a whole bunch of ideas at least floating around in your head. And then once you try and start setting up a server, they will all start to pop up again, right? And they'll all start to like, you, like, Oh, okay, I need a CNI (Container Networking) plugin because something needs to make the services available, right? Or something needs to power the ingress, right? Like, if I wanna be able to get traffic, I need an ingress object. But what listens, what does that, what makes that ingress object do anything? Oh, it's an ingress controller. nginx, you know, almost everyone's heard of nginx, so they're like, okay. Um, nginx, has an ingress control. Actually there's, there used to be two, I assume there's still two, but there's like one that's maintained by Kubernetes, one that's maintained by nginx, the company or whatever. I use traefik, it's fantastic. but yeah, so I think those things kind of fall out and that is almost always my first way to explain it and to start building. And tinkering iteratively. So like, read the documentation, get a good first grasp of it, and then start building yourself because you'll, you'll get way more questions that way. Like, you'll ask way more questions, you won't be able to make progress. Uh, and then of course you can, you know, hop into slacks or like start looking around and, and searching on the internet. oh, one of the things that really helped me out early learning Kubernetes was, Kelsey Hightower's, um, learn Kubernetes the hard way. I'm also a big believer in doing things the hard way, at least knowing what you're choosing to not know, right? distributing file system, Deltas, right? Or like changes to a file system over the network is not a new problem. Other people have solved it. There's a lot of complexity there. but if you at least know the sort of surface level of what the thing does and what it's supposed to do and how it's supposed to do it, you can make a decision on, Oh, how deep am I going to go? Right? To prevent yourself from like, making a mistake or going too deep in the rabbit hole. If you have an idea of the sort of ecosystem and especially like, Oh, here, like the basics of how I can use this thing, that's generally very good. And doing things the hard way is a great way to get a, a feel for that, right? Cause if you take some chunk and like, you know, the first level of doing things the hard way, uh, or, you know, Kelsey Hightower's guide is like, get a machine, right? Like, so, like, if you somehow were like, Oh, I wanna run a Kubernetes cluster. but, you know, I don't want use necessarily EKS and you wanna learn it the hard way. You have to go get a machine, right? If you, if you're not familiar, if you run on Heroku the whole time, like you didn't manage your own machines, you gotta go like, figure out EC2, right? Or, I personally use, hetzner I love hetzner, so you have to go figure out hetzner, digital ocean, whatever. Right. And then the next thing's like, you know, the guide's changed a lot, and I haven't, I haven't looked at it in like, in years, actually a while since I, since I've sort of been, I guess living it, but it's, it's like generate certificates, right? So if you've never dealt with SSL and like, sort of like, or I should say TLS uh, and generating certificates and how that whole dance works, right? Which is fascinating because it's like, oh, right, nothing's secure on the internet, except that we distribute root certificates on computers that are deployed in every OS, right? Like, that's a sort of fundamental understanding you may not go deep enough to realize, but if you are fascinated by it, trying to do it manually would lead you down that path. You'd be like, Oh, what, like what is this thing? What is a CSR? Like, why, who is signing my request? Right? And it's like, why do we trust those people? Right? And it's like, you know, that kind of thing comes out and I feel like you can only get there from trying to do it, you know, answering the questions you can. Right. And again, it takes some judgment to know when you should not go down a rabbit hole. uh, and then iterating. of course there are people who are excellent at explaining. you can find some resources that are shortcuts. But, uh, I think particularly my bread and butter has been just to try and do it the hard way. Avoid pitfalls or like rabbit holes when you can. But know that the rabbit hole is there, and then keep going. And sometimes if something's just too hard, you're not gonna get it the first time. Like maybe you'll have to wait like another three months, you'll try again and you'll know more sort of ambiently about everything else. You get a little further that time. that's how I feel about that. Anyway. [00:15:06] Jeremy: That makes sense to me. I think sometimes when people take on a project, they try to learn too many things at the same time. I, I think the example of Kubernetes and Postgres is pretty good example, where if you're not familiar with how do I install Postgres on bare metal or a vm, trying to make sense of that while you're trying to into is probably gonna be pretty difficult. So, so splitting them up and learning them individually, that makes a lot of sense to me. And the whole deciding how deep you wanna go. That's interesting too, because I think that's very specific to the person right because sometimes you wanna go a little deeper because otherwise you don't understand how the two things connect together. But other times it's just like with the example with certificates, some people they may go like, I just put in let's encrypt it gives me my cert I don't care right then, and then, and some people they wanna know like okay how does the whole certificate infrastructure work which I think is interesting, depending on who you are, maybe you go ahh maybe it doesn't really matter right. [00:16:23] Victor: Yeah, and, you know, shout out to Let's Encrypt . It's, it's amazing, right? think Singlehandedly the most, most of the deployment of HTTPS that happens these days, right? so many so many of like internet providers and uh, sort of service providers will use it right? Under the covers. Like, Hey, we've got you free SSL through Let's Encrypt, right? Like, kind of like under the, under the covers. which is awesome. And they, and they do it. So if you're listening to this, donate to them. I've done it. So now that, now the pressure is on whoever's listening, but yeah, and, and I, I wanna say I am that person as well, right? Like, I use, Cert Manager on my cluster, right? So I'm just like, I don't wanna think about it, but I, you know, but I, I feel like I thought about it one time. I have a decent grasp. If something changes, then I guess I have to dive back in. I think it, you've heard the, um, innovation tokens idea, right? I can't remember the site. It's like, um, do, like do boring tech or something.com (https://boringtechnology.club/) . Like it shows up on sort of hacker news from time to time, essentially. But it's like, you know, you have a certain amount of tokens and sort of, uh, we'll call them tokens, but tolerance for complexity or tolerance for new, new ideas or new ways of doing things, new processes. Uh, and you spend those as you build any project, right? you can be devastatingly effective by just sticking to the stack, you know, and not introducing anything new, even if it's bad, right? and there's nothing wrong with LAMP stack, I don't wanna annoy anybody, but like if you, if you're running LAMP or if you run on a hostgator, right? Like, if you run on so, you know, some, some service that's really old but really works for you isn't, you know, too terribly insecure or like, has the features you need, don't learn Kubernetes then, right? Especially if you wanna go fast. cuz you, you're spending tokens, right? You're spending, essentially brain power, right? On learning whatever other thing. So, but yeah, like going back to that, databases versus databases on Kubernetes thing, you should probably know one of those before you, like, if you're gonna do that, do that thing. You either know Kubernetes and you like, at least feel comfortable, you know, knowing Kubernetes extremely difficult obviously, but you feel comfortable and you feel like you can debug. Little bit of a tangent, but maybe that's even a better, sort of watermark if you know how to debug a thing. If, if it's gone wrong, maybe one or five or 10 or 20 times and you've gotten out. Not without documentation, of course, cuz well, if you did, you're superhuman. But, um, but you've been able to sort of feel your way out, right? Like, Oh, this has gone wrong and you have enough of a model of the system in your head to be like, these are the three places that maybe have something wrong with them. Uh, and then like, oh, and then of course it's just like, you know, a mad dash to kind of like, find, find the thing that's wrong. You should have confidence about probably one of those things before you try and do both when it's like, you know, complex things like databases and distributed systems management, uh, and orchestration. [00:19:18] Jeremy: That's, that's so true in, in terms of you are comfortable enough being able to debug a problem because it's, I think when you are learning about something, a lot of times you start with some kind of guide or some kind of tutorial and you follow the steps. And if it all works, then great. Right? But I think it's such a large leap from that to something went wrong and I have to figure it out. Right. Whether it's something's not right in my Dockerfile or my postgres instance uh, the queries are timing out. so many things that could go wrong, that is the moment where you're forced to figure out, okay, what do I really know about this not thing? [00:20:10] Victor: Exactly. Yeah. Like the, the rubber's hitting the road it's uh you know the car's about to crash or has already crashed like if I open the bonnet, do I know what's happening right or am I just looking at (unintelligible). And that's, it's, I feel sort a little sorry or sad for, for devs that start today because there's so much. Complexity that's been built up. And a lot of it has a point, but you need to kind of have seen the before to understand the point, right? So I like, I like to use front end as an example, right? Like the front end ecosystem is crazy, and it has been crazy for a very long time, but the steps are actually usually logical, right? Like, so like you start with, you know, HTML, CSS and JavaScript, just plain, right? And like, and you can actually go in lots of directions. Like HTML has its own thing. CSS has its own sort of evolution sort of thing. But if we look at JavaScript, you're like, you're just writing JavaScript on every page, right? And like, just like putting in script tags and putting in whatever, and it's, you get spaghetti, you get spaghetti, you start like writing, copying the same function on multiple pages, right? You just, it, it's not good. So then people, people make jquery, right? And now, now you've got like a, a bundled set of like good, good defaults that you can, you can go for, right? And then like, you know, libraries like underscore come out for like, sort of like not dom related stuff that you do want, you do want everywhere. and then people go from there and they go to like backbone or whatever. it's because Jquery sort of also becomes spaghetti at some point and it becomes hard to manage and people are like, Okay, we need to sort of like encapsulate this stuff somehow, right? And like the new tools or whatever is around at the same timeframe. And you, you, you like backbone views for example. and you have people who are kind of like, ah, but that's not really good. It's getting kind of slow. Uh, and then you have, MVC stuff comes out, right? Like Angular comes out and it's like, okay, we're, we're gonna do this thing called dirty checking, and it's gonna be, it's gonna be faster and it's gonna be like, it's gonna be less sort of spaghetti and it's like a little bit more structured. And now you have sort of like the rails paradigm, but on the front end, and it takes people to get a while to get adjusted to that, but then that gets too heavy, right? And then dirty checking is realized to be a mistake. And then, you get stuff like MVVM, right? So you get knockout, like knockout js and you got like Durandal, and like some, some other like sort of front end technologies that come up to address that problem. Uh, and then after that, like, you know, it just keeps going, right? Like, and if you come in at the very end, you're just like, What is happening? Right? Like if it, if it, if someone doesn't sort of boil down the complexity and reduce it a little bit, you, you're just like, why, why do we do this like this? Right? and sometimes there's no good reason. Sometimes the complexity is just like, is unnecessary, but having the steps helps you explain it, uh, or helps you understand how you got there. and, and so I feel like that is something younger people or, or newer devs don't necessarily get a chance to see. Cause it just, it would take, it would take very long right? And if you're like a new dev, let's say you jumped into like a coding bootcamp. I mean, I've got opinions on coding boot camps, but you know, it's just like, let's say you jumped into one and you, you came out, you, you made it. It's just, there's too much to know. sure, you could probably do like HTML in one month. Well, okay, let's say like two weeks or whatever, right? If you were, if you're literally brand new, two weeks of like concerted effort almost, you know, class level, you know, work days right on, on html, you're probably decently comfortable with it. Very comfortable. CSS, a little harder because this is where things get hard. Cause if you, if you give two weeks for, for HTML, CSS is harder than HTML kind of, right? Because the interactions are way more varied. Right? Like, and, and maybe it's one of those things where you just, like, you, you get somewhat comfortable and then just like know that in the future you're gonna see something you don't understand and have to figure it out. Uh, but then JavaScript, like, how many months do you give JavaScript? Because if you go through that first like, sort of progression that I, I I, I, I mentioned everyone would have a perfect sort of, not perfect but good understanding of the pieces, right? Like, why did we start transpiling at all? Right? Like, uh, or why did you know, why did we adopt libraries? Like why did Bower exist? No one talks about Bower anymore, obviously, but like, Bower was like a way to distribute front end only packages, right? Um, what is it? Um, Uh, yes, there's grunt. There's like the whole build system thing, right? Once, once we decide we're gonna, we're gonna do stuff to files before we, before we push. So there's grunt, there's, uh, gulp, which is like grunt, but like, Oh, we're gonna do it all in memory. We're gonna pipe, we're gonna use this pipes thing to make sure everything goes fast. then there's like, of course that leads like the insanity that's webpack. And then there's like parcel, which did better. There's vite there's like, there's all this, there's this progression, but how many months would it take to know that progression? It, it's too long. So they end up just like, Hey, you're gonna learn react. Which is the right thing because it's like, that's what people hire for, right? But then you're gonna be in react and be like, What's webpack, right? And it's like, but you can't go down. You can't, you don't have the time. You, you can't sort of approach that problem from the other direction where you, which would give you better understanding cause you just don't have the time. I think it's hard for newer devs to overcome this. Um, but I think there are some, there's some hope on the horizon cuz some things are simpler, right? Like some projects do reduce complexity, like, by watching another project sort of innovate so like react. Wasn't the first component, first framework, right? Like technically, I, I think, I think you, you might have to give that to like, to maybe backbone because like they had views and like marionette also went with that. Like maybe, I don't know, someone, someone I'm sure will get in like, send me an angry email, uh, cuz I forgot you Moo tools or like, you know, Ember Ember. They've also, they've also been around, I used to be a huge Ember fan, still, still kind of am, but I don't use it. but if you have these, if you have these tools, right? Like people aren't gonna know how to use them and Vue was able to realize that React had some inefficiencies, right? So React innovates the sort of component. So Reintroduces the component based model component first, uh, front end development model. Vue sees that and it's like, wait a second, if we just export this like data object, and of course that's not the only innovation of Vue, but if we just export this data object, you don't have to do this fine grained tracking yourself anymore, right? You don't have to tell React or tell your the system which things change when other things change, right? Like you, you don't have to set up this watching and stuff, right? Um, and that's one of the reasons, like Vue is just, I, I, I remember picking up Vue and being like, Oh, I'm done. I'm done with React now. Because it just doesn't make sense to use React because they Vue essentially either, you know, you could just say they learned from them or they, they realize a better way to do things that is simpler and it's much easier to write. Uh, and you know, functionally similar, right? Um, similar enough that it's just like, oh they boil down some of that complexity and we're a step forward and, you know, in other ways, I think. Uh, so that's, that's awesome. Every once in a while you get like a compression in the complexity and then it starts to ramp up again and you get maybe another compression. So like joining the projects that do a compression. Or like starting to adopting those is really, can be really awesome. So there's, there's like, there's some hope, right? Cause sometimes there is a compression in that complexity and you you might be lucky enough to, to use that instead of, the thing that's really complex after years of building on it. [00:27:53] Jeremy: I think you're talking about newer developers having a tough time making sense of the current frameworks but the example you gave of somebody starting from HTML and JavaScript going to jquery backbone through the whole chain, that that's just by nature of you've put in a lot of time right you've done a lot of work working with each of these technologies you see the progression as if someone is starting new just by nature of you being new you won't have been able to spend that time [00:28:28] Victor: Do you think it could work? again, the, the, the time aspect is like really hard to get like how can you just avoid spending time um to to learn things that's like a general problem I think that problem is called education in the general sense. But like, does it make sense for a, let's say a bootcamp or, or any, you know, school right? To attempt to guide people through the previous solutions that didn't work, right? Like in math, you don't start with calculus, right? It just wouldn't, it doesn't make sense, right? But we try and start with calculus in software, right? We're just like, okay, here's the complexity. You've got all of it. Don't worry. Just look at this little bit. If, you know, if the compiler ever spits out a weird error uh oh, like, you're, you're, you're in for trouble cuz you, you just didn't get the. get the basics. And I think that's maybe some of what is missing. And the thing is, it is like the constraints are hard, right? No one has infinite time, right? Or like, you know, even like, just tons of time to devote to learning, learning just front end, right? That's not even all of computing, That's not even the algorithm stuff that some companies love to throw at you, right? Uh, or the computer sciencey stuff. I wonder if it makes more sense to spend some time taking people through the progression, right? Because discovering that we should do things via components, let's say, or, or at least encapsulate our functionality to components and compose that way, is something we, we not everyone knew, right? Or, you know, we didn't know wild widely. And so it feels like it might make sense to touch on that sort of realization and sort of guide the student through, you know, maybe it's like make five projects in a week and you just get progressively more complex. But then again, that's also hard cause effort, right? It's just like, it's a hard problem. But, but I think right now, uh, people who come in at the end and sort of like see a bunch of complexity and just don't know why it's there, right? Like, if you've like, sort of like, this is, this applies also very, this applies to general, but it applies very well to the Kubernetes problem as well. Like if you've never managed nginx on more than one machine, or if you've never tried to set up a, like a, to format your file system on the machine you just rented because it just, you know, comes with nothing, right? Or like, maybe, maybe some stuff was installed, but, you know, if you had to like install LVM (Logical Volume Manager) yourself, if you've never done any of that, Kubernetes would be harder to understand. It's just like, it's gonna be hard to understand. overlay networks are hard for everyone to understand, uh, except for network people who like really know networking stuff. I think it would be better. But unfortunately, it takes a lot of time for people to take a sort of more iterative approach to, to learning. I try and write blog posts in this way sometimes, but it's really hard. And so like, I'll often have like an idea, like, so I call these, or I think of these as like onion, onion style posts, right? Where you either build up an onion sort of from the inside and kind of like go out and like add more and more layers or whatever. Or you can, you can go from the outside and sort of take off like layers. Like, oh, uh, Kubernetes has a scheduler. Why do they need a scheduler? Like, and like, you know, kind of like, go, go down. but I think that might be one of the best ways to learn, but it just takes time. Or geniuses and geniuses who are good at two things, right? Good at the actual technology and good at teaching. Cuz teaching is a skill and it's very hard. and, you know, shout out to teachers cuz that's, it's, it's very difficult, extremely frustrating. it's hard to find determinism in, in like methods and solutions. And there's research of course, but it's like, yeah, that's, that's a lot harder than the computer being like, Nope, that doesn't work. Right? Like, if you can't, if you can't, like if you, if the function call doesn't work, it doesn't work. Right. If the person learned suboptimally, you won't know Right. Until like 10 years down the road when, when they can't answer some question or like, you know, when they, they don't understand. It's a missing fundamental piece anyway. [00:32:24] Jeremy: I think with the example of front end, maybe you don't have time to walk through the whole history of every single library and framework that came but I think at the very least, if you show someone, or you teach someone how to work with css, and you have them, like you were talking about components before you have them build a site where there's a lot of stuff that gets reused, right? Maybe you have five pages and they all have the same nav bar. [00:33:02] Victor: Yeah, you kind of like make them do it. [00:33:04] Jeremy: Yeah. You make 'em do it and they make all the HTML files, they copy and paste it, and probably your students are thinking like, ah, this, this kind of sucks [00:33:16] Victor: Yeah [00:33:18] Jeremy: And yeah, so then you, you come to that realization, and then after you've done that, then you can bring in, okay, this is why we have components. And similarly you brought up, manual dom manipulation with jQuery and things like that. I, I'm sure you could come up with an example of you don't even necessarily need to use jQuery. I think people can probably skip that step and just use the the, the API that comes with the browser. But you can have them go in like, Oh, you gotta find this element by the id and you gotta change this based on this, and let them experience the. I don't know if I would call it pain, but let them experience like how it was. Right. And, and give them a complex enough task where they feel like something is wrong right. Or, or like, there, should be something better. And then you can go to you could go straight to vue or react. I'm not sure if we need to go like, Here's backbone, here's knockout. [00:34:22] Victor: Yeah. That's like historical. Interesting. [00:34:27] Jeremy: I, I think that would be an interesting college course or something that. Like, I remember when, I went through school, one of the classes was programming languages. So we would learn things like, Fortran and stuff like that. And I, I think for a more frontend centered or modern equivalent you could go through, Hey, here's the history of frontend development here's what we used to do and here's how we got to where we are today. I think that could be actually a pretty interesting class yeah [00:35:10] Victor: I'm a bit interested to know you learned fortran in your PL class. I, think when I went, I was like, lisp and then some, some other, like, higher classes taught haskell but, um, but I wasn't ready for haskell, not many people but fortran is interesting, I kinda wanna hear about that. [00:35:25] Jeremy: I think it was more in terms of just getting you exposed to historically this is how things were. Right. And it wasn't so much of like, You can take strategies you used in Fortran into programming as a whole. I think it was just more of like a, a survey of like, Hey, here's, you know, here's Fortran and like you were saying, here's Lisp and all, all these different languages nd like at least you, you get to see them and go like, yeah, this is kind of a pain. [00:35:54] Victor: Yeah [00:35:55] Jeremy: And like, I understand why people don't choose to use this anymore but I couldn't take away like a broad like, Oh, I, I really wish we had this feature from, I think we were, I think we were using Fortran 77 or something like that. I think there's Fortran 77, a Fortran 90, and then there's, um, I think, [00:36:16] Victor: Like old fortran, deprecated [00:36:18] Jeremy: Yeah, yeah, yeah. So, so I think, I think, uh, I actually don't know if they're, they're continuing to, um, you know, add new things or maintain it or it's just static. But, it's, it's more, uh, interesting in terms of, like we were talking front end where it's, as somebody who's learning frontend development who is new and you get to see how, backbone worked or how Knockout worked how grunt and gulp worked. It, it's like the kind of thing where it's like, Oh, okay, like, this is interesting, but let us not use this again. Right? [00:36:53] Victor: Yeah. Yeah. Right. But I also don't need this, and I will never again [00:36:58] Jeremy: yeah, yeah. It's, um, but you do definitely see the, the parallels, right? Like you were saying where you had your, your Bower and now you have NPM and you had Grunt and Gulp and now you have many choices [00:37:14] Victor: Yeah. [00:37:15] Jeremy: yeah. I, I think having he history context, you know, it's interesting and it can be helpful, but if somebody was. Came to me and said hey I want to learn how to build websites. I get into front end development. I would not be like, Okay, first you gotta start moo tools or GWT. I don't think I would do that but it I think at a academic level or just in terms of seeing how things became the way they are sure, for sure it's interesting. [00:37:59] Victor: Yeah. And I, I, think another thing I don't remember who asked or why, why I had to think of this lately. um but it was, knowing the differentiators between other technologies is also extremely helpful right? So, What's the difference between ES build and SWC, right? Again, we're, we're, we're leaning heavy front end, but you know, just like these, uh, sorry for context, of course, it's not everyone a front end developer, but these are two different, uh, build tools, right? For, for JavaScript, right? Essentially you can think of 'em as transpilers, but they, I think, you know, I think they also bundle like, uh, generally I'm not exactly sure if, if ESbuild will bundle as well. Um, but it's like one is written in go, the other one's written in Rust, right? And sort of there's, um, there's, in addition, there's vite which is like vite does bundle and vite does a lot of things. Like, like there's a lot of innovation in vite that has to have to do with like, making local development as fast as possible and also getting like, you're sort of making sure as many things as possible are strippable, right? Or, or, or tree shakeable. Sorry, is is is the better, is the better term. Um, but yeah, knowing, knowing the, um, the differences between projects is often enough to sort of make it less confusing for me. Um, as far as like, Oh, which one of these things should I use? You know, outside of just going with what people are recommending. Cause generally there is some people with wisdom sometimes lead the crowd sometimes, right? So, so sometimes it's okay to be, you know, a crowd member as long as you're listening to the, to, to someone worth listening to. Um, and, and so yeah, I, I think that's another thing that is like the mark of a good project or, or it's not exclusive, right? It's not, the condition's not necessarily sufficient, but it's like a good projects have the why use this versus x right section in the Readme, right? They're like, Hey, we know you could use Y but here's why you should use us instead. Or we know you could use X, but here's what we do better than X. That might, you might care about, right? That's, um, a, a really strong indicator of a project. That's good cuz that means the person who's writing the project is like, they've done this, the survey. And like, this is kind of like, um, how good research happens, right? It's like most of research is reading what's happening, right? To knowing, knowing the boundary you're about to push, right? Or try and sort of like push one, make one step forward in, um, so that's something that I think the, the rigor isn't in necessarily software development everywhere, right? Which is good and bad. but someone who's sort of done that sort of rigor or, and like, and, and has, and or I should say, has been rigorous about knowing the boundary, and then they can explain that to you. They can be like, Oh, here's where the boundary was. These people were doing this, these people were doing this, these people were doing this, but I wanna do this. So you just learned now whether it's right for you and sort of the other points in the space, which is awesome. Yeah. Going to your point, I feel like that's, that's also important, it's probably not a good idea to try and get everyone to go through historical artifacts, but if just a, a quick explainer and sort of, uh, note on the differentiation, Could help for sure. Yeah. I feel like we've skewed too much frontend. No, no more frontend discussion this point. [00:41:20] Jeremy: It's just like, I, I think there's so many more choices where the, the mental thought that has to go into, Okay, what do I use next I feel is bigger on frontend. I guess it depends on the project you're working on but if you're going to work on anything front end if you haven't done it before or you don't have a lot of experience there's so many build tools so many frameworks, so many libraries that yeah, but we [00:41:51] Victor: Iterate yeah, in every direction, like the, it's good and bad, but frontend just goes in every direction at the same time Like, there's so many people who are so enthusiastic and so committed and and it's so approachable that like everyone just goes in every direction at the same time and like a lot of people make progress and then unfortunately you have try and pick which, which branch makes sense. [00:42:20] Jeremy: We've been kind of talking about, some of your experiences with a few things and I wonder if you could explain the the context you're thinking of in terms of the types of projects you typically work on like what are they what's the scale of them that sort of thing. [00:42:32] Victor: So I guess I've, I've gone through a lot of phases, right? In sort of what I use in in my tooling and what I thought was cool. I wrote enterprise java like everybody else. Like, like it really doesn't talk about it, but like, it's like almost at some point it was like, you're either a rail shop or a Java shop, for so many people. And I wrote enterprise Java for a, a long time, and I was lucky enough to have friends who were really into, other kinds of computing and other kinds of programming. a lot of my projects were wrapped around, were, were ideas that I was expressing via some new technology, let's say. Right? So, I wrote a lot of haskell for, for, for a while, right? But what did I end up building with that was actually a job board that honestly didn't go very far because I was spending much more time sort of doing, haskell things, right? And so I learned a lot about sort of what I think is like the pinnacle of sort of like type development in, in the non-research world, right? Like, like right on the edge of research and actual usability. But a lot of my ideas, sort of getting back to the, the ideas question are just things I want to build for myself. Um, or things I think could be commercially viable or like do, like, be, be well used, uh, and, and sort of, and profitable things, things that I think should be built. Or like if, if I see some, some projects as like, Oh, I wish they were doing this in this way, Right? Like, I, I often consider like, Oh, I want, I think I could build something that would be separate and maybe do like, inspired from other projects, I should say, Right? Um, and sort of making me understand a sort of a different, a different ecosystem. but a lot of times I have to say like, the stuff I build is mostly to scratch an itch I have. Um, and or something I think would be profitable or utilizing technology that I've seen that I don't think anyone's done in the same way. Right? So like learning Kubernetes for example, or like investing the time to learn Kubernetes opened up an entire world of sort of like infrastructure ideas, right? Because like the leverage you get is so high, right? So you're just like, Oh, I could run an aws, right? Like now that I, now that I know this cuz it's like, it's actually not bad, it's kind of usable. Like, couldn't I do that? Right? That kind of thing. Right? Or um, I feel like a lot of the times I'll learn a technology and it'll, it'll make me feel like certain things are possible that they, that weren't before. Uh, like Rust is another one of those, right? Like, cuz like Rust will go from like embedded all the way to WASM, which is like a crazy vertical stack. Right? It's, that's a lot, That's a wide range of computing that you can, you can touch, right? And, and there's, it's, it's hard to learn, right? The, the, the, the, uh, the, the ramp to learning it is quite steep, but, it opens up a lot of things you can write, right? It, it opens up a lot of areas you can go into, right? Like, if you ever had an idea for like a desktop app, right? You could actually write it in Rust. There's like, there's, there's ways, there's like is and there's like, um, Tauri is one of my personal favorites, which uses web technology, but it's either I'm inspired by some technology and I'm just like, Oh, what can I use this on? And like, what would this really be good at doing? or it's, you know, it's one of those other things, like either I think it's gonna be, Oh, this would be cool to build and it would be profitable. Uh, or like, I'm scratching my own itch. Yeah. I think, I think those are basically the three sources. [00:46:10] Jeremy: It's, it's interesting about Rust where it seems so trendy, I guess, in lots of people wanna do something with rust, but then in a lot of they also are not sure does it make sense to write in rust? Um, I, I think the, the embedded stuff, of course, that makes a lot of sense. And, uh, you, you've seen a sort of surge in command line apps, stuff ripgrep and ag, stuff like that, and places like that. It's, I think the benefits are pretty clear in terms of you've got the performance and you have the strong typing and whatnot and I think where there's sort of the inbetween section that's kind of unclear to me at least would I build a web application in rust I'm not sure that sort of thing [00:47:12] Victor: Yeah. I would, I characterize it as kind of like, it's a tool toolkit, so it really depends on the problem. And think we have many tools that there's no, almost never a real reason to pick one in particular right? Like there's, Cause it seems like just most of, a lot of the work, like, unless you're, you're really doing something interesting, right? Like, uh, something that like, oh, I need to, I need to, like, I'm gonna run, you know, billions and billions of processes. Like, yeah, maybe you want erlang at that point, right? Like, maybe, maybe you should, that should be, you know, your, your thing. Um, but computers are so fast these days, and most languages have, have sort of borrowed, not borrowed, but like adopted features from others that there's, it's really hard to find a, a specific use case, for one particular tool. Uh, so I often just categorize it by what I want out of the project, right? Or like, either my goals or project goals, right? Depending on, and, or like business goals, if you're, you know, doing this for a business, right? Um, so like, uh, I, I basically, if I want to go fast and I want to like, you know, reduce time to market, I use type script, right? Oh, and also I'm a, I'm a, like a type zealot. I, I'd say so. Like, I don't believe in not having types, right? Like, it's just like there's, I think it's crazy that you would like have a function but not know what the inputs could be. And they could actually be anything, right? , you're just like, and then you have to kind of just keep that in your head. I think that's silly. Now that we have good, we, we have, uh, ways to avoid the, uh, ceremony, right? You've got like hindley Milner type systems, like you have a way to avoid the, you can, you know, predict what types of things will be, and you can, you don't have to write everything everywhere. So like, it's not that. But anyway, so if I wanna go fast, the, the point is that going back to that early, like the JS ecosystem goes everywhere at the same time. Typescript is excellent because the ecosystem goes everywhere at the same time. And so you've got really good ecosystem support for just about everything you could do. Um, uh, you could write TypeScript that's very loose on the types and go even faster, but in general it's not very hard. There's not too much ceremony and just like, you know, putting some stuff that shows you what you're using and like, you know, the objects you're working with. and then generally if I wanna like, get it really right, I I'll like reach for haskell, right? Cause it's just like the sort of contortions, and again, this takes time, this not fast, but, right. the contortions you can do in the type system will make it really hard to write incorrect code or code that doesn't, that isn't logical with itself. Of course interfacing with the outside world. Like if you do a web request, it's gonna fail sometimes, right? Like the network might be down, right? So you have to, you basically pull that, you sort of wrap that uncertainty in your system to whatever degree you're okay with. And then, but I know it'll be correct, right? But and correctness is just not important. Most of like, Oh, I should , that's a bad quote. Uh, it's not that correct is not important. It's like if you need to get to market, you do not necessarily need every single piece of your code to be correct, Right? If someone calls some, some function with like, negative one and it's not an important, it's not tied to money or it's like, you know, whatever, then maybe it's fine. They just see an error and then like you get an error in your back and you're like, Oh, I better fix that. Right? Um, and then generally if I want to be correct and fast, I choose rust these days. Right? Um, these days. and going back to your point, a lot of times that means that I'm going to write in Typescript for a lot of projects. So that's what I'll do for a lot of projects is cuz I'll just be like, ah, do I need like absolute correctness or like some really, you know, fancy sort of type stuff. No. So I don't pick haskell. Right. And it's like, do I need to be like mega fast? No, probably not. Cuz like, cuz so I don't necessarily don't necessarily need rust. Um, maybe it's interesting to me in terms of like a long, long term thing, right? Like if I, if I'm think, oh, but I want x like for example, tight, tight, uh, integration with WASM, for example, if I'm just like, oh, I could see myself like, but that's more of like, you know, for a fun thing that I'm doing, right? Like, it's just like, it's, it's, you don't need it. You don't, that's premature, like, you know, that's a premature optimization thing. But if I'm just like, ah, I really want the ability to like maybe consider refactoring some of this out into like a WebAssembly thing later, then I'm like, Okay, maybe, maybe I'll, I'll pick Rust. Or like, if I, if I like, I do want, you know, really, really fast, then I'll like, then I'll go Rust. But most of the time it's just like, I want a good ecosystem so I don't have to build stuff myself most of the time. Uh, and you know, type script is good enough. So my stack ends up being a lot of the time just in type script, right? Yeah. [00:52:05] Jeremy: Yeah, I think you've encapsulated the reason why there's so many packages on NPM and why there's so much usage of JavaScript and TypeScript in general is that it, it, it fits the, it's good enough. Right? And in terms of, in terms of speed, like you said, most of the time you don't need of rust. Um, and so typescript I think is a lot more approachable a lot of people have to use it because they do front end work anyways. And so that kinda just becomes the I don't know if I should say the default but I would say it's probably the most common in terms of when somebody's building a backend today certainly there's other languages but JavaScript and TypeScript is everywhere. [00:52:57] Victor: Yeah. Uh, I, I, I, another thing is like, I mean, I'm, of ignored the, like, unreasonable effectiveness of like rails Cause there's just a, there's tons of just like rails warriors out there, and that's great. They're they're fantastic. I'm not a, I'm not personally a huge fan of rails but that's, uh, that's to my own detriment, right? In, in some, in some ways. But like, Rails and Django sort of just like, people who, like, I'm gonna learn this framework it's gonna be excellent. It most, they have a, they have carved out a great ecosystem for themselves. Um, or like, you know, even php right? PHP and like Laravel, or whatever. Uh, and so I'm ignoring those, like, those pockets of productivity, right? Those pockets of like intense productivity that people like, have all their needs met in that same way. Um, but as far as like general, general sort of ecosystem size and speed for me, um, like what you said, like applies to me. Like if I, if I'm just like, especially if I'm just like, Oh, I just wanna build a backend, Like, I wanna build something that's like super small and just does like, you know, maybe a few, a couple, you know, endpoints or whatever and just, I just wanna throw it out there. Right? Uh, I, I will pick, yeah. Typescript. It just like, it makes sense to me. I also think note is a better. VM or platform to build on than any of the others as well. So like, like I, by any of the others, I mean, Python, Perl, Ruby, right? Like sort of in the same class of, of tool. So I I am kind of convinced that, um, Node is better, than those as far as core abilities, right? Like threading Right. Versus the just multi-processing and like, you know, other, other, other solutions and like, stuff like that. So, if you want a boring stack, if I don't wanna use any tokens, right? Any innovation tokens I reach for TypeScript. [00:54:46] Jeremy: I think it's good that you brought up. Rails and, and Django because, uh, personally I've done, I've done work with Rails, and you're right in that Rails has so many built in, and the ways to do them are so well established that your ability to be productive and build something really fast hard to compete with, at least in my experience with available in the Node ecosystem. Um, on the other hand, like I, I also see what you mean by the runtimes. Like with Node, you're, you're built on top of V8 and there's so many resources being poured into it to making it fast and making it run pretty much everywhere. I think you probably don't do too much work with managed services, but if you go to a managed service to run your code, like a platform as a service, they're gonna support Node. Will they support your other preferred language? Maybe, maybe not, You know that they will, they'll be able to run node apps so but yeah I don't know if it will ever happen or maybe I'm just not familiar with it, but feel like there isn't a real rails of javascript. [00:56:14] Victor: Yeah, you're, totally right. There are, there are. It's, it's weird. It's actually weird that there, like Uh, but, but, I kind of agree with you. There's projects that are trying it recently. There's like Adonis, um, there is, there are backends that also do, like, will do basic templating, like Nest, NestJS is like really excellent. It's like one of the best sort of backend, projects out there. I I, I but like back in the day, there were projects like Sails, which was like very much trying to do exactly what Rails did, but it just didn't seem to take off and reach that critical mass possibly because of the size of the ecosystem, right? Like, how many alternatives to Rails are there? Not many, right? And, and now, anyway, maybe let's say the rest of 'em sort of like died out over the years, but there's also like, um, hapi HAPI, uh, which is like also, you know, similarly, it was like angling themselves to be that, but they just never, they never found the traction they needed. I think, um, or at least to be as wide, widely known as Rails is for, for, for the, for the Ruby ecosystem, um, but also for people to kind of know the magic, cause. Like I feel like you're productive in Rails only when you imbibe the magic, right? You, you, know all the magic context and you know the incantations and they're comforting to you, right? Like you've, you've, you have the, you have the sort of like, uh, convention. You're like, if you're living and breathing the convention, everything's amazing, right? Like, like you can't beat that. You're just like, you're in the zone but you need people to get in that zone. And I don't think node has, people are just too, they're too frazzled. They're going like, there's too much options. They can't, it's hard to commit, right? Like, imagine if you'd committed to backbone. Like you got, you can't, It's, it's over. Oh, it's not over. I mean, I don't, no, I don't wanna, you know, disparage the backbone project. I don't use it, but, you know, maybe they're still doing stuff and you know, I'm sure people are still working on it, but you can't, you, it's hard to commit and sort of really imbibe that sort of convention or, or, or sort of like, make yourself sort of breathe that product when there's like 10 products that are kind of similar and could be useful as well. Yeah, I think that's, that's that's kind of big. It's weird that there isn't a rails, for NodeJS, but, but people are working on it obviously. Like I mentioned Adonis, there's, there's more. I'm leaving a bunch of them out, but that's part of the problem. [00:58:52] Jeremy: On, on one hand, it's really cool that people are trying so many different things because hopefully maybe they can find something that like other people wouldn't have thought of if they all stick same framework. but on the other hand, it's ... how much time have we spent jumping between all these different frameworks when what we could have if we had a rails. [00:59:23] Victor: Yeah the, the sort of wasted time is, is crazy to think about it uh, I do think about that from time to time. And you know, and personally I waste a lot of my own time. Like, just, just rec

Welcome to 2023 with our first podcast. Join us as we speak to our first guest from the United States, who is expanding his startup to India. Amjad was born in Jordan, where he grew up with a computer long before others had it. Like any emerging market, his parents wanted him to get a good education. Instead, he became a hacker who built Replit as a side project while working at Yahoo. In 6 years, Replit went from a side project to a company. Today it supports 17M+ developers and is on its way to being a developer unicorn Replit is a browser-based integrated development environment for cross-platform collaborative coding available worldwide. Replit raised from YC after failing thrice to get there. Replit has raised $100M from investors such as Coatue, a16z and YCombinator.

I had fun chatting with Aarthi and Sriram.We discuss what it takes to be successful in technology, what Sriram would say if Elon tapped him to be the next CEO of Twitter, why more married couples don't start businesses together, and how Aarthi hires and finds 10x engineers.Aarthi Ramamurthy and Sriram Krishnan are the hosts of The Good Times Show. They have had leading roles in several technology companies from Meta to Twitter to Netflix and have been founders and investors. Sriram is currently a general partner at a16z crypto and Aarthi is an angel investor.Watch on YouTube. Listen on Apple Podcasts, Spotify, or any other podcast platform. Timestamps(00:00:00) - Intro(00:01:19) - Married Couples Co-founding Businesses(00:09:53) - 10x Engineers(00:16:00) - 15 Minute Meetings(00:22:57) - a16z's Edge?(00:26:42) - Future of Twitter(00:30:58) - Is Big Tech Overstaffed?(00:38:37) - Next CEO of Twitter?(00:43:13) - Why Don't More Venture Capitalists Become Founders?(00:47:32) - Role of Boards(00:52:03) - Failing Upwards(00:56:00) - Underrated CEOs(01:02:18) - Founder Education(01:06:27) - What TV Show Would Sriram Make?(01:10:14) - Undervalued Founder ArchetypesTranscriptThis transcript was autogenerated and thus may contain errors.[00:00:00] Aarthi: it's refreshing to have Elon come in and say, we are gonna work really hard. We are gonna be really hardcore about how we build things.[00:00:05] Dwarkesh: Let's say Elon and says Tomorrow, Sriram, would you be down to be the [00:00:08] Sriram: CEO of Twitter Absolutely not. Absolutely not. But I am married to someone. We [00:00:12] Aarthi: used to do overnights at Microsoft. Like we'd just sleep under our desk,, until the janitor would just , poke us out of there , I really need to vacuum your cubicle. Like, get out of here. There's such joy in , Finding those moments where you work hard and you're feeling really good about it. [00:00:25] Sriram: You'd be amazed at how many times Aarthi and I would have a conversation where be, oh, this algorithm thing.I remember designing it, and now we are on the other side We want to invest in something , where we think the team and the company is going to win and if they do win, there's huge value to be unlocked. [00:00:40] Dwarkesh: Okay. Today I have the, uh, good pleasure to have Arty and Sriram on the podcast and I'm really excited about this.So you guys have your own show, the Arty Andre Good Time show. Um, you guys have had some of the top people in tech and entertainment on Elon Musk, mark Zuckerberg, Andrew Yang, and you guys are both former founders. Advisors, investors, uh, general partner at Anderson Horowitz, and you're an angel investor and an advisor now.Um, so yeah, there's so much to talk about. Um, obviously there's also the, uh, recent news about your, uh, your involvement on, uh, twitter.com. Yeah, yeah. Let's get started. [00:01:19] Married Couples Starting Businesses[00:01:19] Dwarkesh: My first question, you guys are married, of course. People talk about getting a co-founder as finding a spouse, and I'm curious why it's not the case that given this relationship why more married people don't form tech startups.Is, does that already happen, [00:01:35] Aarthi: or, um, I actually am now starting to see a fair bit of it. Uhhuh, . Um, I, I do agree that wasn't a norm before. Um, I think, uh, I, I think I remember asking, uh, pg p the same thing when I went through yc, and I think he kind of pointed to him and Jessica like, you know, YC was their startup , and so, you know, there were even pride.There are a lot of husband and wife, uh, companies. Over the last like decade or so. So I'm definitely seeing that more mainstream. But yeah, you're right, it hasn't been the norm before. Yeah, the, the good time show is our project. It's [00:02:09] Sriram: our startup. Very, I mean, there are some good historical examples. Cisco, for example, uh, came from, uh, uh, husband, wife as a few other examples.I think, you know, on, on the, in, on the pro side, uh, you know, being co-founders, uh, you need trust. You need to really know each other. Uh, you, you go through a lot of like heavy emotional burdens together. And there's probably, and if you, you're for the spouse, hopefully you probably have a lot of chemistry and understanding, and that should help.On the con side, I think one is you, you're prob you know, you, you're gonna show up at work, you know, and startups are really hard, really intense. And you come home and both of you are gonna the exact same wavelength, the exact same time, going through the exact same highs and lows as opposed to two people, two different jobs have maybe differing highs and lows.So that's really hard. Uh, the second part of it is, uh, in a lot of. Work situations, it may just be more challenging where people are like, well, like, you know, person X said this person Y said this, what do I do? Uh, and if you need to fire somebody or you know, something weird happens corporate in a corporate manner, that may also be really hard.Uh, but having said that, you know, uh, [00:03:13] Aarthi: you know, yeah, no, I think both of those are like kind of overblown , like, you know, I think the reason why, um, you know, you're generally, they say you need to have you, it's good to have co-founders is so that you can kind of like write the emotional wave in a complimentary fashion.Uh, and you know, if one person's like really depressed about something, the other person can like pull them out of it and have a more rational viewpoint. I feel like in marriages it works even better. So I feel like to your first point, They know each other really well. You're, you're, you are going to bring your work to home.There is no separation between work and home as far as a startup is concerned. So why not do it together? Oh, [00:03:51] Sriram: well, I think there's one problem, uh, which is, uh, we are kind of unique because we've been together for over 21 years now, and we start for, we've been before, uh, let's not. Wow. There's gonna be some fact checking 19 on this video.99. Close enough. Close enough, right? Like close enough. He wishes he was 21. Oh, right, right, right. Gosh, feels like 21. We have do some, um, [00:04:15] Aarthi: editing on this video. No, no, no. I think 20 years of virtually knowing, 19 years of in-person. [00:04:20] Sriram: There we go. Right. Uh, fact check accurate. Um, ex experts agree. But, um, you know, but when you first met, we, we originally, even before we dating, we were like, Hey, we wanna do a company together.And we bonded over technology, like our first conversation on Yahoo Messenger talking about all these founders and how we wanted to be like them. And we actually then worked together pretty briefly when you were in Microsoft. Uh, before we actually started dating. We were on these sort of talent teams and we kind of met each of the word context.I think a lot of. You know, one is they have never worked together. Um, and so being in work situations, everything from how you run a meeting to how you disagree, uh, you know, uh, is just going to be different. And I think that's gonna be a learning curve for a lot of couples who be like, Hey, it's one thing to have a strong, stable relationship at home.It'll be a different thing to, you know, be in a meeting and you're disagreeing art's meetings very differently from I do. She obsesses over metrics. I'm like, ah, it's close enough. It's fine. , uh, it's close enough. It's fine. as e uh, here already. But, uh, so I do think there's a learning curve, a couples who is like, oh, working together is different than, you know, raising your family and being together.I mean, obviously gives you a strong foundation, but it's not the same thing. Have you guys [00:05:25] Dwarkesh: considered starting a company or a venture together at some point? [00:05:28] Aarthi: Yeah. Um, we've, uh, we've always wanted to do a project together. I don't know if it's a, a startup or a company or a venture. You have done a project together,Yeah, exactly. I think, uh, almost to today. Two years ago we started the Good Time Show, um, and we started at, uh, live Audio on Clubhouse. And, you know, we recently moved it onto video on YouTube. And, um, it's, it's been really fun because now I get to see like, it, it's neither of our full-time jobs, uh, but we spend enough, um, just cycles thinking through what we wanna do with it and what, uh, how to have good conversations and how to make it useful for our audience.So that's our [00:06:06] Sriram: project together. Yep. And we treat it like a, with the intellectual heft of a startup, which is, uh, we look at the metrics, uh, and we are like, oh, this is a good week. The metrics are up into the right and, you know, how do we, you know, what is working for our audience? You know, what do we do to get great guests?What do we do to [00:06:21] Aarthi: get, yeah, we just did our first, uh, in-person meetup, uh, for listeners of the podcast in Chennai. It was great. We had like over a hundred people who showed up. And it was also like, you know, typical startup style, like meet your customers and we could like go talk to these people in person and figure out like what do they like about it?Which episodes do they really enjoy? And it's one thing to see YouTube comments, it's another to like actually in person engage with people. So I think, you know, we started it purely accidentally. We didn't really expect it to be like the show that we are, we are in right now, but we really happy. It's, it's kind of turned out the way it has.[00:06:59] Sriram: Absolutely. And, and it also kind of helps me scratch an edge, which is, uh, you know, building something, you know, keeps you close to the ground. So being able to actually do the thing yourself as opposed to maybe tell someone else, telling you how to do the, so for example, it, it being video editing or audio or how thumbnails, thumbnails or, uh, just the mechanics of, you know, uh, how to build anything.So, uh, I, I dot think it's important. Roll up your sleeves metaphorically and get your hands dirty and know things. And this really helped us understand the world of creators and content. Uh, and it's fun and [00:07:31] Aarthi: go talk to other creators. Uh, like I think when we started out this thing on YouTube, I think I remember Shram just reached out to like so many creators being like, I wanna understand how it works for you.Like, what do you do? And these are people who like, who are so accomplished, who are so successful, and they do this for a living. And we clearly don. And so, uh, just to go learn from these experts. It's, it's kind of nice, like to be a student again and to just learn, uh, a new industry all over again and figure out how to actually be a creator on this platform.Well, you know [00:08:01] Dwarkesh: what's really interesting is both of you have been, uh, executives and led product in social media companies. Yeah. And so you are, you designed the products, these creators, their music, and now on the other end, you guys are building [00:08:12] Sriram: the, oh, I have a great phrase for it, right? Like, somebody, every once in a while somebody would be like, Hey, you know what, uh, you folks are on the leadership team of some of these companies.Why don't you have hundreds of millions of followers? Right? And I would go, Hey, look, it's not like every economist is a billionaire, , uh, uh, you know, it doesn't work that way. Uh, but during that is a parallel, which, which is, uh, you'd be amazed at how many times Aarthi and I would have a conversation where be, oh, this algorithm thing.I remember designing it, or I was in the meeting when this thing happened, and now we are on the other side, which is like, Hey, you might be the economist who told somebody to implement a fiscal policy. And now we are like, oh, okay, how do I actually go do this and create values and how? Anyway, how do we do exactly.Create an audience and go build something interesting. So there is definitely some irony to it, uh, where, uh, but I think hopefully it does give us some level of insight where, uh, we have seen, you know, enough of like what actually works on social media, which is how do you build a connection with your audience?Uh, how do you build, uh, content? How do you actually do it on a regular, uh, teams? I think [00:09:07] Aarthi: the biggest difference is we don't see the algorithm as a bra, as a black box. I think we kind of see it as like when the, with the metrics, we are able to, one, have empathy for the teams building this. And two, I think, uh, we kind of know there's no big magic bullet.Like I think a lot of this is about showing up, being really consistent, um, you know, being able to like put out some really interesting content that people actually want to, and you know, I think a lot of people forget about that part of it and kind of focus. If you did this one thing, your distribution goes up a lot and here's this like, other like secret hack and you know Sure.Like those are like really short term stuff, but really in the long term, the magic is to just like keep at it. Yeah. And, uh, put out really, really good content. [00:09:48] Sriram: Yeah. Yeah. And yeah, absolutely. Yeah. Yeah. Um, that's good to hear. . [00:09:53] 10x Engineers[00:09:53] Dwarkesh: Um, so you've both, um, led teams that have, you know, dozens or even hundreds of people.Um, how easy is it for you to tell who the 10 X engineers are? Is it something that you as managers and executives can tell easily or [00:10:06] Sriram: no? Uh, absolutely. I think you can tell this very easily or repeat of time and it doesn't, I think a couple of ways. One is, uh, Uh, before, let's say before you work with someone, um, 10 x people just don't suddenly start becoming 10 x.They usually have a history of becoming 10 x, uh, of, you know, being really good at what they do. And you can, you know, the cliche line is you can sort of connect the dots. Uh, you start seeing achievements pile up and achievements could be anything. It could be a bunch of projects. It could be a bunch of GitHub code commits.It could be some amazing writing on ck, but whatever it is, like somebody just doesn't show up and become a 10 x person, they probably have a track record of already doing it. The second part of it is, I've seen this is multiple people, uh, who are not named so that they don't get hired from the companies actually want them to be in, or I can then hire them in the future is, uh, you know, they will make incredibly rapid progress very quickly.So, uh, I have a couple of examples and almost independently, I know it's independently, so I have a couple of. Um, and I actually, and name both, right? Like, so one is, uh, this guy named, uh, Vijay Raji, uh, who, uh, was probably one of Facebook's best engineers. He's now the CEO of a company called Stats. And, um, he was probably my first exposure to the real TenX engineer.And I remembered this because, uh, you know, at the time I was. Kind of in my twenties, I had just joined Facebook. I was working on ads, and he basically built a large part of Facebook's ad system over the weekend. And what he would do is he would just go, and then he con he [00:11:24] Aarthi: continued to do that with Facebook marketplace.Yeah. Like he's done this like over and over and over [00:11:28] Sriram: again. . Yeah. And, and it's not that, you know, there's one burst of genius. It's just this consistent stream of every day that's a code checkin stuff is working. New demo somebody, he sent out a new bill or something working. And so before like a week or two, you just like a, you know, you running against Usain Bolt and he's kind of running laps around you.He's so far ahead of everyone else and you're like, oh, this guy is definitely ahead. Uh, the second story I have is, uh, of, uh, John Carmack, uh, you know, who's legend and I never worked with him in, uh, directly with, you know, hopefully someday I can fix. But, uh, somebody told me a story about him. Which is, uh, that the person told me story was like, I never thought a individual could replace the output of a hundred percent team until I saw John.And there's a great story where, um, you know, and so John was the most senior level at Facebook and from a hr, you know, employment insecurity perspective for an individual contributor, and it at, at that level, at Facebook, uh, for folks who kind of work in these big tech companies, it is the most, the highest tier of accomplishment in getting a year in a performance review is something called xcs Expectations, or, sorry, redefines, right?Which basically means like, you have redefined what it means for somebody to perform in this level, right? Like, it's like somebody, you know, like somebody on a four minute mile, I'll be running a two minute mile or whatever, right? You're like, oh, and, and it is incredibly hard sometimes. You doing, and this guy John gets it three years in a row, right?And so there's this leadership team of all the, you know, the really most important people on Facebook. And they're like, well, we should really promote John, right? Like, because he's done this three years in a row, he's changing the industry. Three years in a row and then they realized, oh wait, there is no level to promote him to Nick be CEOWell, maybe I don't think he wanted to. And so, uh, the story I heard, and I dunno, it's true, but I like to believe it's true, is they invented a level which still now only John Carmack has gotten. Right. And, um, and I think, you know, it's his level of productivity, uh, his, uh, intellect, uh, and the consistency over time and mu and you know, if you talk to anybody, Facebook work with him, he's like, oh, he replaced hundred people, teams all by themselves and maybe was better than a hundred percent team just because he had a consistency of vision, clarity, and activity.So those are [00:13:32] Aarthi: the two stories I've also noticed. I think, uh, actually sheam, I think our first kind of exposure to 10 x engineer was actually Barry born, uh, from Microsoft. So Barry, um, uh, basically wrote pretty much all the emulation engines and emulation systems that we all use, uh, and uh, just prolific, uh, and I think in addition to what Fred had said with like qualities and tenets, Um, the, I've generally seen these folks to also be like low ego and kind of almost have this like responsibility to, um, mentor coach other people.Uh, and Barry kind of like took us under his wing and he would do these like Tuesday lunches with us, where we would just ask like, you know, we were like fresh out of college and we just ask these like really dumb questions on, you know, um, scaling things and how do you build stuff. And I was working on, uh, run times and loaders and compilers and stuff.And so he would just take the time to just answer our questions and just be there and be really like, nice about it. I remember when you moved to Redmond, he would just like spend a weekend just like, oh yeah. Driving you about and just doing things like that, but very low ego and within their teams and their art, they're just considered to be legends.Yes. Like, you know, everybody would be like, oh, Barry Bond. Yeah, of course. [00:14:47] Sriram: Yeah. It, I can't emphasize enough the consistency part of it. Um, you know, with Barry. Or I gotta briefly work with Dave Cutler, who's kind of the father of modern operating systems, uh, is every day you're on this email li list at the time, which would show you check-ins as they happen.They would have something every single day, um, every day, and it'll be tangible and meaty and you know, and you just get a sense that this person is not the same as everybody else. Um, by the, this couple of people I can actually point to who haven't worked with, uh, but I follow on YouTube or streaming. Uh, one is, uh, Andrea Ling who builds Serenity Os we had a great episode with him.Oh, the other is George Hart's, uh, geo Hart. And I urge people, if you haven't, I haven't worked with either of them, uh, but if I urge which to kinda watch their streams, right? Because, uh, you go like, well, how does the anti killing build a web browser on an operating system? Which he builds by himself in such a sharp period of time and he watches stream and he's not doing some magical new, you know, bit flipping sorting algorithm anybody has, nobody has seen before.He's just doing everything you would do, but. Five bits of speed. I, yep, exactly. [00:15:48] Dwarkesh: I I'm a big fan of the George Hot Streams and Yeah, that's exactly what, you know, it's like yeah, you, he's also curling requests and he is also, you know, you know, spinning up an experiment in a Jupyter Notebook, but yeah, just doing it [00:15:58] Aarthi: away way faster, way efficiently.Yeah. [00:16:00] 15 Minute Meetings[00:16:00] Dwarkesh: Yeah. That's really interesting. Um, so ar Arthur, I'm, you've gone through Y Combinator and famously they have that 15 minute interview Yes. Where they try to grok what your business is and what your potential is. Yeah, yeah. But just generally, it seems like in Silicon Valley you guys have, make a lot of decisions in terms of investing or other kinds of things.You, in very short calls, you know. Yeah. . Yeah. And how much can you really, what is it that you're learning in these 15 minute calls when you're deciding, should I invest in this person? What is their potential? What is happening in that 15 minutes? [00:16:31] Aarthi: Um, I can speak about YC from the other side, from like, uh, being a founder pitching, right.I think, yes, there is a 15 minute interview, but before that, there is a whole YC application process. And, uh, I think even for the, for YC as, uh, this bunch of the set of investors, I'm sure they're looking for specific signals, but for me as a founder, the application process was so useful, um, because it really makes you think about what you're building.Why are you building this? Are you the right person to be building this? Who are the other people you should be hiring? And so, I mean, there are like few questions or like, one of my favorite questions is, um, how have you hacked a non-computer system to your advantage? Yeah. . And it kind of really makes you think about, huh, and you kind of noticed that many good founders have that pattern of like hacking other systems to their advantage.Um, and so to me, I think more than the interview itself, the process of like filling out the application form, doing that little video, all of that gives you better, um, it gives you the, the entire scope of your company in your head because it's really hard when you have this idea and you're kind of like noodling about with it and talking to a few people.You don't really know if this is a thing. To just like crystallize the whole vision in your head. I think, uh, that's on point. Yes. Um, the 15 minute interview for me, honestly, it was like kind of controversial because, uh, I went in that morning, I did the whole, you know, I, I had basically stayed at the previous night, uh, building out this website and, uh, that morning I showed up and I had my laptop open.I'm like really eager to like tell them what you're building and I keep getting cut off and I realize much later that that's kind of my design. Yeah. And you just like cut off all the time. Be like, why would anybody use this? And you start to answer and be like, oh, but I, I don't agree with that. And there's just like, and it, it's like part of it is like, makes you upset, but part of it is also like, it makes you think how to compress all that information in a really short amount of time and tell them.Um, and so that interview happens, I feel really bummed out because I kind of had this website I wanted to show them. So while walking out the door, I remember just showing Gary, Dan, um, the website and he like kind of like. Scrolls it a little bit, and he is like, this is really beautifully done. And I was like, thank you.I've been wanting to show you this for 15 minutes. Um, and I, I mentioned it to Gary recently and he laughed about it. And then, uh, I didn't get selected in that timeframe. They gave me a call and they said, come back again in the evening and we are going to do round two because we are not sure. Yeah. And so the second interview there was PG and Jessica and they both were sitting there and they were just grueling me.It was a slightly longer interview and PG was like, I don't think this is gonna work. And I'm like, how can you say that? I think this market's really big. And I'm just like getting really upset because I've been waiting this whole day to like get to this point. And he's just being like cynical and negative.And then at some point he starts smiling at Jessica and I'm like, oh, okay. They're just like baiting me to figure it out. And so that was my process. And I, by the evening, I remember Shera was working at. I remember driving down from Mountain View to Facebook and Sheam took me to the Sweet Stop. Oh yeah.Which is like their, you know, Facebook has this like, fancy, uh, sweet store, like the ice cream store. I [00:19:37] Sriram: think they had a lot more perks over the years, but that was very fancy back then. [00:19:40] Aarthi: So I had like two scoops of ice cream in each hand in, and, uh, the phone rang and I was like, oh, hold onto this. And I grabbed it and I, and you know, I think it was Michael Sibu or I don't know who, but somebody called me and said, you're through.So that was kind of my process. So even though there was only 15 minutes, mine was actually much longer after. But even before the, the application process was like much more detailed. So it sounds [00:20:01] Dwarkesh: like the 15 minutes it's really there. Like, can they rattle you? Can they, can they [00:20:06] Aarthi: you and how do you react?Yeah, yeah, yeah. Um, I also think they look for how sex you can be in explaining what the problem is. They do talk to hundreds of companies. It is a lot. And so I think, can you compress a lot of it and convince, if you can convince these folks here in three months or four months time, how are you going to do demo day and convince a whole room full of investors?[00:20:27] Sriram: Yeah. Yeah. For, I think it's a bit different for us, uh, on the VC side, uh, because two things. One, number one is, uh, the day, you know, so much of it is having a prepared mind before you go into the meeting. And, for example, if you're meeting a. very early. Are we investing before having met every single other person who's working in this space, who has ideas in the space.So you generally know what's going on, you know, what the kind of technologies are or go to market approaches are. You've probably done a bunch of homework already. It's usually, uh, it does happen where you meet somebody totally cold and uh, you really want to invest, but most often you've probably done some homework at least in this space, if not the actual company.Um, and so when you're in the meeting, I think you're trying to judge a couple of things. And these are obviously kind of stolen from Christ Dixon and others. Um, one is their ability to kind of go walk you through their idea, ma. And so very simply, um, you know, the idea MAs is, uh, and I think say the biology of Christen came with this, the idea that, hey, um, uh, How you got to the idea for your company really matters because you went and explored all the data ends, all the possibilities.You're managing around for years and years, and you've kind of come to the actual solution. And the way you can tell whether somebody's gone through the idea Mac, is when you ask 'em questions and they tell you about like five different things they've tried, did not work. And it, it's really hard to fake it.I mean, we, you maybe fake it for like one or two questions, but if you talk about like how we tried X, Y, and Z and they have like an opinion what of the opinions, if they've thought about it, you're like, okay, this person really studied the idea, ma. And that's very powerful. Uh, the second part of it is, uh, you know, Alex sample.Uh, uh, one of my partner says this, Yes, some this thing called the Manifestation Framework, which sounds like a self-help book on Amazon, but it's not, uh, uh uh, you know, but what if is, is like, you know, so many, so much of early stage startup founders is about the ability to manifest things. Uh, manifest capital, manifest the first hire, uh, manifest, uh, the first BD partnership.And, um, usually, you know, if you can't, if you don't have a Cigna sign of doing that, it's really hard to then after raising money, go and close this amazing hotshot engineer or salesperson or close this big partnership. And so in the meeting, right? If you can't convince us, right? And these are people, our day job is to give you money, right?Like, if I spent a year without giving anybody money, I'll probably get fired. If you can't, uh, if you can't convince us to give you money, right? If you wanna find probably a hard time to close this amazing engineer and get that person to come over from Facebook or close this amazing partnership against a competitor.And so that's kind of a judge of that. So it is never about the actual 60 Minutes where you're like, we, we are making up of a large part of makeup of mind is. That one or two conversations, but there's so much which goes in before and after that. Yeah, yeah. Speaking of [00:22:57] What is a16z's edge?[00:22:57] Dwarkesh: venture capital, um, I, I'm curious, so interest and Horowitz, and I guess why Combinator too?Um, but I mean, any other person who's investing in startups, they were started at a time when there were much less capital in the space, and today of course, there's been so much more capital pour into space. So how do these firms, like how does A 16 C continue to have edge? What is this edge? How can I sustain it [00:23:20] Sriram: given the fact that so much more capital is entered into the space?We show up on podcasts like the Lunar Society, , and so if you are watching this and you have a startup idea, Uh, come to us, right? Uh, no. Come, come to the Lunar society. . Well, yes. I mean, maybe so Trust me, you go in pat, you're gonna have a find, uh, a Thk pat right there. Uh, actually I, you think I joked, but there's a bit of truth.But no, I've had [00:23:40] Dwarkesh: like lu this [00:23:40] Aarthi: suddenly became very different [00:23:43] Sriram: conversation. I have had people, this is a totally ludicrous [00:23:46] Dwarkesh: idea, but I've had people like, give me that idea. And it's like, it sounds crazy to me because like, I don't know what, it's, what a company's gonna be successful, right? So, but I hasn't [00:23:55] Aarthi: become an investor.[00:23:57] Sriram: I honestly don't know. But it is something like what you're talking about Lu Society Fund one coming up, right? You heard it here first? Uh, uh, well, I think first of all, you know, I think there's something about the firm, uh, um, in terms of how it's set up philosophically and how it's set up, uh, kind of organizationally, uh, and our approach philosoph.The firm is an optimist, uh, uh, more than anything else. At the core of it, we are optimist. We are optimist about the future. We are optimist about the impact of founders on their, on the liberty to kind of impact that future. Uh, we are optimist at heart, right? Like I, I tell people like, you can't work at a six and z if you're not an optimist.That's at the heart of everything that we do. Um, and very tied to that is the idea that, you know, um, software is eating the world. It is, it's true. 10 years ago when Mark wrote that, peace is as true now, and we just see more and more of it, right? Like every week, you know, look at the week we are recording this.You know, everyone's been talking about chat, G p T, and like all the industries that can get shaped by chat, G P T. So our, our feature, our, our idea is that software is gonna go more and more. So, one way to look at this is, yes, a lot more capitalists enter the world, but there should be a lot more, right?Like, because these companies are gonna go bigger. They're gonna have bigger impacts on, uh, human lives and, and the world at large. So that's, uh, you know, uh, one school of thought, the other school of thought, uh, which I think you were asking about, say valuations, uh, et cetera. Is, uh, you know, um, again, one of my other partners, Jeff Jordan, uh, uh, always likes to tell people like, we don't go discount shopping, right?Our, the way we think about it is we want to, when we're investing in a market, We want to really map out the market, right? Uh, so for example, I work on crypto, uh, and, uh, you know, we, you know, if, if you are building something interesting in crypto and we haven't seen you, we haven't talked to you, that's a fail, that's a mess, right?We ideally want to see every single interesting founder company idea. And a category can be very loose. Crypto is really big. We usually segmented something else. Or if you look at enterprise infrastructure, you can take them into like, you know, AI or different layers and so on. But once you map out a category, you want to know everything.You wanna know every interesting person, every interesting founder you wanna be abreast of every technology change, every go to market hack, every single thing. You wanna know everything, right? And then, uh, the idea is that, uh, we would love to invest in, you know, the what is hopefully becomes the market.Set category, uh, or you know, somebody who's maybe close to the, the market leader. And our belief is that these categories will grow and, you know, they will capture huge value. Um, and as a whole, software is still can used to be undervalued by, uh, a, you know, the world. So, um, we, so, which is why, again, going back to what Jeff would say, he's like, we are not in the business of oh, we are getting a great deal, right?We, we are like, we want to invest in something which, where we think the team and the company and their approach is going to win in this space, and we want to help them win. And we think if they do win, there's a huge value to be unlocked. Yeah, I see. I see. Um, [00:26:42] Future of Twitter[00:26:42] Dwarkesh: let's talk about Twitter. [00:26:44] Sriram: Uh, . I need a drink. I need a drink.[00:26:48] Dwarkesh: um, Tell me, what is the future of Twitter? What is the app gonna look like in five years? You've, um, I mean obviously you've been involved with the Musk Venture recently, but, um, you've, you've had a senior position there. You were an executive there before a few years ago, and you've also been an executive at, uh, you've both been at Meta.So what [00:27:06] Sriram: is the future of Twitter? It's gonna be entertaining. Uh, uh, what is it El say the most entertaining outcome is the most, [00:27:12] Aarthi: uh, uh, like, best outcome is the most, uh, most likely outcome is the most entertaining outcome. [00:27:16] Sriram: Exactly right. So I think it's gonna be the most entertaining outcome. Um, I, I mean, I, I, I think a few things, uh, first of all, uh, ideally care about Twitter.Yeah. Uh, and all of my involvement, uh, you know, over the years, uh, uh, professionally, you know, uh, has, it's kind of. A lagging indicator to the value I got from the service person. I have met hundreds of people, uh, through Twitter. Uh, hundreds of people have reached out to me. Thousands. Exactly. Uh, and you know, I met Mark Andresen through Twitter.Uh, I met like, you know, uh, people are not very good friends of mine. We met through Twitter. We met at Twitter, right. There we go. Right. Uh, just [00:27:50] Aarthi: like incredible outsized impact. Yeah. Um, and I think it's really hard to understate that because, uh, right now it's kind of easy to get lost in the whole, you know, Elon, the previous management bio, like all of that.Outside of all of that, I think the thing I like to care about is, uh, focus on is the product and the product experience. And I think even with the product experience that we have today, which hasn't like, dramatically changed from for years now, um, it's still offering such outsized value for. If you can actually innovate and build really good product on top, I think it can, it can just be really, really good for humanity overall.And I don't even mean this in like a cheesy way. I really think Twitter as a tool could be just really, really effective and enormously good for everyone. Oh yeah. [00:28:35] Sriram: Twitter is I think, sort of methodically upstream of everything that happens in culture in uh, so many different ways. Like, um, you know, there was this, okay, I kinda eli some of the details, uh, but like a few years ago I remember there was this, uh, sort of this somewhat salacious, controversial story which happened in entertainment and uh, and I wasn't paying attention to, except that something caught my eye, which was that, uh, every story had the same two tweets.And these are not tweets from any famous person. It was just some, like, some, um, you know, somebody had some followers, but not a lot of, a lot of followers. And I. Why is this being quoted in every single story? Because it's not from the, you know, the person who was actually in the story or themselves. And it turned out that, uh, what had happened was, uh, you know, somebody wrote in the street, it had gone viral, um, it started trending on Twitter, um, and a bunch of people saw it.They started writing news stories about it. And by that afternoon it was now, you know, gone from a meme to now reality. And like in a lot of people entertainment say, kind of go respond to that. And I've seen this again and again, again, right? Uh, sports, politics, culture, et cetera. So Twitter is memetically upstream of so much of life.Uh, you know, one of my friends had said like, Twitter is more important than the real world. Uh, which I don't, I don't know about that, but, uh, you know, I do think it's, um, it has huge sort of, uh, culture shaping value. Yeah. I thing I think about Twitter is so much of. The network is very Lindy. So one of the things I'm sure from now is like five years from now, you know, what does that mean?Well that, uh, is that something which has kind of stood the test of time to some extent? And, um, and, uh, well the Lindy effect generally means, I don't think it's using this context with ideas like things which, with withstood the test of time tend to also with some test of time in the future, right? Like, like if we talked to Naim is like, well, people have lifting heavy weights and doing red wine for 2000 years, so let's continue doing that.It's probably a good thing. Um, but, but, but that's Twitter today. What is the future of Twitter? Well, uh, well, I think so one is, I think that's gonna continue to be true, right? 10 years from now, five years from now, it's still gonna be the metic battleground. It's still gonna be the place where ideas are shared, et cetera.Um, you know, I'm very. Unabashedly a a big fan of what Elon, uh, as a person, as a founder and what he's doing at Twitter. And my hope is that, you know, he can kind of canoe that and, you know, he's, you know, and I can't actually predict what he's gonna go Bill, he's kind of talked about it. Maybe that means bringing in other product ideas.Uh, I think he's talked about payments. He's talked about like having like longer form video. Uh, who knows, right? But I do know, like five years from now, it is still gonna be the place of like active conversation where people fight, yell, discuss, and maybe sometimes altogether. Yeah. Yeah. Uh, the Twitter, [00:30:58] Is Big Tech Overstaffed?[00:30:58] Dwarkesh: um, conversation has raised a lot of, a lot of questions about how over or understaffed, uh, these big tech companies are, and in particular, um, how many people you can get rid of and the thing basically functions or how fragile are these code bases?And having worked at many of these big tech companies, how, how big is the bus factor, would you guess? Like what, what percentage of people could I fire at the random big tech [00:31:22] Sriram: company? Why? I think, uh, [00:31:23] Aarthi: yeah, I think. That's one way to look at it. I think the way I see it is there are a few factors that go into this, right?Like pre covid, post covid, like through covid everybody became remote, remote teams. As you scaled, it was kind of also hard to figure out what was really going on in different parts of the organization. And I think a lot of inefficiencies were overcome by just hiring more people. It's like, oh, you know what, like that team, yeah, that project's like lagging, let's just like add 10 more people.And that's kind of like it became the norm. Yeah. And I think a lot of these teams just got bigger and bigger and bigger. I think the other part of it was also, um, you lot of how performance ratings and culture of like, moving ahead in your career path. And a lot of these companies were dependent on how big your team was and uh, and so every six months or year long cycle or whatever is your performance review cycle, people would be like, this person instead of looking at what has this person shipped or what has like the impact that this person's got had, uh, the team's done.It became more of like, well this person's got a hundred percent arc or 200% arc and next year they're gonna have a 10% increase and that's gonna be like this much. And you know, that was the conversation. And so a lot of the success and promo cycles and all of those conversations were tied around like number of headcount that this person would get under them as such, which I think is like a terrible way to think about how you're moving up the ladder.Um, you should really, like, even at a big company, you should really be thinking about the impact that you've had and customers you've reached and all of that stuff. And I think at some point people kind of like lost that, uh, and pick the more simpler metric, which just headcount and it's easy. Yeah. And to just scale that kind of thing.So I think now with Elon doing this where he is like cutting costs, and I think Elon's doing this for different set of reasons. You know, Twitter's been losing money and I think it's like driving efficiency. Like this is like no different. Anybody else who like comes in, takes over a business and looks at it and says, wait, we are losing money every day.We have to do something about this. Like, it's not about like, you know, cutting fat for the sake of it or anything. It's like this, this business is not gonna be viable if we keep it going the way it is. Yeah. And just pure economics. And so when he came in and did that, I'm now seeing this, and I'm sure Sheam is too at like at eight 16 Z and like his companies, uh, but even outside, and I see this with like my angel investment portfolio of companies, um, and just founders I talk to where people are like, wait, Elon can do that with Twitter.I really need to do that with my company. And it's given them the permission to be more aggressive and to kind of get back into the basics of why are we building what we are building? These are our customers, this is our revenue. Why do we have these many employees? What do they all do? And not from a place of like being cynical, but from a place of.I want people to be efficient in doing what they do and how do we [00:34:06] Sriram: make that happen? Yeah. I, I stole this, I think somebody said this on Twitter and I officially, he said, Elon has shifted the overturn window of, uh, the playbook for running a company. Um, which is, I think if you look at Twitter, uh, you know, and by the way, I would say, you know, you know the sort of, the warning that shows up, which is don't try this at home before, which is like, so don't try some of these unless you're er and maybe try your own version of these.But, you know, number one is the idea that you, you can become better not through growth, but by cutting things. You can become better, by demanding more out of yourself and the people who work for you. Uh, you, you can become better by hiring a, you know, a higher bar, sitting a higher bar for the talent that you bring into the company and, uh, that you reach into the company.I think at the heart of it, by the way, uh, you know, it's one of the things I've kinda observed from Elon. His relentless focus on substance, which is every condition is gonna be like, you know, the, the meme about what have you gotten done this week is, it kinda makes sense to everything else, which is like, okay, what are we building?What is the thing? Who's the actual person doing the work? As opposed to the some manager two levels a about aggregating, you know, the reports and then telling you what's being done. There is a relentless focus on substance. And my theory is, by the way, I think maybe some of it comes from Iran's background in, uh, space and Tesla, where at the end of the day, you are bound by the physics of the real world, right?If you get something wrong, right, you can, the rockets won't take off or won't land. That'd be a kalo, right? Like what, what's a, the phrase that they use, uh, rapid unplanned disassembly is the word. Right? Which is like better than saying it went kaboom. Uh, but, you know, so the constraints are if, if, you know, if you get something wrong at a social media company, people can tell if you get something really wrong at space with the Tesla.People can tap, right? Like very dramatically so and so, and I think, so there was a relentless focus on substance, right? Uh, being correct, um, you know, what is actually being done. And I think that's external Twitter too. And I think a lot of other founders I've talked to, uh, uh, in, sometimes in private, I look at this and go, oh, there is no different playbook that they have always I instituted or they were used to when they were growing up.We saw this when we were growing up. They're definitely seen some other cultures around the world where we can now actually do this because we've seen somebody else do this. And they don't have to do the exact same thing, you know, Elon is doing. Uh, they don't have to, uh, but they can do their variations of demanding more of themselves, demanding more of the people that work for them.Um, focusing on substance, focusing on speed. Uh, I think our all core element. [00:36:24] Aarthi: I also think over the last few years, uh, this may be controversial, I don't know why it is, but it somehow is that you can no longer talk about hard work as like a recipe for success. And you know, like growing up for us. When people say that, or like our parents say that, we just like kind of roll our eyes and be like, yeah, sure.Like, we work hard, like we get it. Yeah. But I think over the last couple of years, it just became not cool to say that if you work hard, then you can, there is a shot at like finding success. And I think it's kind of refreshing almost, uh, to have Elon come in and say, we are gonna work really hard. We are gonna be really hardcore about how we build things.And it's, it's very simple. Like you have to put in the hours. There is no kind of shortcut to it. And I think it's, it's nice to bring it all tight, all back to the basics. And, uh, I like that, like, I like the fact that we are now talking about it again and it's, it's sad that now talking about working really hard or having beds in your office, we used to do that at MicrosoftYeah. Uh, is now like suddenly really controversial. And so, um, I'm, I'm all for this. Like, you know, it's not for everyone, but if you are that type of person who really enjoys working hard, really enjoys shipping things and building really good things, Then I think you might find a fit in this culture. And I think that's a good thing.Yeah. I, [00:37:39] Sriram: I think there's nothing remarkable that has been built without people just working really hard. It doesn't happen for years and years, but I think for strong, some short-term burst of some really passionate, motivated, smart people working some really, you know, and hard doesn't mean time. It can mean so many different dimensions, but I don't think anything great gets built without that.So, uh, yeah, it's interesting. We [00:37:59] Aarthi: used to like do overnights at Microsoft. Like we'd just like sleep under our desk, um, until the janitor would just like, poke us out of there like, I really need to vacuum your cubicle. Like, get out of here. And so we would just like find another bed or something and just like, go crash on some couch.But it was, those were like some of our fun days, like, and we look back at it and you're like, we sh we built a lot. I think at some point sh I think when I walked over to his cubicle, he was like looking at Windows Source code and we're like, we are looking at Windows source code. This is the best thing ever.I think, I think there's such joy in like, Finding those moments where you like work hard and you're feeling really good about it. [00:38:36] Sriram: Yeah, yeah, yeah. Um, so you [00:38:37] Next CEO of Twitter?[00:38:37] Dwarkesh: get working hard and bringing talent into the company, uh, let's say Elon and says Tomorrow, you know what, uh, Riam, I'm, uh, I've got these other three companies that I've gotta run and I need some help running this company.And he says, Sriram would you be down to be the next, [00:38:51] Sriram: uh, next CEO of Twitter Absolutely not. Absolutely not. But I am married to someone. No, uh uh, no, uh uh, you know, you know when, uh, I don't think I was, the answer is absolutely not. And you know this exactly. Fun story. Um, uh, I don't think it says in public before. So when you, when I was in the process, you know, talking to and nor words and, you know, it's, it's not like a, uh, it's not like a very linear process.It's kind of a relationship that kind of develops over time. And I met Mark Andreen, uh, multiple times over the years. They've been having this discussion of like, Hey, do you want to come do venture or do you want to, if you wanna do venture, do you wanna come do with us? And um, and, and one of the things Mark would always tell me is, uh, something like, we would love to have you, but you have to scratch the edge of being an operator first.Um, because there are a lot of, there are a lot of ways VCs fail, uh, operator at VCs fail. Um, and I can get, get into some of them if you're interested, but one of the common ways that they fail is they're like, oh, I really want to go back to, um, building companies. And, uh, and now thing is like antis more than most interest, like really respects entrepreneurship, fraud's the hard of what we do.But he will, like, you have to get that out of a system. You have to be like, okay, I'm done with that word. I want to now do this. Uh, before you know, uh, you want to come over, right? And if you say so, let's have this conversation, but if not, we will wait for you. Right. And a woman telling me this all the time, and at some point of time I decided, uh, that, uh, you know, I just love this modoc.Um, you know, there are many things kind of different about being an operator versus a BC uh, and you kind of actually kind of really train myself in what is actually a new profession. But one of the things is like, you know, you kind of have to be more of a coach and more open to like, working with very different kinds of people without having direct agency.And it's always a very different mode of operation, right? And you have to be like, well, I'm not the person doing the thing. I'm not the person getting the glory. I'm here to fund, obviously, but really help support coach be, uh, a lending hand, be a supporting shoulder, whatever the, uh, the metaphor is, or for somebody else doing the thing.And so you kind of have to have the shift in your brain. And I think sometimes when VCs don't work out, the few operator on VCs don't work out. There are few reasons. Uh, number one reason I would say is when an operator, and I, I hate the word operator by the way, right? It just means you have a regular job.Uh, you know, uh, and, uh, but the number one reason is like when you have a regular job, you know, you're an engineer, you're, you're a product manager, you're a marketer, whatever. , you get feedback every single day about how you're doing. If you're an engineer, you're checking in code or you know your manager, you hire a great person, whatever it is.When you're at Visa, you're not getting direct feedback, right? You know, maybe today what I'm doing now, recording this with you is the best thing ever because some amazing fund is gonna meet it and they're gonna come talk to me, or maybe it's a total waste of time and I should be talking some else. You do have no way of knowing.So you really have to think very differently about how you think about patients, how we think about spending your time, and you don't get the dopamine of like, oh, I'm getting this great reinforcement loop. Um, the second part of it is because of that lack of feedback loop, you often don't know how well you're doing.Also, you don't have that fantastic product demo or you're like, you know, if an engineer like, oh, I got this thing working, the builder is working, it's 10 x faster, or this thing actually works, whatever the thing is, you don't get that feedback loop, uh, because that next great company that, you know, the next Larry and Sergey or Brian Armstrong might walk in through your door or Zoom meeting tomorrow or maybe two years from now.So you don't really have a way to know. Um, so you kind of have to be, you have a focus on different ways to do, uh, get. Kind of figured out how well you're doing. The third part of it is, uh, you know, the, uh, the feedback loops are so long where, uh, you know, you, you can't test it. When I was a product manager, you would ship things, something you, if you don't like it, you kill it, you ship something else.At, at our firm in, you invest in somebody, you're working with them for a decade, if not longer, really for life in some ways. So you are making much more intense, but much less frequent decisions as opposed to when you're in a regular job, you're making very frequent, very common decisions, uh, every single day.So, uh, I get a lot of differences and I think, you know, sometimes, uh, you know, folks who, who are like a former CEO or former like VP product, uh, uh, I talk a lot of them sometimes who went from, came to BC and then went back and they either couldn't adapt or didn't like it, or didn't like the emotions of it.And I had to really convince myself that okay. Hopefully wouldn't fate those problems. I probably, maybe some other problems. And, uh, uh, so yes, the long way of saying no, , [00:43:13] Why Don't More Venture Capitalists Become Founders?[00:43:13] Dwarkesh: um, the desk partly answer another question I had, which was, you know, there is obviously this pipeline of people who are founders who become venture capitalists.And it's interesting to me. I would think that the other end or the converse of that would be just as common because if you're, if you're an angel investor or venture capitalist, you've seen all these companies, you've seen dozens of companies go through all these challenges and then you'd be like, oh, I, I understand.[00:43:36] Sriram: Wait, why do you think more VCs driven apart? You have some strong opinions of this . [00:43:40] Dwarkesh: Should more venture capitalists and investors become founders? I think [00:43:43] Aarthi: they should. I don't think they will. Ouch. I dunno, why not? Um, I think, uh, look, I think the world is better with more founders. More people should start companies, more people should be building things.I fundamentally think that's what needs to happen. Like our single biggest need is like, we just don't have enough founders. And we should just all be trying new things, building new projects, all of that. Um, I think for venture capital is, I think what happens, and this is just my take, I don't know if Farram agrees with it, but, um, I think they see so much from different companies.And if you're like really successful with what you do as a vc, you are probably seeing hundreds of companies operate. You're seeing how the sausage is being made in each one of them. Like an operating job. You kind of sort of like have this linear learning experience. You go from one job to the other.Here you kind of sort of see in parallel, like you're probably on like 50, 60 boards. Uh, and oftentimes when it comes to the investor as like an issue, it is usually a bad problem. Um, and you kind of see like you, you know, you kind of see how every company, what the challenges are, and every company probably has like, you know, the best companies we know, I've all had this like near death experience and they've come out of that.That's how the best founders are made. Um, you see all of that and I think at some point you kind of have this fear of like, I don't know. I just don't think I wanna like, bet everything into this one startup. One thing, I think it's very hard to have focus if you've honed your skillset to be much more breath first and go look at like a portfolio of companies being helpful to every one of them.And I see Sure. And do this every day where I, I have no idea how he does it, but key context, which is every 30 minutes. Yeah. And it's crazy. Like I would go completely and say, where if you told me board meeting this founder pitch, oh, sell this operating role for this portfolio company. Second board meeting, third, board meeting founder, pitch founder pitch founder pitch.And that's like, you know, all day, every day nonstop. Um, that's just like, you, you, I don't think you can like, kind of turn your mindset into being like, I'm gonna clear up my calendar and I'm just gonna like work on this one thing. Yeah. And it may be successful, it may not be, but I'm gonna give it my best shot.It's a very, very different psychology. I don't know. What do you [00:45:57] Sriram: think? Well, Well, one of my partners Triess to say like, I don't know what VCs do all day. The job is so easy, uh, uh, you know, they should start complaining. I mean, being a founder is really hard. Um, and I think, you know, there's a part of it where the VCs are like, oh, wait, I see how hard it is.And I'm like, I'm happy to support, but I don't know whether I can go through with it. So, because it's just really hard and which is kind of like why we have like, so much, uh, sort of respect and empathy, uh, for the whole thing, which is, I, [00:46:20] Aarthi: I do like a lot of VCs, the best VCs I know are people who've been operators in the past because they have a lot of empathy for what it takes to go operate.Um, and I've generally connected better with them because you're like, oh, okay, you're a builder. You've built these things, so, you know, kind of thing. Yeah. Um, but I do think a lot more VCs should become [00:46:38] Sriram: founders than, yeah. I, I think it's some of the couple of other things which happened, which is, uh, uh, like Arthur said, like sometimes, uh, you know, when we see you kind of, you see, you kind of start to pattern match, like on.And you sometimes you analyze and, and you kind of, your brain kind of becomes so focused on context switching. And I think when need a founder, you need to kind of just dedicate, you know, everything to just one idea. And it, it's not just bbc sometimes with academics also, where sometimes you are like a person who's supporting multiple different kinds of disciplines and context switching between like various speech students you support.Uh, but it's very different from being in the lab and working on one problem for like long, long years. Right. So, um, and I think it's kind of hard to then context switch back into just doing the exact, you know, just focus on one problem, one mission, day in and day out. So I think that's hard, uh, and uh, but you should be a founder.Yeah, I think, yeah, I think more people should try. [00:47:32] Role of Boards[00:47:32] Dwarkesh: . Speaking of being on boards, uh, what the FTX Saga has raised some questions about what is like the role of a board, even in a startup, uh, stage company, and you guys are on multiple boards, so I'm curious how you think about, there's a range of between micromanaging everything the CEO does to just rubber stamping everything the CEO does.Where, what is the responsibility of a board and a startup? [00:47:54] Aarthi: What, what, what are the, this is something I'm really curious about too. I'm [00:47:57] Sriram: just, well, I just wanna know on the FDX soccer, whether we are gonna beat the FTX episode in interviews in terms of view your podcast, right? Like, so if you folks are listening, right?Like let's get us to number one. So what you YouTube like can subscriber, they're already listening. [00:48:10] Aarthi: What do you mean? Get us [00:48:10] Sriram: to number one? Okay, then, then spread the word, right? Like, uh, don't [00:48:13] Aarthi: watch other episodes. It's kinda what you [00:48:15] Sriram: should, I mean, if there's [00:48:16] Dwarkesh: like some sort of scandal with a 16 Z, we could definitely be to fdx.[00:48:21] Sriram: Uh, uh, yeah, I think it's gonna, well, it's gonna be really hard to read that one. Uh, , uh, uh, for for sure. Uh, uh, oh my goodness. Um, uh, but no, [00:48:29] Aarthi: I'm, I'm genuinely curious about [00:48:31] Sriram: these two. Well, uh, it's a few things, you know, so the multiple schools of thought, I would say, you know, there's one school of thought, which is the, uh, uh, you know, which I don't think I totally subscribe to, but I think some of the other later stages, especially public market folks that I work with sometimes subscribe to, which is the only job of a, uh, board is to hire and fire the ceo.I don't think I really subscribe to that. I think because we deal with more, uh, early stage venture, um, and our job is like, uh, you know, like lot of the companies I work with are in a cdc c, b, you know, they have something working, but they have a lot long way to go. Um, and hopefully this journey, which goes on for many, many years, and I think the best way I thought about it is to, people would say like, you want to be.Wave form dampener, which is, uh, you know, for example, if the company's kind of like soaring, you want to kind of be like kind the check and balance of what? Like, hey, okay, what do we do to, uh, you know, um, uh, to make sure we are covering our bases or dotting the is dotting the, crossing The ts be very kind of like careful about it because the natural gravitational pool of the company is gonna take it like one direct.On the other hand, uh, if the company's not doing very well and everybody's beating us, beating up about it, you're, you know, your cust you're not able to close deals. The press is beating you up. You want to be the person who is supportive to the ceo, who's rallying, everybody helping, you know, convince management to stay, helping convince, close host, hire.So, um, there are a lot of things, other things that go into being a board member. Obviously there's a fiscal responsibility part of things, and, um, you know, um, because you kind of represent so many stakeholders. But I think at the heart of it, I kind of think about, uh, you know, how do I sort of help the founder, uh, the founder and kind of dampen the waveform.Um, the other Pinteresting part was actually the board meetings. Uh, Themselves do. Uh, and I do think like, you know, about once a year or, uh, so like that there's every kind of, there's, there's almost always a point every 18 months or so in a company's lifetime where you have like some very decisive, interesting moment, right?It could be good, it could be bad. And I think those moments can be, uh, really, really pivotal. So I think there's, there's huge value in showing up to board meetings, being really prepared, uh, uh, where you've done your homework, you, you know, you've kind of had all the conversations maybe beforehand. Um, and you're coming into add real value, like nothing kind of annoying me if somebody's just kind of showing up and, you know, they're kind of maybe cheering on the founder once or twice and they kind of go away.So I don't think you can make big difference, but, uh, you know, I think about, okay, how are we sort of like the waveform, the, you know, make sure the company, [00:50:58] Aarthi: but I guess the question then is like, should startups have better corporate governance compared to where we are today? Would that have avoided, like, say the FTX [00:51:08] Sriram: saga?No, I mean, it's, I mean, we, I guess there'll be a legal process and you'll find out right when the FTX case, nobody really knows, you know, like, I mean, like what level of, uh, who knew what, when, and what level of deceptions, you know, deception, uh, uh, you know, unfolded, right? So, uh, it, yeah. Maybe, but you know, it could have been, uh, it could have been very possible that, you know, uh, somebody, somebody just fakes or lies stuff, uh, lies to you in multiple ways.[00:51:36] Aarthi: To,

“Whatever point you are at, you kind of have to go back and say ‘what is the thing that you're building?' And ‘do people really want it?'” — Immad Akhund This week Sachit (@sachitgupta) chats with Immad Akhund (@immad), CEO of Mercury — The company trusted by more than 100,000 startups for banking*. Mercury gives founders free checking and savings accounts, debit and credit cards*, domestic and USD international wire transfers, Treasury*, venture debt, and more. He co-founded the company in 2017 after his own frustrations as an entrepreneur with the traditional banking hurdles founders face as they set up and run their businesses. He started Mercury to remove that friction by building an intuitive product experience for necessary financial products in order to help founders manage their business with confidence. Launched in 2019, Mercury has raised $163M from a16z, Coatue, CRV and others. Immad is a serial founder who cuts through a problem and catalyzes change for the industry around it. Born in Pakistan and raised in the U.K., Immad immigrated to the U.S. to join Y Combinator with his previous startup Heyzap (acquired by Fyber). He is a former part-time partner at Y Combinator and is an active angel investor, with more than 250 investments in startups including Airtable, Rappi and Substack. Follow our host, Sachit Gupta on Twitter and sign up for the Creators Collective Newsletter. Do you want to learn how to make a living as a creator? Check out the CreatorsMBA. (02:27) - Dichotomy of being a business person and a creative person (04:42) - The impact and rise of no-code tools to build stuff (07:15) - What trends to look for to determine what to build and whether you should raise funds or not (10:00) - YC for creators (14:36) - The process they followed to build Mercury (17:44) - Product-led growth — What is it? (19:26) - 10x improvements they made during the building phase of mercury (21:46) - How they structured the production function (27:07) - Times when Immad wanted to give up (31:11) - How they were iterating to build, without having feedback from customers  (33:39) - Things they did in the early stages that have been giving them massive results (38:07) - What he looks for in people when building a start-up team (40:24) - The difference between great investors and people with money (43:18) - The transition from the building phase to the growth phase (45:50) - Best practices — Product first growth mindset (49:14) - How he enables the culture in order to make sure people support each other (53:45) - What are the first hires to make (55:09) - Has he ever hired 10x engineers (59:02) - Building a remote company with a strong culture and doing rapid innovation (01:03:28) - Mercury as a bank account and platform (01:06:49) - How has his love for SciFi influenced the product building (01:12:28) - How he propagated his ethics in the team (01:14:58) - Politics — His thoughts on banning people  (01:17:15) - Scifi books that have impacted him (01:18:45) - One piece of wisdom that changed the game for him (01:20:30) - One person he is grateful to (01:21:31) - How he has evolved as an entrepreneur (01:22:54) - What it means to be a conscious creator

Brendan Dell gets paid to position his clients to connect with top technology brands, including Expedia, ADP, HP, YC and 99 Start Ups portfolio companies.  Brandon's claim is to help people with their “$1B Pitch.” Brendan's course, $1B Pitch, examines the 8 elements of $1B pitches.  His podcast Billion Dollar Tech reaches founders, executives, VCs, and PE investors globally. In this podcast, Brendan provides high level insights into his work, and book, The 12 Immutable Laws of High-Impact Messaging.  Join this conversation if you'd like an introduction to Brendan's $1B Pitch. Spotify  Apple Podcast  Google Podcast  Manage2Win   ------- This Manage 2 Win Podcast episode is brought to you by Habitly.  I (David) review Habitly best practices regularly, and teach these essential people skills to clients weekly.  This advice has changed my life, and made millions for our clients. I started developing Habitly content in 2004.  Habitly's powerful best practices have now been taught to thousands of people worldwide.  For instance, you can learn how to Create time in your day;  Get more from meetings;  Stay calm;  Achieve significant targets;  and Become a great leader.  Simply study and apply the expert knowledge provided in Habitly courses and micro-learning episodes. Whether you're just out of college, or someone with over 20 years work experience, learn the habits of highly successful people on Habitly.  Test drive Habitly for 7 days on us!  This includes full access to the entire Habitly knowledgebase – www.habitly.com.

One of the most common topics that founders ask us about is pricing and monetization. In this talk, YC Group Partner Aaron Epstein outlines 9 different business models, and highlights lessons from top YC companies on how to best monetize and price your product. Business Model Guide: https://www.ycombinator.com/library/Gh-business-model-guide Apply to Y Combinator: https://www.ycombinator.com/apply/

This week, Mary Ann is taking the reins with another favorite from the TechCrunch Disrupt stage. She sat down with Brex CEO and co-founder, Henrique Dubugras, and Anu Hariharan, YC's managing director for continuity and an early Brex investor, to expose the context around this whirlwind of a year.The conversation candidly uncovers details behind the fintech's pandemic pivot, layoffs, and going remote. If you love the conversation, share it with a friend. And if you want more on Brex, Mary Ann dove deeper into the conversation last month.Equity drops every Monday, Wednesday and Friday at 7 a.m. PT, so subscribe to us on Apple Podcasts, Overcast, Spotify and all the casts. TechCrunch also has a great show on crypto, a show that interviews founders, a show that details how our stories come together and more!