Podcasts about Silicon Graphics

Technology disruption continues to reshape how we work, learn, and connect. From bookstores to browsers, the leap from physical to digital has transformed not only industries, but expectations. According to McKinsey & Company, generative AI alone could add up to $4.4 trillion annually to the global economy, making it vital to understand how curiosity, learning, and innovation fuel this transformation.So what can we learn about today's digital evolution by revisiting the early internet days, especially from someone who built online experiences before “online” was mainstream?On this episode of DisruptED, host Ron J Stefanski reconnects with longtime friend and fellow Borders alum Scott Wilder, now the Global Head of Digital Self-Serve at LastPass. Together, they explore how bookstores, browsers, and bold ideas shaped some of today's most essential tech innovations. Their conversation tracks the early signals of technology disruption, from pioneering web platforms to building scalable, AI-enhanced learning and customer experiences.In this episode, Ron and Scott discuss:Borders as a Digital Pioneer – Borders wasn't just about books. Scott recalls how the company experimented with online media, store-level websites, and event integration—laying the groundwork for modern e-commerce personalization.Early Internet Innovation – From launching web support at Silicon Graphics to building web ad infrastructure at AOL, Scott helped define digital customer engagement before it became standard practice.Curiosity as a Catalyst – Whether in edtech or AI, Scott emphasizes how intellectual curiosity drives innovation, fuels collaboration, and helps overcome fear of new technologies.This is a special treat to have Scott Wilder from Last Pass on the DisruptED podcast. Ron and Scott worked together for 5 years at Borders Books and Music. As they acknowledge on these shows, they learned an awful lot about the kind of intellectual curiosity that fuels innovation.Scott is a recognized thought leader in advancing technology after leading a number of highly innovative tech initiatives as a key executive at Intuit, Google, Hubspot, Udacity, Coursera and Adobe. His passion for technology is fueled by intense curiosity about how to make things work better.

If you're in SF, join us tomorrow for a fun meetup at CodeGen Night!If you're in NYC, join us for AI Engineer Summit! The Agent Engineering track is now sold out, but 25 tickets remain for AI Leadership and 5 tickets for the workshops. You can see the full schedule of speakers and workshops at https://ai.engineer!It's exceedingly hard to introduce someone like Bret Taylor. We could recite his Wikipedia page, or his extensive work history through Silicon Valley's greatest companies, but everyone else already does that.As a podcast by AI engineers for AI engineers, we had the opportunity to do something a little different. We wanted to dig into what Bret sees from his vantage point at the top of our industry for the last 2 decades, and how that explains the rise of the AI Architect at Sierra, the leading conversational AI/CX platform.“Across our customer base, we are seeing a new role emerge - the role of the AI architect. These leaders are responsible for helping define, manage and evolve their company's AI agent over time. They come from a variety of both technical and business backgrounds, and we think that every company will have one or many AI architects managing their AI agent and related experience.”In our conversation, Bret Taylor confirms the Paul Buchheit legend that he rewrote Google Maps in a weekend, armed with only the help of a then-nascent Google Closure Compiler and no other modern tooling. But what we find remarkable is that he was the PM of Maps, not an engineer, though of course he still identifies as one. We find this theme recurring throughout Bret's career and worldview. We think it is plain as day that AI leadership will have to be hands-on and technical, especially when the ground is shifting as quickly as it is today:“There's a lot of power in combining product and engineering into as few people as possible… few great things have been created by committee.”“If engineering is an order taking organization for product you can sometimes make meaningful things, but rarely will you create extremely well crafted breakthrough products. Those tend to be small teams who deeply understand the customer need that they're solving, who have a maniacal focus on outcomes.”“And I think the reason why is if you look at like software as a service five years ago, maybe you can have a separation of product and engineering because most software as a service created five years ago. I wouldn't say there's like a lot of technological breakthroughs required for most business applications. And if you're making expense reporting software or whatever, it's useful… You kind of know how databases work, how to build auto scaling with your AWS cluster, whatever, you know, it's just, you're just applying best practices to yet another problem. "When you have areas like the early days of mobile development or the early days of interactive web applications, which I think Google Maps and Gmail represent, or now AI agents, you're in this constant conversation with what the requirements of your customers and stakeholders are and all the different people interacting with it and the capabilities of the technology. And it's almost impossible to specify the requirements of a product when you're not sure of the limitations of the technology itself.”This is the first time the difference between technical leadership for “normal” software and for “AI” software was articulated this clearly for us, and we'll be thinking a lot about this going forward. We left a lot of nuggets in the conversation, so we hope you'll just dive in with us (and thank Bret for joining the pod!)Timestamps* 00:00:02 Introductions and Bret Taylor's background* 00:01:23 Bret's experience at Stanford and the dot-com era* 00:04:04 The story of rewriting Google Maps backend* 00:11:06 Early days of interactive web applications at Google* 00:15:26 Discussion on product management and engineering roles* 00:21:00 AI and the future of software development* 00:26:42 Bret's approach to identifying customer needs and building AI companies* 00:32:09 The evolution of business models in the AI era* 00:41:00 The future of programming languages and software development* 00:49:38 Challenges in precisely communicating human intent to machines* 00:56:44 Discussion on Artificial General Intelligence (AGI) and its impact* 01:08:51 The future of agent-to-agent communication* 01:14:03 Bret's involvement in the OpenAI leadership crisis* 01:22:11 OpenAI's relationship with Microsoft* 01:23:23 OpenAI's mission and priorities* 01:27:40 Bret's guiding principles for career choices* 01:29:12 Brief discussion on pasta-making* 01:30:47 How Bret keeps up with AI developments* 01:32:15 Exciting research directions in AI* 01:35:19 Closing remarks and hiring at Sierra Transcript[00:02:05] Introduction and Guest Welcome[00:02:05] Alessio: Hey everyone, welcome to the Latent Space Podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co host swyx, founder of smol.ai.[00:02:17] swyx: Hey, and today we're super excited to have Bret Taylor join us. Welcome. Thanks for having me. It's a little unreal to have you in the studio.[00:02:25] swyx: I've read about you so much over the years, like even before. Open AI effectively. I mean, I use Google Maps to get here. So like, thank you for everything that you've done. Like, like your story history, like, you know, I think people can find out what your greatest hits have been.[00:02:40] Bret Taylor's Early Career and Education[00:02:40] swyx: How do you usually like to introduce yourself when, you know, you talk about, you summarize your career, like, how do you look at yourself?[00:02:47] Bret: Yeah, it's a great question. You know, we, before we went on the mics here, we're talking about the audience for this podcast being more engineering. And I do think depending on the audience, I'll introduce myself differently because I've had a lot of [00:03:00] corporate and board roles. I probably self identify as an engineer more than anything else though.[00:03:04] Bret: So even when I was. Salesforce, I was coding on the weekends. So I think of myself as an engineer and then all the roles that I do in my career sort of start with that just because I do feel like engineering is sort of a mindset and how I approach most of my life. So I'm an engineer first and that's how I describe myself.[00:03:24] Bret: You majored in computer[00:03:25] swyx: science, like 1998. And, and I was high[00:03:28] Bret: school, actually my, my college degree was Oh, two undergrad. Oh, three masters. Right. That old.[00:03:33] swyx: Yeah. I mean, no, I was going, I was going like 1998 to 2003, but like engineering wasn't as, wasn't a thing back then. Like we didn't have the title of senior engineer, you know, kind of like, it was just.[00:03:44] swyx: You were a programmer, you were a developer, maybe. What was it like in Stanford? Like, what was that feeling like? You know, was it, were you feeling like on the cusp of a great computer revolution? Or was it just like a niche, you know, interest at the time?[00:03:57] Stanford and the Dot-Com Bubble[00:03:57] Bret: Well, I was at Stanford, as you said, from 1998 to [00:04:00] 2002.[00:04:02] Bret: 1998 was near the peak of the dot com bubble. So. This is back in the day where most people that they're coding in the computer lab, just because there was these sun microsystems, Unix boxes there that most of us had to do our assignments on. And every single day there was a. com like buying pizza for everybody.[00:04:20] Bret: I didn't have to like, I got. Free food, like my first two years of university and then the dot com bubble burst in the middle of my college career. And so by the end there was like tumbleweed going to the job fair, you know, it was like, cause it was hard to describe unless you were there at the time, the like level of hype and being a computer science major at Stanford was like, A thousand opportunities.[00:04:45] Bret: And then, and then when I left, it was like Microsoft, IBM.[00:04:49] Joining Google and Early Projects[00:04:49] Bret: And then the two startups that I applied to were VMware and Google. And I ended up going to Google in large part because a woman named Marissa Meyer, who had been a teaching [00:05:00] assistant when I was, what was called a section leader, which was like a junior teaching assistant kind of for one of the big interest.[00:05:05] Bret: Yes. Classes. She had gone there. And she was recruiting me and I knew her and it was sort of felt safe, you know, like, I don't know. I thought about it much, but it turned out to be a real blessing. I realized like, you know, you always want to think you'd pick Google if given the option, but no one knew at the time.[00:05:20] Bret: And I wonder if I'd graduated in like 1999 where I've been like, mom, I just got a job at pets. com. It's good. But you know, at the end I just didn't have any options. So I was like, do I want to go like make kernel software at VMware? Do I want to go build search at Google? And I chose Google. 50, 50 ball.[00:05:36] Bret: I'm not really a 50, 50 ball. So I feel very fortunate in retrospect that the economy collapsed because in some ways it forced me into like one of the greatest companies of all time, but I kind of lucked into it, I think.[00:05:47] The Google Maps Rewrite Story[00:05:47] Alessio: So the famous story about Google is that you rewrote the Google maps back in, in one week after the map quest quest maps acquisition, what was the story there?[00:05:57] Alessio: Is it. Actually true. Is it [00:06:00] being glorified? Like how, how did that come to be? And is there any detail that maybe Paul hasn't shared before?[00:06:06] Bret: It's largely true, but I'll give the color commentary. So it was actually the front end, not the back end, but it turns out for Google maps, the front end was sort of the hard part just because Google maps was.[00:06:17] Bret: Largely the first ish kind of really interactive web application, say first ish. I think Gmail certainly was though Gmail, probably a lot of people then who weren't engineers probably didn't appreciate its level of interactivity. It was just fast, but. Google maps, because you could drag the map and it was sort of graphical.[00:06:38] Bret: My, it really in the mainstream, I think, was it a map[00:06:41] swyx: quest back then that was, you had the arrows up and down, it[00:06:44] Bret: was up and down arrows. Each map was a single image and you just click left and then wait for a few seconds to the new map to let it was really small too, because generating a big image was kind of expensive on computers that day.[00:06:57] Bret: So Google maps was truly innovative in that [00:07:00] regard. The story on it. There was a small company called where two technologies started by two Danish brothers, Lars and Jens Rasmussen, who are two of my closest friends now. They had made a windows app called expedition, which had beautiful maps. Even in 2000.[00:07:18] Bret: For whenever we acquired or sort of acquired their company, Windows software was not particularly fashionable, but they were really passionate about mapping and we had made a local search product that was kind of middling in terms of popularity, sort of like a yellow page of search product. So we wanted to really go into mapping.[00:07:36] Bret: We'd started working on it. Their small team seemed passionate about it. So we're like, come join us. We can build this together.[00:07:42] Technical Challenges and Innovations[00:07:42] Bret: It turned out to be a great blessing that they had built a windows app because you're less technically constrained when you're doing native code than you are building a web browser, particularly back then when there weren't really interactive web apps and it ended up.[00:07:56] Bret: Changing the level of quality that we [00:08:00] wanted to hit with the app because we were shooting for something that felt like a native windows application. So it was a really good fortune that we sort of, you know, their unusual technical choices turned out to be the greatest blessing. So we spent a lot of time basically saying, how can you make a interactive draggable map in a web browser?[00:08:18] Bret: How do you progressively load, you know, new map tiles, you know, as you're dragging even things like down in the weeds of the browser at the time, most browsers like Internet Explorer, which was dominant at the time would only load two images at a time from the same domain. So we ended up making our map tile servers have like.[00:08:37] Bret: Forty different subdomains so we could load maps and parallels like lots of hacks. I'm happy to go into as much as like[00:08:44] swyx: HTTP connections and stuff.[00:08:46] Bret: They just like, there was just maximum parallelism of two. And so if you had a map, set of map tiles, like eight of them, so So we just, we were down in the weeds of the browser anyway.[00:08:56] Bret: So it was lots of plumbing. I can, I know a lot more about browsers than [00:09:00] most people, but then by the end of it, it was fairly, it was a lot of duct tape on that code. If you've ever done an engineering project where you're not really sure the path from point A to point B, it's almost like. Building a house by building one room at a time.[00:09:14] Bret: The, there's not a lot of architectural cohesion at the end. And then we acquired a company called Keyhole, which became Google earth, which was like that three, it was a native windows app as well, separate app, great app, but with that, we got licenses to all this satellite imagery. And so in August of 2005, we added.[00:09:33] Bret: Satellite imagery to Google Maps, which added even more complexity in the code base. And then we decided we wanted to support Safari. There was no mobile phones yet. So Safari was this like nascent browser on, on the Mac. And it turns out there's like a lot of decisions behind the scenes, sort of inspired by this windows app, like heavy use of XML and XSLT and all these like.[00:09:54] Bret: Technologies that were like briefly fashionable in the early two thousands and everyone hates now for good [00:10:00] reason. And it turns out that all of the XML functionality and Internet Explorer wasn't supporting Safari. So people are like re implementing like XML parsers. And it was just like this like pile of s**t.[00:10:11] Bret: And I had to say a s**t on your part. Yeah, of[00:10:12] Alessio: course.[00:10:13] Bret: So. It went from this like beautifully elegant application that everyone was proud of to something that probably had hundreds of K of JavaScript, which sounds like nothing. Now we're talking like people have modems, you know, not all modems, but it was a big deal.[00:10:29] Bret: So it was like slow. It took a while to load and just, it wasn't like a great code base. Like everything was fragile. So I just got. Super frustrated by it. And then one weekend I did rewrite all of it. And at the time the word JSON hadn't been coined yet too, just to give you a sense. So it's all XML.[00:10:47] swyx: Yeah.[00:10:47] Bret: So we used what is now you would call JSON, but I just said like, let's use eval so that we can parse the data fast. And, and again, that's, it would literally as JSON, but at the time there was no name for it. So we [00:11:00] just said, let's. Pass on JavaScript from the server and eval it. And then somebody just refactored the whole thing.[00:11:05] Bret: And, and it wasn't like I was some genius. It was just like, you know, if you knew everything you wished you had known at the beginning and I knew all the functionality, cause I was the primary, one of the primary authors of the JavaScript. And I just like, I just drank a lot of coffee and just stayed up all weekend.[00:11:22] Bret: And then I, I guess I developed a bit of reputation and no one knew about this for a long time. And then Paul who created Gmail and I ended up starting a company with him too, after all of this told this on a podcast and now it's large, but it's largely true. I did rewrite it and it, my proudest thing.[00:11:38] Bret: And I think JavaScript people appreciate this. Like the un G zipped bundle size for all of Google maps. When I rewrote, it was 20 K G zipped. It was like much smaller for the entire application. It went down by like 10 X. So. What happened on Google? Google is a pretty mainstream company. And so like our usage is shot up because it turns out like it's faster.[00:11:57] Bret: Just being faster is worth a lot of [00:12:00] percentage points of growth at a scale of Google. So how[00:12:03] swyx: much modern tooling did you have? Like test suites no compilers.[00:12:07] Bret: Actually, that's not true. We did it one thing. So I actually think Google, I, you can. Download it. There's a, Google has a closure compiler, a closure compiler.[00:12:15] Bret: I don't know if anyone still uses it. It's gone. Yeah. Yeah. It's sort of gone out of favor. Yeah. Well, even until recently it was better than most JavaScript minifiers because it was more like it did a lot more renaming of variables and things. Most people use ES build now just cause it's fast and closure compilers built on Java and super slow and stuff like that.[00:12:37] Bret: But, so we did have that, that was it. Okay.[00:12:39] The Evolution of Web Applications[00:12:39] Bret: So and that was treated internally, you know, it was a really interesting time at Google at the time because there's a lot of teams working on fairly advanced JavaScript when no one was. So Google suggest, which Kevin Gibbs was the tech lead for, was the first kind of type ahead, autocomplete, I believe in a web browser, and now it's just pervasive in search boxes that you sort of [00:13:00] see a type ahead there.[00:13:01] Bret: I mean, chat, dbt[00:13:01] swyx: just added it. It's kind of like a round trip.[00:13:03] Bret: Totally. No, it's now pervasive as a UI affordance, but that was like Kevin's 20 percent project. And then Gmail, Paul you know, he tells the story better than anyone, but he's like, you know, basically was scratching his own itch, but what was really neat about it is email, because it's such a productivity tool, just needed to be faster.[00:13:21] Bret: So, you know, he was scratching his own itch of just making more stuff work on the client side. And then we, because of Lars and Yen sort of like setting the bar of this windows app or like we need our maps to be draggable. So we ended up. Not only innovate in terms of having a big sync, what would be called a single page application today, but also all the graphical stuff you know, we were crashing Firefox, like it was going out of style because, you know, when you make a document object model with the idea that it's a document and then you layer on some JavaScript and then we're essentially abusing all of this, it just was running into code paths that were not.[00:13:56] Bret: Well, it's rotten, you know, at this time. And so it was [00:14:00] super fun. And, and, you know, in the building you had, so you had compilers, people helping minify JavaScript just practically, but there is a great engineering team. So they were like, that's why Closure Compiler is so good. It was like a. Person who actually knew about programming languages doing it, not just, you know, writing regular expressions.[00:14:17] Bret: And then the team that is now the Chrome team believe, and I, I don't know this for a fact, but I'm pretty sure Google is the main contributor to Firefox for a long time in terms of code. And a lot of browser people were there. So every time we would crash Firefox, we'd like walk up two floors and say like, what the hell is going on here?[00:14:35] Bret: And they would load their browser, like in a debugger. And we could like figure out exactly what was breaking. And you can't change the code, right? Cause it's the browser. It's like slow, right? I mean, slow to update. So, but we could figure out exactly where the bug was and then work around it in our JavaScript.[00:14:52] Bret: So it was just like new territory. Like so super, super fun time, just like a lot of, a lot of great engineers figuring out [00:15:00] new things. And And now, you know, the word, this term is no longer in fashion, but the word Ajax, which was asynchronous JavaScript and XML cause I'm telling you XML, but see the word XML there, to be fair, the way you made HTTP requests from a client to server was this.[00:15:18] Bret: Object called XML HTTP request because Microsoft and making Outlook web access back in the day made this and it turns out to have nothing to do with XML. It's just a way of making HTTP requests because XML was like the fashionable thing. It was like that was the way you, you know, you did it. But the JSON came out of that, you know, and then a lot of the best practices around building JavaScript applications is pre React.[00:15:44] Bret: I think React was probably the big conceptual step forward that we needed. Even my first social network after Google, we used a lot of like HTML injection and. Making real time updates was still very hand coded and it's really neat when you [00:16:00] see conceptual breakthroughs like react because it's, I just love those things where it's like obvious once you see it, but it's so not obvious until you do.[00:16:07] Bret: And actually, well, I'm sure we'll get into AI, but I, I sort of feel like we'll go through that evolution with AI agents as well that I feel like we're missing a lot of the core abstractions that I think in 10 years we'll be like, gosh, how'd you make agents? Before that, you know, but it was kind of that early days of web applications.[00:16:22] swyx: There's a lot of contenders for the reactive jobs of of AI, but no clear winner yet. I would say one thing I was there for, I mean, there's so much we can go into there. You just covered so much.[00:16:32] Product Management and Engineering Synergy[00:16:32] swyx: One thing I just, I just observe is that I think the early Google days had this interesting mix of PM and engineer, which I think you are, you didn't, you didn't wait for PM to tell you these are my, this is my PRD.[00:16:42] swyx: This is my requirements.[00:16:44] mix: Oh,[00:16:44] Bret: okay.[00:16:45] swyx: I wasn't technically a software engineer. I mean,[00:16:48] Bret: by title, obviously. Right, right, right.[00:16:51] swyx: It's like a blend. And I feel like these days, product is its own discipline and its own lore and own industry and engineering is its own thing. And there's this process [00:17:00] that happens and they're kind of separated, but you don't produce as good of a product as if they were the same person.[00:17:06] swyx: And I'm curious, you know, if, if that, if that sort of resonates in, in, in terms of like comparing early Google versus modern startups that you see out there,[00:17:16] Bret: I certainly like wear a lot of hats. So, you know, sort of biased in this, but I really agree that there's a lot of power and combining product design engineering into as few people as possible because, you know few great things have been created by committee, you know, and so.[00:17:33] Bret: If engineering is an order taking organization for product you can sometimes make meaningful things, but rarely will you create extremely well crafted breakthrough products. Those tend to be small teams who deeply understand the customer need that they're solving, who have a. Maniacal focus on outcomes.[00:17:53] Bret: And I think the reason why it's, I think for some areas, if you look at like software as a service five years ago, maybe you can have a [00:18:00] separation of product and engineering because most software as a service created five years ago. I wouldn't say there's like a lot of like. Technological breakthroughs required for most, you know, business applications.[00:18:11] Bret: And if you're making expense reporting software or whatever, it's useful. I don't mean to be dismissive of expense reporting software, but you probably just want to understand like, what are the requirements of the finance department? What are the requirements of an individual file expense report? Okay.[00:18:25] Bret: Go implement that. And you kind of know how web applications are implemented. You kind of know how to. How databases work, how to build auto scaling with your AWS cluster, whatever, you know, it's just, you're just applying best practices to yet another problem when you have areas like the early days of mobile development or the early days of interactive web applications, which I think Google Maps and Gmail represent, or now AI agents, you're in this constant conversation with what the requirements of your customers and stakeholders are and all the different people interacting with it.[00:18:58] Bret: And the capabilities of the [00:19:00] technology. And it's almost impossible to specify the requirements of a product when you're not sure of the limitations of the technology itself. And that's why I use the word conversation. It's not literal. That's sort of funny to use that word in the age of conversational AI.[00:19:15] Bret: You're constantly sort of saying, like, ideally, you could sprinkle some magic AI pixie dust and solve all the world's problems, but it's not the way it works. And it turns out that actually, I'll just give an interesting example.[00:19:26] AI Agents and Modern Tooling[00:19:26] Bret: I think most people listening probably use co pilots to code like Cursor or Devon or Microsoft Copilot or whatever.[00:19:34] Bret: Most of those tools are, they're remarkable. I'm, I couldn't, you know, imagine development without them now, but they're not autonomous yet. Like I wouldn't let it just write most code without my interactively inspecting it. We just are somewhere between it's an amazing co pilot and it's an autonomous software engineer.[00:19:53] Bret: As a product manager, like your aspirations for what the product is are like kind of meaningful. But [00:20:00] if you're a product person, yeah, of course you'd say it should be autonomous. You should click a button and program should come out the other side. The requirements meaningless. Like what matters is like, what is based on the like very nuanced limitations of the technology.[00:20:14] Bret: What is it capable of? And then how do you maximize the leverage? It gives a software engineering team, given those very nuanced trade offs. Coupled with the fact that those nuanced trade offs are changing more rapidly than any technology in my memory, meaning every few months you'll have new models with new capabilities.[00:20:34] Bret: So how do you construct a product that can absorb those new capabilities as rapidly as possible as well? That requires such a combination of technical depth and understanding the customer that you really need more integration. Of product design and engineering. And so I think it's why with these big technology waves, I think startups have a bit of a leg up relative to incumbents because they [00:21:00] tend to be sort of more self actualized in terms of just like bringing those disciplines closer together.[00:21:06] Bret: And in particular, I think entrepreneurs, the proverbial full stack engineers, you know, have a leg up as well because. I think most breakthroughs happen when you have someone who can understand those extremely nuanced technical trade offs, have a vision for a product. And then in the process of building it, have that, as I said, like metaphorical conversation with the technology, right?[00:21:30] Bret: Gosh, I ran into a technical limit that I didn't expect. It's not just like changing that feature. You might need to refactor the whole product based on that. And I think that's, that it's particularly important right now. So I don't, you know, if you, if you're building a big ERP system, probably there's a great reason to have product and engineering.[00:21:51] Bret: I think in general, the disciplines are there for a reason. I think when you're dealing with something as nuanced as the like technologies, like large language models today, there's a ton of [00:22:00] advantage of having. Individuals or organizations that integrate the disciplines more formally.[00:22:05] Alessio: That makes a lot of sense.[00:22:06] Alessio: I've run a lot of engineering teams in the past, and I think the product versus engineering tension has always been more about effort than like whether or not the feature is buildable. But I think, yeah, today you see a lot more of like. Models actually cannot do that. And I think the most interesting thing is on the startup side, people don't yet know where a lot of the AI value is going to accrue.[00:22:26] Alessio: So you have this rush of people building frameworks, building infrastructure, layered things, but we don't really know the shape of the compute. I'm curious that Sierra, like how you thought about building an house, a lot of the tooling for evals or like just, you know, building the agents and all of that.[00:22:41] Alessio: Versus how you see some of the startup opportunities that is maybe still out there.[00:22:46] Bret: We build most of our tooling in house at Sierra, not all. It's, we don't, it's not like not invented here syndrome necessarily, though, maybe slightly guilty of that in some ways, but because we're trying to build a platform [00:23:00] that's in Dorian, you know, we really want to have control over our own destiny.[00:23:03] Bret: And you had made a comment earlier that like. We're still trying to figure out who like the reactive agents are and the jury is still out. I would argue it hasn't been created yet. I don't think the jury is still out to go use that metaphor. We're sort of in the jQuery era of agents, not the react era.[00:23:19] Bret: And, and that's like a throwback for people listening,[00:23:22] swyx: we shouldn't rush it. You know?[00:23:23] Bret: No, yeah, that's my point is. And so. Because we're trying to create an enduring company at Sierra that outlives us, you know, I'm not sure we want to like attach our cart to some like to a horse where it's not clear that like we've figured out and I actually want as a company, we're trying to enable just at a high level and I'll, I'll quickly go back to tech at Sierra, we help consumer brands build customer facing AI agents.[00:23:48] Bret: So. Everyone from Sonos to ADT home security to Sirius XM, you know, if you call them on the phone and AI will pick up with you, you know, chat with them on the Sirius XM homepage. It's an AI agent called Harmony [00:24:00] that they've built on our platform. We're what are the contours of what it means for someone to build an end to end complete customer experience with AI with conversational AI.[00:24:09] Bret: You know, we really want to dive into the deep end of, of all the trade offs to do it. You know, where do you use fine tuning? Where do you string models together? You know, where do you use reasoning? Where do you use generation? How do you use reasoning? How do you express the guardrails of an agentic process?[00:24:25] Bret: How do you impose determinism on a fundamentally non deterministic technology? There's just a lot of really like as an important design space. And I could sit here and tell you, we have the best approach. Every entrepreneur will, you know. But I hope that in two years, we look back at our platform and laugh at how naive we were, because that's the pace of change broadly.[00:24:45] Bret: If you talk about like the startup opportunities, I'm not wholly skeptical of tools companies, but I'm fairly skeptical. There's always an exception for every role, but I believe that certainly there's a big market for [00:25:00] frontier models, but largely for companies with huge CapEx budgets. So. Open AI and Microsoft's Anthropic and Amazon Web Services, Google Cloud XAI, which is very well capitalized now, but I think the, the idea that a company can make money sort of pre training a foundation model is probably not true.[00:25:20] Bret: It's hard to, you're competing with just, you know, unreasonably large CapEx budgets. And I just like the cloud infrastructure market, I think will be largely there. I also really believe in the applications of AI. And I define that not as like building agents or things like that. I define it much more as like, you're actually solving a problem for a business.[00:25:40] Bret: So it's what Harvey is doing in legal profession or what cursor is doing for software engineering or what we're doing for customer experience and customer service. The reason I believe in that is I do think that in the age of AI, what's really interesting about software is it can actually complete a task.[00:25:56] Bret: It can actually do a job, which is very different than the value proposition of [00:26:00] software was to ancient history two years ago. And as a consequence, I think the way you build a solution and For a domain is very different than you would have before, which means that it's not obvious, like the incumbent incumbents have like a leg up, you know, necessarily, they certainly have some advantages, but there's just such a different form factor, you know, for providing a solution and it's just really valuable.[00:26:23] Bret: You know, it's. Like just think of how much money cursor is saving software engineering teams or the alternative, how much revenue it can produce tool making is really challenging. If you look at the cloud market, just as a analog, there are a lot of like interesting tools, companies, you know, Confluent, Monetized Kafka, Snowflake, Hortonworks, you know, there's a, there's a bunch of them.[00:26:48] Bret: A lot of them, you know, have that mix of sort of like like confluence or have the open source or open core or whatever you call it. I, I, I'm not an expert in this area. You know, I do think [00:27:00] that developers are fickle. I think that in the tool space, I probably like. Default towards open source being like the area that will win.[00:27:09] Bret: It's hard to build a company around this and then you end up with companies sort of built around open source to that can work. Don't get me wrong, but I just think that it's nowadays the tools are changing so rapidly that I'm like, not totally skeptical of tool makers, but I just think that open source will broadly win, but I think that the CapEx required for building frontier models is such that it will go to a handful of big companies.[00:27:33] Bret: And then I really believe in agents for specific domains which I think will, it's sort of the analog to software as a service in this new era. You know, it's like, if you just think of the cloud. You can lease a server. It's just a low level primitive, or you can buy an app like you know, Shopify or whatever.[00:27:51] Bret: And most people building a storefront would prefer Shopify over hand rolling their e commerce storefront. I think the same thing will be true of AI. So [00:28:00] I've. I tend to like, if I have a, like an entrepreneur asked me for advice, I'm like, you know, move up the stack as far as you can towards a customer need.[00:28:09] Bret: Broadly, but I, but it doesn't reduce my excitement about what is the reactive building agents kind of thing, just because it is, it is the right question to ask, but I think we'll probably play out probably an open source space more than anything else.[00:28:21] swyx: Yeah, and it's not a priority for you. There's a lot in there.[00:28:24] swyx: I'm kind of curious about your idea maze towards, there are many customer needs. You happen to identify customer experience as yours, but it could equally have been coding assistance or whatever. I think for some, I'm just kind of curious at the top down, how do you look at the world in terms of the potential problem space?[00:28:44] swyx: Because there are many people out there who are very smart and pick the wrong problem.[00:28:47] Bret: Yeah, that's a great question.[00:28:48] Future of Software Development[00:28:48] Bret: By the way, I would love to talk about the future of software, too, because despite the fact it didn't pick coding, I have a lot of that, but I can talk to I can answer your question, though, you know I think when a technology is as [00:29:00] cool as large language models.[00:29:02] Bret: You just see a lot of people starting from the technology and searching for a problem to solve. And I think it's why you see a lot of tools companies, because as a software engineer, you start building an app or a demo and you, you encounter some pain points. You're like,[00:29:17] swyx: a lot of[00:29:17] Bret: people are experiencing the same pain point.[00:29:19] Bret: What if I make it? That it's just very incremental. And you know, I always like to use the metaphor, like you can sell coffee beans, roasted coffee beans. You can add some value. You took coffee beans and you roasted them and roasted coffee beans largely, you know, are priced relative to the cost of the beans.[00:29:39] Bret: Or you can sell a latte and a latte. Is rarely priced directly like as a percentage of coffee bean prices. In fact, if you buy a latte at the airport, it's a captive audience. So it's a really expensive latte. And there's just a lot that goes into like. How much does a latte cost? And I bring it up because there's a supply chain from growing [00:30:00] coffee beans to roasting coffee beans to like, you know, you could make one at home or you could be in the airport and buy one and the margins of the company selling lattes in the airport is a lot higher than the, you know, people roasting the coffee beans and it's because you've actually solved a much more acute human problem in the airport.[00:30:19] Bret: And, and it's just worth a lot more to that person in that moment. It's kind of the way I think about technology too. It sounds funny to liken it to coffee beans, but you're selling tools on top of a large language model yet in some ways your market is big, but you're probably going to like be price compressed just because you're sort of a piece of infrastructure and then you have open source and all these other things competing with you naturally.[00:30:43] Bret: If you go and solve a really big business problem for somebody, that's actually like a meaningful business problem that AI facilitates, they will value it according to the value of that business problem. And so I actually feel like people should just stop. You're like, no, that's, that's [00:31:00] unfair. If you're searching for an idea of people, I, I love people trying things, even if, I mean, most of the, a lot of the greatest ideas have been things no one believed in.[00:31:07] Bret: So I like, if you're passionate about something, go do it. Like who am I to say, yeah, a hundred percent. Or Gmail, like Paul as far, I mean I, some of it's Laura at this point, but like Gmail is Paul's own email for a long time. , and then I amusingly and Paul can't correct me, I'm pretty sure he sent her in a link and like the first comment was like, this is really neat.[00:31:26] Bret: It would be great. It was not your email, but my own . I don't know if it's a true story. I'm pretty sure it's, yeah, I've read that before. So scratch your own niche. Fine. Like it depends on what your goal is. If you wanna do like a venture backed company, if its a. Passion project, f*****g passion, do it like don't listen to anybody.[00:31:41] Bret: In fact, but if you're trying to start, you know an enduring company, solve an important business problem. And I, and I do think that in the world of agents, the software industries has shifted where you're not just helping people more. People be more productive, but you're actually accomplishing tasks autonomously.[00:31:58] Bret: And as a consequence, I think the [00:32:00] addressable market has just greatly expanded just because software can actually do things now and actually accomplish tasks and how much is coding autocomplete worth. A fair amount. How much is the eventual, I'm certain we'll have it, the software agent that actually writes the code and delivers it to you, that's worth a lot.[00:32:20] Bret: And so, you know, I would just maybe look up from the large language models and start thinking about the economy and, you know, think from first principles. I don't wanna get too far afield, but just think about which parts of the economy. We'll benefit most from this intelligence and which parts can absorb it most easily.[00:32:38] Bret: And what would an agent in this space look like? Who's the customer of it is the technology feasible. And I would just start with these business problems more. And I think, you know, the best companies tend to have great engineers who happen to have great insight into a market. And it's that last part that I think some people.[00:32:56] Bret: Whether or not they have, it's like people start so much in the technology, they [00:33:00] lose the forest for the trees a little bit.[00:33:02] Alessio: How do you think about the model of still selling some sort of software versus selling more package labor? I feel like when people are selling the package labor, it's almost more stateless, you know, like it's easier to swap out if you're just putting an input and getting an output.[00:33:16] Alessio: If you think about coding, if there's no ID, you're just putting a prompt and getting back an app. It doesn't really matter. Who generates the app, you know, you have less of a buy in versus the platform you're building, I'm sure on the backend customers have to like put on their documentation and they have, you know, different workflows that they can tie in what's kind of like the line to draw there versus like going full where you're managed customer support team as a service outsource versus.[00:33:40] Alessio: This is the Sierra platform that you can build on. What was that decision? I'll sort of[00:33:44] Bret: like decouple the question in some ways, which is when you have something that's an agent, who is the person using it and what do they want to do with it? So let's just take your coding agent for a second. I will talk about Sierra as well.[00:33:59] Bret: Who's the [00:34:00] customer of a, an agent that actually produces software? Is it a software engineering manager? Is it a software engineer? And it's there, you know, intern so to speak. I don't know. I mean, we'll figure this out over the next few years. Like what is that? And is it generating code that you then review?[00:34:16] Bret: Is it generating code with a set of unit tests that pass, what is the actual. For lack of a better word contract, like, how do you know that it did what you wanted it to do? And then I would say like the product and the pricing, the packaging model sort of emerged from that. And I don't think the world's figured out.[00:34:33] Bret: I think it'll be different for every agent. You know, in our customer base, we do what's called outcome based pricing. So essentially every time the AI agent. Solves the problem or saves a customer or whatever it might be. There's a pre negotiated rate for that. We do that. Cause it's, we think that that's sort of the correct way agents, you know, should be packaged.[00:34:53] Bret: I look back at the history of like cloud software and notably the introduction of the browser, which led to [00:35:00] software being delivered in a browser, like Salesforce to. Famously invented sort of software as a service, which is both a technical delivery model through the browser, but also a business model, which is you subscribe to it rather than pay for a perpetual license.[00:35:13] Bret: Those two things are somewhat orthogonal, but not really. If you think about the idea of software running in a browser, that's hosted. Data center that you don't own, you sort of needed to change the business model because you don't, you can't really buy a perpetual license or something otherwise like, how do you afford making changes to it?[00:35:31] Bret: So it only worked when you were buying like a new version every year or whatever. So to some degree, but then the business model shift actually changed business as we know it, because now like. Things like Adobe Photoshop. Now you subscribe to rather than purchase. So it ended up where you had a technical shift and a business model shift that were very logically intertwined that actually the business model shift was turned out to be as significant as the technical as the shift.[00:35:59] Bret: And I think with [00:36:00] agents, because they actually accomplish a job, I do think that it doesn't make sense to me that you'd pay for the privilege of like. Using the software like that coding agent, like if it writes really bad code, like fire it, you know, I don't know what the right metaphor is like you should pay for a job.[00:36:17] Bret: Well done in my opinion. I mean, that's how you pay your software engineers, right? And[00:36:20] swyx: and well, not really. We paid to put them on salary and give them options and they vest over time. That's fair.[00:36:26] Bret: But my point is that you don't pay them for how many characters they write, which is sort of the token based, you know, whatever, like, There's a, that famous Apple story where we're like asking for a report of how many lines of code you wrote.[00:36:40] Bret: And one of the engineers showed up with like a negative number cause he had just like done a big refactoring. There was like a big F you to management who didn't understand how software is written. You know, my sense is like the traditional usage based or seat based thing. It's just going to look really antiquated.[00:36:55] Bret: Cause it's like asking your software engineer, how many lines of code did you write today? Like who cares? Like, cause [00:37:00] absolutely no correlation. So my old view is I don't think it's be different in every category, but I do think that that is the, if an agent is doing a job, you should, I think it properly incentivizes the maker of that agent and the customer of, of your pain for the job well done.[00:37:16] Bret: It's not always perfect to measure. It's hard to measure engineering productivity, but you can, you should do something other than how many keys you typed, you know Talk about perverse incentives for AI, right? Like I can write really long functions to do the same thing, right? So broadly speaking, you know, I do think that we're going to see a change in business models of software towards outcomes.[00:37:36] Bret: And I think you'll see a change in delivery models too. And, and, you know, in our customer base you know, we empower our customers to really have their hands on the steering wheel of what the agent does they, they want and need that. But the role is different. You know, at a lot of our customers, the customer experience operations folks have renamed themselves the AI architects, which I think is really cool.[00:37:55] Bret: And, you know, it's like in the early days of the Internet, there's the role of the webmaster. [00:38:00] And I don't know whether your webmaster is not a fashionable, you know, Term, nor is it a job anymore? I just, I don't know. Will they, our tech stand the test of time? Maybe, maybe not. But I do think that again, I like, you know, because everyone listening right now is a software engineer.[00:38:14] Bret: Like what is the form factor of a coding agent? And actually I'll, I'll take a breath. Cause actually I have a bunch of pins on them. Like I wrote a blog post right before Christmas, just on the future of software development. And one of the things that's interesting is like, if you look at the way I use cursor today, as an example, it's inside of.[00:38:31] Bret: A repackaged visual studio code environment. I sometimes use the sort of agentic parts of it, but it's largely, you know, I've sort of gotten a good routine of making it auto complete code in the way I want through tuning it properly when it actually can write. I do wonder what like the future of development environments will look like.[00:38:55] Bret: And to your point on what is a software product, I think it's going to change a lot in [00:39:00] ways that will surprise us. But I always use, I use the metaphor in my blog post of, have you all driven around in a way, Mo around here? Yeah, everyone has. And there are these Jaguars, the really nice cars, but it's funny because it still has a steering wheel, even though there's no one sitting there and the steering wheels like turning and stuff clearly in the future.[00:39:16] Bret: If once we get to that, be more ubiquitous, like why have the steering wheel and also why have all the seats facing forward? Maybe just for car sickness. I don't know, but you could totally rearrange the car. I mean, so much of the car is oriented around the driver, so. It stands to reason to me that like, well, autonomous agents for software engineering run through visual studio code.[00:39:37] Bret: That seems a little bit silly because having a single source code file open one at a time is kind of a goofy form factor for when like the code isn't being written primarily by you, but it begs the question of what's your relationship with that agent. And I think the same is true in our industry of customer experience, which is like.[00:39:55] Bret: Who are the people managing this agent? What are the tools do they need? And they definitely need [00:40:00] tools, but it's probably pretty different than the tools we had before. It's certainly different than training a contact center team. And as software engineers, I think that I would like to see particularly like on the passion project side or research side.[00:40:14] Bret: More innovation in programming languages. I think that we're bringing the cost of writing code down to zero. So the fact that we're still writing Python with AI cracks me up just cause it's like literally was designed to be ergonomic to write, not safe to run or fast to run. I would love to see more innovation and how we verify program correctness.[00:40:37] Bret: I studied for formal verification in college a little bit and. It's not very fashionable because it's really like tedious and slow and doesn't work very well. If a lot of code is being written by a machine, you know, one of the primary values we can provide is verifying that it actually does what we intend that it does.[00:40:56] Bret: I think there should be lots of interesting things in the software development life cycle, like how [00:41:00] we think of testing and everything else, because. If you think about if we have to manually read every line of code that's coming out as machines, it will just rate limit how much the machines can do. The alternative is totally unsafe.[00:41:13] Bret: So I wouldn't want to put code in production that didn't go through proper code review and inspection. So my whole view is like, I actually think there's like an AI native I don't think the coding agents don't work well enough to do this yet, but once they do, what is sort of an AI native software development life cycle and how do you actually.[00:41:31] Bret: Enable the creators of software to produce the highest quality, most robust, fastest software and know that it's correct. And I think that's an incredible opportunity. I mean, how much C code can we rewrite and rust and make it safe so that there's fewer security vulnerabilities. Can we like have more efficient, safer code than ever before?[00:41:53] Bret: And can you have someone who's like that guy in the matrix, you know, like staring at the little green things, like where could you have an operator [00:42:00] of a code generating machine be like superhuman? I think that's a cool vision. And I think too many people are focused on like. Autocomplete, you know, right now, I'm not, I'm not even, I'm guilty as charged.[00:42:10] Bret: I guess in some ways, but I just like, I'd like to see some bolder ideas. And that's why when you were joking, you know, talking about what's the react of whatever, I think we're clearly in a local maximum, you know, metaphor, like sort of conceptual local maximum, obviously it's moving really fast. I think we're moving out of it.[00:42:26] Alessio: Yeah. At the end of 23, I've read this blog post from syntax to semantics. Like if you think about Python. It's taking C and making it more semantic and LLMs are like the ultimate semantic program, right? You can just talk to them and they can generate any type of syntax from your language. But again, the languages that they have to use were made for us, not for them.[00:42:46] Alessio: But the problem is like, as long as you will ever need a human to intervene, you cannot change the language under it. You know what I mean? So I'm curious at what point of automation we'll need to get, we're going to be okay making changes. To the underlying languages, [00:43:00] like the programming languages versus just saying, Hey, you just got to write Python because I understand Python and I'm more important at the end of the day than the model.[00:43:08] Alessio: But I think that will change, but I don't know if it's like two years or five years. I think it's more nuanced actually.[00:43:13] Bret: So I think there's a, some of the more interesting programming languages bring semantics into syntax. So let me, that's a little reductive, but like Rust as an example, Rust is memory safe.[00:43:25] Bret: Statically, and that was a really interesting conceptual, but it's why it's hard to write rust. It's why most people write python instead of rust. I think rust programs are safer and faster than python, probably slower to compile. But like broadly speaking, like given the option, if you didn't have to care about the labor that went into it.[00:43:45] Bret: You should prefer a program written in Rust over a program written in Python, just because it will run more efficiently. It's almost certainly safer, et cetera, et cetera, depending on how you define safe, but most people don't write Rust because it's kind of a pain in the ass. And [00:44:00] the audience of people who can is smaller, but it's sort of better in most, most ways.[00:44:05] Bret: And again, let's say you're making a web service and you didn't have to care about how hard it was to write. If you just got the output of the web service, the rest one would be cheaper to operate. It's certainly cheaper and probably more correct just because there's so much in the static analysis implied by the rest programming language that it probably will have fewer runtime errors and things like that as well.[00:44:25] Bret: So I just give that as an example, because so rust, at least my understanding that came out of the Mozilla team, because. There's lots of security vulnerabilities in the browser and it needs to be really fast. They said, okay, we want to put more of a burden at the authorship time to have fewer issues at runtime.[00:44:43] Bret: And we need the constraint that it has to be done statically because browsers need to be really fast. My sense is if you just think about like the, the needs of a programming language today, where the role of a software engineer is [00:45:00] to use an AI to generate functionality and audit that it does in fact work as intended, maybe functionally, maybe from like a correctness standpoint, some combination thereof, how would you create a programming system that facilitated that?[00:45:15] Bret: And, you know, I bring up Rust is because I think it's a good example of like, I think given a choice of writing in C or Rust, you should choose Rust today. I think most people would say that, even C aficionados, just because. C is largely less safe for very similar, you know, trade offs, you know, for the, the system and now with AI, it's like, okay, well, that just changes the game on writing these things.[00:45:36] Bret: And so like, I just wonder if a combination of programming languages that are more structurally oriented towards the values that we need from an AI generated program, verifiable correctness and all of that. If it's tedious to produce for a person, that maybe doesn't matter. But one thing, like if I asked you, is this rest program memory safe?[00:45:58] Bret: You wouldn't have to read it, you just have [00:46:00] to compile it. So that's interesting. I mean, that's like an, that's one example of a very modest form of formal verification. So I bring that up because I do think you have AI inspect AI, you can have AI reviewed. Do AI code reviews. It would disappoint me if the best we could get was AI reviewing Python and having scaled a few very large.[00:46:21] Bret: Websites that were written on Python. It's just like, you know, expensive and it's like every, trust me, every team who's written a big web service in Python has experimented with like Pi Pi and all these things just to make it slightly more efficient than it naturally is. You don't really have true multi threading anyway.[00:46:36] Bret: It's just like clearly that you do it just because it's convenient to write. And I just feel like we're, I don't want to say it's insane. I just mean. I do think we're at a local maximum. And I would hope that we create a programming system, a combination of programming languages, formal verification, testing, automated code reviews, where you can use AI to generate software in a high scale way and trust it.[00:46:59] Bret: And you're [00:47:00] not limited by your ability to read it necessarily. I don't know exactly what form that would take, but I feel like that would be a pretty cool world to live in.[00:47:08] Alessio: Yeah. We had Chris Lanner on the podcast. He's doing great work with modular. I mean, I love. LVM. Yeah. Basically merging rust in and Python.[00:47:15] Alessio: That's kind of the idea. Should be, but I'm curious is like, for them a big use case was like making it compatible with Python, same APIs so that Python developers could use it. Yeah. And so I, I wonder at what point, well, yeah.[00:47:26] Bret: At least my understanding is they're targeting the data science Yeah. Machine learning crowd, which is all written in Python, so still feels like a local maximum.[00:47:34] Bret: Yeah.[00:47:34] swyx: Yeah, exactly. I'll force you to make a prediction. You know, Python's roughly 30 years old. In 30 years from now, is Rust going to be bigger than Python?[00:47:42] Bret: I don't know this, but just, I don't even know this is a prediction. I just am sort of like saying stuff I hope is true. I would like to see an AI native programming language and programming system, and I use language because I'm not sure language is even the right thing, but I hope in 30 years, there's an AI native way we make [00:48:00] software that is wholly uncorrelated with the current set of programming languages.[00:48:04] Bret: or not uncorrelated, but I think most programming languages today were designed to be efficiently authored by people and some have different trade offs.[00:48:15] Evolution of Programming Languages[00:48:15] Bret: You know, you have Haskell and others that were designed for abstractions for parallelism and things like that. You have programming languages like Python, which are designed to be very easily written, sort of like Perl and Python lineage, which is why data scientists use it.[00:48:31] Bret: It's it can, it has a. Interactive mode, things like that. And I love, I'm a huge Python fan. So despite all my Python trash talk, a huge Python fan wrote at least two of my three companies were exclusively written in Python and then C came out of the birth of Unix and it wasn't the first, but certainly the most prominent first step after assembly language, right?[00:48:54] Bret: Where you had higher level abstractions rather than and going beyond go to, to like abstractions, [00:49:00] like the for loop and the while loop.[00:49:01] The Future of Software Engineering[00:49:01] Bret: So I just think that if the act of writing code is no longer a meaningful human exercise, maybe it will be, I don't know. I'm just saying it sort of feels like maybe it's one of those parts of history that just will sort of like go away, but there's still the role of this offer engineer, like the person actually building the system.[00:49:20] Bret: Right. And. What does a programming system for that form factor look like?[00:49:25] React and Front-End Development[00:49:25] Bret: And I, I just have a, I hope to be just like I mentioned, I remember I was at Facebook in the very early days when, when, what is now react was being created. And I remember when the, it was like released open source I had left by that time and I was just like, this is so f*****g cool.[00:49:42] Bret: Like, you know, to basically model your app independent of the data flowing through it, just made everything easier. And then now. You know, I can create, like there's a lot of the front end software gym play is like a little chaotic for me, to be honest with you. It is like, it's sort of like [00:50:00] abstraction soup right now for me, but like some of those core ideas felt really ergonomic.[00:50:04] Bret: I just wanna, I'm just looking forward to the day when someone comes up with a programming system that feels both really like an aha moment, but completely foreign to me at the same time. Because they created it with sort of like from first principles recognizing that like. Authoring code in an editor is maybe not like the primary like reason why a programming system exists anymore.[00:50:26] Bret: And I think that's like, that would be a very exciting day for me.[00:50:28] The Role of AI in Programming[00:50:28] swyx: Yeah, I would say like the various versions of this discussion have happened at the end of the day, you still need to precisely communicate what you want. As a manager of people, as someone who has done many, many legal contracts, you know how hard that is.[00:50:42] swyx: And then now we have to talk to machines doing that and AIs interpreting what we mean and reading our minds effectively. I don't know how to get across that barrier of translating human intent to instructions. And yes, it can be more declarative, but I don't know if it'll ever Crossover from being [00:51:00] a programming language to something more than that.[00:51:02] Bret: I agree with you. And I actually do think if you look at like a legal contract, you know, the imprecision of the English language, it's like a flaw in the system. How many[00:51:12] swyx: holes there are.[00:51:13] Bret: And I do think that when you're making a mission critical software system, I don't think it should be English language prompts.[00:51:19] Bret: I think that is silly because you want the precision of a a programming language. My point was less about that and more about if the actual act of authoring it, like if you.[00:51:32] Formal Verification in Software[00:51:32] Bret: I'll think of some embedded systems do use formal verification. I know it's very common in like security protocols now so that you can, because the importance of correctness is so great.[00:51:41] Bret: My intellectual exercise is like, why not do that for all software? I mean, probably that's silly just literally to do what we literally do for. These low level security protocols, but the only reason we don't is because it's hard and tedious and hard and tedious are no longer factors. So, like, if I could, I mean, [00:52:00] just think of, like, the silliest app on your phone right now, the idea that that app should be, like, formally verified for its correctness feels laughable right now because, like, God, why would you spend the time on it?[00:52:10] Bret: But if it's zero costs, like, yeah, I guess so. I mean, it never crashed. That's probably good. You know, why not? I just want to, like, set our bars really high. Like. We should make, software has been amazing. Like there's a Mark Andreessen blog post, software is eating the world. And you know, our whole life is, is mediated digitally.[00:52:26] Bret: And that's just increasing with AI. And now we'll have our personal agents talking to the agents on the CRO platform and it's agents all the way down, you know, our core infrastructure is running on these digital systems. We now have like, and we've had a shortage of software developers for my entire life.[00:52:45] Bret: And as a consequence, you know if you look, remember like health care, got healthcare. gov that fiasco security vulnerabilities leading to state actors getting access to critical infrastructure. I'm like. We now have like created this like amazing system that can [00:53:00] like, we can fix this, you know, and I, I just want to, I'm both excited about the productivity gains in the economy, but I just think as software engineers, we should be bolder.[00:53:08] Bret: Like we should have aspirations to fix these systems so that like in general, as you said, as precise as we want to be in the specification of the system. We can make it work correctly now, and I'm being a little bit hand wavy, and I think we need some systems. I think that's where we should set the bar, especially when so much of our life depends on this critical digital infrastructure.[00:53:28] Bret: So I'm I'm just like super optimistic about it. But actually, let's go to w

In 2010, Facebook opened its first office in India, four years after it went online.They needed someone bold to lead their journey in India which had a major customer base potential.That someone was Kirthiga Reddy.Under Kirthiga's leadership, Facebook not only grew its user base but also planted deep roots in a complex and rapidly evolving digital ecosystem.Today, India has the most Facebook users with over 448 million, followed by the US (258 million).After six years of phenomenal growth at Facebook, Kirthiga decided it was time for a new challenge.In 2018, she became the first female partner at SoftBank Vision Fund, managing over $5 billion in investments.Today, Kirthiga leads her own venture, Verix, focusing on trust, transparency, and community-driven solutions.In this episode of the NEON Show, Kirthiga Reddy shares her inspiring journey. From a small-town upbringing in India to building Facebook in India, Kirthiga takes us through the challenges of scaling operations, transforming workplace culture, and driving growth. She also opens up about her transition to SoftBank. From leading the fund's first investments in quantum computing and additive manufacturing, Kirthiga shares how she worked closely with founders to shape strategies and scale businesses.Timestamps00:00 - Trailer 01:51 - Intro02:09 - Kirthiga's career from Facebook India to SoftBank03:17 - Childhood in Nanded shaping values04:46 - Early career programming for Let Us C06:20 - Masters in the US and arranged marriage08:33 - Syracuse University and joining its Board09:30 - Silicon Graphics high-tech projects12:20 - Stanford MBA and transition to business17:58 - Startup role in product management21:20 - Motorola acquisition and return to India23:08 - Meeting Sheryl Sandberg27:32 - Joining Facebook as its first Indian employee28:50 - Facebook's 100-100-100 strategy30:40 - Building a Facebook culture35:30 - Personally hiring Facebook India's first 100 employees36:45 - Success stories of early hires37:50 - Leaving Facebook to balance family and career45:20 - Joining SoftBank & managing $5B in investments47:19 - Key investments in IonQ and 8fold.ai52:38 - Transition from SoftBank to new ventures56:14 - Founding Verix and Virtualness57:00 - AI-first companies and tech vision01:00:28 - India's thriving tech ecosystem01:03:51 - Vision for Verix, Virtualness, and social impactHi, I am your host Siddhartha! I have been an entrepreneur from 2012-2017 building two products AddoDoc and Babygogo. After selling my company to SHEROES, I and my partner Nansi decided to start up again. But we felt unequipped in our skillset in 2018 to build a large company. We had known 0-1 journeys from our startups but lacked the experience of building 1-10 journeys. Hence was born The Neon Show (Earlier 100x Entrepreneur) to learn from founders and investors, the mindset to scale yourself and your company. This quest still keeps us excited even after 5 years and doing 200+ episodes.We welcome you to our journey to understand what goes behind building a super successful company. Every episode is done with a very selfish motive, that I and Nansi should come out as a better entrepreneur and professional after absorbing the learnings.-----Check us out on:Website: https://neon.fund/Instagram: https://www.instagram.com/theneonshoww/LinkedIn: https://www.linkedin.com/company/beneon/Twitter: https://x.com/TheNeonShowwConnect with Siddhartha on:LinkedIn: https://www.linkedin.com/in/siddharthaahluwalia/Twitter: https://x.com/siddharthaa7-----This show is for informational purposes only. Send us a text

Sekedar bercerita bahwa pendiri (founder) perusahaan ditendang dari perusahaan yang dia dirikan itu bukan hal yang baru. Adalah kisah Steve Jobs dengan Apple Computer, Jim Clark dengan Silicon Graphics, dan seterusnya.

fWotD Episode 2754: Donkey Kong Country Welcome to Featured Wiki of the Day, your daily dose of knowledge from Wikipedia’s finest articles.The featured article for Monday, 18 November 2024 is Donkey Kong Country.Donkey Kong Country is a 1994 platform game developed by Rare and published by Nintendo for the Super Nintendo Entertainment System (SNES). It is a reboot of Nintendo's Donkey Kong franchise and follows the gorilla Donkey Kong and his nephew Diddy Kong as they set out to recover their stolen banana hoard from the crocodile King K. Rool and his army, the Kremlings. The single-player traverses 40 side-scrolling levels as they jump between platforms and avoid obstacles. They collect items, ride minecarts and animals, defeat enemies and bosses, and find secret bonus stages. In multiplayer modes, two players work cooperatively or race each other.After developing Nintendo Entertainment System games in the 1980s, Rare, a British studio founded by Tim and Chris Stamper, purchased Silicon Graphics workstations to render 3D models. Nintendo sought a game to compete with Sega's Aladdin (1993) and commissioned Rare to revive the dormant Donkey Kong franchise. Rare assembled 12 developers to work on Donkey Kong Country over 18 months. Donkey Kong Country was inspired by the Super Mario series and was one of the first home console games to feature pre-rendered graphics, achieved through a compression technique that converted 3D models into SNES sprites with little loss of detail. It was the first Donkey Kong game neither produced nor directed by the franchise's creator Shigeru Miyamoto, though he contributed design ideas.Following its announcement at the Consumer Electronics Show in June 1994, Donkey Kong Country was highly anticipated and backed by a major marketing campaign that cost $16 million in America alone. It was released in November 1994 to acclaim; critics hailed its visuals as groundbreaking and praised its gameplay and music. Its quality and design were favourably compared to the Super Mario series. Donkey Kong Country received several year-end accolades and set the record for the fastest-selling video game at the time. With 9.3 million copies sold worldwide, it is the third-bestselling SNES game and the bestselling Donkey Kong game. Following the success, Nintendo purchased a large minority stake in Rare, which became a prominent second-party developer for Nintendo during the late 1990s.Donkey Kong Country re-established Donkey Kong as a popular Nintendo franchise and helped maintain the SNES's popularity into the fifth generation of video game consoles. It is considered one of the greatest video games of all time and has been ported to platforms such as the Game Boy Color, Game Boy Advance, and digital distribution services. Rare followed it with two sequels for the SNES, Donkey Kong Country 2: Diddy's Kong Quest (1995) and Donkey Kong Country 3: Dixie Kong's Double Trouble! (1996), and the Nintendo 64 game Donkey Kong 64 (1999). After a hiatus, during which Rare was acquired by the Nintendo competitor Microsoft, Retro Studios revived the series with Donkey Kong Country Returns (2010) for the Wii and Donkey Kong Country: Tropical Freeze (2014) for the Wii U.This recording reflects the Wikipedia text as of 00:30 UTC on Monday, 18 November 2024.For the full current version of the article, see Donkey Kong Country on Wikipedia.This podcast uses content from Wikipedia under the Creative Commons Attribution-ShareAlike License.Visit our archives at wikioftheday.com and subscribe to stay updated on new episodes.Follow us on Mastodon at @wikioftheday@masto.ai.Also check out Curmudgeon's Corner, a current events podcast.Until next time, I'm generative Stephen.

Since Oracle changed the licensing for Java in January 2023, there has been growing demand from customers looking to switch away due to extra costs being imposed. Last summer Azul conducted a study of Oracle Java customers with 86% saying they are migrating all or some of their use and 47% expressed a desire to use an open-source distribution like OpenJDK.  Despite this appetite for change there are still somewhat cliched perceptions about moving to an open source-based JDK, even though the OpenJDK is based on the same source code as Oracle Java. There are some concerns about “better the devil you know” and a preconception that migration is difficult, but as the study showed 75% completed their migration to the OpenJDK within 12 months. To learn more about this I spoke to Scott Sellers, co-founder and CEO of Azul. Scott talks about his background, what Azul does, Azul's benchmarking tests, Azul's new Java Performance Engineering Lab and more.  More about Scott Sellers: With more than 30 years of successful leadership in building high technology companies and delivering advanced products to market, Scott provides the overall strategic leadership and visionary direction for Azul Systems.  Scott has a consistent proven track record of vision, leadership, and success in enterprise, consumer and scientific markets. Prior to co-founding Azul Systems, Scott founded 3dfx Interactive, a graphics processor company that pioneered the 3D graphics market for personal computers and game consoles. Scott served at 3dfx as Vice President of Engineering, CTO and as a member of the board of directors and delivered 7 award-winning products and developed 14 different graphics processors. After a successful initial public offering, 3dfx was later acquired by NVIDIA Corporation.  Prior to 3dfx, Scott was a CPU systems architect at Pellucid, later acquired by MediaVision. Before Pellucid, Scott was a member of the technical staff at Silicon Graphics where he designed high-performance workstations. Scott graduated from Princeton University with a bachelor of science, earning magna cum laude and Phi Beta Kappa honors. Scott has been granted 8 patents in high performance graphics and computing and is a regularly invited keynote speaker at industry conferences.

Since Oracle changed the licensing for Java in January 2023, there has been growing demand from customers looking to switch away due to extra costs being imposed. Last summer Azul conducted a study of Oracle Java customers with 86% saying they are migrating all or some of their use and 47% expressed a desire to use an open-source distribution like OpenJDK. Despite this appetite for change there are still somewhat cliched perceptions about moving to an open source-based JDK, even though the OpenJDK is based on the same source code as Oracle Java. There are some concerns about "better the devil you know" and a preconception that migration is difficult, but as the study showed 75% completed their migration to the OpenJDK within 12 months. To learn more about this I spoke to Scott Sellers, co-founder and CEO of Azul. Scott talks about his background, what Azul does, Azul's benchmarking tests, Azul's new Java Performance Engineering Lab and more. More about Scott Sellers: With more than 30 years of successful leadership in building high technology companies and delivering advanced products to market, Scott provides the overall strategic leadership and visionary direction for Azul Systems. Scott has a consistent proven track record of vision, leadership, and success in enterprise, consumer and scientific markets. Prior to co-founding Azul Systems, Scott founded 3dfx Interactive, a graphics processor company that pioneered the 3D graphics market for personal computers and game consoles. Scott served at 3dfx as Vice President of Engineering, CTO and as a member of the board of directors and delivered 7 award-winning products and developed 14 different graphics processors. After a successful initial public offering, 3dfx was later acquired by NVIDIA Corporation. Prior to 3dfx, Scott was a CPU systems architect at Pellucid, later acquired by MediaVision. Before Pellucid, Scott was a member of the technical staff at Silicon Graphics where he designed high-performance workstations. Scott graduated from Princeton University with a bachelor of science, earning magna cum laude and Phi Beta Kappa honors. Scott has been granted 8 patents in high performance graphics and computing and is a regularly invited keynote speaker at industry conferences. See more podcasts here. More about Irish Tech News Irish Tech News are Ireland's No. 1 Online Tech Publication and often Ireland's No.1 Tech Podcast too. You can find hundreds of fantastic previous episodes and subscribe using whatever platform you like via our Anchor.fm page here: https://anchor.fm/irish-tech-news If you'd like to be featured in an upcoming Podcast email us at Simon@IrishTechNews.ie now to discuss. Irish Tech News have a range of services available to help promote your business. Why not drop us a line at Info@IrishTechNews.ie now to find out more about how we can help you reach our audience. You can also find and follow us on Twitter, LinkedIn, Facebook, Instagram, TikTok and Snapchat.

How has the VFX industry evolved from Silicon Graphics to real-time rendering? In this October 21st episode of Monday Meeting, host EJ Brieva talks with Jeff Lopez, co-head of CG and VFX Supervisor at The Mill, about his 27-year journey in the industry. From his early days at SVA to leading innovation at The Mill, Jeff shares insights on adapting to technological changes while maintaining creative passion. This episode includes: The importance of personality over technical skills in on-set supervision (80/20 rule) How remote work is reshaping studio culture and creating nationwide opportunities Why junior artists should prioritize in-person learning and community building The value of R&D and experimentation in keeping large studios competitive Visit MondayMeeting.org for this episode and other insightful conversations from our motion design community! Reminder: Join us next week for our spooktacular Halloween-themed open discussion. Costumes, masks, and haunting makeup are encouraged! SHOW NOTES: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Monday Meeting Patreon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Monday Meeting Discord⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Monday Meeting LinkedIn⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Monday Meeting Instagram⁠⁠⁠⁠⁠⁠⁠⁠ ⁠The Mill Visual Effects Society ⁠Next "Food In Motion" Motion/Sound Design Collab SignUp Sheet F9 Collective School of Motion Scholarship Program

¿CD o Cartucho? ¿32 o 64 bits? La 5ta generación de consolas fue un caos de propuestas de lo más disímiles, y más de una llevaría la huella de Silicon Graphics, especialistas en gráficos 3D. ¿Por qué querrían meterse en videojuegos, y cuál fue su rol en la creación del Nintendo 64? Todas las respuestas y más, en este episodio.

Conducido por Pablo Wasserman y Juan Ruocco.  Círculo Vicioso https://twitter.com/circulovicioso8 Sitio oficial: https://www.circulovicioso.club/ (0:00) INTRO (3:12) Comienza (6:12) Beepers explosivos (14:52) PsyOps, Mossad e ingeniería social (23:55) Iran y Ayatollahs (32:22) Religion, estado e ilustración (37:40) Protestantismo y Holanda (41:22) Bitcoin y criptografía (46:40) El fin de CV (48:40) Domar a la naturaleza (55:40) Dichos y lunfardo (58:20) Baldwin 4 y Hollywood (59:05) Natalie Portman (1:00:10) Estas a 5 grados (1:04:18) Borge Brende (1:07:11) Terminator 2 (1:11:09) Silicon Graphics (1:13:10) Sonic 3D blast (1:16:00) Show de drones (1:17:16) Drones y tecnología militar (1:25:03) Juegos, Wukong y Warhammer 40000 (1:37:20) La palabra "hello" (1:38:10) La Balgama de Pablo (1:43:40) Opeth y Led Zeppelin (1:45:10) 421 (1:51:15) India y softpower (1:54:20) Guile's Theme meme (2:00:55) Megapiojito - llora canalla

Cliff and Ash drop in on our good mate Shingzy and see what else he was doing, other than making his plumber 3D.We have a look at Silicon Graphics bringing in their good mate in, Paradigm Simulation, to help them show off what the Ultra 64 could be and how that developed in to a sequel to the game that had previously shown off what the SNES could do.Join the conversation on Discord!Theme song by Other ChrisFollow Under Consoletation on TwitterFollow Under Consoletation on InstagramSend your thoughts to feedback@underconsoletation.com Hosted on Acast. See acast.com/privacy for more information.

Clemente Cohen's finance career began in the early 1990s inside the Munich offices of Silicon Graphics, approximately 6,500 miles from the Silicon Valley company's headquarters and 7,500 miles from his birthplace in Argentina. This transcontinental start marked the beginning of a career defined by global problem solving , adaptability and generous helpings of M&A experience. Cohen, who grew up in Germany after moving from Argentina, problem solving perspective to his role. Joining Silicon Graphics as an accountant, Cohen tells us he was able to quickly demonstrate to others a innate curiosity and willingness to go the extra mile. Frequently, his contributions went beyond traditional accounting, delving into financial analysis and supporting the company's rapid growth. This foundational experience in a fast-paced, technology-driven environment would shape Cohen's understanding of finance operations on a global scale. Over the next decade, Cohen's career with Silicon Graphics expanded across continents. He held roles in Germany, the UK, and eventually became the International CFO, overseeing finance and business operations outside the United States. After a dozen years with Silicon Graphics, Cohen joined the London Office of CA Technologies , where Cohen tell us he was able to play a pivotal role in M&A activities and helped drive the company's transition from hardware to software. After spending much of his career at large, global companies, Cohen made a deliberate decision to pursue CFO opportunities at smaller, private equity-backed firms. This shift allowed him to be more hands-on, driving business transformation and growth in a more direct way. The move was not without hesitation, as smaller companies often come with greater challenges and fewer resources. However, Cohen embraced the opportunity to apply his extensive experience in a more entrepreneurial setting.

Lenny's Podcast: Product | Growth | Career ✓ Claim Key Takeaways Check out the episode pageRead the full notes @ podcastnotes.orgMike Maples, Jr. is a legendary early-stage startup investor and a co-founder and partner at Floodgate. He's made early bets on transformative companies like Twitter, Lyft, Twitch, Okta, Rappi, and Applied Intuition and is one of the pioneers of seed-stage investing as a category. He's been on the Forbes Midas List eight times and enjoys sharing the lessons he's learned from his years studying iconic companies. In his new book, Pattern Breakers: Why Some Start-Ups Change the Future, co-authored with Peter Ziebelman, he discusses what he's found separates startups and founders that break through and change the world from those that don't. After spending years reviewing the notes and decks from the thousands of startups he's known over the past two decades, he's uncovered three ways that breakthrough founders think and act differently. In our conversation, Mike talks about:• The three elements of breakthrough startup ideas• Why you need to both think and act differently• How to avoid the “comparison trap” and “conformity trap”• The importance of movements, storytelling, and healthy disagreeableness in startup success• How to apply pattern-breaking principles within large companies• Mike's one piece of advice for founders• Much morePre-order Mike's book here and get a second signed copy for free. Limited copies are available, so order ASAP: patternbreakers.com/lenny.—Brought to you by:• Enterpret—Transform customer feedback into product growth• Anvil—The fastest way to build software for documents• Webflow—The web experience platform—Find the transcript at: https://www.lennysnewsletter.com/p/how-to-find-a-great-startup-idea-mike-maples-jr—Where to find Mike Maples, Jr.:• X: https://x.com/m2jr• LinkedIn: https://www.linkedin.com/in/maples/• Substack: https://greatness.substack.com/• Website: https://www.floodgate.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Mike's background(03:10) The inspiration behind Pattern Breakers(08:09) Uncovering startup insights(11:37) A quick summary of Pattern Breakers(13:52) Coming up with an idea(15:30) Inflections(17:09) Examples of inflections(28:10) Insights(36:58) The power of surprises(47:36) Founder-future fit(55:33) Advice for aspiring founders(56:41) Living in the future: valid opinions(55:34) Case study: Maddie Hall and Living Carbon(58:40) Identifying lighthouse customers(01:00:53) The importance of desperation in customer needs(01:03:57) Creating movements and storytelling(01:24:22) The role of disagreeableness in startups(01:34:42) Applying these principles within a company(01:40:43) Lightning round—Referenced:• Pattern Breakers: Why Some Start-Ups Change the Future: https://www.amazon.com/Pattern-Breakers-Start-Ups-Change-Future/dp/1541704355• Justin.tv: https://en.wikipedia.org/wiki/Justin.tv• Airbnb's CEO says a $40 cereal box changed the course of the multibillion-dollar company: https://fortune.com/2023/04/19/airbnb-ceo-cereal-box-investors-changed-everything-billion-dollar-company/• Brian Chesky's new playbook: https://www.lennysnewsletter.com/p/brian-cheskys-contrarian-approach• The Unconventional Exit: How Justin Kan Sold His First Startup on eBay: https://medium.datadriveninvestor.com/the-unconventional-exit-how-justin-kan-sold-his-first-startup-on-ebay-4d705afe1354• Kyle Vogt on LinkedIn: https://www.linkedin.com/in/kylevogt/• The State of Telehealth Before and After the COVID-19 Pandemic: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9035352/• The Craigslist Killers: https://www.gq.com/story/craigslist-killers• The social radar: Y Combinator's secret weapon | Jessica Livingston (co-founder of Y Combinator, author, podcast host): https://www.lennysnewsletter.com/p/the-social-radar-jessica-livingston• Michael Seibel on LinkedIn: https://www.linkedin.com/in/mwseibel/• The Airbnb Story: How Three Ordinary Guys Disrupted an Industry, Made Billions ... and Created Plenty of Controversy: https://www.amazon.com/Airbnb-Story-Ordinary-Disrupted-Controversy/dp/0544952669• Scott Cook: https://www.forbes.com/profile/scott-cook/• Chegg: https://www.chegg.com/• Aayush Phumbhra on LinkedIn: https://www.linkedin.com/in/aayush/• Osman Rashid on LinkedIn: https://www.linkedin.com/in/osmanrashid/• Okta: https://www.okta.com/• The Man Who Makes the Future: Wired Icon Marc Andreessen: https://www.wired.com/2012/04/ff-andreessen/• Peter Ludwig on LinkedIn: https://www.linkedin.com/in/peterwludwig/• Qasar Younis on LinkedIn: https://www.linkedin.com/in/qasar/• Paul Allen's website: https://paulallen.com/• Louis Pasteur quote: https://www.forbes.com/quotes/6145/• What was Atrium and why did it fail? https://www.failory.com/cemetery/atrium• Patrick Collison on LinkedIn: https://www.linkedin.com/in/patrickcollison/• Drew Houston on LinkedIn: https://www.linkedin.com/in/drewhouston/• William Gibson's quote: https://www.goodreads.com/quotes/681-the-future-is-already-here-it-s-just-not-evenly• Maddie Hall on LinkedIn: https://www.linkedin.com/in/maddie-hall-76293135/• Living Carbon: https://www.livingcarbon.com• Zenefits (now Trinet): https://connect.trinet.com/• Sam Altman on X: https://x.com/sama• Steve Wozniak on LinkedIn: https://www.linkedin.com/in/wozniaksteve/• Horsley Bridge Partners: https://www.horsleybridge.com/• David Swensen: https://en.wikipedia.org/wiki/David_F._Swensen• Judith Elsea on LinkedIn: https://www.linkedin.com/in/judithelsea/• 7 Powers: The Foundations of Business Strategy: https://www.amazon.com/7-Powers-Foundations-Business-Strategy/dp/0998116319• Business strategy with Hamilton Helmer (author of 7 Powers): https://www.lennysnewsletter.com/p/business-strategy-with-hamilton-helmer• Lyft's Focus on Community and the Story Behind the Pink Mustache: https://techcrunch.com/2012/09/17/lyfts-focus-on-community-and-the-story-behind-the-pink-mustache/• Logan Green on LinkedIn: https://www.linkedin.com/in/logangreen/• John Zimmer on LinkedIn: https://www.linkedin.com/in/johnzimmer11/• Storytelling with Nancy Duarte: How to craft compelling presentations and tell a story that sticks: https://www.lennysnewsletter.com/p/storytelling-with-nancy-duarte-how• Steve Jobs Introducing the iPhone at MacWorld 2007: https://www.youtube.com/watch?v=x7qPAY9JqE4• Jonathan Livingston Seagull: https://www.amazon.com/Jonathan-Livingston-Seagull-Richard-Bach/dp/0743278909• The paths to power: How to grow your influence and advance your career | Jeffrey Pfeffer (author of 7 Rules of Power, professor at Stanford GSB): https://www.lennysnewsletter.com/p/the-paths-to-power-jeffrey-pfeffer• Robin Roberts on LinkedIn: https://www.linkedin.com/in/robin-roberts-393a934b/• Skunkworks: https://www.lockheedmartin.com/en-us/who-we-are/business-areas/aeronautics/skunkworks.html• Vision, conviction, and hype: How to build 0 to 1 inside a company | Mihika Kapoor (Product at Figma): https://www.lennysnewsletter.com/p/vision-conviction-hype-mihika-kapoor• Hard-won lessons building 0 to 1 inside Atlassian | Tanguy Crusson (Head of Jira Product Discovery): https://www.lennysnewsletter.com/p/building-0-to-1-inside-atlassian-tanguy-crusson• Figma: https://www.figma.com/• Atlassian: https://www.atlassian.com/• Vinod Khosla: https://www.khoslaventures.com/team/vinod-khosla/• Top Five Regrets of the Dying: A Life Transformed by the Dearly Departing: https://www.amazon.com/Top-Five-Regrets-Dying-Transformed-ebook/dp/B07KNRLY1L• Chase, Chance, and Creativity: The Lucky Art of Novelty: https://www.amazon.com/Chase-Chance-Creativity-Lucky-Novelty/dp/0262511355• Clay Christensen's books: https://www.amazon.com/stores/Clayton-M.-Christensen/author/B000APPD3Y• Resonate: Present Visual Stories That Transform: https://www.amazon.com/Resonate-Present-Stories-Transform-Audiences/dp/0470632011• Ferrari on Prime: https://www.amazon.com/Ferrari-Adam-Driver/dp/B0CNDBN672• Montblanc fountain pens: https://www.montblanc.com/en-us—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

Lenny's Podcast: Product | Growth | Career ✓ Claim Key Takeaways Check out the episode pageRead the full notes @ podcastnotes.orgMike Maples, Jr. is a legendary early-stage startup investor and a co-founder and partner at Floodgate. He's made early bets on transformative companies like Twitter, Lyft, Twitch, Okta, Rappi, and Applied Intuition and is one of the pioneers of seed-stage investing as a category. He's been on the Forbes Midas List eight times and enjoys sharing the lessons he's learned from his years studying iconic companies. In his new book, Pattern Breakers: Why Some Start-Ups Change the Future, co-authored with Peter Ziebelman, he discusses what he's found separates startups and founders that break through and change the world from those that don't. After spending years reviewing the notes and decks from the thousands of startups he's known over the past two decades, he's uncovered three ways that breakthrough founders think and act differently. In our conversation, Mike talks about:• The three elements of breakthrough startup ideas• Why you need to both think and act differently• How to avoid the “comparison trap” and “conformity trap”• The importance of movements, storytelling, and healthy disagreeableness in startup success• How to apply pattern-breaking principles within large companies• Mike's one piece of advice for founders• Much morePre-order Mike's book here and get a second signed copy for free. Limited copies are available, so order ASAP: patternbreakers.com/lenny.—Brought to you by:• Enterpret—Transform customer feedback into product growth• Anvil—The fastest way to build software for documents• Webflow—The web experience platform—Find the transcript at: https://www.lennysnewsletter.com/p/how-to-find-a-great-startup-idea-mike-maples-jr—Where to find Mike Maples, Jr.:• X: https://x.com/m2jr• LinkedIn: https://www.linkedin.com/in/maples/• Substack: https://greatness.substack.com/• Website: https://www.floodgate.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Mike's background(03:10) The inspiration behind Pattern Breakers(08:09) Uncovering startup insights(11:37) A quick summary of Pattern Breakers(13:52) Coming up with an idea(15:30) Inflections(17:09) Examples of inflections(28:10) Insights(36:58) The power of surprises(47:36) Founder-future fit(55:33) Advice for aspiring founders(56:41) Living in the future: valid opinions(55:34) Case study: Maddie Hall and Living Carbon(58:40) Identifying lighthouse customers(01:00:53) The importance of desperation in customer needs(01:03:57) Creating movements and storytelling(01:24:22) The role of disagreeableness in startups(01:34:42) Applying these principles within a company(01:40:43) Lightning round—Referenced:• Pattern Breakers: Why Some Start-Ups Change the Future: https://www.amazon.com/Pattern-Breakers-Start-Ups-Change-Future/dp/1541704355• Justin.tv: https://en.wikipedia.org/wiki/Justin.tv• Airbnb's CEO says a $40 cereal box changed the course of the multibillion-dollar company: https://fortune.com/2023/04/19/airbnb-ceo-cereal-box-investors-changed-everything-billion-dollar-company/• Brian Chesky's new playbook: https://www.lennysnewsletter.com/p/brian-cheskys-contrarian-approach• The Unconventional Exit: How Justin Kan Sold His First Startup on eBay: https://medium.datadriveninvestor.com/the-unconventional-exit-how-justin-kan-sold-his-first-startup-on-ebay-4d705afe1354• Kyle Vogt on LinkedIn: https://www.linkedin.com/in/kylevogt/• The State of Telehealth Before and After the COVID-19 Pandemic: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9035352/• The Craigslist Killers: https://www.gq.com/story/craigslist-killers• The social radar: Y Combinator's secret weapon | Jessica Livingston (co-founder of Y Combinator, author, podcast host): https://www.lennysnewsletter.com/p/the-social-radar-jessica-livingston• Michael Seibel on LinkedIn: https://www.linkedin.com/in/mwseibel/• The Airbnb Story: How Three Ordinary Guys Disrupted an Industry, Made Billions ... and Created Plenty of Controversy: https://www.amazon.com/Airbnb-Story-Ordinary-Disrupted-Controversy/dp/0544952669• Scott Cook: https://www.forbes.com/profile/scott-cook/• Chegg: https://www.chegg.com/• Aayush Phumbhra on LinkedIn: https://www.linkedin.com/in/aayush/• Osman Rashid on LinkedIn: https://www.linkedin.com/in/osmanrashid/• Okta: https://www.okta.com/• The Man Who Makes the Future: Wired Icon Marc Andreessen: https://www.wired.com/2012/04/ff-andreessen/• Peter Ludwig on LinkedIn: https://www.linkedin.com/in/peterwludwig/• Qasar Younis on LinkedIn: https://www.linkedin.com/in/qasar/• Paul Allen's website: https://paulallen.com/• Louis Pasteur quote: https://www.forbes.com/quotes/6145/• What was Atrium and why did it fail? https://www.failory.com/cemetery/atrium• Patrick Collison on LinkedIn: https://www.linkedin.com/in/patrickcollison/• Drew Houston on LinkedIn: https://www.linkedin.com/in/drewhouston/• William Gibson's quote: https://www.goodreads.com/quotes/681-the-future-is-already-here-it-s-just-not-evenly• Maddie Hall on LinkedIn: https://www.linkedin.com/in/maddie-hall-76293135/• Living Carbon: https://www.livingcarbon.com• Zenefits (now Trinet): https://connect.trinet.com/• Sam Altman on X: https://x.com/sama• Steve Wozniak on LinkedIn: https://www.linkedin.com/in/wozniaksteve/• Horsley Bridge Partners: https://www.horsleybridge.com/• David Swensen: https://en.wikipedia.org/wiki/David_F._Swensen• Judith Elsea on LinkedIn: https://www.linkedin.com/in/judithelsea/• 7 Powers: The Foundations of Business Strategy: https://www.amazon.com/7-Powers-Foundations-Business-Strategy/dp/0998116319• Business strategy with Hamilton Helmer (author of 7 Powers): https://www.lennysnewsletter.com/p/business-strategy-with-hamilton-helmer• Lyft's Focus on Community and the Story Behind the Pink Mustache: https://techcrunch.com/2012/09/17/lyfts-focus-on-community-and-the-story-behind-the-pink-mustache/• Logan Green on LinkedIn: https://www.linkedin.com/in/logangreen/• John Zimmer on LinkedIn: https://www.linkedin.com/in/johnzimmer11/• Storytelling with Nancy Duarte: How to craft compelling presentations and tell a story that sticks: https://www.lennysnewsletter.com/p/storytelling-with-nancy-duarte-how• Steve Jobs Introducing the iPhone at MacWorld 2007: https://www.youtube.com/watch?v=x7qPAY9JqE4• Jonathan Livingston Seagull: https://www.amazon.com/Jonathan-Livingston-Seagull-Richard-Bach/dp/0743278909• The paths to power: How to grow your influence and advance your career | Jeffrey Pfeffer (author of 7 Rules of Power, professor at Stanford GSB): https://www.lennysnewsletter.com/p/the-paths-to-power-jeffrey-pfeffer• Robin Roberts on LinkedIn: https://www.linkedin.com/in/robin-roberts-393a934b/• Skunkworks: https://www.lockheedmartin.com/en-us/who-we-are/business-areas/aeronautics/skunkworks.html• Vision, conviction, and hype: How to build 0 to 1 inside a company | Mihika Kapoor (Product at Figma): https://www.lennysnewsletter.com/p/vision-conviction-hype-mihika-kapoor• Hard-won lessons building 0 to 1 inside Atlassian | Tanguy Crusson (Head of Jira Product Discovery): https://www.lennysnewsletter.com/p/building-0-to-1-inside-atlassian-tanguy-crusson• Figma: https://www.figma.com/• Atlassian: https://www.atlassian.com/• Vinod Khosla: https://www.khoslaventures.com/team/vinod-khosla/• Top Five Regrets of the Dying: A Life Transformed by the Dearly Departing: https://www.amazon.com/Top-Five-Regrets-Dying-Transformed-ebook/dp/B07KNRLY1L• Chase, Chance, and Creativity: The Lucky Art of Novelty: https://www.amazon.com/Chase-Chance-Creativity-Lucky-Novelty/dp/0262511355• Clay Christensen's books: https://www.amazon.com/stores/Clayton-M.-Christensen/author/B000APPD3Y• Resonate: Present Visual Stories That Transform: https://www.amazon.com/Resonate-Present-Stories-Transform-Audiences/dp/0470632011• Ferrari on Prime: https://www.amazon.com/Ferrari-Adam-Driver/dp/B0CNDBN672• Montblanc fountain pens: https://www.montblanc.com/en-us—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

Lenny's Podcast: Product | Growth | Career ✓ Claim Key Takeaways Check out the episode pageRead the full notes @ podcastnotes.orgMike Maples, Jr. is a legendary early-stage startup investor and a co-founder and partner at Floodgate. He's made early bets on transformative companies like Twitter, Lyft, Twitch, Okta, Rappi, and Applied Intuition and is one of the pioneers of seed-stage investing as a category. He's been on the Forbes Midas List eight times and enjoys sharing the lessons he's learned from his years studying iconic companies. In his new book, Pattern Breakers: Why Some Start-Ups Change the Future, co-authored with Peter Ziebelman, he discusses what he's found separates startups and founders that break through and change the world from those that don't. After spending years reviewing the notes and decks from the thousands of startups he's known over the past two decades, he's uncovered three ways that breakthrough founders think and act differently. In our conversation, Mike talks about:• The three elements of breakthrough startup ideas• Why you need to both think and act differently• How to avoid the “comparison trap” and “conformity trap”• The importance of movements, storytelling, and healthy disagreeableness in startup success• How to apply pattern-breaking principles within large companies• Mike's one piece of advice for founders• Much morePre-order Mike's book here and get a second signed copy for free. Limited copies are available, so order ASAP: patternbreakers.com/lenny.—Brought to you by:• Enterpret—Transform customer feedback into product growth• Anvil—The fastest way to build software for documents• Webflow—The web experience platform—Find the transcript at: https://www.lennysnewsletter.com/p/how-to-find-a-great-startup-idea-mike-maples-jr—Where to find Mike Maples, Jr.:• X: https://x.com/m2jr• LinkedIn: https://www.linkedin.com/in/maples/• Substack: https://greatness.substack.com/• Website: https://www.floodgate.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Mike's background(03:10) The inspiration behind Pattern Breakers(08:09) Uncovering startup insights(11:37) A quick summary of Pattern Breakers(13:52) Coming up with an idea(15:30) Inflections(17:09) Examples of inflections(28:10) Insights(36:58) The power of surprises(47:36) Founder-future fit(55:33) Advice for aspiring founders(56:41) Living in the future: valid opinions(55:34) Case study: Maddie Hall and Living Carbon(58:40) Identifying lighthouse customers(01:00:53) The importance of desperation in customer needs(01:03:57) Creating movements and storytelling(01:24:22) The role of disagreeableness in startups(01:34:42) Applying these principles within a company(01:40:43) Lightning round—Referenced:• Pattern Breakers: Why Some Start-Ups Change the Future: https://www.amazon.com/Pattern-Breakers-Start-Ups-Change-Future/dp/1541704355• Justin.tv: https://en.wikipedia.org/wiki/Justin.tv• Airbnb's CEO says a $40 cereal box changed the course of the multibillion-dollar company: https://fortune.com/2023/04/19/airbnb-ceo-cereal-box-investors-changed-everything-billion-dollar-company/• Brian Chesky's new playbook: https://www.lennysnewsletter.com/p/brian-cheskys-contrarian-approach• The Unconventional Exit: How Justin Kan Sold His First Startup on eBay: https://medium.datadriveninvestor.com/the-unconventional-exit-how-justin-kan-sold-his-first-startup-on-ebay-4d705afe1354• Kyle Vogt on LinkedIn: https://www.linkedin.com/in/kylevogt/• The State of Telehealth Before and After the COVID-19 Pandemic: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9035352/• The Craigslist Killers: https://www.gq.com/story/craigslist-killers• The social radar: Y Combinator's secret weapon | Jessica Livingston (co-founder of Y Combinator, author, podcast host): https://www.lennysnewsletter.com/p/the-social-radar-jessica-livingston• Michael Seibel on LinkedIn: https://www.linkedin.com/in/mwseibel/• The Airbnb Story: How Three Ordinary Guys Disrupted an Industry, Made Billions ... and Created Plenty of Controversy: https://www.amazon.com/Airbnb-Story-Ordinary-Disrupted-Controversy/dp/0544952669• Scott Cook: https://www.forbes.com/profile/scott-cook/• Chegg: https://www.chegg.com/• Aayush Phumbhra on LinkedIn: https://www.linkedin.com/in/aayush/• Osman Rashid on LinkedIn: https://www.linkedin.com/in/osmanrashid/• Okta: https://www.okta.com/• The Man Who Makes the Future: Wired Icon Marc Andreessen: https://www.wired.com/2012/04/ff-andreessen/• Peter Ludwig on LinkedIn: https://www.linkedin.com/in/peterwludwig/• Qasar Younis on LinkedIn: https://www.linkedin.com/in/qasar/• Paul Allen's website: https://paulallen.com/• Louis Pasteur quote: https://www.forbes.com/quotes/6145/• What was Atrium and why did it fail? https://www.failory.com/cemetery/atrium• Patrick Collison on LinkedIn: https://www.linkedin.com/in/patrickcollison/• Drew Houston on LinkedIn: https://www.linkedin.com/in/drewhouston/• William Gibson's quote: https://www.goodreads.com/quotes/681-the-future-is-already-here-it-s-just-not-evenly• Maddie Hall on LinkedIn: https://www.linkedin.com/in/maddie-hall-76293135/• Living Carbon: https://www.livingcarbon.com• Zenefits (now Trinet): https://connect.trinet.com/• Sam Altman on X: https://x.com/sama• Steve Wozniak on LinkedIn: https://www.linkedin.com/in/wozniaksteve/• Horsley Bridge Partners: https://www.horsleybridge.com/• David Swensen: https://en.wikipedia.org/wiki/David_F._Swensen• Judith Elsea on LinkedIn: https://www.linkedin.com/in/judithelsea/• 7 Powers: The Foundations of Business Strategy: https://www.amazon.com/7-Powers-Foundations-Business-Strategy/dp/0998116319• Business strategy with Hamilton Helmer (author of 7 Powers): https://www.lennysnewsletter.com/p/business-strategy-with-hamilton-helmer• Lyft's Focus on Community and the Story Behind the Pink Mustache: https://techcrunch.com/2012/09/17/lyfts-focus-on-community-and-the-story-behind-the-pink-mustache/• Logan Green on LinkedIn: https://www.linkedin.com/in/logangreen/• John Zimmer on LinkedIn: https://www.linkedin.com/in/johnzimmer11/• Storytelling with Nancy Duarte: How to craft compelling presentations and tell a story that sticks: https://www.lennysnewsletter.com/p/storytelling-with-nancy-duarte-how• Steve Jobs Introducing the iPhone at MacWorld 2007: https://www.youtube.com/watch?v=x7qPAY9JqE4• Jonathan Livingston Seagull: https://www.amazon.com/Jonathan-Livingston-Seagull-Richard-Bach/dp/0743278909• The paths to power: How to grow your influence and advance your career | Jeffrey Pfeffer (author of 7 Rules of Power, professor at Stanford GSB): https://www.lennysnewsletter.com/p/the-paths-to-power-jeffrey-pfeffer• Robin Roberts on LinkedIn: https://www.linkedin.com/in/robin-roberts-393a934b/• Skunkworks: https://www.lockheedmartin.com/en-us/who-we-are/business-areas/aeronautics/skunkworks.html• Vision, conviction, and hype: How to build 0 to 1 inside a company | Mihika Kapoor (Product at Figma): https://www.lennysnewsletter.com/p/vision-conviction-hype-mihika-kapoor• Hard-won lessons building 0 to 1 inside Atlassian | Tanguy Crusson (Head of Jira Product Discovery): https://www.lennysnewsletter.com/p/building-0-to-1-inside-atlassian-tanguy-crusson• Figma: https://www.figma.com/• Atlassian: https://www.atlassian.com/• Vinod Khosla: https://www.khoslaventures.com/team/vinod-khosla/• Top Five Regrets of the Dying: A Life Transformed by the Dearly Departing: https://www.amazon.com/Top-Five-Regrets-Dying-Transformed-ebook/dp/B07KNRLY1L• Chase, Chance, and Creativity: The Lucky Art of Novelty: https://www.amazon.com/Chase-Chance-Creativity-Lucky-Novelty/dp/0262511355• Clay Christensen's books: https://www.amazon.com/stores/Clayton-M.-Christensen/author/B000APPD3Y• Resonate: Present Visual Stories That Transform: https://www.amazon.com/Resonate-Present-Stories-Transform-Audiences/dp/0470632011• Ferrari on Prime: https://www.amazon.com/Ferrari-Adam-Driver/dp/B0CNDBN672• Montblanc fountain pens: https://www.montblanc.com/en-us—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

Text us and say hello!In episode 15 of "Backwards Compatible", Lou is back in the studio with me, as we swing into the jungles of "Donkey Kong Country" on the SNES, released in November of 1994. I first encountered this game as a rental at a friend's house—the same friend whose "Super Mario World" save file I unfortunately erased (sorry, Dane!).  Revisiting it now, the game stands out for its exceptional level design, arguably among the best for side-scrolling platformers. Its gameplay mechanics, inspired by Mario's run button and Sonic's rhythmic precision, showcase the unique platforming challenges that set "Donkey Kong Country" apart.Developed by the acclaimed studio Rare and published by Nintendo, "Donkey Kong Country" was one of the first major titles to utilize pre-rendered 3D graphics, created on Silicon Graphics workstations. This innovative approach resulted in some of the most detailed and realistic visuals on the SNES. The game also boasted a memorable soundtrack by David Wise, Eveline Fischer, and Robin Beanland, with tracks like "Aquatic Ambience" and "Gang-Plank Galleon" that are still celebrated today. Despite my burning hatred for the minecart levels, the game's commercial success and critical acclaim are undeniable. It revitalized the Donkey Kong franchise and established Rare as a powerhouse that would go on to create other hits like "Banjo Kazooie" and "Killer Instinct."As we explore "Donkey Kong Country's" development, graphical breakthroughs, and gameplay, we also reflect on the pop culture milestones of 1994, setting the scene for when this groundbreaking game first captivated players around the world. Join Lou and me as we delve into the legacy of a game that not only defined an era but also continues to influence the platforming genre across gaming generations.Support the Show.We've got merch!Check out the site for some awesome Gen 'S' swag :)

Mike Maples, Jr. is a legendary early-stage startup investor and a co-founder and partner at Floodgate. He's made early bets on transformative companies like Twitter, Lyft, Twitch, Okta, Rappi, and Applied Intuition and is one of the pioneers of seed-stage investing as a category. He's been on the Forbes Midas List eight times and enjoys sharing the lessons he's learned from his years studying iconic companies. In his new book, Pattern Breakers: Why Some Start-Ups Change the Future, co-authored with Peter Ziebelman, he discusses what he's found separates startups and founders that break through and change the world from those that don't. After spending years reviewing the notes and decks from the thousands of startups he's known over the past two decades, he's uncovered three ways that breakthrough founders think and act differently. In our conversation, Mike talks about:• The three elements of breakthrough startup ideas• Why you need to both think and act differently• How to avoid the “comparison trap” and “conformity trap”• The importance of movements, storytelling, and healthy disagreeableness in startup success• How to apply pattern-breaking principles within large companies• Mike's one piece of advice for founders• Much morePre-order Mike's book here and get a second signed copy for free. Limited copies are available, so order ASAP: patternbreakers.com/lenny.—Brought to you by:• Enterpret—Transform customer feedback into product growth• Anvil—The fastest way to build software for documents• Webflow—The web experience platform—Find the transcript at: https://www.lennysnewsletter.com/p/how-to-find-a-great-startup-idea-mike-maples-jr—Where to find Mike Maples, Jr.:• X: https://x.com/m2jr• LinkedIn: https://www.linkedin.com/in/maples/• Substack: https://greatness.substack.com/• Website: https://www.floodgate.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Mike's background(03:10) The inspiration behind Pattern Breakers(08:09) Uncovering startup insights(11:37) A quick summary of Pattern Breakers(13:52) Coming up with an idea(15:30) Inflections(17:09) Examples of inflections(28:10) Insights(36:58) The power of surprises(47:36) Founder-future fit(55:33) Advice for aspiring founders(56:41) Living in the future: valid opinions(55:34) Case study: Maddie Hall and Living Carbon(58:40) Identifying lighthouse customers(01:00:53) The importance of desperation in customer needs(01:03:57) Creating movements and storytelling(01:24:22) The role of disagreeableness in startups(01:34:42) Applying these principles within a company(01:40:43) Lightning round—Referenced:• Pattern Breakers: Why Some Start-Ups Change the Future: https://www.amazon.com/Pattern-Breakers-Start-Ups-Change-Future/dp/1541704355• Justin.tv: https://en.wikipedia.org/wiki/Justin.tv• Airbnb's CEO says a $40 cereal box changed the course of the multibillion-dollar company: https://fortune.com/2023/04/19/airbnb-ceo-cereal-box-investors-changed-everything-billion-dollar-company/• Brian Chesky's new playbook: https://www.lennysnewsletter.com/p/brian-cheskys-contrarian-approach• The Unconventional Exit: How Justin Kan Sold His First Startup on eBay: https://medium.datadriveninvestor.com/the-unconventional-exit-how-justin-kan-sold-his-first-startup-on-ebay-4d705afe1354• Kyle Vogt on LinkedIn: https://www.linkedin.com/in/kylevogt/• The State of Telehealth Before and After the COVID-19 Pandemic: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9035352/• The Craigslist Killers: https://www.gq.com/story/craigslist-killers• The social radar: Y Combinator's secret weapon | Jessica Livingston (co-founder of Y Combinator, author, podcast host): https://www.lennysnewsletter.com/p/the-social-radar-jessica-livingston• Michael Seibel on LinkedIn: https://www.linkedin.com/in/mwseibel/• The Airbnb Story: How Three Ordinary Guys Disrupted an Industry, Made Billions ... and Created Plenty of Controversy: https://www.amazon.com/Airbnb-Story-Ordinary-Disrupted-Controversy/dp/0544952669• Scott Cook: https://www.forbes.com/profile/scott-cook/• Chegg: https://www.chegg.com/• Aayush Phumbhra on LinkedIn: https://www.linkedin.com/in/aayush/• Osman Rashid on LinkedIn: https://www.linkedin.com/in/osmanrashid/• Okta: https://www.okta.com/• The Man Who Makes the Future: Wired Icon Marc Andreessen: https://www.wired.com/2012/04/ff-andreessen/• Peter Ludwig on LinkedIn: https://www.linkedin.com/in/peterwludwig/• Qasar Younis on LinkedIn: https://www.linkedin.com/in/qasar/• Paul Allen's website: https://paulallen.com/• Louis Pasteur quote: https://www.forbes.com/quotes/6145/• What was Atrium and why did it fail? https://www.failory.com/cemetery/atrium• Patrick Collison on LinkedIn: https://www.linkedin.com/in/patrickcollison/• Drew Houston on LinkedIn: https://www.linkedin.com/in/drewhouston/• William Gibson's quote: https://www.goodreads.com/quotes/681-the-future-is-already-here-it-s-just-not-evenly• Maddie Hall on LinkedIn: https://www.linkedin.com/in/maddie-hall-76293135/• Living Carbon: https://www.livingcarbon.com• Zenefits (now Trinet): https://connect.trinet.com/• Sam Altman on X: https://x.com/sama• Steve Wozniak on LinkedIn: https://www.linkedin.com/in/wozniaksteve/• Horsley Bridge Partners: https://www.horsleybridge.com/• David Swensen: https://en.wikipedia.org/wiki/David_F._Swensen• Judith Elsea on LinkedIn: https://www.linkedin.com/in/judithelsea/• 7 Powers: The Foundations of Business Strategy: https://www.amazon.com/7-Powers-Foundations-Business-Strategy/dp/0998116319• Business strategy with Hamilton Helmer (author of 7 Powers): https://www.lennysnewsletter.com/p/business-strategy-with-hamilton-helmer• Lyft's Focus on Community and the Story Behind the Pink Mustache: https://techcrunch.com/2012/09/17/lyfts-focus-on-community-and-the-story-behind-the-pink-mustache/• Logan Green on LinkedIn: https://www.linkedin.com/in/logangreen/• John Zimmer on LinkedIn: https://www.linkedin.com/in/johnzimmer11/• Storytelling with Nancy Duarte: How to craft compelling presentations and tell a story that sticks: https://www.lennysnewsletter.com/p/storytelling-with-nancy-duarte-how• Steve Jobs Introducing the iPhone at MacWorld 2007: https://www.youtube.com/watch?v=x7qPAY9JqE4• Jonathan Livingston Seagull: https://www.amazon.com/Jonathan-Livingston-Seagull-Richard-Bach/dp/0743278909• The paths to power: How to grow your influence and advance your career | Jeffrey Pfeffer (author of 7 Rules of Power, professor at Stanford GSB): https://www.lennysnewsletter.com/p/the-paths-to-power-jeffrey-pfeffer• Robin Roberts on LinkedIn: https://www.linkedin.com/in/robin-roberts-393a934b/• Skunkworks: https://www.lockheedmartin.com/en-us/who-we-are/business-areas/aeronautics/skunkworks.html• Vision, conviction, and hype: How to build 0 to 1 inside a company | Mihika Kapoor (Product at Figma): https://www.lennysnewsletter.com/p/vision-conviction-hype-mihika-kapoor• Hard-won lessons building 0 to 1 inside Atlassian | Tanguy Crusson (Head of Jira Product Discovery): https://www.lennysnewsletter.com/p/building-0-to-1-inside-atlassian-tanguy-crusson• Figma: https://www.figma.com/• Atlassian: https://www.atlassian.com/• Vinod Khosla: https://www.khoslaventures.com/team/vinod-khosla/• Top Five Regrets of the Dying: A Life Transformed by the Dearly Departing: https://www.amazon.com/Top-Five-Regrets-Dying-Transformed-ebook/dp/B07KNRLY1L• Chase, Chance, and Creativity: The Lucky Art of Novelty: https://www.amazon.com/Chase-Chance-Creativity-Lucky-Novelty/dp/0262511355• Clay Christensen's books: https://www.amazon.com/stores/Clayton-M.-Christensen/author/B000APPD3Y• Resonate: Present Visual Stories That Transform: https://www.amazon.com/Resonate-Present-Stories-Transform-Audiences/dp/0470632011• Ferrari on Prime: https://www.amazon.com/Ferrari-Adam-Driver/dp/B0CNDBN672• Montblanc fountain pens: https://www.montblanc.com/en-us—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

Tamara Steffens is a seasoned tech executive with a remarkable track record in scaling teams, infrastructures, and products. She has contributed significantly to early mobile and SaaS pioneers, including Boingo, Software.com, Fusion One, and Color. Tamara has held executive roles at Microsoft and Openwave, leading large teams and driving innovation. Her tech career began at Sun Microsystems and Silicon Graphics, where she architected partnerships that defined entire industries. Tamara holds a BS in finance from Michigan State University and is actively involved in shaping the future of business and innovation as a board member at the Broad Business School and a member of the National Advisory Council on Innovation and Entrepreneurship at the U.S. Department of Commerce. She currently works as an MD at Thomson Reuters Ventures; we are thrilled to welcome Tamara to AI and the Future of Work.In this episode,  we discuss:Corporate Venture Capital Insights: Tamara shares her journey from working at tech companies like Sun Microsystems and Silicon Graphics to leading Thomson Reuters' venture fund. She explains how her extensive go-to-market experience shapes her investment strategy.Investment Strategies in AI: We explore how Thomson Reuters' corporate venture arm approaches AI investments, emphasizing the importance of product-market fit, revenue generation, and strategic alignment with the company's broader goals.Differences Between Corporate and Traditional VCs: Tamara outlines the unique considerations of corporate VCs, such as potential go-to-market synergies and strategic benefits, compared to traditional VCs which primarily focus on financial returns.Case Studies of AI Investments: We delve into specific investments, like WiseDocs and CentML, highlighting the processes, investment theses, and strategic benefits these companies bring to Thomson Reuters and their respective industries.The Impact of AI on the Legal Industry: Tamara discusses how AI is transforming the legal sector, enhancing efficiency, and changing the nature of legal work, particularly for junior lawyers and paralegals.Responsible AI and Data Governance: We talk about the importance of responsible AI, data privacy, and governance in AI investments. Tamara explains Thomson Reuters' approach to ensuring ethical AI practices and compliance with legal standards.ResourceConnect with Tamara AI fun fact articleAn episode you might like about breaking into venture capital

Aylin Uysal shares her story of leading enterprise design, the reality of being an exec and a parent, and how patience and perseverance have served her well. Highlights include: Why is it important to have a good grasp of the details as a senior design leader? How do you know when you haven't got the work-parent balance quite right? What changed at Oracle to enable the culture to significantly support design? How do you work across Oracle to ensure that users' experience great design? Why can't business apps be as simple and delightful as consumer apps? ====== Who is Aylin Uysal? Currently the VP of User Experience for Cloud Applications at Oracle, Aylin is at the forefront of design at one of the tech industry's most established companies, helping its customers to see data in new ways, discover insights and unlock endless possibilities. During over two decades at Oracle Aylin has held several senior leadership roles, serving previously as a Senior Director of User Experience, a Director of Applications User Experience, and as a Senior Manager of HCM User Experience. Before her long-standing tenure at Oracle, Aylin was a valued member of the design team at SAP, where she was a lead designer. She also made her mark as a senior designer at Silicon Graphics, a legendary Silicon Valley icon. Originally from Turkey, Aylin graduated from Middle East Technical University with a Bachelor's in Industrial Design. She further honed her craft, obtaining a Master of Fine Arts from San Francisco's Academy of Art University. Aylin's influence is not just corporate; she's been celebrated as one of the top thirty influential Turkish-American women by Turk of Amerika, she is a board member of the TUSIAD Silicon Valley Network, and is credited on 8 US patents.  ====== Find Aylin here: LinkedIn: https://www.linkedin.com/in/aylinuysal/ X: https://twitter.com/aylinuysal ====== Liked what you heard and want to hear more? Subscribe and support the show by leaving a review on Apple Podcasts (or wherever you listen). Follow us on our other social channels for more great Brave UX content! YouTube: https://www.youtube.com/TheSpaceInBetween/ LinkedIn: https://www.linkedin.com/company/the-space-in-between/ Instagram: https://www.instagram.com/thespaceinbetw__n/ ====== Hosted by Brendan Jarvis: LinkedIn: https://www.linkedin.com/in/brendanjarvis/ Website: https://thespaceinbetween.co.nz/ Twitter: https://twitter.com/brendanjarvis/

Paul Nerger is a seasoned industry expert with a diverse background spanning technology, business management, and academia. He holds a bachelor's degree in computer science from Washington State University with a focus in Artificial Intelligence. His academic journey continued with coursework at Templeton College at the University of Oxford as well as serving as a lecturer at MIT's Applied Innovation Institute and the University of California, Berkeley's Center for Entrepreneurship and Technology.Paul's entrepreneurial spirit shines through his roles as a co-founder and CTO of Happtique, Inc., AppCentral, dotMobi, and Argogroup all of which were sold to larger companies. Paul also has experience at larger companies including senior positions at Digital Equipment, Sequent Computer Systems, Silicon Graphics, and Informix Software.  Currently, as a VP at Blue Prism, Paul leads a team dedicated to fostering collaboration and innovation within the RPA ecosystem including how to apply advanced AI to solving business problems.Paul has served on the board of directors and technical advisory boards for several companies including the Boeing Company and British Aerospace.  He served as a U.S. Air Force Officer and the Air Defense Advisor to NATO.With a rich tapestry of experiences encompassing academia, entrepreneurship, and corporate leadership, Paul continues to drive innovation and empower organizations to thrive in the ever-evolving landscape of technology and business.Paul is a member the Royal Air Force Club and Fellow of the Royal Institute of Arts in London.Support the showFollow me on Facebook ⬇️https://www.facebook.com/manuj.aggarwal❤️ ID - Manuj Aggarwal■ LinkedIn: https://www.linkedin.com/in/manujaggarwal/ ■ Facebook: https://www.facebook.com/realmanuj■ Instagram: ...

Original text by Henry Bortman. Be's roller coaster ride from 1990-1998: the 1995 O.J. Simpson trial, Commodore's Irving Gould, a thirty-mile hike to the sea, headhunting disgruntled Apple employees, and what to do when Apple says you're not allowed to exhibit at WWDC 1996. Jean-Louis Gassée's story about having dinner with John Sculley from the 2011 Steve Jobs Legacy event at the Churchill Club. The 1996 BeOS vs. NeXTSTEP bakeoff story as told by Avie Tevanian. Acorn co-founder Hermann Hauser reflecting on Larry Tesler choosing ARM over the AT&T Hobbit. Guy Kawasaki on corporate offsite retreats. The Computer Chronicles stops by the Be, Inc. booth at Macworld Boston 1996. Steve Sakoman left Be for Silicon Graphics in 1994, then returned to Be in 1996. He went back to Apple in 2003, and according to Jon Rubinstein, was supposed to be Avie Tevanian's successor in 2006 but “didn't get the tap on the shoulder”.

In our chat, "Pioneers of '80s Art & Innovation," from February 7, 2024, a panel of icons joins Peter Bauman and Conrad House. They share their diverse perspectives on the 1980s in digital and generative art, reflecting the decade's richness and complexity. Speakers include: Mark Wilson, Copper Giloth, Dan Sandin, David Em, William Latham, Stephen Todd, Darcy Gerbarg + Geoff Davis Chapters

This week on the Expert Voices podcast, Randy Wootton, CEO of Maxio, speaks with Thomas Lah, co-founder of the Technology Services Industry Association (TSIA). Randy and Thomas take an in-depth exploration of the journey from traditional software models to SaaS, the dynamics of profitability within the industry, and the development of key success metrics. Thomas shares valuable experiences from his tenure at Silicon Graphics to his groundbreaking approach in founding an association focused on data and insights for the technology services industry. Randy and Thomas navigate through the transformational shift from on-premises software models to cloud-native SaaS businesses, revealing trends, challenges, and strategies for acclimating to new market realities. Quotes"If your RAC (revenue acquisition cost) number is higher than your competitors, you have a problem. You have a serious problem because you are not as efficient at generating revenue growth. And that's going to catch up with you. How much time and treasure you're going to have to spend to get market share.” -Thomas Lah [22:20]“SaaS companies can be replaced. As a CEO or CFO, you have to think about your unique value in a way that doesn't lock the customer in. You have to continue to give value. It's a value conversation versus a price increase conversation.” -Randy Wootton [38:58]Expert Takeaways The Rule of 35, proposed by TSIA, serves as a new benchmark for operational efficiency, complementing the well-known Rule of 40 in guiding SaaS companies towards profitability.Monetizing service motions, migrating commercials, and leveraging data for growth are crucial levers for improving SaaS profitability.The RAC (Revenue Acquisition Cost) to CAC (Customer Acquisition Cost) metric provides a clearer picture of growth efficiency compared to CAC alone.There has been an increase in focus on financial austerity among SaaS companies, with significant layoffs marking a move toward more sustainable growth strategies.Timestamps[03:25] Transformation from on-prem to cloud-native software [07:13] Migration from on-prem to managed service offers [10:19] Challenges of achieving profitability in the SaaS business model [13:07] Tech companies have eliminated almost a million jobs [14:18] Importance of being profitable and the rule of 40 [22:10] Salesforce, ServiceNow, and Zscaler's rack numbers compared to competitors [24:37] CFOs need to shift from Excel to database models for data analysis [29:15] CFOs need to shift from compliance to strategic partnership [31:44] The "porpoise principle" of becoming profitable before making growth investments [40:01] Changing the operating model is the hard work for profitability [40:57] "Digital Hesitation" and "As a Service Playbook" are recommended booksLinksMAXIOUpcoming EventsMaxio Institute Report

Nintendo profits crash, Next gen console battle begins & Arcades go 3D These stories and many more on this episode of the VGNRTM This episode we will look back at the biggest stories in and around the video game industry in October 1993.  As always, we'll mostly be using magazine cover dates, and those are of course always a bit behind the actual events. Alex Smith of They Create Worlds is our cohost.  Check out his podcast here: https://www.theycreateworlds.com/ and order his book here: https://www.theycreateworlds.com/book Get us on your mobile device: Android:  https://www.google.com/podcasts?feed=aHR0cHM6Ly92aWRlb2dhbWVuZXdzcm9vbXRpbWVtYWNoaW5lLmxpYnN5bi5jb20vcnNz iOS:      https://podcasts.apple.com/de/podcast/video-game-newsroom-time-machine And if you like what we are doing here at the podcast, don't forget to like us on your podcasting app of choice, YouTube, and/or support us on patreon! https://www.patreon.com/VGNRTM Send comments on Mastodon @videogamenewsroomtimemachine@oldbytes.space Or twitter @videogamenewsr2 Or Instagram https://www.instagram.com/vgnrtm Or videogamenewsroomtimemachine@gmail.com Links: A complete set of links can be found here: https://www.patreon.com/posts/95287239 7 Minutes in Heaven: Hired Guns Video Version:  https://www.patreon.com/posts/7-minutes-in-95284763 https://www.mobygames.com/game/6742/hired-guns/ https://www.mobygames.com/game/83985/overcooked/ https://www.mobygames.com/game/59006/spaceteam/ Corrections: September 1993 Ep - https://www.patreon.com/posts/september-1993-93580366 Ethan's fine site The History of How We Play: https://thehistoryofhowweplay.wordpress.com/ Video Game Historian - Aladdin Deck Enhancer - https://youtu.be/_eG-PSZU5MI?si=UkmcQ6RDEs_Ljm-w 1993-10: JAMMA show brings the tech     https://archive.org/details/electronic-gaming-monthly-issue-51-october-1993/page/222/mode/1up?view=theater Riiiiiiiiiiiiidge Racer debuts, remember that one?     https://archive.org/details/electronic-gaming-monthly-issue-51-october-1993/page/64/mode/1up?view=theater     https://www.youtube.com/watch?v=eaBUeINW_3s Sega takes fighting 3D     https://archive.org/details/electronic-gaming-monthly-issue-51-october-1993/page/66/mode/1up?view=theater Sega teams up with W Industries     https://segaretro.org/Press_release:_1993-07-01:_W_INDUSTRIES_MAKES_VIRTUAL_REALITY_A_REALITY_FOR_SEGA         https://archive.org/details/Video_Games_The_Ultimate_Gaming_Magazine_Issue_57_Oct_1993/page/n13/mode/1up?view=theater Williams sues Capcom     Play Meter Oct. 1993, pg. 3 7-Eleven's coinop exodus continued     Play Meter Oct. 1993, pg. 3      Nintendo reduces profit outlook     (October 5, 1993, Tuesday). Nintendo. The Times. https://advance.lexis.com/api/document?collection=news&id=urn:contentItem:3T2M-8VY0-00H1-F1G8-00000-00&context=1516831.        https://www.poundsterlinglive.com/bank-of-england-spot/historical-spot-exchange-rates/usd/USD-to-JPY-1993         They expect exports to make up 59% of their sales in the first half of the year and only 42% in the second half.   (October 5, 1993). Nintendo to suffer 1st profit decline in 10 years. Report From Japan. https://advance.lexis.com/api/document?collection=news&id=urn:contentItem:3SKM-Y970-004C-93PW-00000-00&context=1516831. BY YUZO SAEKI, Staff writer. (October 11, 1993).      Nintendo expects profits to fall 26%; HIGH YEN, COMPETITION HURT PERFORMANCE. The Nikkei Weekly (Japan). https://advance.lexis.com/api/document?collection=news&id=urn:contentItem:3S8H-4NH0-000H-H0BX-00000-00&context=1516831.  Garth Alexander and Helen Davidson. (October 10, 1993, Sunday).      Super Mario under threat as Sega closes profits gap. The Sunday Times (London). https://advance.lexis.com/api/document?collection=news&id=urn:contentItem:3T2M-8WK0-00H1-F37F-00000-00&context=1516831.     Garth Alexander and Helen Davidson. (October 10, 1993, Sunday). Super Mario under threat as Sega closes profits gap. The Sunday Times (London). https://advance.lexis.com/api/document?collection=news&id=urn:contentItem:3T2M-8WK0-00H1-F37F-00000-00&context=1516831. Sega calls for truce     By MAT TOOR. (October 21, 1993). Sega calls for truce. Marketing. https://advance.lexis.com/api/document?collection=news&id=urn:contentItem:419K-59R0-00X8-J073-00000-00&context=1516831. Sega beats Nintendo in UK     Dominic Mills. (October 30, 1993, Saturday). Ad of the Week. The Times. https://advance.lexis.com/api/document?collection=news&id=urn:contentItem:3T2M-8YV0-00H1-F3G0-00000-00&context=1516831.   https://youtu.be/X-LGs3AkkXY?si=tuzHTmEqjM2fSFuc Jaguar role out plans revealed     https://archive.org/details/GamePro_Issue_051_October_1993  pg. 16     https://archive.org/details/electronic-gaming-monthly-issue-51-october-1993/page/58/mode/1up?view=theater EGM goes hands-on with 3DO     https://archive.org/details/electronic-gaming-monthly-issue-51-october-1993/page/60/mode/1up?view=theater     Edge 1, pg. 49     Edge 1 pg. 54     Edge1 pg. 58 Nintendo signs up Silicon Graphics     https://archive.org/details/electronic-gaming-monthly-issue-51-october-1993/page/n5/mode/1up?view=theater   https://archive.org/details/electronic-gaming-monthly-issue-51-october-1993/page/70/mode/1up?view=theater CGI vs  clayamation vs. Digitization     https://archive.org/details/play-time-1993-10/page/n9/mode/1up?view=theater        https://archive.org/details/Video_Games_The_Ultimate_Gaming_Magazine_Issue_57_Oct_1993/page/n13/mode/1up?view=theater     https://archive.org/details/play-time-1993-10/page/n13/mode/1up?view=theater        https://archive.org/details/Aktueller_Software_Markt_-_Ausgabe_1993.10/page/n9/mode/1up Nintendo gives away Mario All-Stars     https://archive.org/details/GamePro_Issue_051_October_1993  pg. 168        https://archive.org/details/Video_Games_The_Ultimate_Gaming_Magazine_Issue_57_Oct_1993/page/n13/mode/1up?view=theater Wolfenstein 3D to come to the SNES     https://archive.org/details/electronic-gaming-monthly-issue-51-october-1993/page/220/mode/1up?view=theater Sega does Sports     https://archive.org/details/GamePro_Issue_051_October_1993  pg. 132 EA announces EA Sports Soccer     https://archive.org/details/GamePro_Issue_051_October_1993  pg. 149 Sega introduces the Activator     https://archive.org/details/electronic-gaming-monthly-issue-51-october-1993/page/60/mode/1up?view=theater     https://segaretro.org/Activator Move Over Gameboy, Newton is here     https://archive.org/details/electronic-gaming-monthly-issue-51-october-1993/page/207/mode/1up?view=theater     https://en.wikipedia.org/wiki/Apple_Newton ReelMagic wants to bring FMV to the PC     https://archive.org/details/computer-game-review-and-cd-rom-entertainment-october-1993/page/56/mode/1up?view=theater    Buggy software on the rise     https://archive.org/details/computer-game-review-and-cd-rom-entertainment-october-1993/page/4/mode/1up?view=theater Centergold prepares for stock launch     By PAUL TAYLOR. (October 7, 1993, Thursday). CentreGold valued at Pounds 50m. Financial Times (London,England). https://advance.lexis.com/api/document?collection=news&id=urn:contentItem:3SKR-N110-006F-W48W-00000-00&context=1516831.        GAIL COUNSELL, Business Correspondent. (October 5, 1993, Tuesday). Nintendo losing ground to Sega ; Video games giant blames profit warning on soaring yen. The Independent (London). https://advance.lexis.com/api/document?collection=news&id=urn:contentItem:3T47-8F30-0021-R1WR-00000-00&context=1516831. Apple goes Multimedia     https://archive.org/details/powerplaymagazine-1993-10/page/n32/mode/1up EA plans to ditch floppies     Edge 1, pg. 21 Sam & Max undergoes pizza party testing     https://archive.org/details/Aktueller_Software_Markt_-_Ausgabe_1993.10/page/n9/mode/1up More details of AT&T deal to buy TSN emerge     https://archive.org/details/GamePro_Issue_051_October_1993  pg. 168     https://www.nytimes.com/1993/08/31/business/company-encountering-digital-age-occasional-look-computers-everday-life-keyboard.html Arnie Katz argues for National Electronic Gaming Convention     https://archive.org/details/computer-game-review-and-cd-rom-entertainment-october-1993/page/52/mode/1up?view=theater Ziff Davis buys CGW     https://archive.org/details/computer-game-review-and-cd-rom-entertainment-october-1993/page/56/mode/1up?view=theater Edge 1 premieres     Edge 1      Mario teaches... English?     https://archive.org/details/powerplaymagazine-1993-10/page/n29/mode/2up        https://www.nexgam.de/artikel/buch-super-mario-super-englisch-multi Mortal Kombat goes multimedia     https://archive.org/details/cashbox57unse_6/page/30/mode/1up TSR brings video to board games     https://archive.org/details/Video_Games_The_Ultimate_Gaming_Magazine_Issue_57_Oct_1993/page/n14/mode/1up?view=theater Matt Groening launches Bongo Comics     https://archive.org/details/electronic-gaming-monthly-issue-51-october-1993/page/208/mode/1up?view=theater Recommended Links: The History of How We Play: https://thehistoryofhowweplay.wordpress.com/ Gaming Alexandria: https://www.gamingalexandria.com/wp/ They Create Worlds: https://tcwpodcast.podbean.com/ Digital Antiquarian: https://www.filfre.net/ The Arcade Blogger: https://arcadeblogger.com/ Retro Asylum: http://retroasylum.com/category/all-posts/ Retro Game Squad: http://retrogamesquad.libsyn.com/ Playthrough Podcast: https://playthroughpod.com/ Retromags.com: https://www.retromags.com/ Games That Weren't - https://www.gamesthatwerent.com/ Modo Historia - https://www.youtube.com/c/ModoHistoriaPodcast Sound Effects by Ethan Johnson of History of How We Play. Copyright Karl Kuras

VR glove manufacturer HaptX is releasing their groundbreaking G1 Glove, their first commercial product since they began the quest in 2014 to make the virtual world indistinguishable from real life. HaptX invents and builds wearable technology that simulates touch with unprecedented realism, enabling haptic interaction in virtual reality and robotics.  Joining me to explore the magic of the HaptX G1 glove and the future of human-computer interaction is Linda Jacobson, the Director of Marketing at HaptX.An industry pioneer, Linda helped seed VR technology as the world's first VR evangelist driving early research efforts of VR in healthcare. She is a Co-founding editor of Wired Magazine and author of "CyberArts: Exploring Art + Technology" and "Garage Virtual Reality". She has helped hundreds of clients and has introduced thousands of seniors to virtual reality, social media, digital health and wellness. Learn about HaptX Gloves G1 system, including the HaptX SDK:HaptX.comAWE Nite: Getting Started with Haptics a webinar recorded on Nov. 16, 2023: Designed by developers for developers, we delve into the basics of adding realistic haptics to your virtual scenarios and VR training programs. VR developers from HaptX, Lowe's Innovation Labs, Y-12 National Security Complex, and University of Central Florida will show you how to get up and running with haptics integration in VR using Unreal Engine.Linda's Links from the wayback machine:Star Trek's holodeck in its first major appearance, 1987: Star Trek: The Next Generation, “The Big Goodbye” (Season 1, Episode 11)ABC Primetime Live, 1991, presenting VR and Virtuality location-based entertainment arcade gameTV show “The Computer Chronicles” episode, “Virtual Reality,” 1992 (with Linda Jacobson)“Six Degrees of Freedom: Designers & Engineers Put Virtual Reality to Work,” 1996: documentary written and directed by Linda Jacobson for Silicon Graphics, Inc.CONNECT WITH LINDALinkedInCONNECT WITH SICILIANA sicilianatrevino.com LinkedIn WHAT WE'RE PLAYING IN VRGorilla Tag - holiday update! Asgard's Wrath 2LEGO® Bricktales Liminal - Relax. Unwind. Engage. Explore.PowerWash Simulator VR

Part 1 of 3. My guest for this week's episode is Kittu Kolluri, Founder and Managing Director of Neotribe Ventures, an early- and growth-stage venture capital firm investing in companies that solve hard technical problems and disrupt non-traditional industry sectors. Neotribe is led by a team of serial entrepreneurs with a track record of supporting and advising startups from seed round to IPO.

Avinash is the global Chief Strategy Officer of Croud, a leading full-service marketing Agency. His prior professional experience includes a sixteen-year stint at Google, and roles at Intuit, DirecTV, Silicon Graphics in the US & DHL in Saudi Arabia. Through his newsletter “The Marketing < > Analytics Intersect”, his blog “Occam's Razor,” and his best-selling books “Web Analytics: An Hour A Day” and “Web Analytics 2.0,” Avinash has become recognized as an authoritative voice on how marketers, executives' teams and industry leaders can leverage data to fundamentally reinvent their digital existence. Avinash puts a common-sense framework around the often-frenetic world of web analytics and combines that with the philosophy that investing in talented analysts is the key to long-term success. He passionately advocates customer centricity and leveraging bleeding edge competitive intelligence techniques. Avinash has received rave reviews for bringing his energetic, inspiring, and practical insights to companies like Unilever, Dell, Time Warner, Vanguard, Porsche, and IBM. He has delivered keynotes at a variety of global conferences, including Ad-Tech, Monaco Media Forum, Search Engine Strategies, JMP Innovators' Summit, The Art of Marketing and Web 2.0. Acting on his passion for teaching, Avinash has lectured at major universities such as Stanford University, University of Virginia, University of California - Los Angeles and University of Utah. Among the awards Avinash has received are Statistical Advocate of the Year from the American Statistical Association, Most Influential Industry Contributor from the Web Analytics Association, and Founder's Award from Google.

Jonathan Herbert (b. 1952, New York City) explores the nonverbal relationship between cosmology and consciousness. He creates unique, intuitive formulations of water-based paint using acrylic and urethane media made on the spot, mid-process. He explores the nonverbal nature of creative inspiration via intuition. These works examine the richness of the present moment while simultaneously referring to a concurrent interest in the expression of the past, of his traumatic experiences and resulting emotions. Much of his work has been informed by his extremely abusive childhood and the unsurprisingly drug- and alcohol-ridden years of his life prior to 1986. His experiences as a night shift cab driver in bankrupt New York inspired the years-long body of work, Views from a Yellow Cab. He drove a quarter-million miles over the course of five years. An important and interesting and uncommon view of humankind, as evidenced in the movie Taxi Driver. Herbert received his diploma from the School of the Museum of Fine Arts, Boston in 1977. He continued his studies, via an Independent Study Award from the Museum School, for more than a year in Antwerp, Belgium. He began exhibiting in 1978 in Soho and the East Village and has garnered several solo exhibitions. Many of his group shows have been in New York City, including tagging subways and walls in the East Village of the 1970s. In New York in the mid-eighties, shortly after MacPaint had first been released, Herbert was one of the founders of the Digital Art Movement. During his digital years, Silicon Graphics decorated their entire Seybold booth with his work, flew him to San Francisco and asked him to demonstrate his process during the convention. His digital work has been featured internationally. Herbert for years labored lovingly over the creation of digital medical drawings for pharmaceutical books and journals, continuously expanding his education, which fed his fascination with medicine. His work as a digital artist even led to being interviewed on network TV. Herbert's bibliography begins in December 1982, in the regular Cookie Mueller column “Art and About” in Warhol's Details Magazine. There is also a Jonathan Herbert entry in the Cookie Mueller Encyclopedia. He has appeared in and been reviewed in many publications. Portraits of Herbert are in both Nightline by Peter Donahoe and Taxi: The Social History of the New York City Cab Driver. Herbert's work is in the collection of the Estate of Jean-Michel Basquiat, the Brooklyn Art Library, Pfizer Incorporated, the law firm Kirkland and Ellis, and The Kinsey Institute in Bloomington, Indiana. Herbert currently lives and works in Sarasota, Florida, where, every day, he struggles to live fully in the face of multiple invisible disabilities including lymphoma, PTSD, and cognitive impairment, most of which result from 9/11 survivorship. Across the Universe, Acrylic and urethane on canvas 40 x 60 x 1.5 in Wish, Alchemical acrylic and urethane on canvas 60 x 40 in Shan Shui, acrylic and urethane on canvas 72 x 60 x 1.5 in

Mike recalls memories from living in London and San Francisco in 1998. Topics discussed include: "Claire", Keri, Dek, Brighton, The Moon, throwups at Meanwhile, graffiti over graffiti, UFO, Abstract, Phunkateck, Ed Rush, Optical, Sage, Eklektic, GHB, Grove Park Yard with Egs, Network SouthEast trains, Trans Am show, Camdentown, Psycho, breaking car mirrors, removing fingerprints from spray cans, foiled mission at Uckfield Station, Brighton Yard, window-down on BritRail train, Kill All Cars, high speed car chase, falling through a roof, head wound, returning to San Francisco, brief stay with Claire, Jase, Laura, moving into a room near McAllister and Arguello, Kearny Book and Video, North Beach, cool manager, video arcades, cleaning crew, 4-hour videos for homeless people, The Thursday Guy, poppers (amyl nitrate), growing dislike of porn, Animal, Rosie the tweaker flower salesman, The Swiper, Bigfoot, Sam Flores, Kodik Joe, City Lights Bookstore, Jack Kerouac and Charles Bukowski, Avery, Skullz Press, Lisa, solo graffiti mission, Justo from Detroit, Dame, 3rd Street Yard, painting fast, getting tattoo from Nalla, Dase ATT, trackside with KR, Krink, failed mission in Safeway Tunnels, Noah Hurwitz, Imagination Plantation, Wild Brain, 2-week notice at porn shop, Twist, texture mapping, Hershey's kisses commercials, stop-motion animation, Mac and Silicon Graphics computers, Maya, Fern Gully scenes, Toon Render, Golden Eye 007, painting walls with Dalek, getting tattoo equipment from Nalla, red foil National shader, tattooing left leg, tattooing friends for free, 22nd and Illinois wall, Chris Woodcock, Willy Wonka candy, KFC, Jets, replacing bus shelter posters with Apex, Kaws.

Today we talk with Lucien Harriot, what we consider a "digital renaissnce man", about the ins and outs and ups and downs of all things VXF and AI...and the Rubix Cube! Since 1996, Lucien Harriot has been the driving force behind Mechanism Digital, a New York City-based studio specializing in award-winning visual effects, animation, and next-gen media for marketing and entertainment. As both a creative and technical director, Lucien develops advanced workflows to further content production. Under Lucien's leadership, Mechanism Digital has become an industry trailblazer in CGI and VFX. The studio serves a diverse clientele, from feature films to medical education and corporate communications. Lucien's agile problem-solving and quick decision-making have guided teams of technical artists in both studio and on-set environments. Always forward-thinking, the studio leverages AI in post-production to benefit projects. Lucien is a VFX-supervisor for 2D/3D animation, design, and experiential projects. But he's not just about work; he's a man of diverse experiences. An avid sailor, Lucien enjoys racing and family overnights on Chesapeake Bay or Hudson River. He's a pilot, a DJ, and in the '80s, taught himself to solve the Rubik's Cube. His life has been a tapestry of unique experiences: from summers in nudist communities to living in a Tennessee school bus, and an Amsterdam houseboat. He's led a blind runner through two marathons, volunteered at Ground Zero, and enjoys Burning Man. He's raced classic sports cars, survived high-speed motorcycle crashes, and enjoys longboarding in NYC with his boys and night SCUBA diving with sharks. Raised in SOHO among artists, Lucien maintains a loft lifestyle. He's a published author, experimental photographer, and a concert sound engineer. He mentors disadvantaged entrepreneurs, believe the best way to learn is to teach, enjoys math, puzzles, and singing. He's been arrested, awarded, and does all his own stunts. A member of both Visual Effects Society and Producers Guild of America, his studio has garnered numerous awards, testifying to Lucien's dual strengths in technical mastery & creative innovation. www.mechanmismdigital.com https://www.linkedin.com/in/lucienharriot/

An airhacks.fm conversation with Paul Sandoz (@paulsandoz) about: bbc micro, Archimedes was the start of ARM, the Elite game, writing a painting application, graphics protocol emulation, studying cybernetics, remote control of production factories, developing a VR headset, using Silicon Graphics machines, building a 3D engine, working on Sun Microsystems on the CDE environment, switching to XML technology group at Sun Microsystems, Apache Jelly, SOAP was the past of least resistance, the WS-* specifications, Roy Fielding and Representational State Transfer (REST) architecture style, starting to work on JAX-RS, the Convention over Configuration trade-offs, joining CloudBees to work Kohsuke Kawaguchi "#143 How Hudson and Jenkins happened", starting at Oracle's Java team to work on project Jigsaw and Streams Paul Sandoz on twitter: @paulsandoz

In the first episode of our 3-part Halloween series, Dave Egts, Mulesoft Public Sector Field CTO at Salesforce, details what's scaring the public sector most and how Salesforce is utilizing - and securing - AI to improve customer experience with their Einstein Trust Layer. Additionally, Carolyn and Dave dive into the spooky worlds of brain cell chips, mind-reading AI and more.Key Topics[02:17] Starting the Dave & Gunnar Show[04:14] Dave's Role At Salesforce[05:18] What's Scaring the Public Sector Most?[10:22] Ways Agencies are Attracting Talent[13:56] How Agencies Are Handling Legacy Systems[15:45] What MuleSoft Does & Generative AI's Role[22:44] Salesforce's Einstein Trust Layer[29:21] PoisonGPT[36:07] Brain Organoids & Other Spooky, Ethically Questionable Experiments[42:15] Tech Talk Questions: Halloween Edition Quotable QuotesConsiderations for the Public Sector While Using AI: "As you're going on your AI journey, you've got to be looking at the EULA [End User License Agreement] and making sure that, okay, if I give you data, what are you going to do with it?"On Bias & Disinformation in Generative AI: "There were some previous studies that show that people are more likely to go with the generative AI results if they trust the company and they trust the model. So it's like, 'Oh, it came from Google, so how can that be wrong?' Or 'I'm trusting the brand,' or 'I'm trusting the model.'"About Our GuestDavid Egts is MuleSoft's first-ever Public Sector field CTO. Outside of MuleSoft, David is the founding co-chair of the WashingtonExec CTO Council, where he advises numerous companies on working with the public sector. David has received numerous industry-wide recognitions, including as an FCW Federal 100 winner, a FedScoop 50 Industry Leadership awardee and one of WashingtonExec's Top Cloud Executives to Watch. He has won multiple employee honors from Red Hat, Silicon Graphics and Concurrent Technologies Corporation.Episode LinksDave & Gunnar Show EpisodesEpisode 165- If you can't measure it, you can't manage itEpisode 185- In Your Brain, Nobody Can Hear You ScreamEpisode 227- Meetings and PunishmentEpisodes 248 & 249- Stay tuned to the Dave & Gunnar Show for these episodes to go liveAdditional LinksMinority Report Cuyahoga Valley National ParkFlowers For Algernon

This is episode 624. Read the complete transcription on the Sales Game Changers Podcast website. Purchase Fred Diamond's new best-sellers Love, Hope, Lyme: What Family Members, Partners, and Friends Who Love a Chronic Lyme Survivor Need to Know and Insights for Sales Game Changers now! After a successful career in sales leadership at companies such as Salesforce, Silicon Graphics, Oracle, and DEC, Joe Markwordt is taking his talents to Loyola University in Baltimore teaching sales to college students. Joe also appeared on the podcast in 2018. Listen to that podcast here. JOE'S TIP: "It took me about six years to become what I would consider to be a sales professional, and another five years to earn what I consider to be a PhD in sales. You might say, where do you get a PhD in sales? Well, you get it in the University of Hard Knocks, and that's where tuition payments are the commissions lost on deals that you could have won. Here's my advice. Learn from your mistakes. You mentioned that early on, learning, you're going to lose deals, you're going to blow calls, you're going to mess up. Every time you do that, you're paying a tuition payment into getting that PhD in sales. But you got to learn from it. You've got to incorporate the learnings into the next thing, so the next time instead of spending six months on a deal you're going to lose, you cut the bait after two months, you disqualify, and you move on to the next deal."

In this episode of Web3 Unlocked, Kenzi Wang and Sachi Kamiya speak to Yat Siu, a tech entrepreneur and angel investor who has been working on solutions since the early days of the internet.  Coming from a musician family, Siu was training to be a musician when he wrote software on his Atari ST in the 1980s to read music notations. While his software did not win him any marks with his teachers, he found that others used and appreciated it enough to pay him for it. Soon, Siu would begin working for Atari themselves. He would also go on to work for Silicon Graphics and AT&T. His earliest tech entrepreneurial pursuit was establishing Hong Kong Cybercity (the first free web page and e-mail provider in Asia, later renamed Freenation). His foray into Web3 was, thus, inevitable. In 2014, Siu co-founded Animoca Brands, which now uses blockchain and artificial intelligence to build games and other products. This occurred when Siu and his co-founders understood that NFTs enabled digital ownership of items. In fact, this principle led to Animoca Brands pivoting to blockchain. “It's a belief and conviction that came on a theory we had, which is ownership. So that's why we always talked about digital ownership, which eventually became treated as property rights back in 2018. The principle of ownership creates network effects in which people build and compose on top will become so large that it basically becomes unstoppable." Listen to this episode as Siu discusses how he went from learning music to becoming a tech entrepreneur, the ventures he has worked on and launched, his early days in Web3, his advice for Web3 founders, and so much more. The episode is sponsored by Symbolic Capital and beacon Accelerator. Anchor: https://anchor.fm/web3unlocked  Spotify: https://open.spotify.com/show/0crIhuj7R0huRS3y4ypmuB  Twitter: https://twitter.com/Web3Unlockedxyz    Website: https://www.web3unlocked.xyz/ 

Kim Smith is the founder of LearnerStudio, an equity-focused education investment studio being incubated inside Cambiar Education. She is also the founder and CEO of the Pahara Institute, a national nonprofit that aims to identify, strengthen, and sustain diverse high-potential leaders who are transforming public education. Immediately prior, she was co-founder of Bellwether Education Partners. Earlier in her career she was a founding team member at Teach For America, created an AmeriCorps program serving community-based leaders in youth development, led a trade show start-up, and did a stint in online learning at Silicon Graphics. After completing her MBA at Stanford, she co-founded the NewSchools Venture Fund, a philanthropy focused on catalyzing a bipartisan, cross-sector community of entrepreneurial change agents for public education.Kim was featured in Newsweek's report on the “Women of the 21st Century” as “the kind of woman who will shape America's new century.”Recommended Resources:The Persuaders: At the Front Lines of the Fight for Hearts, Minds, and Democracy by Anand GirardharasThe Righteous Mind: Why Good People are Divided by Politics and Religion by Jonathan Haidt

At the dawn of 3D acceleration a battle was fought over who would control the APIs that would allow programmers to unlock the power of this new type of PC hardware.  Would it be an open source community effort born of Silicon Graphics tech or would the industry juggernaut Microsoft win the day? Our guests today, Servan Keondjian, lead architect of Direct3D and game development veteran Casey Muratori take us into those heady days, the zealous arguments and how it all panned out. Recorded September 2022. Get us on your mobile device: Android:  https://www.google.com/podcasts?feed=aHR0cHM6Ly92aWRlb2dhbWVuZXdzcm9vbXRpbWVtYWNoaW5lLmxpYnN5bi5jb20vcnNz iOS:      https://podcasts.apple.com/de/podcast/video-game-newsroom-time-machine And if you like what we are doing here at the podcast, don't forget to like us on your podcasting app of choice, YouTube, and/or support us on patreon! https://www.patreon.com/VGNRTM Send comments on twitter @videogamenewsr2 Or Instagram https://www.instagram.com/vgnrtm Or Mastodon https://oldbytes.space/@videogamenewsroomtimemachine Or videogamenewsroomtimemachine@gmail.com Links: https://www.linkedin.com/in/servan-keondjian-a6b56/?originalSubdomain=uk https://twitter.com/servankeo http://servanlog.blogspot.com/p/training-history.html https://earthsim.tv/ https://twitter.com/cmuratori youtube.com/mollyrocket,  https://twitch.tv/molly_rocket, https://computerenhance.com https://mollyrocket.com

Azul is the largest provider of commercial support for OpenJDK, supporting more versions of Java than any other vendor, including Oracle.The University of Sydney has recently selected Azul as the institution's sole Java provider, switching from Oracle Java. The announcement takes place amid major changes to Oracle Java pricing and a rapid increase in the adoption of OpenJDK-based Java runtimes. By some estimates, usage of Oracle Java has fallen from roughly 75 per cent in 2020 to 34 per cent in 2022.We speak with Scott Sellers, President, CEO and Co-Founder of Azul, visitng Australia from the USA to meet with customers and partners.With more than 30 years of successful leadership in building high technology companies and delivering advanced products to market, Scott provides the overall strategic leadership and visionary direction for Azul Systems. Scott has a consistent proven track record of vision, leadership, and success in enterprise, consumer and scientific markets. Prior to co-founding Azul Systems, Scott founded 3dfx Interactive, a graphics processor company that pioneered the 3D graphics market for personal computers and game consoles. Scott served at 3dfx as Vice President of Engineering, CTO and as a member of the board of directors and delivered 7 award-winning products and developed 14 different graphics processors. After a successful initial public offering, 3dfx was later acquired by NVIDIA Corporation. Prior to 3dfx, Scott was a CPU systems architect at Pellucid, later acquired by MediaVision. Before Pellucid, Scott was a member of the technical staff at Silicon Graphics where he designed high-performance workstations. Scott graduated from Princeton University with a bachelor of science, earning magna cum laude and Phi Beta Kappa honors. Scott has been granted 8 patents in high performance graphics and computing and is a regularly invited keynote speaker at industry conferences.Read more - https://chiefit.me/university-of-sydney-boards-the-azul-train/#azul #java #mysecuritytv

Our guest for Episode 090 of Underserved is Joe Frascati. Joe moved several times as a teen, honing his skills in quickly sizing up new social situations and identifying the players and roles. This skill served him well in his career, from a retail startup to the legendary Silicon Graphics and beyond. We also talk about Stevedoring, electric buses and their charging demands, and VTOL as the flying car that might actually come to be.   CIO Marathon: https://www.ciseeducationfund.com/marathon Merritt College Cybersecurity Program: https://www.merrittsecurity.com/ Predictive Index: https://www.predictiveindex.com/ The StrataFusion Group: https://www.stratafusion.com/ And for your comedic pleasure - Coleco Football! https://youtu.be/FBLZY-cjJUs

Welcome to Dev Game Club, where this week we begin a new series on 1997's Rare classic, GoldenEye 007. We set the game in its time before getting down to brass tacks, including comparing the experience to the film. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary. Sections played: First full mission (three levels) Issues covered: the license, a bit about the film and the film series, 1997 in games, the flourishing of the first person shooter, late in a console cycle, disparity between PC FPSes and console FPSes, Rare with a lot of games and a lot of further game studios, missing the original controller, remapping shenanigans, threading the needle on a film adaptation, filling in gaps in the license, choosing your exciting set piece, wide level design, the triple cut, Hong Kong cinema, cinematic choices, contrasting with later cinematic games, how many mechanics will you incorporate, chasing this game, choosing different presentation, showing death the character death, an era of accessibility needs recognition, at last listening to our hate mail. Games, people, and influences mentioned or discussed: Nintendo, Fatal Frame, PlayStation, Pierce Brosnan, Nintendo 64, Sean Bean, Famke Janssen, Alan Cumming, Judi Dench, Desmond Llewelyn, Ralph Fiennes, Daniel Craig, Skyfall, Diablo, Castlevania: Symphony of the Night, Fallout, Quake, SW: Jedi Knight: DF2, Blood, Outlaws, Turok, Shadow Warrior, Hexen II, Raven Software, 3D Realms, GT Interactive, Duke Nuke'em, Postal, Curse of Monkey Island, Age of Empires, The Last Express, Final Fantasy VII, Colony Wars, Wing Commander: Prophecy, Riven, MYST, XvT, Interstate '76, Mario Kart 64, OddWorld, Grand Theft Auto, Gran Turismo, Diddy Kong Racing, The Stamp brothers, NES, Slalom, Wizards and Warriors, Battletoads, Killer Instinct, Perfect Dark, Microsoft, Viva Pinata, Banjo Kazooie (series), Donkey Kong Country, Silicon Graphics, Timesplitters, Free Radical, John Romero, Majora's Mask, Minish Cap, Metroid Fusion, The Fugitive, Harrison Ford, Mission: Impossible, John Woo, Hard Target, Broken Arrow, Face Off, Metal Gear Solid, Conker's Bad Fur Day, Alpha Protocol, Telltale Games, IO Interactive, Machine Games, Colin "The Shots," Devil May Cry, Dark Souls, Celeste, Luke Harris, Tetris 64, Starfighter/JSF, 343 Industries, Kingdom Hearts (series), Republic Commando, Kirk Hamilton, Aaron Evers, Mark Garcia. Next time: More GoldenEye 007 Twitch: brettdouville or timlongojr, instagram:timlongojr, Twitter: @timlongojr and @devgameclub DevGameClub@gmail.com

The Hard Thing About Hard Things

Welcome to Episode 145 of Autism Parenting Secrets. Returning to the show is Peter Sullivan - founder and CEO of Clear Light Ventures, Inc.  For nearly two decades he's been a change agent to improve environmental health.  And in addition to promoting awareness, he's an environmental health funder who focuses on toxins and wireless safety.  We focus on how technology contributes to dysregulation and what you can do about it.  The Secret This Week is…TECH Is The Great DYSREGULATORYou'll Discover:The Root Cause of So Many Issues (6:04)Why It's More Than a Problem, It's An Addiction (12:26)The Surprising Thing EVERYTHING Relates To (16:01)Things To Do When You're Ramped Up (18:21)The Greatest Regulators (28:37)The Issue With Odors and Lights (31:21)Arguably The Most Toxic Dysregulator (34:49)What You Want To Measure Inside Your Home (36:31)About Our Guest:Peter Sullivan is the founder and CEO of Clear Light Ventures, Inc., as well as an environmental health funder who focuses on toxins and wireless safety. He has spent the last 17 years focusing on environmental health. Peter's work on detoxification and EMF (electromagnetic fields) has been featured in the book Toxin Toxout, Mother Jones magazine, Paleo Magazine, and CNN's Morgan Spurlock: Inside Man. He is an executive producer of the documentary “Generation Zapped”, about the health effects of wireless, and co-executive producer of the film “The Devil We Know” about Teflon pollution. Peter serves as a board advisor to Pure Earth (pollution.org), and the International Institute for Building-Biology & Ecology. Previously, he worked as a software designer, making software easier to use at Netflix, Inc., Interwoven, Inc., Excite@Home, and Silicon Graphics. He also served as an Executive Officer and pilot in the United States Navy. He has a B.A. in psychology from the University of Detroit and an M.S. in computer science from Stanford University.References in The Episode:APS Episode 22 You CAN Protect Your Child From EMFsWireless and EMF Reduction for AutismGeneration Zapped DVDThe Devil We Know DVDThe Out of Sync Child by Carol KranowitzAutism Parenting Secrets Episode 26 The Body Is Electric And Dirty Electricity HarmsAutism Parenting Secrets Episode 57 Dirty Electricity DEMANDS AttentionReset Your Child's Brain by Victoria DunkleyStatus of the Neuroendocrine System in Animals Chronically Exposed to Electromagnetic Fields of 5G Mobile Network Base StationsVielight Red Light Therapy (in nose and head)Sauna Space Photon Near Infrared LightEmotional Freedom Technique - TappingU.S. BiomagnetsFrequency Specific Microcurrent for PainDr. Tenant's ProtocolTuning The Human Biofield by Eileen Day McKusickPhilip Stein Sleep BandsShielded Healing Lighting GuideStink movieBreath by James NestorFlow by Mihaly CsikszentmihalyiBody Keeps the Score by Bessel van der Kolk M.D.IQ Air - Air Visual Air Quality MeterAdditional Resources:Take The Quiz: What's YOUR Top Autism Parenting Blindspot?To learn more about Cass & Len, visit us at www.autismparentingsecrets.comBe sure to follow Cass & Len on InstagramIf you enjoyed this episode, share it with your friends.

About BrianBrian leads the Google Cloud Product and Industry Marketing team. This team is focused on accelerating the growth of Google Cloud by establishing thought leadership, increasing demand and usage, enabling their sales teams and partners to tell their product stories with excellence, and helping their customers be the best advocates for them.Before joining Google, Brian spent over 25 years in product marketing or engineering in different forms. He started his career at Microsoft and had a very non-traditional path for 20 years. Brian worked in every product division except for cloud. He did marketing, product management, and engineering roles. And, early on, he was the first speech writer for Steve Ballmer and worked on Bill Gates' speeches too. His last role was building up the Microsoft Surface business from scratch as VP of the hardware businesses. After Microsoft, Brian spent a year as CEO at a hardware startup called Doppler Labs, where they made a run at transforming hearing, and then spent two years as VP at Amazon Web Services leading product marketing, developer advocacy, and a bunch more marketing teams.Brian has three kids still at home, Barty, Noli, and Alder, who are all named after trees in different ways. His wife Edie and him met right at the beginning of their first year at Yale University, where Brian studied math, econ, and philosophy and was the captain of the Swim and Dive team his senior year. Edie has a PhD in forestry and runs a sustainability and forestry consulting firm she started, that is aptly named “Three Trees Consulting”. As a family they love the outdoors, tennis, running, and adventures in Brian's 1986 Volkswagen Van, which is his first and only car, that he can't bring himself to get rid of.Links Referenced: Google Cloud: https://cloud.google.com @isforat: https://twitter.com/IsForAt LinkedIn: https://www.linkedin.com/in/brhall/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is brought to us by our friends at Pinecone. They believe that all anyone really wants is to be understood, and that includes your users. AI models combined with the Pinecone vector database let your applications understand and act on what your users want… without making them spell it out. Make your search application find results by meaning instead of just keywords, your personalization system make picks based on relevance instead of just tags, and your security applications match threats by resemblance instead of just regular expressions. Pinecone provides the cloud infrastructure that makes this easy, fast, and scalable. Thanks to my friends at Pinecone for sponsoring this episode. Visit Pinecone.io to understand more.Corey: This episode is brought to you in part by our friends at Veeam. Do you care about backups? Of course you don't. Nobody cares about backups. Stop lying to yourselves! You care about restores, usually right after you didn't care enough about backups. If you're tired of the vulnerabilities, costs, and slow recoveries when using snapshots to restore your data, assuming you even have them at all living in AWS-land, there is an alternative for you. Check out Veeam, that's V-E-E-A-M for secure, zero-fuss AWS backup that won't leave you high and dry when it's time to restore. Stop taking chances with your data. Talk to Veeam. My thanks to them for sponsoring this ridiculous podcast.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. This episode is brought to us by our friends at Google Cloud and, as a part of that, they have given me someone to, basically, harass for the next half hour. Brian Hall is the VP of Product Marketing over at Google Cloud. Brian, welcome back.Brian: Hello, Corey. It's good to be here, and technically, we've given you time to harass me by speaking with me because you never don't have the time to harass me on Twitter and other places, and you're very good at it.Corey: Well, thank you. Again, we first met back when you were doing, effectively, the same role over at AWS. And before that, you spent only 20 years or so at Microsoft. So, you've now worked at all three of the large hyperscale cloud providers. You probably have some interesting perspectives on how the industry has evolved over that time. So, at the time of this recording, it is after Google Next and before re:Invent. There was also a Microsoft event there that I didn't pay much attention to. Where are we as a culture, as an industry, when it comes to cloud?Brian: Well, I'll start with it is amazing how early days it still is. I don't want to be put on my former Amazon cap too much, and I think it'd be pushing it a little bit to say it's complete and total day one with the cloud. But there's no question that there is a ton of evolution still to come. I mean, if you look at it, you can kind of break it into three eras so far. And roll with me here, and happy to take any dissent from you.But there was kind of a first era that was very much led by Amazon. We can call it the VM era or the component era, but being able to get compute on-demand, get nearly unlimited or actually unlimited storage with S3 was just remarkable. And it happened pretty quickly that startups, new tech companies, had to—like, it would be just wild to not start with AWS and actually start ordering servers and all that kind of stuff. And so, I look at that as kind of the first phase. And it was remarkable how long Amazon had a run really as the only player there. And maybe eight years ago—six years ago—we could argue on timeframes, things shifted a little bit because the enterprises, the big companies, and the governments finally realized, “Holy crow. This thing has gotten far enough that it's not just for these startups.”Corey: Yeah. There was a real change. There was an eye-opening moment there where it isn't just, “I want to go and sell things online.” It's, “And I also want to be a bank. Can we do that with you?” And, “Huh.”Brian: My SAP—like I don't know big that darn thing is going to get. Could I put it in your cloud? And, “Oh, by the way, CapEx forecasting stinks. Can you get me out of that?” And so, it became like the traditional IT infrastructure. All of the sudden, the IT guys showed up at the party, which I know is—it sounds fun to me, but that doesn't sound like the best addition to a party for many people. And so essentially, old-school IT infrastructure finally came to the cloud and Microsoft couldn't miss that happening when it did. But it was a major boon for AWS just because of the position that they had already.Corey: And even Google as well. All three of you now are pivoting in a lot of the messaging to talk to the big E enterprises out there. And I've noticed for the last few years, and I'm not entirely alone. When I go to re:Invent, and I look at announcements they're making, sure they have for the serverless stuff and how to run websites and EC2 nonsense. And then they're talking about IOT things and other things that just seem very oriented on a persona I don't understand. Everyone's doing stuff with mainframes now for example. And it feels like, “Oh, those of us who came here for the web services like it says on the name of the company aren't really feeling like it's for us anymore.” It's the problem of trying to be for everyone and pivoting to where the money is going, but Google's done this at least as much as anyone has in recent years. Are those of us who don't have corporate IT-like problems no longer the target market for folks or what's changed?Brian: It's still the target market, so like, you take the corporate IT, they're obviously still moving to the cloud. And there's a ton of opportunity. Just take existing IT spending and see a number over $1 trillion per year, and if you take the run rates of Microsoft, Amazon, Google Cloud, it's certainly over $100 billion, but that means it's still less than ten percent of what is existing IT spending. There are many people that think that existing IT spend number is significantly higher than that. But to your point on what's changing, there's actually a third wave that's happening.So, if the first wave was you start a company. You're a tech company, of course, you start it on AWS or on the Cloud. Second wave is all the IT people, IT departments, the central organizations that run technology for all the people that are not technology people come to the cloud. This third wave is everybody has to become a technology person. If you're a business leader, like you're at a fast-food restaurant and you're responsible for the franchisee relations, before, like, you needed to get an EDI system running or something, and so you told your IT department to figure out.Now, you have to actually think about what apps do we want to provide to our customers. How do I get the right data to my franchisees so that they can make business decisions? How can I automate all that? And you know, whereas before I was a guy wearing a suit or a gal wearing a suit who didn't need to know technology, I now have to. And that's what's changing the most. And it's why the Target Addressable Market—or the TAM as business folk sometimes say—it's really hard to estimate looking forward if every business is really needing to become a technology business in many ways. And it didn't dawn on me, honestly, and you can give me all the ribbing that I probably deserve for this—but it didn't really dawn on me until I came to Google and kept hearing the transformation word, “Digital transformation, digital transformation,” and honestly, having been in software for so long, I didn't really know what digital transformation meant until I started seeing all of these folks, like every company have to become a tech company effectively.Corey: Yeah. And it turns out there aren't enough technologists to go around, so it's very challenging to wind up getting the expertise in-house. It's natural to start looking at, “Well, how do we effectively outsource this?” And well, you can absolutely have a compression algorithm for experience. It's called, “Buying products and services and hiring people who have that experience already baked in either to the product or they show up knowing how to do something because they've done this before.”Brian: That's right. The thing I think we have to—for those of us that come from the technology side, this transformation is scary for the people who all of the sudden have to get tech and be like—Corey, if you or I—actually, you're very artistic, so maybe this wouldn't do it for you—but if I were told, “Hey, Brian, for your livelihood, you now need to incorporate painting,” like…Corey: [laugh]. I can't even write legibly let alone draw or paint. That is not my skill set. [laugh].Brian: I'd be like, “Wait, what? I'm not good at painting. I've never been a painting person, like I'm not creative.” “Okay. Great. Then we're going to fire you, or we're going to bring someone in who can.” Like, that'd be scary. And so, having more services, more people that can help as every company goes through a transition like that—and it's interesting, it's why during Covid, the cloud did really well, and some people kind of said, “Well, it's because they—people didn't want to send their people into their data centers.” No. That wasn't it. It was really because it just forced the change to digital. Like the person to, maybe, batter the analogy a little bit—the person who was previously responsible for all of the physical banks, which are—a bank has, you know, that are retail locations—the branches—they have those in order to service the retail customers.Corey: Yeah.Brian: That person, all of the sudden, had to figure out, “How do I do all that service via phone, via agents, via an app, via our website.” And that person, that entire organization, was forced digital in many ways. And that certainly had a lot of impact on the cloud, too.Corey: Yeah. I think that some wit observed a few years back that Covid has had more impact on your digital transformation than your last ten CIOs combined.Brian: Yeah.Corey: And—yeah, suddenly, you're forcing people into a position where there really is no other safe option. And some of that has unwound but not a lot of it. There's still seem to be those same structures and ability to do things from remote locations then there were before 2020.Brian: Yeah. Since you asked, kind of, where we are in the industry, to bring all of that to an endpoint, now what this means is people are looking for cloud providers, not just to have the primitives, not just to have the IT that they—their central IT needed, but they need people who can help them build the things that will help their business transform. It makes it a fun, new stage, new era, a transformation era for companies like Google to be able to say, “Hey, here's how we build things. Here's what we've learned over a period of time. Here's what we've most importantly learned from other customers, and we want to help be your strategic partner in that transformation.” And like I said, it'd be almost impossible to estimate what the TAM is for that. The real question is how quickly can we help customers and innovate in our Cloud solutions in order to make more of the stuff more powerful and faster to help people build.Corey: I want to say as well that—to be clear—you folks can buy my attention but not my opinion. I will not say things if I do not believe them. That's the way the world works here. But every time I use Google Cloud for something, I am taken aback yet again by the developer experience, how polished it is. And increasingly lately, it's not just that you're offering those low-lying primitives that composed together to build things higher up the stack, you're offering those things as well across a wide variety of different tooling options. And they just tend to all make sense and solve a need rather than requiring me to build it together myself from popsicle sticks.And I can't shake the feeling that that's where the industry is going. I'm going to want someone to sell me an app to do expense reports. I'm not going to want—well, I want a database and a front-end system, and how I wind up storing all the assets on the backend. No. I just want someone to give me something that solves that problem for me. That's what customers across the board are looking for as best I can see.Brian: Well, it certainly expands the number of customers that you can serve. I'll give you an example. We have an AI agent product called Call Center AI which allows you to either build a complete new call center solution, or more often it augments an existing call center platform. And we could sell that on an API call basis or a number of agent seats basis or anything like that. But that's not actually how call center leaders want to buy. Imagine we come in and say, “This many API calls or $4 per seat or per month,” or something like that. There's a whole bunch of work for that call center leader to go figure out, “Well, do I want to do this? Do I not? How should I evaluate it versus others?” It's quite complex. Whereas, if we come in and say, “Hey, we have a deal for you. We will guarantee higher customer satisfaction. We will guarantee higher agent retention. And we will save you money. And we will only charge you some percentage of the amount of money that you're saved.”Corey: It's a compelling pitch.Brian: Which is an easier one for a business decision-maker to decide to take?Corey: It's no contest. I will say it's a little odd that—one thing—since you brought it up, one thing that struck me as a bit strange about Contact Center AI, compared to most of the services I would consider to be Google Cloud, instead of, “Click here to get started,” it's, “Click here to get a demo. Reach out to contact us.” It feels—Brian: Yeah.Corey: —very much like the deals for these things are going to get signed on a golf course.Brian: [laugh]. They—I don't know about signed on a golf course. I do know that there is implementation work that needs to be done in order to build the models because it's the model for the AI, figuring out how your particular customers are served in your particular context that takes the work. And we need to bring in a partner or bring in our expertise to help build that out. But it sounds to me like you're looking to go golfing since you've looked into this situation.Corey: Just like painting, I'm no good at golfing either.Brian: [laugh].Corey: Honestly, it's—it just doesn't have the—the appeal isn't there for me for whatever reason. I smile; I nod; I tend to assume that, “Yeah, that's okay. I'll leave some areas for other people to go exploring in.”Brian: I see. I see.Corey: So, two weeks before Google Cloud Next occurred, you folks wound up canceling Stadia, which had been rumored for a while. People had been predicting it since it was first announced because, “Just wait. They're going to Google Reader it.” And yeah, it was consumer-side, and I do understand that that was not Cloud. But it did raise the specter of—for people to start talking once again about, “Oh, well, Google doesn't have any ability to focus on things long-term. They're going to turn off Cloud soon, too. So, we shouldn't be using it at all.” I do not agree with that assessment.But I want to get your take on it because I do have some challenges with the way that your products and services go to market in some ways. But I don't have the concern that you're going to turn it all off and decide, “Yeah, that was a fun experiment. We're done.” Not with Cloud, not at this point.Brian: Yeah. So, I'd start with at Google Cloud, it is our job to be a trusted enterprise platform. And I can't speak to before I was here. I can't speak to before Thomas Kurian, who's our CEO, was here before. But I can say that we are very, very focused on that. And deprecating products in a surprising way or in a way that doesn't take into account what customers are on it, how can we help those customers is certainly not going to help us do that. And so, we don't do that anymore.Stadia you brought up, and I wasn't part of starting Stadia. I wasn't part of ending Stadia. I honestly don't know anything about Stadia that any average tech-head might not know. But it is a different part of Google. And just like Amazon has deprecated plenty of services and devices and other things in their consumer world—and Microsoft has certainly deprecated many, many, many consumer and other products—like, that's a different model. And I won't say whether it's good, bad, or righteous, or not.But I can say at Google Cloud, we're doing a really good job right now. Can we get better? Of course. Always. We can get better at communicating, engaging customers in advance. But we now have a clean deprecation policy with a set of enterprise APIs that we commit to for stated periods of time. We also—like people should take a look. We're doing ten-year deals with companies like Deutsche Bank. And it's a sign that Google is here to last and Google Cloud in particular. It's also at a market level, just worth recognizing.We are a $27 billion run rate business now. And you earn trust in drips. You lose it in buckets. And we're—we recognize that we need to just keep every single day earning trust. And it's because we've been able to do that—it's part of the reason that we've gotten as large and as successful as we have—and when you get large and successful, you also tend to invest more and make it even more clear that we're going to continue on that path. And so, I'm glad that the market is seeing that we are enterprise-ready and can be trusted much, much more. But we're going to keep earning every single day.Corey: Yeah. I think it's pretty fair to say that you have definitely gotten yourselves into a place where you've done the things that I would've done if I wanted to shore up trust that the platform was not going to go away. Because these ten-year deals are with the kinds of companies that, shall we say, do not embark on signing contracts lightly. They very clearly, have asked you the difficult, pointed questions that I'm basically asking you now as cheap shots. And they ask it in very serious ways through multiple layers of attorneys. And if the answers aren't the right answers, they don't sign the contract. That is pretty clearly how the world works.The fact that companies are willing to move things like core trading systems over to you on a ten-year time horizon, tells me that I can observe whatever I want from the outside, but they have actual existential risk questions tied to what they're doing. And they are in some ways betting their future on your folks. You clearly know what those right answers are and how to articulate them. I think that's the side of things that the world does not get to see or think about very much. Because it is easy to point at all the consumer failings and the hundreds of messaging products that you continually replenish just in order to kill.Brian: [laugh].Corey: It's—like, what is it? The tree of liberty must be watered periodically from time to time, but the blood of patriots? Yeah. The logo of Google must be watered by the blood of canceled messaging products.Brian: Oh, come on. [laugh].Corey: Yeah. I'm going to be really scared if there's an actual, like, Pub/Sub service. I don't know. That counts as messaging, sort of. I don't know.Brian: [laugh]. Well, thank you. Thank you for the recognition of how far we've come in our trust from enterprises and trust from customers.Corey: I think it's the right path. There's also reputational issues, too. Because in the absence of new data, people don't tend to change their opinion on things very easily. And okay, there was a thing I was using. It got turned off. There was a big kerfuffle. That sticks in people's minds. But I've never seen an article about a Google service saying, “Oh, yeah. It hasn't been turned off or materially changed. In fact, it's gotten better with time. And it's just there working reliably.” You're either invisible, or you're getting yelled at.It feels like it's a microcosm of my early career stage of being a systems administrator. I'm either invisible or the mail system's broke, and everyone wants my head. I don't know what the right answer is—Brian: That was about right to me.Corey: —in this thing. Yeah. I don't know what the right answer on these things is, but you're definitely getting it right. I think the enterprise API endeavors that you've gone through over the past year or two are not broadly known. And frankly, you've definitely are ex-AWS because enterprise APIs is a terrible name for what these things are.Brian: [laugh].Corey: I'll let you explain it. Go ahead. And bonus points if you can do it without sounding like a press release. Take it away.Brian: There are a set of APIs that developers and companies should be able to know are going to be supported for the period of time that they need in order to run their applications and truly bet on them. And that's what we've done.Corey: Yeah. It's effectively a commitment that there will not be meaningful deprecations or changes to the API that are breaking changes without significant notice periods.Brian: Correct.Corey: And to be clear, that is exactly what all of the cloud providers have in their enterprise contracts. They're always notice periods around those things. There are always, at least, certain amounts of time and significant breach penalties in the event that, “Yeah, today, I decided that we were just not going to spin up VMs in that same way as we always have before. Sorry. Sucks to be you.” I don't see that happening on the Google Cloud side of the world very often, not like it once did. And again, we do want to talk about reputations.There are at least four services that I'm aware of that AWS has outright deprecated. One, Sumerian has said we're sunsetting the service in public. But on the other end of the spectrum, RDS on VMWare has been completely memory-holed. There's a blog post or two but nothing else remains in any of the AWS stuff, I'm sure, because that's an, “Enterprise-y” service, they wound up having one on one conversations with customers or there would have been a hue and cry. But every cloud provider does, in the fullness of time, turn some things off as they learn from their customers.Brian: Hmm. I hadn't heard anything about AWS Infinidash for a while either.Corey: No, no. It seems to be one of those great services that we made up on the internet one day for fun. And I love that just from a product marketing perspective. I mean, you know way more about that field than I do given that it's your job, and I'm just sitting here in this cheap seats throwing peanuts at you. But I love the idea of customers just come up and make up a product one day in your space and then the storytelling that immediately happens thereafter. Most companies would kill for something like that just because you would expect on some level to learn so much about how your reputation actually works. When there's a platonic ideal of a service that isn't bothered by pesky things like, “It has to exist,” what do people say about it? And how does that work?And I'm sort of surprised there wasn't more engagement from Amazon on that. It always seems like they're scared to say anything. Which brings me to a marketing question I have for you. You and Amazing have similar challenges—you being Google in this context, not you personally—in that your customers take themselves deadly seriously. And as a result, you have to take yourselves with at least that same level of seriousness. You can't go on Twitter and be the Wendy's Twitter account when you're dealing with enterprise buyers of cloud platforms. I'm kind of amazed, and I'd love to know. How can you manage to say anything at all? Because it just seems like you are so constrained, and there's no possible thing you can say that someone won't take issue with. And yes, some of the time, that someone is me.Brian: Well, let's start with going back to Infinidash a little bit. Yes, you identified one interesting thing about that episode, if I can call it an episode. The thing that I tell you though that didn't surprise me is it shows how much of cloud is actually learned from other people, not from the cloud provider itself. I—you're going to be going to re:Invent. You were at Google Cloud Next. Best thing about the industry conferences is not what the provider does. It's the other people that are there that you learn from. The folks that have done something that you've been trying to do and couldn't figure out how to do, and then they explained it to you, just the relationships that you get that help you understand what's going on in this industry that's changing so fast and has so much going on.And so,   And so, that part didn't surprise me. And that gets a little bit to the second part of your—that we're talking about. “How do you say anything?” As long as you're helping a customer say it. As long as you're helping someone who has been a fan of a product and has done interesting things with it say it, that's how you communicate for the most part, putting a megaphone in front of the people who already understand what's going on and helping their voice be heard, which is a lot more fun, honestly, than creating TV ads and banner ads and all of the stuff that a lot of consumer and traditional companies. We get to celebrate our customers and our creators much, much more.Corey: This episode is sponsored in part by our friends at Uptycs, because they believe that many of you are looking to bolster your security posture with CNAPP and XDR solutions. They offer both cloud and endpoint security in a single UI and data model. Listeners can get Uptycs for up to 1,000 assets through the end of 2023 (that is next year) for $1. But this offer is only available for a limited time on UptycsSecretMenu.com. That's U-P-T-Y-C-S Secret Menu dot com.Corey: I think that it's not super well understood by a lot of folks out there that the official documentation that any cloud provider puts out there is kind of a last resort. Or I'm looking for the specific flag to a specific parameter of a specific command. Great. Sure. But what I really want to do whenever I'm googling how to do something—and yes, that—we're going to be googling—welcome. You've successfully owned that space to the point where it's become common parlance. Good work is I want to see what other people had said. I want to find blog posts, ideally recent ones, talking about how to do the thing that I'm trying to do. If I'm trying to do something relatively not that hard or not that uncommon, if I spin up three web servers behind a load-balancer, and I can't find any community references on how to do that thing, either I'm trying to do something absolutely bizarre and I should re-think it, or there is no community/customer base for the product talking about how to do things with it.And I have noticed a borderline Cambrian explosion over the last few years of the Google Cloud community. I'm seeing folks who do not work at Google, and also who have never worked at Google, and sometimes still think they work at Google in some cases. It's not those folks. It is people who are just building things as a customer. And they, in turn, become very passionate advocates for the platform. And they start creating content on these things.Brian: Yeah. We've been blessed to have, not only, the customer base grow, but essentially the passion among that customer base, and we've certainly tried to help building community and catalyzing the community, but it's been fun to watch how our customers' success turns into our success which turns into customer success. And it's interesting, in particular, to see too how much of that passion comes from people seeing that there is another way to do things.It's clear that many people in our industry knew cloud through the lens of Amazon, knew tech in general through the lenses of Microsoft and Oracle and a lot of other companies. And Google, which we try and respect specifically what people are trying to accomplish and how they know how to do it, we also many ways have taken a more opinionated approach, if you will, to say, “Hey, here's how this could be done in a different way.” And when people find something that's unexpectedly different and also delightful, it's more likely that they're going to be strong advocates and share that passion with the world.Corey: It's a virtuous cycle that leads to the continued growth and success of a platform. Something I've been wondering about in the broader sense, is what happens after this? Because if, let's say for the sake of argument, that one of the major cloud providers decided, “Okay. You know, we're going to turn this stuff off. We've decided we don't really want to be in the cloud business.” It turns out that high-margin businesses that wind up turning into cash monsters as soon as you stop investing heavily in growing them, just kind of throw off so much that, “We don't know what to do with. And we're running out of spaces to store it. So, we're getting out of it.” I don't know how that would even be possible at some point. Because given the amount of time and energy some customers take to migrate in, it would be a decade-long project for them to migrate back out again.So, it feels on some level like on the scale of a human lifetime, that we will be seeing the large public cloud providers, in more or less their current form, for the rest of our lives. Is that hopelessly naïve? Am I missing—am I overestimating how little change happens in the sweep of a human lifetime in technology?Brian: Well, I've been in the tech industry for 27 years now. And I've just seen a continual moving up the stack. Where, you know, there are fundamental changes. I think the PC becoming widespread, fundamental change; mobile, certainly becoming primary computing experience—what I know you call a toilet computer, I call my mobile; that's certainly been a change. Cloud has certainly been a change. And so, there are step functions for sure. But in general, what has been happening is things just keep moving up the stack. And as things move up the stack, there are companies that evolve and learn to do that and provide more value and more value to new folks. Like I talked about how businesspeople are leaders in technology now in a way that they never were before. And you need to give them the value in a way that they can understand it, and they can consume it, and they can trust it. And it's going to continue to move in that direction.And so, what happens then as things move up the stack, the abstractions start happening. And so, there are companies that were just major players in the ‘90s, whether it's Novell or Sun Microsystems or—I was actually getting a tour of the Sunnyvale/Mountain View Google Campuses yesterday. And the tour guide said, “This used to be the site of a company that was called Silicon Graphics. They did something around, like, making things for Avatar.” I felt a little aged at that point.But my point is, there are these companies that were amazing in their time. They didn't move up the stack in a way that met the net set of needs. And it's not like that crater the industry or anything, it's just people were able to move off of it and move up. And I do think that's what we'll see happening.Corey: In some cases, it seems to slip below the waterline and become, effectively, plumbing, where everyone uses it, but no one knows who they are or what they do. The Tier 1 backbone providers these days tend to be in that bucket. Sure, some of them have other businesses, like Verizon. People know who Verizon is, but they're one of the major Tier 1 carriers in the United States just of the internet backbone.Brian: That's right. And that doesn't mean it's not still a great business.Corey: Yeah.Brian: It just means it's not front of mind for maybe the problems you're trying to solve or the opportunities we're trying to capture at that point in time.Corey: So, my last question for you goes circling back to Google Cloud Next. You folks announced an awful lot of things. And most of them, from my perspective, were actually pretty decent. What do you think is the most impactful announcement that you made that the industry largely overlooked?Brian: Most impactful that the industry—well, overlooked might be the wrong way to put this. But there's this really interesting thing happening in the cloud world right now where whereas before companies, kind of, chose their primary cloud writ large, today because multi-cloud is actually happening in the vast majority of companies have things in multiple places, people make—are making also the decision of, “What is going to be my strategic data provider?” And I don't mean data in the sense of the actual data and meta-data and the like, but my data cloud.Corey: Mm-hmm.Brian: How do I choose my data cloud specifically? And there's been this amazing profusion of new data companies that do better ETL or ELT, better data cleaning, better packaging for AI, new techniques for scaling up/scaling down at cost. A lot of really interesting stuff happening in the dataspace. But it's also created almost more silos. And so, the most important announcement that we made probably didn't seem like a really big announcement to a lot of people, but it really was about how we're connecting together more of our data cloud with BigQuery, with unstructured and structured data support, with support for data lakes, including new formats, including Iceberg and Delta and Hudi to come how—Looker is increasingly working with BigQuery in order to make it, so that if you put data into Google Cloud, you not only have these super first-class services that you can use, ranging from databases like Spanner to BigQuery to Looker to AI services, like Vertex AI, but it's also now supporting all these different formats so you can bring third-party applications into that one place. And so, at the big cloud events, it's a new service that is the biggest deal. For us, the biggest deal is how this data cloud is coming together in an open way to let you use the tool that you want to use, whether it's from Google or a third party, all by betting on Google's data cloud.Corey: I'm really impressed by how Google is rather clearly thinking about this from the perspective of the data has to be accessible by a bunch of different things, even though it may take wildly different forms. It is making the data more fluid in that it can go to where the customer needs it to be rather than expecting the customer to come to it where it lives. That, I think, is a trend that we have not seen before in this iteration of the tech industry.Brian: I think you got that—you picked that up very well. And to some degree, if you step back and look at it, it maybe shouldn't be that surprising that Google is adept at that. When you think of what Google search is, how YouTube is essentially another search engine producing videos that deliver on what you're asking for, how information is used with Google Maps, with Google Lens, how it is all about taking information and making it as universally accessible and helpful as possible. And if we can do that for the internet's information, why can't we help businesses do it for their business information? And that's a lot of where Google certainly has a unique approach with Google Cloud.Corey: I really want to thank you for being so generous with your time. If people want to learn more about what you're up to, where's the best place for them to find you?Brian: cloud.google.com for Google Cloud information of course. And if it's still running when this podcast goes, @isforat, I-S-F-O-R-A-T, on Twitter.Corey: And we will put links to both of those in the show notes. Thank you so much for you time. I appreciate it.Brian: Thank you, Corey. It's been good talking with you.Corey: Brian Hall, VP of Product Marketing at Google Cloud. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice. Whereas, if you've hated this podcast, please, leave a five-star review on your podcast platform of choice along with an insulting angry comment dictating that, “No. Large companies make ten-year-long commitments casually all the time.”Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

What I learned from rereading The New New Thing: A Silicon Valley Story by Michael LewisSubscribe to listen to Founders DailySupport Founders's sponsors: Tiny: The easiest way to sell your business. Quick and straightforward exits for Founders. Fable: Make your product accessible to more people. Tegus is a search engine for business knowledge that's used by founders, investors, and executives. Try it for free by visiting Tegus[1:23] Maybe somewhere in a footnote, it would be mentioned that he came from nothing, grew up poor, dropped out of high school, and made himself three or four billion dollars.[7:41] She explained that the shares in Netscape that Clark had given them had made them rich."And you have to understand," she said, “that when this happened, we were poor. I was ready to cook the cat."I assumed this was a joke, and laughed. I assumed wrong.[12:48] He was expelled from school and left town.  One time he came home talking about nothing but computers. No one in Plainview had even seen a computer except in the movies.[13:21] I remember him telling me when he came back from the Navy, ‘Mama, I'm going to show Plainview.'[14:42] In under eight years this person, considered unfit to graduate from high school, had earned himself a Ph.D. in Computer Science.[15:05] I grew up in black and white. I thought the whole world was shit, and I was sitting in the middle of it.[17:17] If you want to understand the entrepreneur, study the juvenile delinquent. The delinquent is saying with his actions, “This sucks. I'm going to do my own thing. — Yvon Chouinard[17:56] The most powerful paragraph in the book: One day I was sitting at home and, I remember having the thought ‘You can did this hole as deep as you want to dig it.' I remember thinking ‘My God, I'm going to spend the rest of my life in this fucking hole.' You can reach these points in life when you say, ‘Fuck, I've reached some sort of dead-end here. And you descend into chaos. All those years you thought you were achieving something. And you achieved nothing. I was thirty-eight years old. I'd just been fired. My second wife had just left me. I had somehow fucked up. I developed this maniacal passion for wanting to achieve something.[19:00] Two part series on Vannevar BushPieces of the Action by Vannevar Bush. (Founders #270) and Endless Frontier: Vannevar Bush, Engineer of the American Century by G. Pascal Zachary. (Founders #271) [21:38] New Growth Theory argued that wealth came from the human imagination. Wealth wasn't chiefly having more of old things; it was having entirely new things.[22:54] On creating new wealth/companies: A certain tolerance for nonconformism is really critical to the process.[24:31] The internet has massively broadened the possible space of careers, and most people haven't figured this out yet. —The Almanack of Naval Ravikant: A Guide to Wealth and Happiness by Naval Ravikant and Eric Jorgenson. (Founders #191)[25:06] A master in the art of living draws no sharp distinction between his work and his play; his labor and his leisure; his mind and his body; his education and his recreation. He hardly knows which is which. He simply pursues his vision of excellence through whatever he is doing, and leaves others to determine whether he is working or playing. To himself, he always appears to be doing both.[27:36] George Lucas: A Life by Brian Jay Jones. (Founders #35) and Steven Spielberg: A Biography by Joseph McBride. (Founders #209)[33:10] The independence and the control is worth a lot more than the money.[33:32] These people could never build the machines of the future, but they could sell the machines of the present.[35:02] Clark on how to avoid being disrupted: For a technology company to succeed, he argued, it needed always to be looking to destroy itself. If it didn't, someone else would. “It's the hardest thing in business to do,” he would say. “Even creating a lower-cost product runs against the grain, because the low-cost products undercut the high-cost, more profitable products.” Everyone in a successful company, from the CEO on down, has a stake in whatever the company is currently selling. It does not naturally occur to anyone to find a way to undermine that product.[40:41] The young were forever eating the old. In this drama technology played a very clear role. It was the murder weapon.[40:55] The art of storytelling is critically important. Most of the entrepreneurs who come to us can't tell a story. Learning to tell a story is incredibly important because that's how the money works. The money flows as a function of the stories. —Don Valentine[42:53] The Pmarca Blog Archive Ebook by Marc Andreessen (Founders #50)[45:48] What is the role I want to play in my company? I need to make sure to design my environment so I am always playing that role. Make sure you design the job you want. What is the point of being an entreprenuer if you don't do that?[47:45] John Doerr had cleared $500 million in 18 months. 30 times his original investment.[49:13] You must find extraordinary people.I noticed that the dynamic range between what an average person could accomplish and what the best person could accomplish was 50 or 100 to 1.Given that, you're well advised to go after the cream of the cream. That's what we've done.A small team of A+ players can run  circles around a giant team of B and C players.— In the Company of Giants: Candid Conversations With the Visionaries of the Digital World by Rama Dev Jager and Rafael Ortiz. (Founders #208)[52:03] Clark liked to say that human beings when they took risks, fell into one of two types, pigs or chickens. “The difference between these two kinds of people is the difference between the pig and the chicken in the ham-and-eggs breakfast. The chicken is interested, the pig is committed. If you are going to do anything worth doing, you need a lot of pigs.”[53:14] In our 10 days at sea the value of his holdings had nearly tripled. This is fantasy land he said.[53:54] There are vastly more conceivable possibilities than realized outcomes.—Subscribe to listen to Founders Daily—Get 60 days free of Readwise. It's the best app I pay for. I couldn't make Founders without it.—“I have listened to every episode released and look forward to every episode that comes out. The only criticism I would have is that after each podcast I usually want to buy the book because I am interested so my poor wallet suffers. ” — GarethBe like Gareth. Buy a book: All the books featured on Founders Podcast

About ScottWith more than 28 years of successful leadership in building high technology companies and delivering advanced products to market, Scott provides the overall strategic leadership and visionary direction for Azul Systems.Scott has a consistent proven track record of vision, leadership, and success in enterprise, consumer and scientific markets. Prior to co-founding Azul Systems, Scott founded 3dfx Interactive, a graphics processor company that pioneered the 3D graphics market for personal computers and game consoles. Scott served at 3dfx as Vice President of Engineering, CTO and as a member of the board of directors and delivered 7 award-winning products and developed 14 different graphics processors. After a successful initial public offering, 3dfx was later acquired by NVIDIA Corporation.Prior to 3dfx, Scott was a CPU systems architect at Pellucid, later acquired by MediaVision. Before Pellucid, Scott was a member of the technical staff at Silicon Graphics where he designed high-performance workstations.Scott graduated from Princeton University with a bachelor of science, earning magna cum laude and Phi Beta Kappa honors. Scott has been granted 8 patents in high performance graphics and computing and is a regularly invited keynote speaker at industry conferences.Links Referenced:Azul: https://www.azul.com/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: I come bearing ill tidings. Developers are responsible for more than ever these days. Not just the code that they write, but also the containers and the cloud infrastructure that their apps run on. Because serverless means it's still somebody's problem. And a big part of that responsibility is app security from code to cloud. And that's where our friend Snyk comes in. Snyk is a frictionless security platform that meets developers where they are - Finding and fixing vulnerabilities right from the CLI, IDEs, Repos, and Pipelines. Snyk integrates seamlessly with AWS offerings like code pipeline, EKS, ECR, and more! As well as things you're actually likely to be using. Deploy on AWS, secure with Snyk. Learn more at Snyk.co/scream That's S-N-Y-K.co/screamCorey: This episode is sponsored in part by our friends at AWS AppConfig. Engineers love to solve, and occasionally create, problems. But not when it's an on-call fire-drill at 4 in the morning. Software problems should drive innovation and collaboration, NOT stress, and sleeplessness, and threats of violence. That's why so many developers are realizing the value of AWS AppConfig Feature Flags. Feature Flags let developers push code to production, but hide that that feature from customers so that the developers can release their feature when it's ready. This practice allows for safe, fast, and convenient software development. You can seamlessly incorporate AppConfig Feature Flags into your AWS or cloud environment and ship your Features with excitement, not trepidation and fear. To get started, go to snark.cloud/appconfig. That's snark.cloud/appconfig.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. My guest on this promoted episode today is Scott Sellers, CEO and co-founder of Azul. Scott, thank you for joining me.Scott: Thank you, Corey. I appreciate the opportunity in talking to you today.Corey: So, let's start with what you're doing these days. What is Azul? What do you folks do over there?Scott: Azul is an enterprise software and SaaS company that is focused on delivering more efficient Java solutions for our customers around the globe. We've been around for 20-plus years, and as an entrepreneur, we've really gone through various stages of different growth and different dynamics in the market. But at the end of the day, Azul is all about adding value for Java-based enterprises, Java-based applications, and really endearing ourselves to the Java community.Corey: This feels like the sort of space where there are an awful lot of great business cases to explore. When you look at what's needed in that market, there are a lot of things that pop up. The surprising part to me is that this is the direction that you personally went in. You started your career as a CPU architect, to my understanding. You were then one of the co-founders of 3dfx before it got acquired by Nvidia.You feel like you've spent your career more as a hardware guy than working on the SaaS side of the world. Is that a misunderstanding of your path, or have things changed, or is this just a new direction? Help me understand how you got here from where you were.Scott: I'm not exactly sure what the math would say because I continue to—can't figure out a way to stop time. But you're correct that my academic background, I was an electrical engineer at Princeton and started my career at Silicon Graphics. And that was when I did a lot of fantastic and fascinating work building workstations and high-end graphics systems, you know, back in the day when Silicon Graphics really was the who's who here in Silicon Valley. And so, a lot of my career began in the context of hardware. As you mentioned, I was one of the founders of graphics company called 3dfx that was one of, I think, arguably the pioneer in terms of bringing 3d graphics to the masses, if you will.And we had a great run of that. That was a really fun business to be a part of just because of what was going on in the 3d world. And we took that public and eventually sold that to Nvidia. And at that point, my itch, if you will, was really learning more about the enterprise segment. I'd been involved with professional graphics with SGI, I had been involved with consumer graphics with 3dfx.And I was fascinated just to learn about the enterprise segment. And met a couple people through a mutual friend around the 2001 timeframe, and they started talking about this thing called Java. And you know, I had of course heard about Java, but as a consumer graphics guy, didn't have a lot of knowledge about it or experience with it. And the more I learned about it, recognized that what was going on in the Java world—and credit to Sun for really creating, obviously, not only language, but building a community around Java—and recognized that new evolutions of developer paradigms really only come around once a decade if then, and was convinced and really got excited about the opportunity to ride the wave of Java and build a company around that.Corey: One of the blind spots that I have throughout the entire world of technology—and to be fair, I have many of them, but the one most relevant to this conversation, I suppose, is the Java ecosystem as a whole. I come from a background of being a grumpy Unix sysadmin—because I've never met a happy one of those in my entire career—and as a result, scripting languages is where everything that I worked with started off. And on the rare occasions, I worked in Java shops, it was, “Great. We're going to go—here's a WAR file. Go ahead and deploy this with Tomcat,” or whatever else people are going to use. But basically, “Don't worry your pretty little head about that.”At most, I have to worry about how to configure a heap or whatnot. But it's from the outside looking in, not having to deal with that entire ecosystem as a whole. And what I've seen from that particular perspective is that every time I start as a technologist, or even as a consumer trying to install some random software package in the depths of the internet, and I have to start thinking about Java, it always feels like I'm about to wind up in a confusing world. There are a number of software packages that I installed back in, I want to say the early-2010s or whatnot. “Oh, you need to have a Java runtime installed on your Mac,” for example.And okay, going through Oracle site, do I need the JRE? Do I need the JDK? Oh, there's OpenJDK, which kind of works, kind of doesn't. Amazon got into the space with Corretto, which because that sounds nothing whatsoever, like Java, but strange names coming from Amazon is basically par for the course for those folks. What is the current state of the Java ecosystem, for those of us who have—basically the closest we've ever gotten is JavaScript, which is nothing alike except for the name.Scott: And you know, frankly, given the protection around the name Java—and you know, that is a trademark that's owned by Oracle—it's amazing to me that JavaScript has been allowed to continue to be called JavaScript because as you point out, JavaScript has nothing to do with Java per se.Corey: Well, one thing they do have in common I found out somewhat recently is that Oracle also owns the trademark for JavaScript.Scott: Ah, there you go. Maybe that's why it continues.Corey: They're basically a law firm—three law firms in a trench coat, masquerading as a tech company some days.Scott: Right. But anyway, it is a confusing thing because you know, I think, arguably, JavaScript, by the numbers, probably has more programmers than any other language in the world, just given its popularity as a web language. But to your question about Java specifically, it's had an evolving life, and I think the state where it is today, I think it's in the most exciting place it's ever been. And I'll walk you through kind of why I believe that to be the case.But Java has evolved over time from its inception back in the days when it was called, I think it was Oak when it was originally conceived, and Sun had eventually branded it as Java. And at the time, it truly was owned by Sun, meaning it was proprietary code; it had to be licensed. And even though Sun gave it away, in most cases, it still at the end of the day, it was a commercially licensed product, if you will, and platform. And if you think about today's world, it would not be conceivable to create something that became so popular with programmers that was a commercially licensed product today. It almost would be mandated that it would be open-source to be able to really gain the type of traction that Java has gained.And so, even though Java was really garnering interest, you know, not only within the developer community, but also amongst commercial entities, right, everyone—and the era now I'm talking about is around the 2000 era—all of the major software vendors, whether it was obviously Sun, but then you had Oracle, you had IBM, companies like BEA, were really starting to blossom at that point. It was a—you know, you could almost not find a commercial software entity that was not backing Java. But it was still all controlled by Sun. And all that success ultimately led to a strong outcry from the community saying this has to be open-source; this is too important to be beholden to a single vendor. And that decision was made by Sun prior to the Oracle acquisition, they actually open-sourced the Java runtime code and they created an open-source project called OpenJDK.And to Oracle's credit, when they bought Sun—which I think at the time when you really look back, Oracle really did not have a lot of track record, if you will, of being involved with an open-source community—and I think when Oracle acquired Sun, there was a lot of skepticism as to what's going to happen to Java. Is Oracle going to make this thing, you know, back to the old days, proprietary Oracle, et cetera? And really—Corey: I was too busy being heartbroken over Solaris at that point to pay much attention to the Java stuff, but it felt like it was this—sort of the same pattern, repeated across multiple ecosystems.Scott: Absolutely. And even though Sun had also open-sourced Solaris, with the OpenSolaris project, that was one of the kinds of things that it was still developed very much in a closed environment, and then they would kind of throw some code out into the open world. And no one really ran OpenSolaris because it wasn't fully compatible with Solaris. And so, that was a faint attempt, if you will.But Java was quite different. It was truly all open-sourced, and the big difference that—and again, I give Oracle a lot of credit for this because this was a very important time in the evolution of Java—that Oracle, maintained Sun's commitment to not only continue to open-source Java but most importantly, develop it in the open community. And so, you know, again, back and this is the 2008, ‘09, ‘10 timeframe, the evolution of Java, the decisions, the standards, you know, what goes in the platform, what doesn't, decisions about updates and those types of things, that truly became a community-led world and all done in the open-source. And credit to Oracle for continuing to do that. And that really began the transition away from proprietary implementations of Java to one that, very similar to Linux, has really thrived because of the true open-source nature of what Java is today.And that's enabled more and more companies to get involved with the evolution of Java. If you go to the OpenJDK page, you'll see all of the not only, you know, incredibly talented individuals that are involved with the evolution of Java, but again, a who's who in pretty much every major commercial entities in the enterprise software world is also somehow involved in the OpenJDK community. And so, it really is a very vibrant, evolving standard. And some of the tactical things that have happened along the way in terms of changing how versions of Java are released still also very much in the context of maintaining compatibility and finding that careful balance of evolving the platform, but at the same time, recognizing that there is a lot of Java applications out there, so you can't just take a right-hand turn and forget about the compatibility side of things. But we as a community overall, I think, have addressed that very effectively, and the result has been now I think Java is more popular than ever and continues to—we liken it kind of to the mortar and the brick walls of the enterprise. It's a given that it's going to be used, certainly by most of the enterprises worldwide today.Corey: There's a certain subset of folk who are convinced the Java, “Oh, it's this a legacy programming language, and nothing modern or forward-looking is going to be built in it.” Yeah, those people generally don't know what the internal language stack looks like at places like oh, I don't know, AWS, Google, and a few others, it is very much everywhere. But it also feels, on some level, like, it's a bit below the surface-level of awareness for the modern full-stack developer in some respects, right up until suddenly it's very much not. How is Java evolving in a cloud these days?Scott: Well, what we see happening—you know, this is true for—you know, I'm a techie, so I can talk about other techies. I mean as techies, we all like the new thing, right? I mean, it's not that exciting to talk about a language that's been around for 20-plus years. But that doesn't take away from the fact that we still all use keyboards. I mean, no one really talks about what keyboard they use anymore—unless you're really into keyboards—but at the end of the day, it's still a fundamental tool that you use every single day.And Java is kind of in the same situation. The reason that Java continues to be so fundamental is that it really comes back to kind of reinventing the wheel problem. Are there are other languages that are more efficient to code in? Absolutely. Are there other languages that, you know, have some capabilities that the Java doesn't have? Absolutely.But if you have the ability to reinvent everything from scratch, sure, go for it. And you also don't have to worry about well, can I find enough programmers in this, you know, new hot language, okay, good luck with that. You might be able to find dozens, but when you need to really scale a company into thousands or tens of thousands of developers, good luck finding, you know, everyone that knows, whatever your favorite hot language of the day is.Corey: It requires six years experience in a four-year-old language. Yeah, it's hard to find that, sometimes.Scott: Right. And you know, the reality is, is that really no application ever is developed from scratch, right? Even when an application is, quote, new, immediately, what you're using is frameworks and other things that have written long ago and proven to be very successful.Corey: And disturbing amounts of code copied and pasted from Stack Overflow.Scott: Absolutely.Corey: But that's one of those impolite things we don't say out loud very often.Scott: That's exactly right. So, nothing really is created from scratch anymore. And so, it's all about building blocks. And this is really where this snowball of Java is difficult to stop because there is so much third-party code out there—and by that, I mean, you know, open-source, commercial code, et cetera—that is just so leveraged and so useful to very quickly be able to take advantage of and, you know, allow developers to focus on truly new things, not reinventing the wheel for the hundredth time. And that's what's kind of hard about all these other languages is catching up to Java with all of the things that are immediately available for developers to use freely, right, because most of its open-source. That's a pretty fundamental Catch-22 about when you start talking about the evolution of new languages.Corey: I'm with you so far. The counterpoint though is that so much of what we're talking about in the world of Java is open-source; it is freely available. The OpenJDK, for example, says that right on the tin. You have built a company and you've been in business for 20 years. I have to imagine that this is not one of those stories where, “Oh, all the things we do, we give away for free. But that's okay. We make it up in volume.” Even the venture capitalist mindset tends to run out of patience on those kinds of timescales. What is it you actually do as a business that clearly, obviously delivers value for customers but also results in, you know, being able to meet payroll every week?Scott: Right? Absolutely. And I think what time has shown is that, with one very notable exception and very successful example being Red Hat, there are very, very few pure open-source companies whose business is only selling support services for free software. Most successful businesses that are based on open-source are in one-way shape or form adding value-added elements. And that's our strategy as well.The heart of everything we do is based on free code from OpenJDK, and we have a tremendous amount of business that we are following the Red Hat business model where we are selling support and long-term access and a huge variety of different operating system configurations, older Java versions. Still all free software, though, right, but we're selling support services for that. And that is, in essence, the classic Red Hat business model. And that business for us is incredibly high growth, very fast-moving, a lot of that business is because enterprises are tired of paying the very high price to Oracle for Java support and they're looking for an open-source alternative that is exactly the same thing, but comes in pure open-source form and with a vendor that is as reputable as Oracle. So, a lot of our businesses based on that.However, on top of that, we also have value-added elements. And so, our product that is called Azul Platform Prime is rooted in OpenJDK—it is OpenJDK—but then we've added value-added elements to that. And what those value-added elements create is, in essence, a better Java platform. And better in this context means faster, quicker to warm up, elimination of some of the inconsistencies of the Java runtime in terms of this nasty problem called garbage collection which causes applications to kind of bounce around in terms of performance limitations. And so, creating a better Java is another way that we have monetized our company is value-added elements that are built on top of OpenJDK. And I'd say that part of the business is very typical for the majority of enterprise software companies that are rooted in open-source. They're typically adding value-added components on top of the open-source technology, and that's our similar strategy as well.And then the third evolution for us, which again is very tried-and-true, is evolving the business also to add SaaS offerings. So today, the majority of our customers, even though they deploy in the cloud, they're stuck customer-managed and so they're responsible for where do I want to put my Java runtime on building out my stack and cetera, et cetera. And of course, that could be on-prem, but like I mentioned, the majority are in the cloud. We're evolving our product offerings also to have truly SaaS-based solutions so that customers don't even need to manage those types of stacks on their own anymore.Corey: On some level, it feels like we're talking about two different things when we talk about cloud and when we talk about programming languages, but increasingly, I'm starting to see across almost the entire ecosystem that different languages and different cloud providers are in many ways converging. How do you see Java changing as cloud-native becomes the default rather than the new thing?Scott: Great question. And I think the thing to recognize about, really, most popular programming languages today—I can think of very few exceptions—these languages were created, envisioned, implemented if you will, in a day when cloud was not top-of-mind, and in many cases, certainly in the case of Java, cloud didn't even exist when Java was originally conceived, nor was that the case when you know, other languages, such as Python, or JavaScript, or on and on. So, rethinking how these languages should evolve in very much the context of a cloud-native mentality is a really important initiative that we certainly are doing and I think the Java community is doing overall. And how you architect not only the application, but even the Java runtime itself can be fundamentally different if you know that the application is going to be deployed in the cloud.And I'll give you an example. Specifically, in the world of any type of runtime-based language—and JavaScript is an example of that; Python is an example of that; Java is an example of that—in all of those runtime-based environments, what that basically means is that when the application is run, there's a piece of software that's called the runtime that actually is running that application code. And so, you can think about it as a middleware piece of software that sits between the operating system and the application itself. And so, that runtime layer is common across those languages and those platforms that I mentioned. That runtime layer is evolving, and it's evolving in a way that is becoming more and more cloud-native in it's thinking.The process itself of actually taking the application, compiling it into whatever underlying architecture it may be running on—it could be an x86 instance running on Amazon; it could be, you know, for example, an ARM64, which Amazon has compute instances now that are based on an ARM64 processor that they call Graviton, which is really also kind of altering the price-performance of the compute instances on the AWS platform—that runtime layer magically takes an application that doesn't have to be aware of the underlying hardware and transforms that into a way that can be run. And that's a very expensive process; it's called just-in-time compiling, and that just-in-time compilation, in today's world—which wasn't really based on cloud thinking—every instance, every compute instance that you deploy, that same JIT compilation process is happening over and over again. And even if you deploy 100 instances for scalability, every one of those 100 instances is doing that same work. And so, it's very inefficient and very redundant. Contrast that to a cloud-native thinking: that compilation process should be a service; that service should be done once.The application—you know, one instance of the application is actually run and there are the other ninety-nine should just reuse that compilation process. And that shared compiler service should be scalable and should be able to scale up when applications are launched and you need more compilation resources, and then scaled right back down when you're through the compilation process and the application is more moving into the—you know, to the runtime phase of the application lifecycle. And so, these types of things are areas that we and others are working on in terms of evolving the Java runtime specifically to be more cloud-native.Corey: This episode is sponsored in part by our friends at Sysdig. Sysdig secures your cloud from source to run. They believe, as do I, that DevOps and security are inextricably linked. If you wanna learn more about how they view this, check out their blog, it's definitely worth the read. To learn more about how they are absolutely getting it right from where I sit, visit Sysdig.com and tell them that I sent you. That's S Y S D I G.com. And my thanks to them for their continued support of this ridiculous nonsense.Corey: This feels like it gets even more critical when we're talking about things like serverless functions across basically all the cloud providers these days, where there's the whole setup, everything in the stack, get it running, get it listening, ready to go, to receive a single request and then shut itself down. It feels like there are a lot of operational efficiencies possible once you start optimizing from a starting point of yeah, this is what that environment looks like, rather than us big metal servers sitting in a rack 15 years ago.Scott: Yeah. I think the evolution of serverless appears to be headed more towards serverless containers as opposed to serverless functions. Serverless functions have a bunch of limitations in terms of when you think about it in the context of a complex, you know, microservices-based deployment framework. It's just not very efficient, to spin up and spin down instances of a function if that actually is being—it is any sort of performance or latency-sensitive type of applications. If you're doing something very rarely, sure, it's fine; it's efficient, it's elegant, et cetera.But any sort of thing that has real girth to it—and girth probably means that's what's driving your application infrastructure costs, that's what's driving your Amazon bill every month—those types of things typically are not going to be great for starting and stopping functional instances. And so, serverless is evolving more towards thinking about the container itself not having to worry about the underlying operating system or the instance on Amazon that it's running on. And that's where, you know, we see more and more of the evolution of serverless is thinking about it at a container-level as opposed to a functional level. And that appears to be a really healthy steady state, so it gets the benefits of not having to worry about all the underlying stuff, but at the same time, doesn't have the downside of trying to start and stop functional influences at a given point in time.Corey: It seems to me that there are really two ways of thinking about cloud. The first is what I think a lot of companies do their first outing when they're going into something like AWS. “Okay, we're going to get a bunch of virtual machines that they call instances in AWS, we're going to run things just like it's our data center except now data transfer to the internet is terrifyingly expensive.” The more quote-unquote, “Cloud-native” way of thinking about this is what you're alluding to where there's, “Here's some code that I wrote. I want to throw it to my cloud provider and just don't tell me about any of the infrastructure parts. Execute this code when these conditions are met and leave me alone.”Containers these days seem to be one of our best ways of getting there with a minimum of fuss and friction. What are you seeing in the enterprise space as far as adoption of those patterns go? Or are we seeing cloud repatriation showing up as a real thing and I'm just not in the right place to see it?Scott: Well, I think as a cloud journey evolves, there's no question that—and in fact it's even silly to say that cloud is here to stay because I think that became a reality many, many years ago. So really, the question is, what are the challenges now with cloud deployments? Cloud is absolutely a given. And I think you stated earlier, it's rare that, whether it's a new company or a new application, at least in most businesses that don't have specific regulatory requirements, that application is highly, highly likely to be envisioned to be initially and only deployed in the cloud. That's a great thing because you have so many advantages of not having to purchase infrastructure in advance, being able to tap into all of the various services that are available through the cloud providers. No one builds databases anymore; you're just tapping into the service that's provided by Azure or AWS, or what have you.And, you know, just that specific example is a huge amount of savings in terms of just overhead, and license costs, and those types of stuff, and there's countless examples of that. And so, the services that are available in the cloud are unquestioned. So, there's countless advantages of why you want to be in the cloud. The downside, however, the cloud that is, if at the end of the day, AWS, Microsoft with Azure, Google with GCP, they are making 30% margin on that cloud infrastructure. And in the days of hardware, when companies would actually buy their servers from Dell, or HP, et cetera, those businesses are 5% margin.And so, where's that 25% going? Well, the 25% is being paid for by the users of cloud, and as a result of that, when you look at it purely from an operational cost perspective, it is more expensive to run in the cloud than it is back in the legacy days, right? And that's not to say that the industry has made the wrong choice because there's so many advantages of being in cloud, there's no doubt about it. And there should be—you know, and the cloud providers deserve to take some amount of margin to provide the services that they provide; there's no doubt about that. The question is, how do you do the best of all worlds?And you know, there is a great blog by a couple of the partners in Andreessen Horowitz, they called this the Cloud Paradox. And the Cloud Paradox really talks about the challenges. It's really a Catch-22; how do you get all the benefits of cloud but do that in a way that is not overly taxing from a cost perspective? And a lot of it comes down to good practices and making sure that you have the right monitoring and culture within an enterprise to make sure that cloud cost is a primary thing that is discussed and metric, but then there's also technologies that can help so that you don't have to even think about what you really don't ever want to do: repatriating, which is about the concept of actually moving off the cloud back to the old way of doing things. So certainly, I don't believe repatriation is a practical solution for ongoing and increasing cloud costs. I believe technology is a solution to that.And there are technologies such as our product, Azul Platform Prime, that in essence, allows you to do more with less, right, get all the benefits of cloud, deploy in your Amazon environment, deploy in your Azure environment, et cetera, but imagine if instead of needing a hundred instances to handle your given workload, you could do that with 50 or 60. Tomorrow, that means that you can start savings and being able to do that simply by changing your JVM from a standard OpenJDK or Oracle JVM to something like Platform Prime, you can immediately start to start seeing the benefits from that. And so, a lot of our business now and our growth is coming from companies that are screaming under the ongoing cloud costs and trying to keep them in line, and using technology like Azul Platform Prime to help mitigate those costs.Corey: I think that there is a somewhat foolish approach that I'm seeing taken by a lot of folks where there are some companies that are existentially anti-cloud, if for no other reason than because if the cloud wins, then they don't really have a business anymore. The problem I see with that is that it seems that their solution across the board is to turn back the clock where if I'm going to build a startup, it's time for me to go buy some servers and a rack somewhere and start negotiating with bandwidth providers. I don't see that that is necessarily viable for almost anyone. We aren't living in 1995 anymore, despite how much some people like to pretend we are. It seems like if there are workloads—for which I agree, cloud is not necessarily an economic fit, first, I feel like the market will fix that in the fullness of time, but secondly, on an individual workload belonging in a certain place is radically different than, “Oh, none of our stuff should live on cloud. Everything belongs in a data center.” And I just think that companies lose all credibility when they start pretending that it's any other way.Scott: Right. I'd love to see the reaction of the venture capitalists' face when an entrepreneur walks in and talks about how their strategy for deploying their SaaS service is going to be buying hardware and renting some space in the local data center.Corey: Well, there is a good cost control method, if you think about it. I mean very few engineers are going to accidentally spin up an $8 million cluster in a data center a second time, just because there's no space left for it.Scott: And you're right; it does happen in the cloud as well. It's just, I agree with you completely that as part of the evolution of cloud, in general, is an ever-improving aspect of cost and awareness of cost and building in technologies that help mitigate that cost. So, I think that will continue to evolve. I think, you know, if you really think about the cloud journey, cost, I would say, is still in early phases of really technologies and practices and processes of allowing enterprises to really get their head around cost. I'd still say it's a fairly immature industry that is evolving quickly, just given the importance of it.And so, I think in the coming years, you're going to see a radical improvement in terms of cost awareness and technologies to help with costs, that again allows you to the best of all worlds. Because, you know, if you go back to the Dark Ages and you start thinking about buying servers and infrastructure, then you are really getting back to a mentality of, “I've got to deploy everything. I've got to buy software for my database. I've got to deploy it. What am I going to do about my authentication service? So, I got to buy this vendor's, you know, solution, et cetera.” And so, all that stuff just goes away in the world of cloud, so it's just not practical, in this day and age I think, to think about really building a business that's not cloud-native from the beginning.Corey: I really want to thank you for spending so much time talking to me about how you view the industry, the evolution we've seen in the Java ecosystem, and what you've been up to. If people want to learn more, where's the best place for them to find you?Scott: Well, there's a thing called a website that you may not have heard of, it's really cool.Corey: Can I build it in Java?Scott: W-W-dot—[laugh]. Yeah. Azul website obviously has an awful lot of information about that, Azul is spelled A-Z-U-L, and we sometimes get the question, “How in the world did you name a company—why did you name it Azul?”And it's kind of a funny story because back in the days of Azul when we thought about, hey, we want to be big and successful, and at the time, IBM was the gold standard in terms of success in the enterprise world. And you know, they were Big Blue, so we said, “Hey, we're going to be a little blue. Let's be Azul.” So, that's where we began. So obviously, go check out our site.We're very present, also, in the Java community. We're, you know, many developer conferences and talks. We sponsor and run many of what's called the Java User Groups, which are very popular 10-, 20-person meetups that happen around the globe on a regular basis. And so, you know, come check us out. And I appreciate everyone's time in listening to the podcast today.Corey: No, thank you very much for spending as much time with me as you have. It's appreciated.Scott: Thanks, Corey.Corey: Scott Sellers, CEO and co-founder of Azul. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an entire copy of the terms and conditions from Oracle's version of the JDK.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

"A lot of the companies I've worked for were trying to transition from proprietary or very siloed products, very black box products to more standards based products. And that seems to be a common thread that I've gone through even in proprietary companies. Avaya also was trying to move away from a very, very monolithic black box voice messaging system that they had millions of dollars invested in called the Octel Voice Messaging system. "They wanted to go to more of a standards based system where, and also a more componentized system, if you will, with the voice server at the back, and then all the UI and the functions and the application server and the front.  "Especially in the embedded space, articulating the value of a company based distribution, say like a Wind River versus roll-your-own was really hard because if you looked at that market in those days 75 to 80% of customers wanted to roll their own. And so the 20% of the market was kind of split between all the commercial vendors. "It's been hard through the timeframe from then to now to really find good ways to monetize you know, over open source. And as you know, Red Hat's been one of the most successful companies in this area, but most companies have really struggled to monetize and, and sustain an open source based business. "The cloud is providing a better business model. Delivering the product as a service because the operationalization of an open source product is so difficult to do, and it saves you the time of installation, integration, support, testing. You can just start running the product from day one. I think that's been a pretty good business model. What is really, really interesting to me is how open source community becomes an extended engineering team for you. And that you can then focus on your core competency while leveraging the extended team for common components that all of us use." -- Nithya Ruff Resources from this Episode Beau Vrolek: https://www.hpcwire.com/1999/11/16/sgi-in-the-new-millennium-an-interview-with-beau-vrolyk/ (https://www.hpcwire.com/1999/11/16/sgi-in-the-new-millennium-an-interview-with-beau-vrolyk/) Dave McAllister: https://www.linkedin.com/in/davemc/details/experience/ (https://www.linkedin.com/in/davemc/details/experience/) Silicon Graphics: https://en.wikipedia.org/wiki/Silicon_Graphics (https://en.wikipedia.org/wiki/Silicon_Graphics) IRIX: https://en.wikipedia.org/wiki/IRIX (https://en.wikipedia.org/wiki/IRIX) Wyatt Starnes - Tripwire: https://www.cerias.purdue.edu/site/blog/post/in_memorium_wyatt_starnes/ (https://www.cerias.purdue.edu/site/blog/post/in_memorium_wyatt_starnes/) Wind River: https://en.wikipedia.org/wiki/Wind_River_Systems (https://en.wikipedia.org/wiki/Wind_River_Systems) Sumit Sadana: https://www.linkedin.com/in/sumitsadana/ (https://www.linkedin.com/in/sumitsadana/) Gene Kim: https://www.linkedin.com/in/realgenekim/

Selling With Love is more than a podcast! Join the community of like-minded entrepreneurs ready to overcome their sales blockages and transform the planet at: https://www.linkedin.com/groups/14070148/ ===== What can we learn from the pre-internet era of sales? How technology has affected sales? How B2B high-value complex sales are different from warrior B2C sales? Clive Miller, with 45 years of experience as a seller, is a goldmine of wisdom and real-life know-how. During this episode, you'll discover why in a complex B2B sale, the salesperson is more of a project manager making a business plan than the classic stereotype of the go-getter seller. Grab pen and paper and discover how the ins and outs of B2B and B2C sales have evolved in the last 40 years. =====

Jim Irving started his career selling office equipment door to door in Scotland, where soon after his career rapidly developed into senior selling and sales leadership roles, then ultimately to senior executive positions at major multinationals (including becoming the UK MD of Information Builders – a leading US-based enterprise software company). Jim now runs his own consulting business helping start-ups to improve their B2B strategy and selling results. He has advised and helped many start-ups to better execute and grow their businesses. Jim has spent over 43 years in B2B selling with a number of industry-leading technology organizations including Amdahl, Sequent, Silicon Graphics, and Information Builders. Join us as we discuss Jim's journey in professional sales as well as different tips he has for you that can help you out in your professional career. Highlights The fundamentals of B2B selling How he moved from the corporate world to training, coaching, and mentoring The best practices for sales he swears by What discovery is and its importance What does it take to get a sales qualified lead What his recent clients have to say after undergoing his training and mentoring The key to the whole discovery process Episode Resources Connect with Mark Cox https://www.inthefunnel.com/ https://ca.linkedin.com/in/markandrewcox https://www.facebook.com/inthefunnel Connect with Jim Irving https://b2bsellingguidebook.com/index.html https://www.linkedin.com/in/jimirving 

Una obra de arte virtual desemboca en un juicio millonario por el código de Google Earth. Llegamos a esta serie de Netflix por sugerencia de Javier Yañez en el grupo Telegram de ElSiglo21esHoy.com “El código que valía millones” o “El código de la discordia” (The billón Dollar code) es una serie de Netflix de 4 capítulos en la que reconstruyen con unos personajes ficticios lo que habría ocurrido en la realidad entre las compañías Skyline y Google, en un juicio para establecer la autoría original del código del software Google Earth. La serie logra ejemplificar con agudeza los problemas de la era del software y de los emprendimientos tecnológicos… y plantea un par de conceptos muy fuertes sobre la innovación y los inventos.Aquí algunos puntos que tratamos en este episodio:- 
Episodio 1: 6 días antes de juicio- Episodio 2: 2 años antes del juicio - Guiños a Star Trek - Episodio 3: acusan a Google de una práctica legal ruin- Episodio 4: the Network effect (más tiempo: más información)- los primeros 90 segundos de la serie son magníficos- Se parece a The Social Network / Silicon Valley / Goodbye Lenin - Son artistas en busca de una obra de arte virtual en 1993- Llegan con la idea a Deustche Telekom - Una idea imposible y buscar la forma de resolver el problema que la hace imposible - ¿Qué pasa cuando una idea no se considera lograble? - La innovación se fundamenta en lo que no sabemos hacer hoy- “Si todos los inventos hubieran sido seguros desde el comienzo… no habrían existido”- Un proyecto de arte digital para Deustche Telekom: Terra Vision - Reclutamiento de talento - Una Onyx SGI, sistema operativo IRIX, de Unix y creado por Silicon Graphics. - Con set de gráficos RealityEngine- Podía costar hasta 1/4 de millón de dólares. - Jurassic Park, Twister, Congo, Toy Story,- Mapas, imágenes satelitales, geodatos, fotos aéreas a diferentes alturas para proporcionar la sensación de vuelo al usuario de Terra Vision - La forma en que eligen al contable - Algoritmo de sistema de coordenadas flotantes- Terra Vision 1994 vs Google Earth 2005

Una obra de arte virtual desemboca en un juicio millonario por el código de Google Earth. Llegamos a esta serie de Netflix por sugerencia de Javier Yañez en el grupo Telegram de ElSiglo21esHoy.com “El código que valía millones” o “El código de la discordia” (The billón Dollar code) es una serie de Netflix de 4 capítulos en la que reconstruyen con unos personajes ficticios lo que habría ocurrido en la realidad entre las compañías Skyline y Google, en un juicio para establecer la autoría original del código del software Google Earth. La serie logra ejemplificar con agudeza los problemas de la era del software y de los emprendimientos tecnológicos… y plantea un par de conceptos muy fuertes sobre la innovación y los inventos.Aquí algunos puntos que tratamos en este episodio:- 
Episodio 1: 6 días antes de juicio- Episodio 2: 2 años antes del juicio - Guiños a Star Trek - Episodio 3: acusan a Google de una práctica legal ruin- Episodio 4: the Network effect (más tiempo: más información)- los primeros 90 segundos de la serie son magníficos- Se parece a The Social Network / Silicon Valley / Goodbye Lenin - Son artistas en busca de una obra de arte virtual en 1993- Llegan con la idea a Deustche Telekom - Una idea imposible y buscar la forma de resolver el problema que la hace imposible - ¿Qué pasa cuando una idea no se considera lograble? - La innovación se fundamenta en lo que no sabemos hacer hoy- “Si todos los inventos hubieran sido seguros desde el comienzo… no habrían existido”- Un proyecto de arte digital para Deustche Telekom: Terra Vision - Reclutamiento de talento - Una Onyx SGI, sistema operativo IRIX, de Unix y creado por Silicon Graphics. - Con set de gráficos RealityEngine- Podía costar hasta 1/4 de millón de dólares. - Jurassic Park, Twister, Congo, Toy Story,- Mapas, imágenes satelitales, geodatos, fotos aéreas a diferentes alturas para proporcionar la sensación de vuelo al usuario de Terra Vision - La forma en que eligen al contable - Algoritmo de sistema de coordenadas flotantes- Terra Vision 1994 vs Google Earth 2005

Imagine being able to open your consciousness so that your deepest fears recede into the background, allowing you to contact your creative essence.Would that ability CHANGE your business, your relationships, your LIFE forever?When it comes to your fears… the problem is never what you think it is.When you open up to your feelings and find a place of clarity and “pure consciousness”, suddenly everything comes together. (and FAST!)The reason we don't get to that state of pure consciousness is because we're unwilling to face and feel the things that are in the way. There's no problem that can't be solved with 10 minutes of sweaty conversation, but sometimes that sweaty conversation has to be with yourself.A perfect example comes from a conversation Gay had with Ed McCracken, the founder of Silicon Graphics years ago. They were $100 million dollars apart on a deal with a movie studio, running up against one problem after another. “The problem is never what you think it is.” Ed assumed the problem was money but it turned out the REAL issue was the guys they were doing the deal with were afraid they didn't like them.They were from such different cultures that they were afraid that they disapproved of their culture.Fortunately, Ed's wife was very familiar with meditation so they got everyone into a room together and into a meditative state.They opened up to their feelings about it until they got to a place of clarity and shared consciousness. Instead of arguing about numbers, they went underneath the whole thing and suddenly the deal came together.The $100 million dollar thing evaporated and they got the deal done in 20 minutes. Once you understand these concepts and start doing the practices, you go into a nonlinear place, where something you think should take a year to accomplish, can be done in two or three weeks. It speeds up time because it eliminates barriers that you didn't even know were barriers, and it eliminates problems that look like intractable recycling problems.One of the ways to speed up time is by SLOWING DOWN YOUR MIND.