Podcasts about wozniak

In der neuen Folge von Brandschutz To Go von Stephan Wenzel geht es um ein Thema, das im Baurecht immer wieder für Fragen sorgt: Bestandsschutz im Brandschutz. Zu Gast ist Kathrin Wozniak, Architektin bei VIVAWEST und vorher knapp 10 Jahre bei der Bauaufsicht tätig. Gemeinsam wird verständlich erklärt, wann ein Gebäude geschützt ist, warum das Alter allein nicht ausreicht und an welchen Punkten Bestandsschutz auch enden kann. Besonders spannend:

This week on The Razzle Dazzle Show, we're joined by Nick Wozniak, co-founder of Yacht Club Games and one of the creative forces behind the iconic Shovel Knight! We dive into his journey through the indie game scene, his approach to art and animation, and what it takes to build games that feel both nostalgic and completely fresh. Plus, we take a look at Mina the Hollower—Yacht Club's bold new gothic adventure—what makes it stand out, and why it might be their most exciting project yet. Special Guest - Nick "Woz" Wozniak X: @norkwoz IG: @norkwozhttps://www.yachtclubgames.com/games/mina-the-hollower/ https://store.steampowered.com/app/1875580/Mina_the_Hollower/Host: Jared Gonzalez. Cohosts: Chaz Hawkins, Mauro Piquera. Master Chief Engineer: Jared Gonzalez. Editor: Jared Gonzalez. Graphics Editor: Jared Gonzalez. Digital Media Editor: Jared Gonzalez. Producer: Jared Gonzalez. ⁠https://linktr.ee/razzledazzleshowpodcast?utm_source=linktree_profile_share

Wozniak conia l'actual intelligence. I datacenter alzano la temperatura. Il Papa pubblica Magnifica Humanitas. Una retrospettiva su Mythos. Queste e molte altre le notizie tech commentate nella puntata di questa settimana.Dallo studio distribuito di digitalia:Francesco Facconi, Giulio Cupini, Massimo De SantoProduttori esecutivi:Simone Magnaschi, Andrea Bottaro, Angelo Travaglione, Valerio Galano, Giulio Magnifico, Claudio Galante, Davide Bellia, Nicola Gramola, Paolo Bernardini, Fabrizio Mele, Fiorenzo Pilla, Ligea Technology Di D'esposito Antonio, Manuel Zavatta, Alessandro Grossi, Luca Ongaro, Mattia Vailati, Alessandro Lago, Fabio Zappa, Massimiliano Sgroi, Roberto Basile, Matteo Tarabini, Antonio Gargiulo, Giuseppe Baldi, Luca Di Stefano, Giuliano Arcinotti, Davide Tinti, Piero Alberto Mazzo, Fabio Filisetti, Filippo Brancaleoni, Mattia Lanzoni, Isacco Tacchella, Antonio Manna, Gabriele Gambini, Enrico De Anna, Christian Schwarz, Massimo Pollastri, Alessandro Blasi, Valerio Bendotti, Fabrizio Reina, Gabriele Tubertini, Paola Bellini, Gianfranco Di Summa, Silvano Carradori, John MeyerSponsor:Squarespace.com - utilizzate il codice coupon "DIGITALIA" per avere il 10% di sconto sul costo del primo acquisto.Links:SIRENAI has contorted the job market for twentysomethings leaving college this MayUsing AI is more expensive than paying human employeesApple cofounder Steve Wozniak got cheers not boos after telling students they 'all have AI actual intelligence'The AI Backlash Could Get Very UglyData centers raise nearby temperatures by up to 4 degrees in PhoenixLettera Enciclica "Magnifica Humanitas" di Papa Leone XIV sulla custodia della persona umana nel tempo dell'intelligenza artificiale (15 maggio 2026)Pope Leo XIV's first encyclical Magnifica humanitas to be published May 25Si intitolerà “Magnifica humanitas” la prima enciclica di Leone XIV. Parlerà di dignità umana e IAProject Glasswing: An initial updateProject Glasswing: what Mythos showed usGoogle publishes exploit code threatening millions of Chromium usersL'IA Claude Mythos fa paura alle banche, martedì riunione in BceChiuso Cinemagoal: con loperazione Tutto chiaro la GDF scopre una forma di pirateria totalmente ineditaPirateria audiovisiva scoperto il sistema Cinemagoal: centinaia di sequestri in tutto il PaeseWelcome to the personal software revolutionCell phone users can't stop incriminating themselvesThe data is abundantly clear: the EU Digital Markets Act is working10 anni di Gdpr, ora deve sopravvivere all'AIMusk, Zuckerberg derail Trump AI orderGingilli del giorno:How LLMs WorkShadowRocket - Reroute Proxy TrafficLa mappa dei cavi sottomarini.Supporta Digitalia, diventa produttore esecutivo.

How can you supercharge your creativity in an age when AI is reshaping everything — including how we write, edit, and market our books? What does it look like to use AI as a genuine creative partner rather than a shortcut? And could professional speaking become an income stream that complements your writing career? With James Taylor. In the intro, Audible's new royalty model; New royalty model details [ACX; Kindlepreneur]; Public Speaking for Authors, Creatives and other Introverts; Why Indie Authors Should Ignore the Market's Mood and Focus on their Mission [Self-Publishing with ALLi]; Lichfield Cathedral; This podcast is sponsored by Kobo Writing Life, which helps authors self-publish and reach readers in global markets through the Kobo eco-system. You can also subscribe to the Kobo Writing Life podcast for interviews with successful indie authors. This show is also supported by my Patrons. Join my Community at Patreon.com/thecreativepenn James Taylor is a nonfiction author, professional speaker, podcaster, and entrepreneur who helps people unlock their creative potential. He hosts the SuperCreativity Podcast and his latest book is SuperCreativity: Augmenting Human Creativity in the Age of Artificial Intelligence. You can listen above or on your favorite podcast app or read the notes and links below. Here are the highlights and the full transcript is below. Show Notes How to define creativity and why it's becoming the most valuable skill in the age of AI The five stages of the creative process — and the stage most people skip Three types of creative purpose: play, self-expression, and legacy How James used multiple AI tools alongside human collaborators to write, edit, and market SuperCreativity Bulk book sales, industry-specific editions, and revenue models for nonfiction author-speakers Practical tips for authors who want to break into professional keynote speaking You can find James at JamesTaylor.me. Transcript of the interview with James Taylor Jo: James Taylor is a nonfiction author, professional speaker, podcaster, and entrepreneur who helps people unlock their creative potential. He hosts the SuperCreativity Podcast and his latest book is SuperCreativity: Augmenting Human Creativity in the Age of Artificial Intelligence. Welcome to the show, James. James: Well, thank you for having me as a guest. I'm looking forward to this conversation today. Jo: It's going to be really good. First up— Tell us a bit more about you and how you got into writing and publishing. James: Well, today I'm a professional keynote speaker, so I deliver about fifty to a hundred keynotes per year in twenty-five-plus countries. Primarily I speak on creativity, innovation, and artificial intelligence. Go back into my deepest, darkest history—I actually used to manage rock stars. That was my old job. I used to be in the music industry for many, many years. I worked with members of The Rolling Stones, and for our listeners in the UK, I managed bands like Deacon Blue. Then I went to the dark side. In 2010, I moved to California to work in Silicon Valley, to work in the world of tech. That got me involved in artificial intelligence. Right about 2017, I was speaking at an event in San Francisco and someone came up to me and said, “You realise you could probably speak for a living, you could do this for a living.” So I thought, well, how does that work? And he told me. Then I embarked on the career that I have today, which is primarily as a speaker, with writing now coming a bit more to the fore. Jo: Wow, I remember Deacon Blue. James: Yes. Jo: “Dignity.” That's crazy. Very, very cool backstory there, but we'll come back to the career side of things. Let's get into super creativity, because my listeners are certainly creatives. Most of the listeners will have a book either on the way or they might even have lots of books. So we all do want to be super creative. How do you define creativity, and why is it important to keep focusing on this even if we do identify that way? James: For me, creativity is about bringing new ideas to the mind. Innovation is about bringing new ideas to the world, but without creativity, there is no innovation. So creativity is really the engine of innovation. Whether that is designing new products, new services, or creating new works of art and new books. The reason that creativity is becoming more important is because of what we're seeing right now in terms of artificial intelligence. AI is going to replace a lot of the non-creative tasks that we currently do in our jobs. If you look at things like the World Economic Forum, there was recently a study with a thousand global business leaders, and work from companies like LinkedIn—they all highlight that creativity is going to be one of the foremost important soft skills for this new future. So creativity, strangely, will actually become more important, not less important, as we go ahead. That's the creativity side. Probably for many of the listeners here, they'll consider themselves to be creative. That is not the norm. As I mentioned, I speak in about twenty-five countries a year, and if I ask the audiences—primarily corporate audiences—to put their hands up if they consider themselves to be creative, only between ten to forty per cent of the audience will raise their hands. So part of my job is to show them why they are more creative than they think they are and why we're all born with this creative potential. Then moving into the super creativity side, it's really to show them how they can augment that creativity by collaborating more deeply with other people or machines—things like artificial intelligence. So SuperCreativity, the book that I've written and the speeches I give on it, is really about how we can augment our individual creativity by collaborating more deeply with other people or artificial intelligence. For me, that's been the thing I've been fascinated by for the past few years, and probably for many of our listeners who are now using AI in their writing, their researching, and their marketing of their books, they're probably getting into this space as well. I really wanted to dive into that—both the collaboration with other people and with machines and AI. Jo: In terms of the super creativity then, do you have any practices or ideas? Before we get into collaboration, many of us authors work alone—and of course we can come back to the AI stuff in a minute—but in terms of super creativity, are there ways that we can even supercharge what we do already? Then, of course there are people listening who might not feel creative. So give us a few tips on how we can potentially change our mindset or become even more creative. James: In the book I talk about what I call the eight Ps of super creativity, which are purpose, personality, practice, people, process, place, product, and persuasion. Persuasion is really the marketing piece at the end. Probably the one that could be most useful to many listeners today is the practice piece—the practice or the process side of things. For many of us, what that usually consists of is just having some type of daily creative practice. Different people do it in different ways. Many of your listeners will know the works of people like Julia Cameron—the morning pages style of having some type of daily practice. Other people do it in slightly different ways. The process bit is really interesting. I talk about this creative process that we all have, and I talk about these five stages of the creative process. The first stage, let's say if we're writing a book, is really that preparation stage. That is usually the stage where we are trying to absorb as much information as possible about the thing that we're going to be writing about. The topic, if it's nonfiction, or going to the places, visiting the scenes that we're going to set certain things within for the book. So that preparation stage is really about absorbing as much information as possible from the outside. It's not going to look very creative. We're just absorbing at that stage. Now the mistake that a lot of people tend to make is they immediately try to jump from that preparation stage to looking to generate ideas. But what all the studies show us is we should spend a little bit of time in what we call the incubation stage. This is where it's often very useful if we've done some research, that we put things to one side for a little while, maybe a few weeks, move on to another project, think about something completely different. Your brain will continue to work in the background. Your unconscious brain will work on that content you've been absorbing. Then what often happens as a result of that is we come to this third stage, which is that insight stage—that aha moment. That happens for various different reasons and you can seed that in slightly different ways so you're more likely to get inspiration in your day-to-day work. Then as we know—as you are a writer of many, many books—many people think, “Well, that's it. I've done it. The idea for that book or that chapter has come to me.” That is really just the first five per cent of the process. The next stage is where we look at all the different ideas we have and decide which ones we want to pursue, which ones are going to make the grade. This is what we call the evaluation stage. Once we've done that, we move to that final stage, which is the elaboration stage. If it's a startup, this is when you're building your minimum viable product. As a writer, this is where you're actually doing the work, putting those words out onto the page. It's a very iterative process, so it's not necessarily linear. You'll go back and forth. Even as you're getting input from readers and audiences in that last stage, that is then giving you the material to move back to the preparation stage and think, “Oh, I wonder if this next book in this series, maybe I go in a slightly different direction with this character.” So each of those different stages, you can do different things to increase your levels of creativity. Jo: I love all of that, but can we go back to purpose? Because you mentioned that as one of the Ps and I think this is something that a lot of us need. As we are recording this in April 2026, the world is an interesting place. There are lots of things going on that have people worried. Well, we are not talking about politics, but I think one of the things that people struggle with is, what's the point in writing this story, for example, or what's the point in trying to get my words out there when things are difficult? I feel like coming back to purpose is perhaps the thing that helps people even take it into the process as you were talking about. And then of course, just from a practical angle— Is purpose about making money or reaching people? So maybe you could talk about the purpose side of things. James: Yes. So I talk about three different purposes, and it's not that there's just one that predominates, but usually there's one that maybe predominates on different projects. The first one is creativity as play. It's what we're basically, as humans, hardwired to do—this instinctive joy that we get just for creating for its own sake. There's nothing that really sits beyond that. We just have fun. We find pleasure in creating something. That could be a musician creating a piece of music, a sculptor creating a sculpture, an entrepreneur creating a new business or product or service. There's just this sense of play. One of the things I talk about in the book is this idea of being childlike, not childish. If you look at children, you see this very instinctively. If you see a three-year-old or a five-year-old, you give them some crayons and they will just naturally create. That's part of who they are and it's pretty abstract. Then what happens is they go to school and they're taught useful conventions—”this is how you should do it.” You even see their work start to change. You start to see them move from abstract paintings to more formal structures. Then you get your peer group, then you go to college or university and the world of work, and you're taught all these useful conventions. That's fine, but as adults, it is our responsibility to become what we call post-conventional, where we see these conventions as a useful signpost but we're willing to challenge them. We're willing to have a playfulness in what we do. So the first one is just this hardwired thing—creativity as play. The second one, and this is maybe for a lot of your listeners the reason that they are writers, is self-expression. It's a way of placing something out into the world. I was actually just in France recently, and I was talking to a young visual artist, a painter from Hungary, and she had to go up and give a speech. She really hated doing it. She was having to talk about her work and she was really uncomfortable. I could see the discomfort and my heart went out for her, because that is not the way she primarily expresses herself. She expresses herself through her art form, which is painting. For many of us, we might struggle to get on a stage, but we can express ourselves in the written word. We have something we want to say, a position we want to have, and we want to express that and get that out into the world. The final one is just this idea of legacy. That is not going to be for everyone. I can tell you, for me personally, legacy is not the reason that I write and do a lot of the stuff that I do. Maybe that changes—maybe as we get a bit older, we want to leave a body of work. So those are the three main purposes that we tend to see. Then you mentioned the financial side of what we do as well. This starts to come into that self-expression, because we need to be able to get people to buy our books or download our books and read our books in order to give us the ability to write new works and create new things. The financial side is an important component of it, but it is not the only one. I think there's a great question any writer should ask themselves. One of the first questions that I asked myself as a relatively new nonfiction writer is: why am I writing this book? What is the purpose of this book? For me, primarily it is a form of self-expression, and then you have to go, “Well, that's fine, but I also need it to have some type of financial basis for it.” It doesn't need to be the main driver of my income, but I need to have some type of revenue model. I'm happy to talk about revenue models, because probably the type of revenue model that I have as a writer is going to be different from other listeners. I tend to focus more on bulk selling of books rather than individual selling of books. Jo: Yes, I definitely want to come back to revenue models and business, but a few other things first. I want to circle back to collaboration, because I've certainly co-written with some humans, and I know a lot of listeners either have co-written or collaborated with other humans—and some of it works and some of it doesn't. You have some great information on human-plus-human creativity and collaboration. So maybe you could give us some tips on how we can be more effective collaborators with other humans. James: So there's a whole section about this idea of creative pairs. Often if you look at great creative work or innovative companies, very often when you strip it all back, you'll find at the core lots and lots of creative pairings. That is usually two different but complementary personalities who are willing to develop and challenge and improve each other's ideas. We think of Jobs and Wozniak in the world of business, or Warren Buffett and Charlie Munger. For authors, often that relationship is the work with their editor. There was a documentary I saw—I think it was a New Yorker documentary that came out a while ago—talking with a writer of history books about his relationship with his editor. It was a really beautiful relationship. These were two very different personalities, but what worked was the fact that they were different. A core component of having these creative pairings is a sense of trust—or what some people today would call psychological safety—that you are willing to challenge someone's ideas, but in a space of trust. The Germans have a great phrase for it. In English it translates as “someone to steal horses with,” which I love. Hopefully our listeners have that person where you can go to them and say, “I had this idea for a book or a chapter or a character,” and that person is a “yes, and.” Like, “Yes, and have you thought about doing it this way?” or “What would happen if you did this?” They stress test your ideas. They make your ideas better. For many of us, maybe it's our husbands or wives, our partners. Some of us are lucky enough to have editors. When I started rewriting this latest book, I actually had someone like that—a human, not an AI—that I worked with, especially on taking all these random thoughts and ideas I've been expressing in keynotes and putting them into more of a book form. The format and the structures that we use for telling stories in a speech are quite different from the structure that we would use for a nonfiction book. I didn't have as much experience there, so I wanted someone who could say, “Have you thought about structuring it this way?” or “This is a great story arc you might want to think about.” So I don't know, for you, who is your creative pairing? Who is your “someone to steal horses with”? Jo: Well, it's funny. I really think since the arrival of Claude Opus 4.6, it is absolutely Claude. James: Yes, yes. Jo: All the way. I mean, so we could come onto that next in terms of how AI has changed, because I do still work with a professional editor for both fiction and nonfiction, but it is very much in the “make my finished work better” stage. It is not in the exploratory phase. I find particularly the latest reasoning models to just be fantastic at this. And my Claude is not sycophantic. The Opus 4.6—I'm sure you've been using it too—it just doesn't behave in the way that a lot of people think these AIs did. They did behave like that, and now it's changed. So let's talk about that. What are your thoughts on collaborating more effectively with AI tools, especially as they become more and more powerful? As we record this, Claude Mythos has not come out, but it's certainly rumoured to arrive. I'm pretty excited. James: So because I've been doing this AI thing for a little while, it's given me the ability to experiment with things—the early versions of what many people are using today. I'll give you an example. Even before I started writing the book, I decided to write a book proposal. Even though I could pretty much sense I wanted to independently publish this book through my own publishing company, I thought it's a good practice to put it down into a proposal form, even though I don't go to a traditional publisher or a hybrid publisher. One of the things I did within that was get a sense of who my ideal readers are. I used a very early version—this was a few years ago—of an IBM AI tool, creating what we call a psychometric map of my ideal reader. This basically tells me, over about seventy-two different factors, how this person thinks, how they feel, what their value system is, very broadly for my ideal reader. I pulled in different sources. I knew the kind of magazines and books they were reading and what their general worldview was. So I created this—going one step beyond just creating your ideal reader to really understanding their psychometrics. I do this in my keynotes too. Before I ever give a keynote or an important pitch or a presentation, I use AI to analyse the psychometrics of the audience I'm going to be speaking to. This might tell me, for example, this audience values humour a little bit more, or this audience values a bit more practicality so they want actionable next steps, or this audience is going to be a little bit authority-challenging so they're going to push back. So even in those very early stages, just starting to think about the book—who was I writing this book for, what was the purpose of the book—I was using AI to understand the psychometrics of my absolutely perfect, ideal reader. I gave her a name. It was a female reader. There was someone similar to her that I already knew. Probably for some of your listeners, they do this instinctively anyway. They maybe have a person or a few different people they think of in their head. Then from that stage, because I've been delivering lots and lots of keynotes—and this may be an important distinction in the way that I have decided to write books as opposed to how other people write books—my family were all jazz musicians. The difference between a rock musician or a pop musician and a jazz musician is this: a rock or pop musician will go into the studio, create this opus, this work, and then tour that for the next two years. A jazz musician, on the other hand, goes out and performs the songs and the things from the album that they're eventually going to create hundreds of times, thousands of times, to find out what works with audiences, and then they go into the studio and record the stuff that works best. So I created a book more like a jazz musician. I'd delivered keynote versions of the book hundreds of times before I ever decided to actually write the book. So it had been stress-tested with real people to a certain extent. Then, getting into it, I thought—well, what works as a keynote is not necessarily going to work as a structure for a book. So what I did was start using ChatGPT models at that point to think about the structural edit of the book. What was the structure going to be? What was great is you can basically feed it every single keynote you've given over the years, all the notes, everything you've done, and it could start to give me something to riff with and really get into thinking about how I was going to create this. I was using it a little like that creative pairing we spoke about earlier. Then once I'd done that—so I've now got an idea of a structural edit essentially—I then go back and speak to some humans about it. “What do you think about this?” “What do you think about that?” And try some things out over dinner conversations. “I'm thinking about doing this—what do you think?” Then once I did that, I just did the thing that I really didn't want to do, but I guess you absolutely have to do: sit in a seat for multiple weeks and just get that crappy first draft done. That was just me writing, from my voice, in my way of doing things. Every so often I would use an AI to research a particular thing, but I didn't want to slow down the pace too much. I was focused on getting that word count done. Once I had the first draft, I then brought the AI back in. In this case, I was still using OpenAI at this stage, to act more like an editor. To tell me what was weak about the book. At this point I was starting to give it the overall framing. What was weak, what chapters needed to be improved. I then went back, started reworking each of the chapters, and worked chapter by chapter using that AI as a sparring partner. But once again, the AI is not really writing my words for me. It's maybe saying, “This part could be said better. You might want to think about doing it this way,” or “You are missing a really powerful case study or example here,” or at the very end of each chapter, I have actionable next steps, and “You're missing some things here.” So I've gone through that entire process of writing, and now I'm essentially at the second draft. At this point, what I'm doing is using another AI tool—Claude, in this case—to have a different perspective on it. I gave it the work. I mentioned a couple of editors that I really respect and different writers I respect and said, “I'm going to create a virtual beta readers group. Give me feedback on this now.” For someone that's listening to this, and we're recording this in April 2026, here's some good news for you. There are now a bunch of tools out there that use AI swarms, as we call them. You can basically feed it your book and it will create synthetic readers—thousands and thousands of synthetic readers that read your kind of style of book—and it will then give you feedback from these synthetic readers. Essentially, I was just doing an early version of that. So I got the feedback from the synthetic readers, the AI readers, and then reworked a little bit. Some of the stuff I just decided not to do because it didn't align with what I was trying to say in the book. Then the next stage was I had a beta reader group of about thirty human beta readers—my ideal readers. I sent the book to them, they gave me feedback. I then used AI to give me an overview report of all their feedback, and then I was able to go back into reworking the book. That's still really just draft three of the book, not the final book at this stage. But just to give everyone a sense of opening up the process: you could see how the human and machine were working together. Jo: Yes, I love that. I also often say to people who are speakers first that you can, if you have recordings of your talks or if you use your slide decks to record them as MP3s and then just use that transcript as the basis of a draft. Obviously it's not the book or a chapter, but it can actually preserve your voice—your speaking voice—which I think can be really effective for speakers. I like your multi-step process there. And then of course, if you have audience avatars in AI, that can help you design your book marketing. So take this into book marketing and how you're doing that. James: So I still decided to go old school with a human editor—a book editor that someone had recommended to me. I used that human book editor just to go through the book. At that point we're talking about style, some stylistic things that we wanted to do, and they can pick up other things as well. So I've got that book, and then I'm obviously starting to use AI to understand what tags, what kind of copy do I want to have in terms of putting it onto Amazon, putting it onto IngramSpark, and all these other platforms I want to put it out into. I'm using Claude here in particular—and with Claude, you have something called Cowork. It wasn't quite fully happening at that point, but there were early versions of it and Claude Code—to almost start working with and creating a virtual marketing team. I give it the book and then they could start thinking about: what is the marketing strategy for this book? What does the campaign look like? What are the things that we need to do? That was then starting to break it down. We're now three months out or so before the book is due to get released, and I'm starting to deploy that particular campaign. So for example, I'm on a podcast right now, and we try different versions. We have a human going out and reaching out to potential shows for me to be a guest on, but I also have an agent. There's also one going out and finding and researching podcasts and reaching out to those podcast hosts to have me as a potential guest. So they're doing some of the tactical work there at the same time. One mistake I made—and I don't know if you've experienced this as well—if I was to go back, one thing I would do differently is this: I decided to record the audiobook version after the physical book was already committed and ready to go out. Jo: Mm-hmm. James: And I noticed so many small errors or things I would change after having spent two days in a studio recording the voice for the entire book—changes I would have made. This is something other people did ask me: why are you not using ElevenLabs or an AI clone of your voice to read the script? There are some things I feel quite personal about, and my voice is one of those things. As a professional keynote speaker, I decided I wanted to keep that and have it in there. So it's going to be different for everyone which things they decide to offload to AI, which things they decide to give to a human member of their team, and what they decide to keep to themselves. Jo: Yes, I mean, I human-record my nonfiction, but I have an AI voice clone with ElevenLabs for my fiction now. But obviously, for people listening, you can't put an ElevenLabs voice-cloned audiobook on Audible, and a lot of your sales will be on Audible, especially for a book like this. So I think that's also important. I agree with you on doing the audio edit. There's always things you want to change. But as you mentioned, you're self-publishing this, so you can just go in and change your files. James: Yes, and that was the other reason, and this was part of the marketing—now we're moving into the marketing and the business model behind the book. For me, the book doesn't have to be a financial driver in its own sense. The way that I sell books, and usually people like myself—professional speakers—is we bulk sell books to our clients. Let's say I'm speaking at four different events this month. Each has about a thousand people at them. Those organisers will buy, say, a thousand copies of the book. So at the end of that month, you might have sold four thousand copies—not individual copies. Anything that sells on Amazon or in other places is almost like a positioning piece. Obviously you want people to buy the book and learn things from the book, but in terms of the distribution model, it's slightly different because I'm primarily selling through bulk sales. Now, here's a little twist you can do on this, and this is a decision I made even before we released this version of the book. I speak to lots of different industries. There was a speaker and author—I've forgotten his name now, I think he was from Florida—and what he decided to do was to write a slightly different version of his main book every year, but for a different industry. So what this allows him to do is, let's say in my case, I'm doing a version of the SuperCreativity book just for legal professionals because I speak to a lot of law firms and legal groups. I've already started working on a version of the book which is a little bit more attuned to that audience. As a speaker, it allows me to go to all these law firms and legal associations and bar associations and say, “Hey, I've just written the book on creativity and artificial intelligence for the legal industry.” That makes you a very bookable proposition for a client. And then obviously you can sell books from that as well. And that's before we get into the foreign language versions. That's just a model that happens to work pretty well for my part of the industry, but obviously it's going to be very different for other types of authors. Jo: No, I think that's great. For nonfiction authors, as you say, there are different revenue models. Your income, I guess, would be what, eighty, ninety per cent speaking revenue? Or do you have other things as well? James: Yes, primarily it's the keynote speaking, and anything that comes from the back of that. Sometimes it's boardroom advisory work that I do as well. But primarily it's the speaking side. So really the book is just the simplest form to get my ideas out and the most affordable form. Jo: Mm-hmm. James: Because the other thing is, you want as many people getting your ideas as possible, and there is no better, more affordable way of getting someone's ideas out there than in the form of a book. I think it's just the most unbelievable transmitter of knowledge—a book. That's why I love to write the book as well. A lot of my friends say, “Listen, books are old hat. You don't need to do a book any more. You can do these other things, other forms, online courses.” I've done lots of online courses in the past and membership sites and all those things, but there's just something that is great about a book—to be able to summarise your ideas at a particular point in time. It's also a great transmitter of value to other people. And it is affordable. Any book, someone can download a book on Audible or wherever they want—that's just an affordable way of absorbing that content. Jo: Yes. Well, of course we are all fans of books here. I do speak—I don't tend to do keynote speaking. I do more content speaking at conferences. For people listening, keynote speaking is where you tend to get the higher revenue. So if people listening have books already—let's say they have nonfiction books or even fiction books that could be turned somehow into different topics—if people want to get booked for speaking gigs, preferably ones that pay— How would you recommend authors think about moving into speaking if that's something they want to do? James: So obviously it's much easier for nonfiction authors to do that. I mean, I'll give you an example. I was speaking at an event last week in New York for L'Oréal, the hair care and cosmetics company. They had six different speakers. One of them was a speaker on macroeconomics and geopolitics. Another was an expert on communications. Another was an expert on AI. Another was an expert on storytelling. So you have to think: does my topic have value for that type of audience—that corporate audience? An easy way of finding that is if you just go onto any of the speaker bureau websites, type in “speaker bureaus,” look for the speaker bureaus, and then type in your topic area—emotional intelligence or whatever the topic area is—and look at the other speakers. See if there is obviously a number of speakers talking on this area. Importantly, look at how busy they are and look at their fee levels as well. I did an online summit a few years ago called the International Speakers Summit, where I interviewed a hundred and fifty of the world's best professional keynote speakers. I interviewed Sally Hogshead, who's an author and a speaker, and she said to me, “James, you're going out speaking about creativity, but if you just twisted it a little bit and spoke more in terms of innovation rather than creativity, you would earn an extra five thousand dollars per keynote.” So creativity and innovation—an extra five thousand dollars. That's just a simple thing that, as you get to understand the industry, you learn. Then once you do that, it's like any business—you have to treat it like a business, obviously. What makes someone a great storyteller on stages is not the same as what makes a great storyteller on the written word. So depending on where you're at, you might need certain training and skills development. If you are listening to this from America, there are things like the National Speakers Association, the NSA. If you're living in the UK, the Professional Speakers Association. These are great ways just to develop your skill set and learn from other professional speakers. Here's the good news, I didn't know anything about professional speaking until 2017–18, and it was only from having a conversation with someone who said, “Listen, you have some original thoughts. You can get paid to speak about this on stage.” Then I spent the next year really researching and understanding and looking at how to do it and creating a minimum viable product—a speech—that was a very short period of time, a year. Most of the listeners here have gone through that process of writing a book, which takes many, many months. So you have the stamina to do this type of work. You just need to find out where you fit. I thought I was going to be a speaker in marketing. I thought that was going to be my thing. And it turns out that's not what the market wanted from me. They wanted me to talk about creativity and artificial intelligence. So you have to listen to the market, like you have to listen to your readers. Jo: Yes, I think that's really interesting. I was also a member of the PSA here, and I learned in Australia with the NSAA as it was. James: Yes. Jo: And that thing about who you speak to—I mainly speak to author conferences, who, I just want to be frank, don't pay very well, if at all. So exactly what you said there— If you want to be a highly paid speaker, you have to pick the audience who's going to pay, as well as a topic that works with them. It is a very different thing to writing a book, I think. James: It is a different model. This is what was interesting when I interviewed those hundred and fifty professional speakers—the thing that came back loud and clear is there is a model to suit everyone. Jo: Mm. James: So the model that works for me—getting paid high fees to go and travel around the world, speaking on stages to primarily corporate audiences—that is not the only model. There is another model, which is called the “sell from the stage” model, where you maybe don't get paid anything to go and speak on the stage, or very little, but what you're doing is you're selling your consulting, your online course, your books, your other products from the back of the stage. That's another model as well. I have friends who have young families and they are writers and they don't want to schlep on planes like I do. I know one speaker in particular who never leaves his own city. He is a very successful professional speaker. He happens to live in Orlando, Florida, which is one of the busiest cities for conferences. So literally, he's home with his kids every night. He gets to do all this cool stuff he wants. He never has to step on a plane if he doesn't want to. That just shows you the range. I remember I once interviewed a person whose title was a Buddhist monk, French speaker, and author. He figured out he could live very affordably by living in Thailand. So he lives in Thailand for part of the year and he's very into meditation, mindfulness, yoga, and writing. He figured out he only had to give two keynotes per year to pay for his entire lifestyle. That was it. So that gives him a lot of freedom. He does those two corporate keynotes a year and for the rest of the year he's doing his yoga, his meditation, his writing, and surfboarding, whatever he's into as well. So you can see there's a whole range of different ways you can design that life. Jo: Yes, we talk a lot about definition of success and it's great to hear those different examples. So before we finish up, I just want to come back to your journey into the writing side, into books and self-publishing. We all understand, me and the listeners, how hard it is to write a book and also to market a book, but we've got the bug. So we wonder: how much have you got the bug? Do you plan on doing more writing, more books, or do you still want to lean more heavily into speaking? James: Primarily the income for me will still come from speaking. I remember listening to Elizabeth Gilbert once when she talked about her writing. She said she always wanted to have other things, so she never had to push onto her writing that it had to be the income stream for her. If it was successful, great, that's fantastic. So I have a little bit of a similar view to that. In terms of my own writing, I've got about five different nonfiction book ideas I'm now looking at. Some of them relate to speeches that I already do. Some don't. I'm looking at different versions of the SuperCreativity book, so there'll be other versions coming out—different industries, different languages. That gives you a few years of work. The other side that I want to develop is the fiction writing side. I'm already starting to work on a fiction book at the moment—a little bit like this idea of one for them, one for me. Jo: Mm-hmm. James: So one for them is for the corporate audience, that world that I live in, and the other one is for me, for my own creativity. My hope—and I don't know, maybe we need to speak in a year's time when I've written and published it—is that by doing the fiction side, it will make me a better storyteller on stages as well for my corporate audience. It will help me understand story arcs, slightly different ways of expressing stories, building emotion, building the anti-hero characters within a book, for example. So I'm hoping that they both feed off each other. But we will see. Jo: Yes, we will. All the best with that. So where can people find you and your books and everything you do online? James: The easiest place to go is JamesTaylor.me, and you can find the book, which is called SuperCreativity, there. Or just go to wherever you buy your books—your local independent bookstore—and get a copy of SuperCreativity. The audiobook may already be out by the time you're listening to this as well. If you want to learn a little bit more, we also have a podcast called the SuperCreativity Podcast, where I interview lots of wonderful guests talking about this area of super creativity. Jo: Well, thanks so much for your time, James. That was brilliant. James: Thank you, Joanna. Thanks for having me as a guest on the show.The post SuperCreativity And KeyNote Speaking With A Non-Fiction Book With James Taylor first appeared on The Creative Penn.

There's a scene in the Steve Jobs biopic where Steve Wozniak asks Jobs what he actually does. Wozniak understood his own role clearly: he was an engineer. He wrote code. He built things. But Jobs? Jobs described himself as the conductor of an orchestra. I've been thinking about that exchange a lot lately, because I think it captures exactly where we're all heading. AI isn't turning us into supercharged doers. It's turning us into conductors, and that requires a completely different mindset. The problem nobody talks about I've been coaching a number of people on integrating AI into their workflows recently, and I keep running into the same pattern. The people who aren't getting time savings from AI aren't failing because they don't understand what it can do. They're not failing because they lack access to the right tools. They're failing because they're fundamentally disorganized. AI is only as useful as the foundation it's built on. If your work processes are messy, your context is scattered, and your task management is a loose collection of mental notes and sticky tabs, AI can't do much for you. It needs structure to work from. I hear this complaint constantly: “AI has been mis-sold to me. I'm not saving any time.” But it hasn't been mis-sold. It's just that AI can only deliver on its promise if there's an organized workflow underneath it. Build that first, and the time savings follow. That's why I've written before about building AI playbooks and developing proper AI skills. These aren't nice-to-haves. They're the infrastructure that lets AI actually work. The conductor problem But here's the deeper shift, the one that's genuinely harder to adapt to. When you're doing tactical work, you're usually focused on one or two tasks at a time. You go deep, you finish a thing, you move on. It's cognitively manageable. A conductor doesn't work like that. A conductor holds the entire orchestra in mind simultaneously: what the strings are doing, where the brass comes in, what the percussion is building toward. They're not playing any of the instruments. They're managing the relationships between all of them. In a world of AI agents, we're going to be managing multiple projects running in parallel, all moving faster than any human team would. We're task-switching constantly. We're accountable for outputs we didn't directly produce. And we have to resist the urge to dive in and do the work ourselves, because that's precisely where we get bogged down. The design leader parallel This isn't a new challenge, as it happens. Design leaders face exactly this transition when they move from senior practitioner to managing a team. I've watched a lot of talented designers struggle with that shift. They get promoted because they're brilliant at the work, and then they spend the next year quietly sneaking back into Figma because they can't let go of doing. They micromanage their reports. They redesign things that were already fine. They can't operate at the level of abstraction that leadership requires. Working with AI agents is going to feel very similar. The temptation to wrestle with the AI until it produces exactly the output you had in your head, rather than accepting a good result and moving on, is going to be real. Learning to let go of that control is a skill in itself. The good news is that unlike a team of designers, you can't upset an AI agent by micromanaging it. But you can waste enormous amounts of time doing it, and that defeats the whole point. AI burnout is already real There's one more aspect of this I want to flag, because I don't think it gets talked about enough. When you're managing a team of agents all moving at AI speed, the cognitive load is significant. You're context-switching constantly across multiple workstreams. Things are completing faster than you can review them. It's relentless in a way that managing a human team simply isn't. This is what's increasingly being called AI burnout. Learning to pace yourself, to batch your reviews, to build in breathing room: these are the organizational skills that will separate people who thrive in an AI-augmented world from those who burn out in it. Where to start If I had to distill this to one practical thing: start building the habits of a manager now, before the agents fully take over. Get organized. Build the infrastructure that AI needs to work from. Practice delegating, even to imperfect tools, rather than doing everything yourself. Work on your ability to hold multiple projects in your head without losing the thread on any of them. If you want help working through that transition, I offer coaching specifically for this. It's something I'm increasingly focused on, because I think it's one of the most valuable things I can help people with right now. I'm also running a workshop with Smashing Magazine in July. Modern UX Practitioner covers a lot of this ground in a more structured way, if that's more your style. The shift from doer to conductor is coming whether we prepare for it or not. The people who handle it best will be the ones who start thinking like managers now.

What if ransomware did not begin with criminals, but with curiosity? In this episode of Breaking Math, Autumn and Noah talk with Anja Shortland, professor of political economy at King's College London and author of Dark Screens. This conversation explores how playful hacking evolved into professionalized cybercrime, why ransomware gangs operate like morally questionable internet startups, how cryptocurrency made ransomware scalable, and why hospitals, governments, universities, and critical infrastructure remain especially vulnerable. We also dig into the mathematics behind encryption, asymmetric cryptography, game theory, negotiation, cyber insurance, and the uncomfortable trade-offs between freedom, privacy, and regulation. Chapters 00:00 The origins of ransomware and early hacker culture 02:13 The evolution of ransomware attacks since 2013 03:14 The paradox of cybercriminals as entrepreneurs 06:19 Early hackers: Steve Jobs and Wozniak as pioneers 12:34 The moral and legal landscape of hacking and cybercrime 13:39 The importance of cybersecurity awareness for individuals 15:03 The arms race: attackers vs defenders and the role of math 16:02 The technological innovations behind ransomware 19:21 Asymmetric encryption and cryptocurrency in ransomware 20:53 Bitcoin and the dark web: enabling cybercrime 22:45 The impact of AI on future cyber threats and defenses 34:07 The future of ransomware and cybersecurity challenges Follow Anja Shortland on LinkedIn (https://uk.linkedin.com/in/anja-shortland-53133b231)Book (https://amzn.to/4d6pB4X) Follow Breaking Math on Substack (https://breakingmath.substack.com/) Twitter (https://x.com/breakingmathpod) X (https://www.instagram.com/breakingmathmedia/) Bluesky (https://bsky.app/profile/breakingmath.bsky.social) Website (https://www.breakingmath.io/) Follow Noah onInstagram (https://www.instagram.com/profnoahgian/)Twitter (https://x.com/ProfNoahGian)Bluesky (https://bsky.app/profile/profnoahgian.bsky.social)Follow Autumn on X (https://x.com/1autumn_leaf) Bluesky (https://bsky.app/profile/1autumnleaf.bsky.social) Instagram (https://www.instagram.com/1autumnleaf/) Substack (https://substack.com/@1autumnleaf) email: breakingmathpodcast@gmail.com

**Palabras clave:** - **Wozniak**, **Jobs**, **Apple II**, **Macintosh**, **Xerox**, **Bill Atkinson**, **Copland**, **Schooley** --- ### El mito del garaje y la verdad de Hewlett-Packard ### Ingeniería minimalista y la revolución visual ## BASIC en la ROM: la “memoria del idioma” ### ️ Ranuras de expansión: crecimiento sin límites ### Steve Jobs: el puente entre técnica y mercado ### La cultura corporativa tóxica y la presión de los plazos ### Xerox y la transferencia de tecnología ### Bill Atkinson y la superposición de ventanas ### ⚖️ Conflicto interno: Jobs vs. Schooley ### ️ Fracasos del sistema operativo Copland y la “muerte piadosa” ### Patrones útiles observados ### ✅ Conclusión

È arrivata la conferma ufficiale da parte del governo iraniano che le navi che vogliono attraversare lo stretto di Hormuz devono pagare il pedaggio in bitcoin, perché 'unica valuta che resiste a confische e sanzioni. Questa controversa notizia sta facendo il giro del mondo. Ne parliamo insieme.Inoltre: due nuovi paper scientifici smontano nuovamente la quantum FUD, diversi smart contract shitcoin hackerati, fishing sull'App Store di Apple con una falsa app di Ledger, e una sentenza inglese definisce il concetto legale di proprietà realtivo a Bitcoin.It's showtime!

Today, Apple is a $3.5 trillion company with over 150,000 employees worldwide. Fifty years ago, it was two Steves – Jobs and Wozniak – working out of a Los Gatos garage. (All great Silicon Valley origin stories seem to include a garage.) Since its inception, Apple has not only introduced culture shifting technology like the Macintosh computer and iPhone, it has also influenced how we live here in the Bay Area, on the edge of the continent and a future being cast by technologists, innovators, and entrepreneurs. We talk about the influence of Apple. Guests: Margaret O'Mara, professor of American History, University of Washington; author, "The Code: Silicon Valley and the Remaking of America" Hansen Hsu, curator, Software History Center at the Computer History Museum; former Apple employee; historian and sociologist Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of Mark and Pete, we look at the astonishing story behind Apple's 50th anniversary—and the man who walked away from one of the greatest opportunities in modern history.When Steve Jobs, Steve Wozniak, and Ronald Wayne founded Apple in 1976, it looked like a modest garage project. Within days, Wayne—older, cautious, and understandably wary of financial risk—sold his 10% stake for around $800. Today, that decision would be worth roughly $300–370 billion, making it perhaps the most expensive “better safe than sorry” moment in business history.We explore the founding of Apple, the early dynamics between Jobs and Wozniak, and the deeper reasons behind Apple's extraordinary success: design simplicity, product integration, cultural vision, and timing. Apple didn't just build computers—it reshaped how ordinary people relate to technology.But beneath the business story lies a sharper question. Was Wayne foolish or simply prudent? And where is the line between wisdom and fear?Drawing on Ecclesiastes 11:4, we reflect on the danger of waiting for perfect conditions before acting. There is a kind of caution that protects—and another that quietly closes the door on what might have been.This episode considers risk, opportunity, and the cost of hesitation in a world where outcomes are rarely obvious at the start.Sometimes the difference between history-makers and spectators is not intelligence, but action.And sometimes, the greatest losses are not the ones we suffer but the ones we carefully avoid.

El 1 de abril de 1976, tres personas firmaron un papel en un garaje. Hoy, es una de las empresas más valoradas del mundo. En este episodio especial de cumpleaños recorro los 50 años de Apple desde el único ángulo que de verdad importa: el software. El código que hubo detrás de cada producto. Las decisiones técnicas que nadie cuenta y que lo explican todo. ¿Sabías que el Apple I nació porque Wozniak quería programar en BASIC un videojuego que había diseñado en hardware para Atari? ¿Que escribió su propio intérprete de BASIC a mano, instrucción a instrucción, traduciendo ensamblador a código máquina en papel, sin ninguna herramienta? ¿Que el primer pedido del Apple I acabó en sorpresa porque Terrell esperaba un ordenador completo y recibió una placa de circuito? ¿Sabías que el sistema operativo que hoy corre en tu iPhone lo construyó Jobs cuando lo echaron de Apple? ¿Que Apple compró NeXT porque su propio proyecto interno de nuevo sistema operativo —500 ingenieros, 250 millones de dólares al año— fracasó sin lanzar nada? ¿Que iOS nació de la competición interna entre dos equipos, uno liderado por Tony Fadell con el OS del iPod, y otro por Scott Forstall con Mac OS X comprimido, y Jobs eligió la opción más arriesgada? ¿Sabías que Chris Lattner pasó año y medio construyendo Swift en secreto, sin contárselo a nadie, ni a sus compañeros más cercanos? Y que Jobs mató voluntariamente el iPod —cuando representaba casi la mitad de los ingresos de Apple— porque sabía que si no lo hacía él, lo haría el mercado. 50 años de Apple contados desde donde nadie los cuenta: desde dentro del código.

David Pogue discusses his new book, Apple: The First 50 Years, covering the inspiration behind it, the unusual format, and the research required to assemble its stories and images. The discussion explores Apple's greatest turning points, quirky Steve Jobs anecdotes, unseen prototypes, and the company's enduring mission. The conversation also looks at why Apple inspires such loyalty, scrutiny, and fascination across generations.  This edition of MacVoices is brought to you by the MacVoices Dispatch, our weekly newsletter that keeps you up-to-date on any and all MacVoices-related information. Subscribe today and don't miss a thing. Show Notes: Chapters: [0:00] Introduction to David Pogue and the new Apple history book [1:18] How the idea for the 50-year Apple book began [2:29] The book's unusual format and non-linear design [4:01] Apple as the greatest turnaround story in business [5:57] The story behind the iMac name [7:00] Rare photos, prototypes, and early iPod concepts [9:26] The challenge of gathering and licensing images [11:10] Printing decisions, color production, and book pricing [12:29] Steve Jobs' quirky side and the Mr. Macintosh story [14:41] Wozniak, pranks, and Jobs' lesser-seen personality [16:23] Lessons from Apple's history and enduring mission [18:45] Apple's obsession with excellence and product accuracy [19:34] Why Apple draws so much scrutiny and devotion [21:38] Final thoughts on the book's value and impact Guests: David Pogue is a seven-time Emmy-winning correspondent for CBS Sunday Morning. He's also a New York Times bestselling author, a five-time TED speaker, and host of 20 NOVA science specials on PBS. From 2000 to 2013, he was The New York Times weekly tech columnist. He's written or cowritten more than 120 books, including dozens in the Missing Manual tech series, which he created in 1999; six books in the For Dummies line (including Macs, Magic, Opera, and Classical Music); two novels; his three bestselling Pogue's Basics books of tips and shortcuts (on Tech, Money, and Life); his practical guide to the climate crisis, How to Prepare for Climate Change; and his 2026 magnum opus, Apple: The First 50 Years. After graduating summa cum laude from Yale in 1985 with distinction in music, Pogue spent ten years conducting and arranging Broadway musicals in New York. He has won a Loeb Award for journalism, two Webby awards, and an honorary doctorate in music. He lives with his wife Nicki near New York City. Links: Apple: The First 50 Years by David Poguehttps://amzn.to/4m04rJL David Pogue.comhttps://davidpogue.com   Become a MacVoices Patron on Patreon: http://patreon.com/macvoices Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:     http://macvoices.com      Twitter:     http://www.twitter.com/chuckjoiner     http://www.twitter.com/macvoices      Mastodon:     https://mastodon.cloud/@chuckjoiner      Facebook:     http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:     http://www.facebook.com/macvoices/      MacVoices Group on Facebook:     http://www.facebook.com/groups/macvoice      LinkedIn:     https://www.linkedin.com/in/chuckjoiner/      Instagram:     https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes     Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Explore 50 years of Apple innovation with Steve Wozniak, co‑founder of Apple. From the Apple I and II to the iPhone and beyond, Wozniak shares untold stories, his views on accessibility, and the future of personal tech. Steven Scott and Shaun Preece celebrate Apple's 50th anniversary with an extended conversation with Steve Wozniak. Wozniak reflects on the early days of Apple, his passion for making technology accessible and affordable, and the revolutionary impact of the Apple II on gaming and home computing. He discusses universal access, the rise of VoiceOver, and how tech empowers blind and visually impaired users. Woz also speaks candidly about privacy, ownership of digital media, AI, and the shift from personal computing to cloud‑based services. He shares personal anecdotes about the Homebrew Computer Club, his approach to invention, face blindness, and how near‑death experiences shaped his life. The episode ends with reflections on the Mac Pro's discontinuation, the rise of the MacBook Neo, and where Apple is headed next. ----Follow on:YouTube: https://www.doubletaponair.com/youtubeX (formerly Twitter): https://www.doubletaponair.com/xInstagram: https://www.doubletaponair.com/instagramTikTok: https://www.doubletaponair.com/tiktokThreads: https://www.doubletaponair.com/threadsFacebook: https://www.doubletaponair.com/facebookLinkedIn: https://www.doubletaponair.com/linkedin Subscribe to the Podcast:Apple: https://www.doubletaponair.com/appleSpotify: https://www.doubletaponair.com/spotifyRSS: https://www.doubletaponair.com/podcastiHeadRadio: https://www.doubletaponair.com/iheart About Double TapHosted by the insightful duo, Steven Scott and Shaun Preece, Double Tap is a treasure trove of information for anyone who's blind or partially sighted and has a passion for tech. Steven and Shaun not only demystify tech, but they also regularly feature interviews and welcome guests from the community, fostering an interactive and engaging environment. Tune in every day of the week, and you'll discover how technology can seamlessly integrate into your life, enhancing daily tasks and experiences, even if your sight is limited."Double Tap" is a registered trademark of Double Tap Productions Inc. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

David Pogue discusses his new book, Apple: The First 50 Years, covering the inspiration behind it, the unusual format, and the research required to assemble its stories and images. The discussion explores Apple's greatest turning points, quirky Steve Jobs anecdotes, unseen prototypes, and the company's enduring mission. The conversation also looks at why Apple inspires such loyalty, scrutiny, and fascination across generations.  This edition of MacVoices is brought to you by the MacVoices Dispatch, our weekly newsletter that keeps you up-to-date on any and all MacVoices-related information. Subscribe today and don't miss a thing. Show Notes: Chapters: [0:00] Introduction to David Pogue and the new Apple history book [1:18] How the idea for the 50-year Apple book began [2:29] The book's unusual format and non-linear design [4:01] Apple as the greatest turnaround story in business [5:57] The story behind the iMac name [7:00] Rare photos, prototypes, and early iPod concepts [9:26] The challenge of gathering and licensing images [11:10] Printing decisions, color production, and book pricing [12:29] Steve Jobs' quirky side and the Mr. Macintosh story [14:41] Wozniak, pranks, and Jobs' lesser-seen personality [16:23] Lessons from Apple's history and enduring mission [18:45] Apple's obsession with excellence and product accuracy [19:34] Why Apple draws so much scrutiny and devotion [21:38] Final thoughts on the book's value and impact Guests: David Pogue is a seven-time Emmy-winning correspondent for CBS Sunday Morning. He's also a New York Times bestselling author, a five-time TED speaker, and host of 20 NOVA science specials on PBS. From 2000 to 2013, he was The New York Times weekly tech columnist. He's written or cowritten more than 120 books, including dozens in the Missing Manual tech series, which he created in 1999; six books in the For Dummies line (including Macs, Magic, Opera, and Classical Music); two novels; his three bestselling Pogue's Basics books of tips and shortcuts (on Tech, Money, and Life); his practical guide to the climate crisis, How to Prepare for Climate Change; and his 2026 magnum opus, Apple: The First 50 Years. After graduating summa cum laude from Yale in 1985 with distinction in music, Pogue spent ten years conducting and arranging Broadway musicals in New York. He has won a Loeb Award for journalism, two Webby awards, and an honorary doctorate in music. He lives with his wife Nicki near New York City. Links: Apple: The First 50 Years by David Pogue https://amzn.to/4m04rJL David Pogue.com https://davidpogue.com   Become a MacVoices Patron on Patreon: http://patreon.com/macvoices Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:      http://macvoices.com      Twitter:      http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices      Mastodon:      https://mastodon.cloud/@chuckjoiner      Facebook:      http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:      http://www.facebook.com/macvoices/      MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice      LinkedIn:      https://www.linkedin.com/in/chuckjoiner/      Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Hoy se celebran cinco décadas de Apple, un periodo en el que la empresa de Cupertino ha transformado profundamente la tecnología gracias a avances en computación y telefonía. Durante este tiempo ha pasado de ser un proyecto modesto a convertirse en una de las compañías más valiosas del planeta. Todo comenzó con la visión de dos jóvenes estudiantes, Steve Jobs y Steve Wozniak, quienes abandonaron sus estudios para crear una firma que cambiaría la historia. Durante años se pensó que el origen estaba en un garaje, pero esa idea no es del todo cierta. Wozniak ha explicado repetidamente que aquel espacio en Los Altos, California, era solo un lugar de reunión y a veces servía como almacén de piezas. En realidad no existía un sitio único de trabajo, aunque la historia se difundió tanto que incluso fue reconocido oficialmente como punto histórico. Así arrancó todo: el 1 de abril de 1976, cuando Jobs, Wozniak y Ronald Wayne fundaron Apple Computer Company. El primer producto fue el Apple I, diseñado por Wozniak en su tiempo libre mientras trabajaba en Hewlett-Packard. Aunque apenas se vendieron unas doscientas unidades a una tienda local, ya mostraba rasgos de la creatividad que definiría a la empresa. Era un equipo que no requería ensamblaje complejo, bastaba añadir monitor y teclado. Ocho años después apareció el Macintosh, que introdujo ventanas, iconos, menús y un puntero, en contraste con los sistemas basados en comandos. Además, incorporó el uso del ratón y destacó por un diseño más atractivo que el de sus rivales. Décadas más tarde, el iPhone revolucionó la telefonía al popularizar una pantalla táctil manejada con los dedos y un navegador web completo como Safari. A pesar de no ser el primero, redefinió la experiencia móvil. Tras medio siglo de avances, surge la pregunta: ¿queda algún límite tecnológico que Apple no pueda intentar superar? en los próximos años de innovación constante global

A 214 pounder! Chris tries to talk about tech stuff. ALSO: Wozniak: good guy? PLUS: Greg reveals his nom de pleur?!?!?Song of the week - The Alcohol Stuntband "Arenacross" - downloadable mp3 on Patreon!Cold Brew Patreon: Patreon.com/ChrisCroftonChannel Nonfiction: ChannelNonfiction.com

Episode 87. Simon Wozniak

Documentary filmmaker Adam Bhala Lough joins the Chuck ToddCast for a provocative, darkly funny, and unsettling conversation about AI, power, and the people building the future faster than anyone can regulate it. Lough unpacks the thinking behind his documentary Deepfaking Sam Altman, exploring why artificial intelligence inspires both awe and terror, how tech elites quietly prepare for social backlash, and why many of the skills we once told young people to master—like coding—may soon be obsolete. From Silicon Valley’s obsession with immortality and bunker-building to the fear that any job done on a computer could disappear within a few years, the discussion confronts what happens when innovation outruns accountability. The episode also dives deep into Sam Altman’s mystique, Silicon Valley’s moral blind spots, and how fear—of China, regulation, or losing dominance—is used to shape public debate around AI. Lough explains how deepfakes are made, why AI-driven scams are about to explode, and what lawmakers fundamentally misunderstand about regulating rapidly evolving technology. Ultimately, this conversation argues that the antidote to AI anxiety isn’t panic or denial—but transparency, literacy, and a serious public reckoning with who controls the tools reshaping human society. Timeline: 00:00 Adam Bhala Lough joins the Chuck ToddCast 02:30 Tech titans know the pitchforks are coming & are building bunkers 03:15 Did you create “Deepfaking Sam Altman” assuming the worst about AI? 05:00 The phrase Artificial Intelligence is great branding, but creates fear 06:15 How did you find funding for the documentary? 06:45 AI was one of the reasons the writer’s guild was protesting 07:30 Kids who grew up learning to code won’t have a job due to AI 08:15 Coding is now a useless skill when it was THE skill to have 10 years ago 10:15 Any job done on a computer could be gone within 3 years 10:45 Teaching critical thinking skills when a machine can do it for you? 13:00 Humans won’t be ok with robots replacing, but may not have a choice 13:30 If AI destroys humanity, it wouldn’t be deliberate 14:15 There’s a theory that AI would keep us around & find a use for us 15:00 Sam Altman has a giant collection of guns & weapons, like a prepper 15:45 Wealth creates a “prepper” mentality 17:00 There’s an obsession Silicon Valley with living forever 17:45 Was trying to interview Sam Altman always the premise of the doc? 18:45 Thought getting an interview with Sam Altman would be easy 19:15 Still haven’t heard from Altman in light of the documentary 20:45 What made you so threatening that Altman avoided you? 22:30 Other tech companies were more open to talking than OpenAI 23:15 Altman uses AI to read and summarize his emails, he doesn’t read them 24:00 Tech CEO’s tend to be antisocial, created platforms to compensate? 24:45 Many created products the world didn’t need just to get rich 26:00 Social media causes problems, but also have positives like Arab Spring 26:45 Totalitarian regimes found a way to weaponize social media 27:45 Chinese documentarian used AI to avoid government crackdown 29:15 Altman uses fear of China’s use of AI to avoid regulation & get investment 30:15 Sam Altman is a Marvel level super villain 30:45 Elon Musk is even more of a villain than Altman 31:15 Altman doesn’t have a personality, Elon has a crazy one 32:00 Google’s Gemini has caught up and surpassed ChatGPT 32:45 Altman could be a flash in the pan, or the next Steve Jobs 34:30 Steve Jobs and Sam Altman share a similar drive 35:45 Apple wouldn’t have been as successful under Wozniak, he’s too nice 37:00 You don’t have to be an asshole to be a successful tech CEO 38:30 Political leaders have given business leaders permission to be awful 39:00 What do you want people to take away from the documentary? 39:45 The best way to cure AI anxiety is to create a conversation about it 40:45 Concerned about legal exposure from the documentary? 41:15 The documentary shows how the deepfake was made 42:30 AI image & video generators should be forced to include a logo 43:15 What should politicians understand about AI regulation? 44:30 AI slop is getting harder than ever to identify as fake 46:15 AI will be an incredible tool for scamming people 47:00 People should have a safeword to avoid deepfake scams 49:15 AI will be very useful in creating archival footage 51:00 AI gets dystopian when you put it into weapons 52:30 What topics are you interested in covering next? 55:00 Terms & conditions that force arbitration is very coercive 57:15 Deepfaking Sam Altman took 18 months to createSee omnystudio.com/listener for privacy information.

In this urgent and unsettling episode of the Chuck ToddCast, Chuck argues that America is in the midst of a historic “Great Unraveling,” marked by the collapse of trust, consent, and the basic social contract that has held the country together for generations. He examines a chilling series of events in Minneapolis—two fatal shootings by federal agents in three weeks, including the killing of Alex Pretti, who was legally carrying a firearm—raising profound questions about accountability, constitutional rights, and whether the federal government can still be trusted to tell the truth when video evidence directly contradicts official accounts. As administration officials stumble through indefensible explanations, Chuck connects the domestic breakdown to a broader global rupture: allies like Canada openly describing relations with the U.S. as “ruptured,” the post–World War II rules-based order splintering, science and public health consensus eroding, and political power being wielded through favoritism and fear. The episode paints a stark picture of a country growing weaker, more isolated, and more vulnerable—not because of fate, but because unraveling is a process, and it’s happening in real time. Then, documentary filmmaker Adam Bhala Lough joins the Chuck ToddCast for a provocative, darkly funny, and unsettling conversation about AI, power, and the people building the future faster than anyone can regulate it. Lough unpacks the thinking behind his documentary Deepfaking Sam Altman, exploring why artificial intelligence inspires both awe and terror, how tech elites quietly prepare for social backlash, and why many of the skills we once told young people to master—like coding—may soon be obsolete. From Silicon Valley’s obsession with immortality and bunker-building to the fear that any job done on a computer could disappear within a few years, the discussion confronts what happens when innovation outruns accountability. The episode also dives deep into Sam Altman’s mystique, Silicon Valley’s moral blind spots, and how fear—of China, regulation, or losing dominance—is used to shape public debate around AI. Lough explains how deepfakes are made, why AI-driven scams are about to explode, and what lawmakers fundamentally misunderstand about regulating rapidly evolving technology. Ultimately, this conversation argues that the antidote to AI anxiety isn’t panic or denial—but transparency, literacy, and a serious public reckoning with who controls the tools reshaping human society. Finally, Chuck weighs in on the political disaster that is unfolding for Republicans, hops into the ToddCast Time Machine to draw parallels between modern America and Bloody Sunday in Northern Ireland in the 70’s and answers listeners’ question in the “Ask Chuck” segment. Get your wardrobe sorted and your gift list handled with Quince. Don't wait! Go to https://Quince.com/CHUCK for free shipping on your order and 365-day returns. Now available in Canada, too! Protect your family with life insurance from Ethos. Get up to $3 million in coverage in as little as 10 minutes at https://ethos.com/chuck. Application times may vary. Rates may vary. Thank you Wildgrain for sponsoring. Visit http://wildgrain.com/TODDCAST and use the code "TODDCAST" at checkout to receive $30 off your first box PLUS free Croissants for life! Timeline: (Timestamps may vary based on advertisements) 00:00 Chuck Todd’s introduction 01:45 America is going through a “Great Unraveling” 04:45 January 2026 has been a horrendous month in American history 05:45 We’re watching the collapse of consent 06:15 Federal agents involved in 2 fatal shootings in 3 week in Minneapolis 07:00 Alex Pretti was shot 10 times, this was an assassination 07:30 No consequences for agent that shot Renee Good sent a message 08:15 The federal government won’t uphold the law or constitutional rights 09:30 Administration officials make fools of themselves defending this 10:15 Alex Pretti was legally carrying his firearm 10:45 January 6th protestors were also armed 11:45 The federal government is behaving like fascists 12:45 What remains of the social contract? 13:15 Trump’s leadership is destroying everything we knew about America 14:00 Canada’s PM Mark Carney describes relations with U.S. as “ruptured” 14:45 The rules based order in splintering 15:15 TikTok deal was purely favoritism & media alignment for Trump allies 16:15 CDC now discarding science, openly questioning the polio vaccine 17:00 Government shutdown is coming later this week 18:00 100 years of consensus is shattering 19:00 Alex Pretti was carrying, not brandishing his weapon 19:45 Alex Pretti was killed in cold blood 20:30 Thank god there was video, you can’t trust the federal government 21:00 Bystander video contradicts federal government account 21:45 Patel and Noem have no credibility outside of Trump’s base 22:45 Federal agents violated half the bill of rights in one incident 24:30 Middle powers can’t assume alignment with US gives stability 25:30 Canada’s response to Trump is seismic & entirely rational 26:30 The post WW2 order was held together by trust, & that’s been shattered 28:15 Trump’s appointees are making us vulnerable to eradicated diseases 29:30 TikTok will be used by Trump allies for political alignment 30:45 Unraveling isn’t destiny… it’s process 31:30 Trump is making us weaker, more vulnerable and poorer 32:45 We’re losing our country… literally 33:30 We can’t believe anything the federal government says 40:00 Adam Bhala Lough joins the Chuck ToddCast 42:30 Tech titans know the pitchforks are coming & are building bunkers 43:15 Did you create “Deepfaking Sam Altman” assuming the worst about AI? 45:00 The phrase Artificial Intelligence is great branding, but creates fear 46:15 How did you find funding for the documentary? 46:45 AI was one of the reasons the writer’s guild was protesting 47:30 Kids who grew up learning to code won’t have a job due to AI 48:15 Coding is now a useless skill when it was THE skill to have 10 years ago 50:15 Any job done on a computer could be gone within 3 years 50:45 Teaching critical thinking skills when a machine can do it for you? 53:00 Humans won’t be ok with robots replacing, but may not have a choice 53:30 If AI destroys humanity, it wouldn’t be deliberate 54:15 There’s a theory that AI would keep us around & find a use for us 55:00 Sam Altman has a giant collection of guns & weapons, like a prepper 55:45 Wealth creates a “prepper” mentality 57:00 There’s an obsession Silicon Valley with living forever 57:45 Was trying to interview Sam Altman always the premise of the doc? 58:45 Thought getting an interview with Sam Altman would be easy 59:15 Still haven’t heard from Altman in light of the documentary 1:00:45 What made you so threatening that Altman avoided you? 1:02:30 Other tech companies were more open to talking than OpenAI 1:03:15 Altman uses AI to read and summarize his emails, he doesn’t read them 1:04:00 Tech CEO’s tend to be antisocial, created platforms to compensate? 1:04:45 Many created products the world didn’t need just to get rich 1:06:00 Social media causes problems, but also have positives like Arab Spring 1:06:45 Totalitarian regimes found a way to weaponize social media 1:07:45 Chinese documentarian used AI to avoid government crackdown 1:09:15 Altman uses fear of China’s use of AI to avoid regulation & get investment 1:10:15 Sam Altman is a Marvel level super villain 1:10:45 Elon Musk is even more of a villain than Altman 1:11:15 Altman doesn’t have a personality, Elon has a crazy one 1:12:00 Google’s Gemini has caught up and surpassed ChatGPT 1:12:45 Altman could be a flash in the pan, or the next Steve Jobs 1:14:30 Steve Jobs and Sam Altman share a similar drive 1:15:45 Apple wouldn’t have been as successful under Wozniak, he’s too nice 1:17:00 You don’t have to be an asshole to be a successful tech CEO 1:18:30 Political leaders have given business leaders permission to be awful 1:19:00 What do you want people to take away from the documentary? 1:19:45 The best way to cure AI anxiety is to create a conversation about it 1:20:45 Concerned about legal exposure from the documentary? 1:21:15 The documentary shows how the deepfake was made 1:22:30 AI image & video generators should be forced to include a logo 1:23:15 What should politicians understand about AI regulation? 1:24:30 AI slop is getting harder than ever to identify as fake 1:26:15 AI will be an incredible tool for scamming people 1:27:00 People should have a safeword to avoid deepfake scams 1:29:15 AI will be very useful in creating archival footage 1:31:00 AI gets dystopian when you put it into weapons 1:32:30 What topics are you interested in covering next? 1:35:00 Terms & conditions that force arbitration is very coercive 1:37:15 Deepfaking Sam Altman took 18 months to create 1:41:30 Chuck’s thoughts on interview with Adam Bhala Lough 1:43:30 Elected Republicans trying to distance from Trump’s DHS 1:45:00 Marjorie Taylor-Greene argues the small c conservative position 1:46:00 MTG uses hypothetical shooting of a MAGA by Biden’s DOJ 1:48:00 Trump’s defenders try to blame Trump’s advisors rather than Trump 1:49:00 The administration is trampling the Bill of Rights 1:50:00 Minneapolis is a political disaster for Trump 1:51:00 Conservative pundits are pitching a Minneapolis off-ramp 1:52:45 Greg Bovino is trying invoke violence in the way he dresses 1:54:00 Trump’s coalition is breaking apart 1:55:45 ToddCast Time Machine 1:56:30 January 30th, 1972 - Bloody Sunday in Northern Ireland 1:57:45 British army turned into an occupying force 1:58:30 Unarmed civilians were shot by soldiers 1:59:00 Bloody Sunday ended the belief that the government could be neutral 2:00:00 When the state lies about violence, radicalism ensues 2:01:30 U2’s anthem about Bloody Sunday is expression of moral fatigue 2:02:30 Trump is the only person that can de-escalate and he refuses to 2:04:00 States tell themselves they are restoring order, consequences are permanent 2:04:45 Trust collapsed in Northern Island & happening now in Minneapolis 2:05:45 Ask Chuck 2:06:15 Agents involved in shootings weren’t new recruits? 2:11:00 How naive were we to think “it can’t happen here” How do we navigate it?See omnystudio.com/listener for privacy information.

Joe Piscopo interviews Stan Wozniak who adds a layer of protective grit to this legacy, recounting a legal dismissal that followed a physical confrontation with a rude photographer. Learn more about your ad choices. Visit megaphone.fm/adchoices

Send the show a text message!In this episode of the Space Between Podcast, host Renae Lipsmeyer engages in a heartfelt conversation with Kristan, a passionate fan of Dave Matthews Band. They discuss the band's impact on their lives, the diverse fan community, and the memorable experiences at live shows. Kristan shares her journey of discovering the band, her favorite songs, and how the music has been a constant companion through life's ups and downs.  Support the showTo share your DMB fan journey, email Renae: renae@thespacebetweenpodcastDMB.com

When a high-achieving scientist realized the traditional definition of success no longer fit, she chose a radically different path. In this episode, Brie shares how she walked away from a predictable biotech career, trusted her instincts, and built a portfolio-style consulting business that aligns with her values, energy, and love for animal welfare.   What you'll learn How to recognize when your "successful" career no longer feels meaningful Why trusting your instincts is essential when your values begin to shift How career experiments (like Social Goldilocks) can reveal unexpected paths What it takes to design a more flexible, values-aligned version of success   Our book, Happen To Your Career: An Unconventional Approach To Career Change and Meaningful Work, is now available on audiobook! Visit  happentoyourcareer.com/audible to order it now! Visit happentoyourcareer.com/book for more information or buy the print or ebook here! Want to chat with our team about your unique situation? Schedule a conversation   Free Resources What career fits you? Join our free 8 Day Mini Course to figure it out! Career Change Guide - Learn how high-performers discover their ideal career and find meaningful, well-paid work without starting over.   Related Episodes Designing Career Experiments and Testing New Careers (Spotify / Apple Podcasts) Discover Your Strengths to Find Your Ideal Career (Spotify / Apple Podcasts) Social Goldilocks Experiment (Watch Here)

Two teachers, one middle school and one elementary, share how they have made writing instruction a priority. Josie Wozniak and Kimberly Voge are avid users and proponents of EduProtocols to support their writing instruction. In this episode they share how students are able to write more. But more importantly, how the students take more responsibility for improving their writing.Twitter: @‌ms_woz @kvoge71LinkedIn: https://www.linkedin.com/in/kim-voge-662b905b/Facebook: (5) Facebook(5) EduProtocols Community | FacebookInstagram: @‌jwoz_teaches @‌hermajestyvogeBluesky: @‌jwoz-teaches.bsky.socialTik Tok: @‌jwoz_teaches @techsassyDeploying EduProtocols This podcast sponsored by:The Bell Ringer, a weekly newsletter providing news, tools, and resources on the science of learning, written by education reporter Holly Korbey. Subscribe here. Murmuration Author Services by Mark Combes. Looking to write your first book? Murmuration Author Services is your friend and coach for this journey. Learn more here. 

Scott Kelly, founder/CEO of Black Dog Venture Partners, shares 30 years of lessons helping tech and consumer brands fund, sell, and scale. We dig into why “sales is a lost art,” why your network is your real funding source, and how to build relationships that lead to opportunities. Plus: keystone habits, outworking 21-year-olds at 61, and why you should love practice as much as the game.Highlights & Timestamps0:00 Meet Scott Kelly — exits, accelerators, and why he never really “retired”2:42 What success actually looks like (solve problems, create opportunities)4:13 Sweet spot: early-stage tech & CPG; why sales often fixes everything5:00 The lost art of asking for the sale (and handling “no”)6:37 Stop doing $5/hr tasks when you're paid for $500/hr outcomes8:02 “Wozniak & Jobs” — know your lane; if you can't sell, hire it8:45 Learn the ratios: leads → calls → closes (practice, not theory)9:55 Investor-readiness: your pitch, story, questions, & live “VC Fast Pitch” reps11:25 Follow-up matters: most wins happen on touches 5–6+11:45 Money is in your list: coffees > cold banks; DM your “couch money”12:24 Daily relationship reps: LinkedIn to real conversations; 100 lunches challenge13:49 Don't pitch-slap investors on first contact; relationships first13:57 Old school still works: direct mail & handwritten notes that close deals15:26 Keystone habit: “obscene work ethic” — love the grind, love the practice17:29 Parting advice: never stop learning, be confident & humble, don't give upPull Quotes“Sales is a lost art. Ask for the money—and be okay hearing ‘no.'”“Stop doing $5/hour tasks when you're paid to produce $500/hour outcomes.”“Relationships lead to opportunity. Don't pitch-slap on the first message.”“If you can't sell, be honest—find someone who can.”“Love the practice as much as the game.”Guest Links

Actor Daniel Wozniak had no money, a wedding he could not afford, and a plan that would shock California. Instead of working to fix his problems, he chose murder. His first victim was 26-year-old Army veteran Sam Herr, a friend who trusted him and had more than $60,000 in savings. Wozniak lured Sam to a theater, shot him twice, and began staging a twisted cover-up.To make Sam look like a killer on the run, Wozniak tricked 23-year-old Julie Kibuishi into visiting Sam's apartment. He murdered her and staged the scene to look like a jealous rage killing. Then he put on his costume, walked on stage, and performed in a musical as if nothing had happened.But the illusion fell apart fast. Police traced ATM withdrawals to a teenager who exposed Wozniak's scheme. Confronted with overwhelming evidence, he confessed. Jurors took only one hour to convict him.Was this the desperate act of a man cornered by debt, or the performance of a cold-blooded killer who valued applause more than human life?Follow True Crime Recaps for more stories where the truth is darker than fiction.

In this episode of the Live Unreal Podcast, Jeff Glover sits down with Cleveland, Ohio Realtor® Kelsey Wozniak at the 2025 Live Unreal Retreat in Traverse City. With over a decade in real estate, Kelsey has built a thriving business defined by focus, systems, and resilience. In 2024, Kelsey sold 42 homes for $12.8 million in volume, and by mid-2025, she had already closed 24 units for $7.7 million, on track to hit her ambitious goal of 65 units and $20 million for the year. In this interview, Kelsey opens up about:

Steve Wozniak is the engineer who built Apple. Then he did something Silicon Valley still doesn't understand: he gave millions of his own money away to early employees, walked away from power, and refused to play the game everyone else was playing. While HP rejected his design and competitors built walled gardens, Wozniak's philosophy of open architecture, the very one a young Steve Jobs fought against, is what saved Apple long enough for it to become Apple. This is the story of the reluctant founder who won by refusing to compromise, and a blueprint for success without selling your soul. ----- Chapters: (00:00) Introduction (01:31) Part 1: Pranks and Paper Computers (18:11) Part 2: The First Personal Computer (30:46) Part 3: Apple Computer Corporation (41:02) Part 4: Apple's Decline (46:02) Epilogue (48:02) Rules To Live By ----- Upgrade: Get hand-edited transcripts and an ad-free experience, and so much more. Learn more @ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠fs.blog/membership⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ------ Newsletter: The Brain Food newsletter delivers actionable insights and thoughtful ideas every Sunday. It takes 5 minutes to read, and it's completely free. See what you're missing: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠fs.blog/newsletter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ------ Follow Shane Parrish X ⁠⁠⁠⁠⁠@ShaneAParrish⁠⁠⁠⁠⁠ Insta ⁠@farnamstreet⁠ LinkedIn ⁠Shane Parrish ------ This episode is for informational purposes only. Learn more about your ad choices. Visit megaphone.fm/adchoices

We open with a sobering follow-up: the future is less about AI toast (though Red Dwarf predicted it) and more about a soul-stripping "infrastructure of meaningless" after an AWS outage proved how fragile the internet is. Corporate overlords, like Elon Musk, are taking note: he finally addressed Starlink's use by Asian scam syndicates, but his attention is mostly on superintelligence, which Wozniak, Prince Harry, and 800 others want banned. Meanwhile, Meta, despite pouring $27 billion into data centers, suddenly cut 600 AI jobs, and Amazon is preparing to automate a half-million warehouse positions, offering drivers AR spy glasses and suggesting a new "Help Me Decide" AI tool to automate the exhausting micro-decision of which air fryer to buy. This dystopian fever dream peaked when Suzanne Somers' widower revealed he built a full-on robotic AI twin of the late actress. Predictably, Tesla stock tumbled, and the crypto grift continued with the pardoning of Binance founder Zhao, leaving SBF to ponder his failed check-bounce in jail.Speaking of soul-crushing, Disney's latest nostalgia raid, Tron: Ares, tanked harder than anticipated, proving not every Gen-X intellectual property is a worthy cash cow. But fear not, there's still great TV to be had: we recommend the clever dramas Slow Horses and The Diplomat Season 3, the high-stakes culinary nightmare Knives Edge: Chasing Michelin Stars, and the surprisingly excellent Gen V (which you must watch before the next season of The Boys). We also got our fix with the Pluribus trailer, Bullet Train, Dr. Horrible's Sing-Along Blog, and the deliciously low-stakes reality shows Come Dine With Me, Hotel Costiera, and The Celebrity Traitors UK/Canada. Sadly, we must mourn the end of Food Network's The Kitchen. Yet, no matter how good the show, you still have to deal with Ticketmaster, which is still lying about "fighting bots" while cornering the secondary market.In the world of Apps & Doodads, OpenAI dropped its "Anti-Web" browser, ChatGPT Atlas (a data mule in disguise), and a new app now fakes your vacation photos (perfect for burned-out users). X is poised to sell "rare" usernames for millions (with a terrible subscription catch), while some clever hacker figured out a $60 mod to disable the privacy light on Meta's Ray-Ban spy glasses. Fellow podcast host Dave Bittner joined us to agree that the new Hall of Presidents format is better without the political posturing and confirmed the joy of old-school, purple-ink-smelling Spirit Duplicators (and we checked out a Star Wars fan film trailer for the AT THE LIBRARY section). Don't forget your Tilly Hat! Finally, R.I.P. Soft Cell's musical force Dave Ball, aged 66; the hits still hit.Sponsors:Private Internet Access - Go to GOG.Show/vpn and sign up today. For a limited time only, you can get OUR favorite VPN for as little as $2.03 a month.SetApp - With a single monthly subscription you get 240+ apps for your Mac. Go to SetApp and get started today!!!1Password - Get a great deal on the only password manager recommended by Grumpy Old Geeks! gog.show/1passwordMasterClass - Get an additional 15% off any annual membership at MASTERCLASS.com/GRUMPYOLDGEEKSCleanMyMac - clnmy.com/GrumpyOldGeeks - Use code OLDGEEKS for 20% off.Show notes at https://gog.show/719FOLLOW UPDoes Anyone Want Any Toast? | Red Dwarf | BBCA Tool That Crushes CreativityIN THE NEWSAmazon's AWS outage knocked services like Alexa, Snapchat, Fortnite, Venmo and more offlineSpaceX disables 2,500 Starlink terminals allegedly used by Asian scam centersYelp is getting more AI, including an upgraded chatbotSteve Wozniak, Prince Harry and 800 others want a ban on AI ‘superintelligence'Suzanne Somers' Widower Built “AI Twin” of Late ActressMeta Cuts 600 AI Roles From Its Superintelligence Labs After $27 Billion Data Center DealNew report leaks Amazon's proposed mass-automation plansAmazon Rolls Out New AI Tool to Help You Decide What to Buy: The Great Mental Outsourcing continues.Amazon unveils AI-powered augmented reality glasses for delivery driversTesla reports revenue growth after two down quarters. Why the stock is fallingTrump pardons convicted Binance founder Zhao, White House saysCrypto billionaire pardon is insane by CoffeezillaMEDIA CANDY‘Tron: Ares' Is an Even Bigger Bomb Than We ThoughtTron: LegacyHuman: Into the AmericasHuman: Building EmpiresCome Dine With MeFood Network's The Kitchen to End After 40 SeasonsKnifes Edge: Chasing Michelin StarsPluribus — Official Trailer | Apple TVBullet TrainDr. Horrible's Sing-Along BlogHotel CostieraSlow HorsesThe Diplomat Season 3The Celebrity Traitors UKTraitors Canada Season 3Ticketmaster Is Going to Have to Do Better Than ThatAPPS & DOODADSOpenAI's AI-powered browser, ChatGPT Atlas, launches on macOS todayChatGPT's Atlas: The Browser That's Anti-Web By Anil DashToo burned out to travel? This new app fakes your summer vacation photos for youX's handle marketplace will sell some 'rare' usernames for millions of dollarsA $60 Mod to Meta's Ray-Bans Disables Its Privacy-Protecting Recording LightTHE DARK SIDE WITH DAVEDave BittnerThe CyberWireHacking HumansCaveatControl LoopOnly Malware in the BuildingGen VTilly HatsFirefly | The World's Smallest Pro-Audio MicrophoneSpirit Duplicators: Copies Never Smelled So GoodSTAR WARS ENTRENCHED: Fan Film TEASER 2CLOSING SHOUT-OUTSSoft Cell's musical force Dave Ball dies, aged 66See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Pastor Wayne Wozniak returns for World Missions Sunday to discuss the missions work being done in Columbia as well as Peru

9/12/25: MTA Pres Max Page w/ Jason Wozniak, organizer at Debt Collective. Garrick Perry, incumbent & Northampton city councilor at-large candidate. OTones' Mary Witt & Forbes' Library Dir Lisa Downing: launching the Hess Performance Stage. Author Jeanne Birdsall on “The Library of Unruly Treasures.” Donnabelle Casis w/ Cima Khademi & Leila Rahnamaabadi, exhibitors at APE's "My Mind in Bloom."

Author, coach, and xNBA Exec Michael Wozniak joins the podcast to explain wy people don't decide to quit or disengage overnight.   It's a process filled with dozens of micro-offenses that lead to employee drift.   Michael unpacks how to fight back against that drift using: - Support - Clarity - Trust   Purchase Michael's book here.   Connect with Michael here.   Connect with your host Josh Swing.   Stay Saucy!  

You might already be familiar with filling out the FAFSA form, or you might only know it by reputation. That reputation is somewhere between filing your annual income taxes and running an Ironman triathalon. Revisions, technology issues and widespread confusion over the availability of the form over the past two years might make it seem even more sinister.Let's back up. What is the FAFSA? If you have a child finishing high school this school year, the FAFSA plays a big part in determining how much financial aid you could receive—including grants, loans and scholarships—to help pay for college. In Indiana, most families are now required by law to fill out the FAFSA unless they seek a waiver.   Despite recent tumult, all signs point to the FAFSA being ready to fill out this year by the traditional launch date of Oct. 1. Our guest this week is Bill Wozniak, vice president and chief marketing officer of INvestEd, a nonprofit based in Indianapolis and created by the Indiana Legislature to help families navigate the FAFSA process. He provides an overview for the uninitiated and shares some of the biggest misconceptions of FAFSA. For example, if you think you are sufficiently wealthy to put any financial assistance out of reach, you very well could be wrong. If you think you just need to get it done by the end of the year, you might want to think again. And, Wozniak says, the process isn't nearly as arduous today as its reputation might suggest.

In this conversation, Michael Wozniak discusses his book 'Employee Drift' and explores the concept that employees do not quit jobs but drift away due to poor leadership. He shares insights from his experience in the NBA, emphasizing the importance of trust, clarity, and support in leadership. Wozniak reflects on his own leadership journey, the significance of understanding employee needs, and the necessity of addressing root causes of workplace issues rather than just symptoms. He advocates for a culture of accountability and empowerment, highlighting the role of authentic leadership in transforming workplace culture. TAKEAWAYS People don't quit jobs, they drift from poor leadership. Most leadership is very transactional, leading to employee drift. Trust is essential for effective leadership. Leaders must focus on building relationships, not just managing tasks. Support, clarity, and trust are key components of effective leadership. Identifying root causes of workplace issues is crucial for improvement. Creating a culture of accountability fosters growth and development. Empowering employees leads to better performance and satisfaction. Authentic leadership builds trust and connection with employees. Clarity in roles and expectations prevents burnout and drift. A QUICK GLIMPSE INTO OUR PODCAST Podcast: Transform Your Workplace, sponsored by Xenium HR Host: Brandon Laws In Brandon's own words: “The Transform Your Workplace podcast is your go-to source for the latest workplace trends, big ideas, and time-tested methods straight from the mouths of industry experts and respected thought-leaders.” About Xenium HR Xenium HR is on a mission to transform workplaces by providing expert outsourced HR and payroll services for small and medium-sized businesses. With a people-first approach, Xenium helps organizations create thriving work environments where employees feel valued and supported. From navigating compliance to enhancing workplace culture, Xenium offers tailored solutions that empower growth and simplify HR.

Send us a textMichael Wozniak - leadership coach/ business strategist/author/former executive with PepsiCo and the NBA - takes us on his journey of faith and work including growing up in a catholic home where faith was personal; an alcoholic father and the subconscious push to athletics; an exchange of performance for authenticity; his older brother becoming his “dad”; the idea of God owing us something; finding identity in Christ; “be, do, have”; the distraction of comparison; getting into sports marketing in Japan through God's no; helping establish the NBA's Japan market; the challenges of the Japanese business culture; his book “Employee Drift”; building covenants with your people; the childlike lesson of getting watermelon from red pepper seeds; shifting leadership dynamics to trust; seeing work as worship; and much, much more! https://michaelwozniak.net/tinyurl.com/EmployeeDriftBook Support the show

In this episode of The Curious Builder Podcast, host Mark Williams sits down with longtime family friend and uber-talented designer Mary Wozniak from Shadow Falls Design. Mary shares her journey from running a bustling paint and design store on Grand Avenue in St. Paul to building a personal, client-centered design business and reflects on key lessons learned, from valuing relationships and privacy to navigating challenges and embracing the changing design industry. The conversation is full of warmth, personal anecdotes (including the famous inside-out couch!), and offers great advice on staying true to your values while growing as an entrepreneur.  Support the show - https://www.curiousbuilderpodcast.com/shop   See our upcoming live events - https://www.curiousbuilderpodcast.com/events   The host of the Curious Builder Podcast is Mark D. Williams, the founder of Mark D. Williams Custom Homes Inc. They are an award-winning Twin Cities-based home builder, creating quality custom homes and remodels, one-of-a-kind dream homes of all styles and scopes. Whether you're looking to reimagine your current space or start fresh with a new construction, we build homes that reflect how you live your everyday life.   Sponsors for the Episode:   Pella Website: https://www.pella.com/ppc/professionals/why-wood/   Olive and Vine Socials Website - https://oliveandvinesocials.com   Adaptive https://www.adaptive.build   Where to find the Guest: Website: https://Shadowfallsdesign.com Facebook: https://www.facebook.com/ShadowfallsDesign/   Where to find the Host: Website - https://www.mdwilliamshomes.com/ Podcast Website - https://www.curiousbuilderpodcast.com Instagram - https://www.instagram.com/markdwilliams_customhomes/ Facebook - https://www.facebook.com/MarkDWilliamsCustomHomesInc/ LinkedIn - https://www.linkedin.com/in/mark-williams-968a3420/ Houzz - https://www.houzz.com/pro/markdwilliamscustomhomes/mark-d-williams-custom-homes-inc

Si parla dell'intervista di Craig Federighi e Greg Joswiak, di come eliminare la parte "video" delle live photos, di come effettuare il takekout da Google Photos, di una curiosa fotocamera per bambini, di macOS e docker nativo, dei colori invertiti del...

What happens when God asks you to make a move that looks like career suicide? Michael Wozniak, business leadership coach, author, and former global NBA executive, said "yes" and it changed everything.In this episode, we explore Michael's remarkable journey of obedience, risk, and faith. After a meteoric rise at Pepsi and completing graduate school, he felt called by God to pivot into international sports marketing by taking a job without pay and in a country where he didn't even speak the language. Mike's courage and trust led to a dream role with the NBA, leading the launch of its global expansion during the 1992 “Dream Team” Olympics in Japan.God later asked Mike to lay down his “Isaac” (his love for sports) and step into ministry. Through unexpected connections, he helped launch “Kid's Games,” a Bible-based global sports outreach now in over 140 countries.Today, Mike coaches leaders and teams, focusing on culture, communication, and self-awareness. Drawing on tools like the Five Voices of Leadership, he equips others to lead with humility and courage.This episode is a masterclass in what it means to trust God when the path makes no sense. Mike reminds us: “When ‘good and faithful servant' is your mantra, your path will not be linear. When you're walking in obedience, never trust your eyes, because it'll never look the way you think it should.”More about Mike:Michael Wozniak is a Business Leadership coach fighting for people's highest good unlocking leadership potential at every level. He believes strongly helping owners and leaders grow themselves, grow their people, and grow their business. A relational intelligence expert, his focus is on culture, communication, relationships, alignment, and execution driving performance and profit. Prior, Michael worked at the National Basketball Association around the 1992 Dream Team and launched the NBA in Japan. He also helped launch Kids Games, a global children & sports movement, scaling it to over 150 countries reaching millions of children annually. Michael has owned multiple businesses and currently owns a volleyball club along with his consulting agency. He is an author of the book “Employee Drift” sharing how to lead people purposefully in support, clarity & trust. Employee disengagement doesn't happen overnight. It's a gradual process, a drift, often caused by a lack of effective leadership. However, when employees feel valued, supported, and inspired, they show up differently. They stop working for you and start working with you. Michael and wife Beth have been married for 32 years and have four adult children, a daughter-in-law, and one granddaughter. He lives in Grand Rapids, MI.Support the showTransforming the workplace one Bible study at a time - DONATE today! CONNECT WITH US:B-B-T.org | News | LinkedIn Biblical Business Training (“BBT”) equips busy, working people to grow in the grace and knowledge of Jesus Christ and empowers them in small-group Bible study settings to apply Biblical principles to their every day lives - especially in the workplace. BBT is a nonprofit 501(c)(3) organization which exists to help people develop their Christian “Faith for Work – Leadership for Life!”

Great products start with an idea, and a lot of tinkering. Edison and his lightbulb. Jobs and Wozniak in their garage. The image is familiar—a lone inventor, obsessing over details, experimenting, failing, learning, and eventually discovering something great. South Louisiana has a pretty rich tradition of entrepreneurship and invention. Consider the crawfish boat, for instance. And, when you think about it, Cajun and Creole food in general can be likened to hare-brained contraptions. We’re constantly tinkering with ways to improve recipes to make them more efficient, cheaper or more flavorful — all without losing their essence. Gumbo There’s nothing more essential in Cajun cooking than the trinity — onion, bell pepper and celery, known around here as the Trinity, and depending on your bent toward Catholicism or sacrelige, even "The Holy Trinity." Dreux Barrah is Founder and Chief Chopping Officer at C’est Tout Dried Trinity Mix. Dreux’s path to business began in his home garden with an overabundance of bell peppers. He came up with drying vegetables as a way to preserve his surplus and created a dehydrated holy trinity. Through experimentation, Dreux perfected his process, even crafting custom equipment like his flour-toasting "Rouxster." Now, C’est Tout sells not just dehydrated vegetable mixes but also fully dried dish starters for classics like gumbo, jambalaya, and etouffee. Whiskey One thing Cajuns aren’t famous for is whiskey — apart from drinking it, we don’t really make it. That is, until Philip Mestayer came along. Philip is Co-Owner and Head Distiller at Distillerie Acadian, a small-batch distillery based in New Iberia. Philip started as a weekend hobbyist, distilling whiskey with his dad and brother. Their goal was ambitious—create Louisiana’s first bourbon, a spirit more associated with Kentucky Bluegrass than Cajun prairies. What began as a passion evolved into a business, but not without a whole lot of elbow grease. Philip designed and welded much of their initial distilling equipment himself, navigating complicated federal regulations, supply chain issues, and tricky logistics. Today, Distillerie Acadian offers seven unique spirits, from bourbon to handcrafted gin. Out to Lunch Acadiana was recorded live over lunch at Tsunami Sushi in downtown Lafayette. You can find photos from this show by Astor Morgan at itsacadiana.com.See omnystudio.com/listener for privacy information.

Season 5: Episode 209This special episode of the Ag Sales Professionals Podcast is being featured on North American Ag as Chrissy Wozniak was recently invited by host Greg Martinelli to join him for a conversation about ag marketing, media, and the rapidly evolving world of ag technology. We're excited to offer this episode to our listeners, as Chrissy shares her perspective on how to effectively communicate in the ag space, the importance of cutting through buzzwords, and what producers really want from the companies that serve them. From her work with North American Ag to her role at Ecorobotix and American Agri-Women, Chrissy opens up about her journey and her mission to help tell the real story of agriculture. We're proud to bring this important conversation to our audience. Send us a textAgritechnica in Hannover, Germany is held every other year, this year long-time tech writer & ag journalist Willie Vogt has put together for ag enthusiasts! The Agritechnica tour includes three days at the huge equipment and farm technology event. Learn more - https://agtoursusa.com/agritechnica.htmlSubscribe to North American Ag at https://northamericanag.com

Melanie Wozniak talks making the move from Perth to LA, working on the ABC show "Itch", her new film "A Girl Like Him", and shares an emotional audition story! About Melanie: Born in Chile and raised in Australia, Melanie Wozniak is a dynamic and multi-talented creative force in the entertainment industry. Her passion for acting began at a young age, starring in TV commercials and feature films, which laid the foundation for her future in the industry. With over a decade of experience in film and television, Melanie's versatility as an actor continues to shine. In 2019, Melanie landed her breakout role in the ABC TV series 'Itch', portraying the series regular "Jack" in a story based on Simon Mayo's bestselling novel. Her physical background proved invaluable as she performed many of her own stunts, including Tae Kwon Do and BMX bike riding, demonstrating her commitment and versatility as an actress. Melanie's dedication to her craft has been honed with training in film and television acting, including classes at the Upright Citizens Brigade school in Los Angeles. Recently, she showcased her talents as a motion capture performer in the highly anticipated video game Diablo IV and Diablo V. Most recently, she starred as the lead in the feature film 'A Girl Like Him', written and directed by Amy S. Weber, opposite the iconic Tovah Feldshuh. With a growing portfolio of diverse roles and a reputation for excellence, Melanie is undoubtedly a talent to watch, poised for even greater success in the years ahead.  Follow the show on social media!          Instagram: https://instagram.com/thanksforcominginpodcast/          Twitter: https://twitter.com/tfci_podcast          Facebook: http://facebook.com/thanksforcominginpodcast/           Patreon: patreon.com/thanksforcomingin YouTube: https://www.youtube.com/channel/UCXj8Rb1bEmhufSBFSCyp4JQ Theme Music by Andrew Skrabutenas Producers: Jillian Clare & Susan Bernhardt Channel: Realm For more information, go to thanksforcominginpodcast.com  Learn more about your ad choices. Visit megaphone.fm/adchoices

Two childhood friends, teammates, and now opposing coaches... Jamey Bridges head coach at Columbia H.S. in Illinois, and Chad Wozniak head coach at Louisville Collegiate. These two talk about their programs, recent tragedy, culture, wins, and more. These Granite City alums also tie together their own experiences under the great Gene Baker and how it has affected their own coaching strategies and beyond! Be sure to give Prospect 2 Player a follow on Insta to keep up on recruiting tips/tricks And don't forget to go to "Choose It Right" for your SDP discount for your college recruit's search and resume needs! Learn more about your ad choices. Visit megaphone.fm/adchoices

Click Here to Get All Podcast Show Notes!Most people don't fail because they're lazy. They fail because they don't know what to do next. In this episode, Sharran tackles the biggest problem holding people back: useless advice. Phrases like “just do it” or “stay disciplined” sound great, but they don't tell you what to do next. That's where the Action Filter comes in. It's a tactical system that helps you break down advice into steps you can execute immediately. It helps turn vague advice into clear, executable steps that drive results.Sharran walks through real-world examples from Michael Jordan, Marvel, and Steve Jobs to show how elite performers turn plans into results. If you're tired of motivation without action, this episode will give you the clarity you need to move forward.Stop listening to generic advice. Tune in to learn the Action Filter and execute your biggest goals today!“Execution is what separates winners from wannabes.”- Sharran SrivatsaaTimestamps:01:20 - Why most advice is useless without execution02:20 - The ‘Just Do It' myth and why motivation isn't enough04:13 - The power of making your goals public (Marvel's $29B strategy)07:10 - Why finding the right partner accelerates success (Jobs & Wozniak)09:40 - The escape room mindset: Just focus on the next clue11:39 - The 80/20 rule: Why small shifts create massive results14:52 - How Pixar's 10-slide rule forces clarity in any project17:23 - Recap: The Action FilterResources:- Join the Future Proof Community - https://futureproofsecrets.com/- The Real Brokerage - https://www.joinreal.com/- Top Agent Power Pack - https://sharran.activehosted.com/f/121- The 5am Club - https://sharran.com/5amclub/- Join the 10K Wisdom Private Partner Podcast, now available to you for free - https://www.highlandprime.com/optin-10k-wisdom- The Job of a CEO - https://www.highlandprime.com/download-job-of-ceo- Join Sharran's VIP Community - https://sharran.com/vip/- ARC Multifamily Real Estate Investing - https://arcmf.com/- Sharran's...

Today's episode is with Paul Klein, founder of Browserbase. We talked about building browser infrastructure for AI agents, the future of agent authentication, and their open source framework Stagehand.* [00:00:00] Introductions* [00:04:46] AI-specific challenges in browser infrastructure* [00:07:05] Multimodality in AI-Powered Browsing* [00:12:26] Running headless browsers at scale* [00:18:46] Geolocation when proxying* [00:21:25] CAPTCHAs and Agent Auth* [00:28:21] Building “User take over” functionality* [00:33:43] Stagehand: AI web browsing framework* [00:38:58] OpenAI's Operator and computer use agents* [00:44:44] Surprising use cases of Browserbase* [00:47:18] Future of browser automation and market competition* [00:53:11] Being a solo founderTranscriptAlessio [00:00:04]: 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.swyx [00:00:12]: Hey, and today we are very blessed to have our friends, Paul Klein, for the fourth, the fourth, CEO of Browserbase. Welcome.Paul [00:00:21]: Thanks guys. Yeah, I'm happy to be here. I've been lucky to know both of you for like a couple of years now, I think. So it's just like we're hanging out, you know, with three ginormous microphones in front of our face. It's totally normal hangout.swyx [00:00:34]: Yeah. We've actually mentioned you on the podcast, I think, more often than any other Solaris tenant. Just because like you're one of the, you know, best performing, I think, LLM tool companies that have started up in the last couple of years.Paul [00:00:50]: Yeah, I mean, it's been a whirlwind of a year, like Browserbase is actually pretty close to our first birthday. So we are one years old. And going from, you know, starting a company as a solo founder to... To, you know, having a team of 20 people, you know, a series A, but also being able to support hundreds of AI companies that are building AI applications that go out and automate the web. It's just been like, really cool. It's been happening a little too fast. I think like collectively as an AI industry, let's just take a week off together. I took my first vacation actually two weeks ago, and Operator came out on the first day, and then a week later, DeepSeat came out. And I'm like on vacation trying to chill. I'm like, we got to build with this stuff, right? So it's been a breakneck year. But I'm super happy to be here and like talk more about all the stuff we're seeing. And I'd love to hear kind of what you guys are excited about too, and share with it, you know?swyx [00:01:39]: Where to start? So people, you've done a bunch of podcasts. I think I strongly recommend Jack Bridger's Scaling DevTools, as well as Turner Novak's The Peel. And, you know, I'm sure there's others. So you covered your Twilio story in the past, talked about StreamClub, you got acquired to Mux, and then you left to start Browserbase. So maybe we just start with what is Browserbase? Yeah.Paul [00:02:02]: Browserbase is the web browser for your AI. We're building headless browser infrastructure, which are browsers that run in a server environment that's accessible to developers via APIs and SDKs. It's really hard to run a web browser in the cloud. You guys are probably running Chrome on your computers, and that's using a lot of resources, right? So if you want to run a web browser or thousands of web browsers, you can't just spin up a bunch of lambdas. You actually need to use a secure containerized environment. You have to scale it up and down. It's a stateful system. And that infrastructure is, like, super painful. And I know that firsthand, because at my last company, StreamClub, I was CTO, and I was building our own internal headless browser infrastructure. That's actually why we sold the company, is because Mux really wanted to buy our headless browser infrastructure that we'd built. And it's just a super hard problem. And I actually told my co-founders, I would never start another company unless it was a browser infrastructure company. And it turns out that's really necessary in the age of AI, when AI can actually go out and interact with websites, click on buttons, fill in forms. You need AI to do all of that work in an actual browser running somewhere on a server. And BrowserBase powers that.swyx [00:03:08]: While you're talking about it, it occurred to me, not that you're going to be acquired or anything, but it occurred to me that it would be really funny if you became the Nikita Beer of headless browser companies. You just have one trick, and you make browser companies that get acquired.Paul [00:03:23]: I truly do only have one trick. I'm screwed if it's not for headless browsers. I'm not a Go programmer. You know, I'm in AI grant. You know, browsers is an AI grant. But we were the only company in that AI grant batch that used zero dollars on AI spend. You know, we're purely an infrastructure company. So as much as people want to ask me about reinforcement learning, I might not be the best guy to talk about that. But if you want to ask about headless browser infrastructure at scale, I can talk your ear off. So that's really my area of expertise. And it's a pretty niche thing. Like, nobody has done what we're doing at scale before. So we're happy to be the experts.swyx [00:03:59]: You do have an AI thing, stagehand. We can talk about the sort of core of browser-based first, and then maybe stagehand. Yeah, stagehand is kind of the web browsing framework. Yeah.What is Browserbase? Headless Browser Infrastructure ExplainedAlessio [00:04:10]: Yeah. Yeah. And maybe how you got to browser-based and what problems you saw. So one of the first things I worked on as a software engineer was integration testing. Sauce Labs was kind of like the main thing at the time. And then we had Selenium, we had Playbrite, we had all these different browser things. But it's always been super hard to do. So obviously you've worked on this before. When you started browser-based, what were the challenges? What were the AI-specific challenges that you saw versus, there's kind of like all the usual running browser at scale in the cloud, which has been a problem for years. What are like the AI unique things that you saw that like traditional purchase just didn't cover? Yeah.AI-specific challenges in browser infrastructurePaul [00:04:46]: First and foremost, I think back to like the first thing I did as a developer, like as a kid when I was writing code, I wanted to write code that did stuff for me. You know, I wanted to write code to automate my life. And I do that probably by using curl or beautiful soup to fetch data from a web browser. And I think I still do that now that I'm in the cloud. And the other thing that I think is a huge challenge for me is that you can't just create a web site and parse that data. And we all know that now like, you know, taking HTML and plugging that into an LLM, you can extract insights, you can summarize. So it was very clear that now like dynamic web scraping became very possible with the rise of large language models or a lot easier. And that was like a clear reason why there's been more usage of headless browsers, which are necessary because a lot of modern websites don't expose all of their page content via a simple HTTP request. You know, they actually do require you to run this type of code for a specific time. JavaScript on the page to hydrate this. Airbnb is a great example. You go to airbnb.com. A lot of that content on the page isn't there until after they run the initial hydration. So you can't just scrape it with a curl. You need to have some JavaScript run. And a browser is that JavaScript engine that's going to actually run all those requests on the page. So web data retrieval was definitely one driver of starting BrowserBase and the rise of being able to summarize that within LLM. Also, I was familiar with if I wanted to automate a website, I could write one script and that would work for one website. It was very static and deterministic. But the web is non-deterministic. The web is always changing. And until we had LLMs, there was no way to write scripts that you could write once that would run on any website. That would change with the structure of the website. Click the login button. It could mean something different on many different websites. And LLMs allow us to generate code on the fly to actually control that. So I think that rise of writing the generic automation scripts that can work on many different websites, to me, made it clear that browsers are going to be a lot more useful because now you can automate a lot more things without writing. If you wanted to write a script to book a demo call on 100 websites, previously, you had to write 100 scripts. Now you write one script that uses LLMs to generate that script. That's why we built our web browsing framework, StageHand, which does a lot of that work for you. But those two things, web data collection and then enhanced automation of many different websites, it just felt like big drivers for more browser infrastructure that would be required to power these kinds of features.Alessio [00:07:05]: And was multimodality also a big thing?Paul [00:07:08]: Now you can use the LLMs to look, even though the text in the dome might not be as friendly. Maybe my hot take is I was always kind of like, I didn't think vision would be as big of a driver. For UI automation, I felt like, you know, HTML is structured text and large language models are good with structured text. But it's clear that these computer use models are often vision driven, and they've been really pushing things forward. So definitely being multimodal, like rendering the page is required to take a screenshot to give that to a computer use model to take actions on a website. And it's just another win for browser. But I'll be honest, that wasn't what I was thinking early on. I didn't even think that we'd get here so fast with multimodality. I think we're going to have to get back to multimodal and vision models.swyx [00:07:50]: This is one of those things where I forgot to mention in my intro that I'm an investor in Browserbase. And I remember that when you pitched to me, like a lot of the stuff that we have today, we like wasn't on the original conversation. But I did have my original thesis was something that we've talked about on the podcast before, which is take the GPT store, the custom GPT store, all the every single checkbox and plugin is effectively a startup. And this was the browser one. I think the main hesitation, I think I actually took a while to get back to you. The main hesitation was that there were others. Like you're not the first hit list browser startup. It's not even your first hit list browser startup. There's always a question of like, will you be the category winner in a place where there's a bunch of incumbents, to be honest, that are bigger than you? They're just not targeted at the AI space. They don't have the backing of Nat Friedman. And there's a bunch of like, you're here in Silicon Valley. They're not. I don't know.Paul [00:08:47]: I don't know if that's, that was it, but like, there was a, yeah, I mean, like, I think I tried all the other ones and I was like, really disappointed. Like my background is from working at great developer tools, companies, and nothing had like the Vercel like experience. Um, like our biggest competitor actually is partly owned by private equity and they just jacked up their prices quite a bit. And the dashboard hasn't changed in five years. And I actually used them at my last company and tried them and I was like, oh man, like there really just needs to be something that's like the experience of these great infrastructure companies, like Stripe, like clerk, like Vercel that I use in love, but oriented towards this kind of like more specific category, which is browser infrastructure, which is really technically complex. Like a lot of stuff can go wrong on the internet when you're running a browser. The internet is very vast. There's a lot of different configurations. Like there's still websites that only work with internet explorer out there. How do you handle that when you're running your own browser infrastructure? These are the problems that we have to think about and solve at BrowserBase. And it's, it's certainly a labor of love, but I built this for me, first and foremost, I know it's super cheesy and everyone says that for like their startups, but it really, truly was for me. If you look at like the talks I've done even before BrowserBase, and I'm just like really excited to try and build a category defining infrastructure company. And it's, it's rare to have a new category of infrastructure exists. We're here in the Chroma offices and like, you know, vector databases is a new category of infrastructure. Is it, is it, I mean, we can, we're in their office, so, you know, we can, we can debate that one later. That is one.Multimodality in AI-Powered Browsingswyx [00:10:16]: That's one of the industry debates.Paul [00:10:17]: I guess we go back to the LLMOS talk that Karpathy gave way long ago. And like the browser box was very clearly there and it seemed like the people who were building in this space also agreed that browsers are a core primitive of infrastructure for the LLMOS that's going to exist in the future. And nobody was building something there that I wanted to use. So I had to go build it myself.swyx [00:10:38]: Yeah. I mean, exactly that talk that, that honestly, that diagram, every box is a startup and there's the code box and then there's the. The browser box. I think at some point they will start clashing there. There's always the question of the, are you a point solution or are you the sort of all in one? And I think the point solutions tend to win quickly, but then the only ones have a very tight cohesive experience. Yeah. Let's talk about just the hard problems of browser base you have on your website, which is beautiful. Thank you. Was there an agency that you used for that? Yeah. Herb.paris.Paul [00:11:11]: They're amazing. Herb.paris. Yeah. It's H-E-R-V-E. I highly recommend for developers. Developer tools, founders to work with consumer agencies because they end up building beautiful things and the Parisians know how to build beautiful interfaces. So I got to give prep.swyx [00:11:24]: And chat apps, apparently are, they are very fast. Oh yeah. The Mistral chat. Yeah. Mistral. Yeah.Paul [00:11:31]: Late chat.swyx [00:11:31]: Late chat. And then your videos as well, it was professionally shot, right? The series A video. Yeah.Alessio [00:11:36]: Nico did the videos. He's amazing. Not the initial video that you shot at the new one. First one was Austin.Paul [00:11:41]: Another, another video pretty surprised. But yeah, I mean, like, I think when you think about how you talk about your company. You have to think about the way you present yourself. It's, you know, as a developer, you think you evaluate a company based on like the API reliability and the P 95, but a lot of developers say, is the website good? Is the message clear? Do I like trust this founder? I'm building my whole feature on. So I've tried to nail that as well as like the reliability of the infrastructure. You're right. It's very hard. And there's a lot of kind of foot guns that you run into when running headless browsers at scale. Right.Competing with Existing Headless Browser Solutionsswyx [00:12:10]: So let's pick one. You have eight features here. Seamless integration. Scalability. Fast or speed. Secure. Observable. Stealth. That's interesting. Extensible and developer first. What comes to your mind as like the top two, three hardest ones? Yeah.Running headless browsers at scalePaul [00:12:26]: I think just running headless browsers at scale is like the hardest one. And maybe can I nerd out for a second? Is that okay? I heard this is a technical audience, so I'll talk to the other nerds. Whoa. They were listening. Yeah. They're upset. They're ready. The AGI is angry. Okay. So. So how do you run a browser in the cloud? Let's start with that, right? So let's say you're using a popular browser automation framework like Puppeteer, Playwright, and Selenium. Maybe you've written a code, some code locally on your computer that opens up Google. It finds the search bar and then types in, you know, search for Latent Space and hits the search button. That script works great locally. You can see the little browser open up. You want to take that to production. You want to run the script in a cloud environment. So when your laptop is closed, your browser is doing something. The browser is doing something. Well, I, we use Amazon. You can see the little browser open up. You know, the first thing I'd reach for is probably like some sort of serverless infrastructure. I would probably try and deploy on a Lambda. But Chrome itself is too big to run on a Lambda. It's over 250 megabytes. So you can't easily start it on a Lambda. So you maybe have to use something like Lambda layers to squeeze it in there. Maybe use a different Chromium build that's lighter. And you get it on the Lambda. Great. It works. But it runs super slowly. It's because Lambdas are very like resource limited. They only run like with one vCPU. You can run one process at a time. Remember, Chromium is super beefy. It's barely running on my MacBook Air. I'm still downloading it from a pre-run. Yeah, from the test earlier, right? I'm joking. But it's big, you know? So like Lambda, it just won't work really well. Maybe it'll work, but you need something faster. Your users want something faster. Okay. Well, let's put it on a beefier instance. Let's get an EC2 server running. Let's throw Chromium on there. Great. Okay. I can, that works well with one user. But what if I want to run like 10 Chromium instances, one for each of my users? Okay. Well, I might need two EC2 instances. Maybe 10. All of a sudden, you have multiple EC2 instances. This sounds like a problem for Kubernetes and Docker, right? Now, all of a sudden, you're using ECS or EKS, the Kubernetes or container solutions by Amazon. You're spending up and down containers, and you're spending a whole engineer's time on kind of maintaining this stateful distributed system. Those are some of the worst systems to run because when it's a stateful distributed system, it means that you are bound by the connections to that thing. You have to keep the browser open while someone is working with it, right? That's just a painful architecture to run. And there's all this other little gotchas with Chromium, like Chromium, which is the open source version of Chrome, by the way. You have to install all these fonts. You want emojis working in your browsers because your vision model is looking for the emoji. You need to make sure you have the emoji fonts. You need to make sure you have all the right extensions configured, like, oh, do you want ad blocking? How do you configure that? How do you actually record all these browser sessions? Like it's a headless browser. You can't look at it. So you need to have some sort of observability. Maybe you're recording videos and storing those somewhere. It all kind of adds up to be this just giant monster piece of your project when all you wanted to do was run a lot of browsers in production for this little script to go to google.com and search. And when I see a complex distributed system, I see an opportunity to build a great infrastructure company. And we really abstract that away with Browserbase where our customers can use these existing frameworks, Playwright, Publisher, Selenium, or our own stagehand and connect to our browsers in a serverless-like way. And control them, and then just disconnect when they're done. And they don't have to think about the complex distributed system behind all of that. They just get a browser running anywhere, anytime. Really easy to connect to.swyx [00:15:55]: I'm sure you have questions. My standard question with anything, so essentially you're a serverless browser company, and there's been other serverless things that I'm familiar with in the past, serverless GPUs, serverless website hosting. That's where I come from with Netlify. One question is just like, you promised to spin up thousands of servers. You promised to spin up thousands of browsers in milliseconds. I feel like there's no real solution that does that yet. And I'm just kind of curious how. The only solution I know, which is to kind of keep a kind of warm pool of servers around, which is expensive, but maybe not so expensive because it's just CPUs. So I'm just like, you know. Yeah.Browsers as a Core Primitive in AI InfrastructurePaul [00:16:36]: You nailed it, right? I mean, how do you offer a serverless-like experience with something that is clearly not serverless, right? And the answer is, you need to be able to run... We run many browsers on single nodes. We use Kubernetes at browser base. So we have many pods that are being scheduled. We have to predictably schedule them up or down. Yes, thousands of browsers in milliseconds is the best case scenario. If you hit us with 10,000 requests, you may hit a slower cold start, right? So we've done a lot of work on predictive scaling and being able to kind of route stuff to different regions where we have multiple regions of browser base where we have different pools available. You can also pick the region you want to go to based on like lower latency, round trip, time latency. It's very important with these types of things. There's a lot of requests going over the wire. So for us, like having a VM like Firecracker powering everything under the hood allows us to be super nimble and spin things up or down really quickly with strong multi-tenancy. But in the end, this is like the complex infrastructural challenges that we have to kind of deal with at browser base. And we have a lot more stuff on our roadmap to allow customers to have more levers to pull to exchange, do you want really fast browser startup times or do you want really low costs? And if you're willing to be more flexible on that, we may be able to kind of like work better for your use cases.swyx [00:17:44]: Since you used Firecracker, shouldn't Fargate do that for you or did you have to go lower level than that? We had to go lower level than that.Paul [00:17:51]: I find this a lot with Fargate customers, which is alarming for Fargate. We used to be a giant Fargate customer. Actually, the first version of browser base was ECS and Fargate. And unfortunately, it's a great product. I think we were actually the largest Fargate customer in our region for a little while. No, what? Yeah, seriously. And unfortunately, it's a great product, but I think if you're an infrastructure company, you actually have to have a deeper level of control over these primitives. I think it's the same thing is true with databases. We've used other database providers and I think-swyx [00:18:21]: Yeah, serverless Postgres.Paul [00:18:23]: Shocker. When you're an infrastructure company, you're on the hook if any provider has an outage. And I can't tell my customers like, hey, we went down because so-and-so went down. That's not acceptable. So for us, we've really moved to bringing things internally. It's kind of opposite of what we preach. We tell our customers, don't build this in-house, but then we're like, we build a lot of stuff in-house. But I think it just really depends on what is in the critical path. We try and have deep ownership of that.Alessio [00:18:46]: On the distributed location side, how does that work for the web where you might get sort of different content in different locations, but the customer is expecting, you know, if you're in the US, I'm expecting the US version. But if you're spinning up my browser in France, I might get the French version. Yeah.Paul [00:19:02]: Yeah. That's a good question. Well, generally, like on the localization, there is a thing called locale in the browser. You can set like what your locale is. If you're like in the ENUS browser or not, but some things do IP, IP based routing. And in that case, you may want to have a proxy. Like let's say you're running something in the, in Europe, but you want to make sure you're showing up from the US. You may want to use one of our proxy features so you can turn on proxies to say like, make sure these connections always come from the United States, which is necessary too, because when you're browsing the web, you're coming from like a, you know, data center IP, and that can make things a lot harder to browse web. So we do have kind of like this proxy super network. Yeah. We have a proxy for you based on where you're going, so you can reliably automate the web. But if you get scheduled in Europe, that doesn't happen as much. We try and schedule you as close to, you know, your origin that you're trying to go to. But generally you have control over the regions you can put your browsers in. So you can specify West one or East one or Europe. We only have one region of Europe right now, actually. Yeah.Alessio [00:19:55]: What's harder, the browser or the proxy? I feel like to me, it feels like actually proxying reliably at scale. It's much harder than spending up browsers at scale. I'm curious. It's all hard.Paul [00:20:06]: It's layers of hard, right? Yeah. I think it's different levels of hard. I think the thing with the proxy infrastructure is that we work with many different web proxy providers and some are better than others. Some have good days, some have bad days. And our customers who've built browser infrastructure on their own, they have to go and deal with sketchy actors. Like first they figure out their own browser infrastructure and then they got to go buy a proxy. And it's like you can pay in Bitcoin and it just kind of feels a little sus, right? It's like you're buying drugs when you're trying to get a proxy online. We have like deep relationships with these counterparties. We're able to audit them and say, is this proxy being sourced ethically? Like it's not running on someone's TV somewhere. Is it free range? Yeah. Free range organic proxies, right? Right. We do a level of diligence. We're SOC 2. So we have to understand what is going on here. But then we're able to make sure that like we route around proxy providers not working. There's proxy providers who will just, the proxy will stop working all of a sudden. And then if you don't have redundant proxying on your own browsers, that's hard down for you or you may get some serious impacts there. With us, like we intelligently know, hey, this proxy is not working. Let's go to this one. And you can kind of build a network of multiple providers to really guarantee the best uptime for our customers. Yeah. So you don't own any proxies? We don't own any proxies. You're right. The team has been saying who wants to like take home a little proxy server, but not yet. We're not there yet. You know?swyx [00:21:25]: It's a very mature market. I don't think you should build that yourself. Like you should just be a super customer of them. Yeah. Scraping, I think, is the main use case for that. I guess. Well, that leads us into CAPTCHAs and also off, but let's talk about CAPTCHAs. You had a little spiel that you wanted to talk about CAPTCHA stuff.Challenges of Scaling Browser InfrastructurePaul [00:21:43]: Oh, yeah. I was just, I think a lot of people ask, if you're thinking about proxies, you're thinking about CAPTCHAs too. I think it's the same thing. You can go buy CAPTCHA solvers online, but it's the same buying experience. It's some sketchy website, you have to integrate it. It's not fun to buy these things and you can't really trust that the docs are bad. What Browserbase does is we integrate a bunch of different CAPTCHAs. We do some stuff in-house, but generally we just integrate with a bunch of known vendors and continually monitor and maintain these things and say, is this working or not? Can we route around it or not? These are CAPTCHA solvers. CAPTCHA solvers, yeah. Not CAPTCHA providers, CAPTCHA solvers. Yeah, sorry. CAPTCHA solvers. We really try and make sure all of that works for you. I think as a dev, if I'm buying infrastructure, I want it all to work all the time and it's important for us to provide that experience by making sure everything does work and monitoring it on our own. Yeah. Right now, the world of CAPTCHAs is tricky. I think AI agents in particular are very much ahead of the internet infrastructure. CAPTCHAs are designed to block all types of bots, but there are now good bots and bad bots. I think in the future, CAPTCHAs will be able to identify who a good bot is, hopefully via some sort of KYC. For us, we've been very lucky. We have very little to no known abuse of Browserbase because we really look into who we work with. And for certain types of CAPTCHA solving, we only allow them on certain types of plans because we want to make sure that we can know what people are doing, what their use cases are. And that's really allowed us to try and be an arbiter of good bots, which is our long term goal. I want to build great relationships with people like Cloudflare so we can agree, hey, here are these acceptable bots. We'll identify them for you and make sure we flag when they come to your website. This is a good bot, you know?Alessio [00:23:23]: I see. And Cloudflare said they want to do more of this. So they're going to set by default, if they think you're an AI bot, they're going to reject. I'm curious if you think this is something that is going to be at the browser level or I mean, the DNS level with Cloudflare seems more where it should belong. But I'm curious how you think about it.Paul [00:23:40]: I think the web's going to change. You know, I think that the Internet as we have it right now is going to change. And we all need to just accept that the cat is out of the bag. And instead of kind of like wishing the Internet was like it was in the 2000s, we can have free content line that wouldn't be scraped. It's just it's not going to happen. And instead, we should think about like, one, how can we change? How can we change the models of, you know, information being published online so people can adequately commercialize it? But two, how do we rebuild applications that expect that AI agents are going to log in on their behalf? Those are the things that are going to allow us to kind of like identify good and bad bots. And I think the team at Clerk has been doing a really good job with this on the authentication side. I actually think that auth is the biggest thing that will prevent agents from accessing stuff, not captchas. And I think there will be agent auth in the future. I don't know if it's going to happen from an individual company, but actually authentication providers that have a, you know, hidden login as agent feature, which will then you put in your email, you'll get a push notification, say like, hey, your browser-based agent wants to log into your Airbnb. You can approve that and then the agent can proceed. That really circumvents the need for captchas or logging in as you and sharing your password. I think agent auth is going to be one way we identify good bots going forward. And I think a lot of this captcha solving stuff is really short-term problems as the internet kind of reorients itself around how it's going to work with agents browsing the web, just like people do. Yeah.Managing Distributed Browser Locations and Proxiesswyx [00:24:59]: Stitch recently was on Hacker News for talking about agent experience, AX, which is a thing that Netlify is also trying to clone and coin and talk about. And we've talked about this on our previous episodes before in a sense that I actually think that's like maybe the only part of the tech stack that needs to be kind of reinvented for agents. Everything else can stay the same, CLIs, APIs, whatever. But auth, yeah, we need agent auth. And it's mostly like short-lived, like it should not, it should be a distinct, identity from the human, but paired. I almost think like in the same way that every social network should have your main profile and then your alt accounts or your Finsta, it's almost like, you know, every, every human token should be paired with the agent token and the agent token can go and do stuff on behalf of the human token, but not be presumed to be the human. Yeah.Paul [00:25:48]: It's like, it's, it's actually very similar to OAuth is what I'm thinking. And, you know, Thread from Stitch is an investor, Colin from Clerk, Octaventures, all investors in browser-based because like, I hope they solve this because they'll make browser-based submission more possible. So we don't have to overcome all these hurdles, but I think it will be an OAuth-like flow where an agent will ask to log in as you, you'll approve the scopes. Like it can book an apartment on Airbnb, but it can't like message anybody. And then, you know, the agent will have some sort of like role-based access control within an application. Yeah. I'm excited for that.swyx [00:26:16]: The tricky part is just, there's one, one layer of delegation here, which is like, you're authoring my user's user or something like that. I don't know if that's tricky or not. Does that make sense? Yeah.Paul [00:26:25]: You know, actually at Twilio, I worked on the login identity and access. Management teams, right? So like I built Twilio's login page.swyx [00:26:31]: You were an intern on that team and then you became the lead in two years? Yeah.Paul [00:26:34]: Yeah. I started as an intern in 2016 and then I was the tech lead of that team. How? That's not normal. I didn't have a life. He's not normal. Look at this guy. I didn't have a girlfriend. I just loved my job. I don't know. I applied to 500 internships for my first job and I got rejected from every single one of them except for Twilio and then eventually Amazon. And they took a shot on me and like, I was getting paid money to write code, which was my dream. Yeah. Yeah. I'm very lucky that like this coding thing worked out because I was going to be doing it regardless. And yeah, I was able to kind of spend a lot of time on a team that was growing at a company that was growing. So it informed a lot of this stuff here. I think these are problems that have been solved with like the SAML protocol with SSO. I think it's a really interesting stuff with like WebAuthn, like these different types of authentication, like schemes that you can use to authenticate people. The tooling is all there. It just needs to be tweaked a little bit to work for agents. And I think the fact that there are companies that are already. Providing authentication as a service really sets it up. Well, the thing that's hard is like reinventing the internet for agents. We don't want to rebuild the internet. That's an impossible task. And I think people often say like, well, we'll have this second layer of APIs built for agents. I'm like, we will for the top use cases, but instead of we can just tweak the internet as is, which is on the authentication side, I think we're going to be the dumb ones going forward. Unfortunately, I think AI is going to be able to do a lot of the tasks that we do online, which means that it will be able to go to websites, click buttons on our behalf and log in on our behalf too. So with this kind of like web agent future happening, I think with some small structural changes, like you said, it feels like it could all slot in really nicely with the existing internet.Handling CAPTCHAs and Agent Authenticationswyx [00:28:08]: There's one more thing, which is the, your live view iframe, which lets you take, take control. Yeah. Obviously very key for operator now, but like, was, is there anything interesting technically there or that the people like, well, people always want this.Paul [00:28:21]: It was really hard to build, you know, like, so, okay. Headless browsers, you don't see them, right. They're running. They're running in a cloud somewhere. You can't like look at them. And I just want to really make, it's a weird name. I wish we came up with a better name for this thing, but you can't see them. Right. But customers don't trust AI agents, right. At least the first pass. So what we do with our live view is that, you know, when you use browser base, you can actually embed a live view of the browser running in the cloud for your customer to see it working. And that's what the first reason is the build trust, like, okay, so I have this script. That's going to go automate a website. I can embed it into my web application via an iframe and my customer can watch. I think. And then we added two way communication. So now not only can you watch the browser kind of being operated by AI, if you want to pause and actually click around type within this iframe that's controlling a browser, that's also possible. And this is all thanks to some of the lower level protocol, which is called the Chrome DevTools protocol. It has a API called start screencast, and you can also send mouse clicks and button clicks to a remote browser. And this is all embeddable within iframes. You have a browser within a browser, yo. And then you simulate the screen, the click on the other side. Exactly. And this is really nice often for, like, let's say, a capture that can't be solved. You saw this with Operator, you know, Operator actually uses a different approach. They use VNC. So, you know, you're able to see, like, you're seeing the whole window here. What we're doing is something a little lower level with the Chrome DevTools protocol. It's just PNGs being streamed over the wire. But the same thing is true, right? Like, hey, I'm running a window. Pause. Can you do something in this window? Human. Okay, great. Resume. Like sometimes 2FA tokens. Like if you get that text message, you might need a person to type that in. Web agents need human-in-the-loop type workflows still. You still need a person to interact with the browser. And building a UI to proxy that is kind of hard. You may as well just show them the whole browser and say, hey, can you finish this up for me? And then let the AI proceed on afterwards. Is there a future where I stream my current desktop to browser base? I don't think so. I think we're very much cloud infrastructure. Yeah. You know, but I think a lot of the stuff we're doing, we do want to, like, build tools. Like, you know, we'll talk about the stage and, you know, web agent framework in a second. But, like, there's a case where a lot of people are going desktop first for, you know, consumer use. And I think cloud is doing a lot of this, where I expect to see, you know, MCPs really oriented around the cloud desktop app for a reason, right? Like, I think a lot of these tools are going to run on your computer because it makes... I think it's breaking out. People are putting it on a server. Oh, really? Okay. Well, sweet. We'll see. We'll see that. I was surprised, though, wasn't I? I think that the browser company, too, with Dia Browser, it runs on your machine. You know, it's going to be...swyx [00:30:50]: What is it?Paul [00:30:51]: So, Dia Browser, as far as I understand... I used to use Arc. Yeah. I haven't used Arc. But I'm a big fan of the browser company. I think they're doing a lot of cool stuff in consumer. As far as I understand, it's a browser where you have a sidebar where you can, like, chat with it and it can control the local browser on your machine. So, if you imagine, like, what a consumer web agent is, which it lives alongside your browser, I think Google Chrome has Project Marina, I think. I almost call it Project Marinara for some reason. I don't know why. It's...swyx [00:31:17]: No, I think it's someone really likes the Waterworld. Oh, I see. The classic Kevin Costner. Yeah.Paul [00:31:22]: Okay. Project Marinara is a similar thing to the Dia Browser, in my mind, as far as I understand it. You have a browser that has an AI interface that will take over your mouse and keyboard and control the browser for you. Great for consumer use cases. But if you're building applications that rely on a browser and it's more part of a greater, like, AI app experience, you probably need something that's more like infrastructure, not a consumer app.swyx [00:31:44]: Just because I have explored a little bit in this area, do people want branching? So, I have the state. Of whatever my browser's in. And then I want, like, 100 clones of this state. Do people do that? Or...Paul [00:31:56]: People don't do it currently. Yeah. But it's definitely something we're thinking about. I think the idea of forking a browser is really cool. Technically, kind of hard. We're starting to see this in code execution, where people are, like, forking some, like, code execution, like, processes or forking some tool calls or branching tool calls. Haven't seen it at the browser level yet. But it makes sense. Like, if an AI agent is, like, using a website and it's not sure what path it wants to take to crawl this website. To find the information it's looking for. It would make sense for it to explore both paths in parallel. And that'd be a very, like... A road not taken. Yeah. And hopefully find the right answer. And then say, okay, this was actually the right one. And memorize that. And go there in the future. On the roadmap. For sure. Don't make my roadmap, please. You know?Alessio [00:32:37]: How do you actually do that? Yeah. How do you fork? I feel like the browser is so stateful for so many things.swyx [00:32:42]: Serialize the state. Restore the state. I don't know.Paul [00:32:44]: So, it's one of the reasons why we haven't done it yet. It's hard. You know? Like, to truly fork, it's actually quite difficult. The naive way is to open the same page in a new tab and then, like, hope that it's at the same thing. But if you have a form halfway filled, you may have to, like, take the whole, you know, container. Pause it. All the memory. Duplicate it. Restart it from there. It could be very slow. So, we haven't found a thing. Like, the easy thing to fork is just, like, copy the page object. You know? But I think there needs to be something a little bit more robust there. Yeah.swyx [00:33:12]: So, MorphLabs has this infinite branch thing. Like, wrote a custom fork of Linux or something that let them save the system state and clone it. MorphLabs, hit me up. I'll be a customer. Yeah. That's the only. I think that's the only way to do it. Yeah. Like, unless Chrome has some special API for you. Yeah.Paul [00:33:29]: There's probably something we'll reverse engineer one day. I don't know. Yeah.Alessio [00:33:32]: Let's talk about StageHand, the AI web browsing framework. You have three core components, Observe, Extract, and Act. Pretty clean landing page. What was the idea behind making a framework? Yeah.Stagehand: AI web browsing frameworkPaul [00:33:43]: So, there's three frameworks that are very popular or already exist, right? Puppeteer, Playwright, Selenium. Those are for building hard-coded scripts to control websites. And as soon as I started to play with LLMs plus browsing, I caught myself, you know, code-genning Playwright code to control a website. I would, like, take the DOM. I'd pass it to an LLM. I'd say, can you generate the Playwright code to click the appropriate button here? And it would do that. And I was like, this really should be part of the frameworks themselves. And I became really obsessed with SDKs that take natural language as part of, like, the API input. And that's what StageHand is. StageHand exposes three APIs, and it's a super set of Playwright. So, if you go to a page, you may want to take an action, click on the button, fill in the form, etc. That's what the act command is for. You may want to extract some data. This one takes a natural language, like, extract the winner of the Super Bowl from this page. You can give it a Zod schema, so it returns a structured output. And then maybe you're building an API. You can do an agent loop, and you want to kind of see what actions are possible on this page before taking one. You can do observe. So, you can observe the actions on the page, and it will generate a list of actions. You can guide it, like, give me actions on this page related to buying an item. And you can, like, buy it now, add to cart, view shipping options, and pass that to an LLM, an agent loop, to say, what's the appropriate action given this high-level goal? So, StageHand isn't a web agent. It's a framework for building web agents. And we think that agent loops are actually pretty close to the application layer because every application probably has different goals or different ways it wants to take steps. I don't think I've seen a generic. Maybe you guys are the experts here. I haven't seen, like, a really good AI agent framework here. Everyone kind of has their own special sauce, right? I see a lot of developers building their own agent loops, and they're using tools. And I view StageHand as the browser tool. So, we expose act, extract, observe. Your agent can call these tools. And from that, you don't have to worry about it. You don't have to worry about generating playwright code performantly. You don't have to worry about running it. You can kind of just integrate these three tool calls into your agent loop and reliably automate the web.swyx [00:35:48]: A special shout-out to Anirudh, who I met at your dinner, who I think listens to the pod. Yeah. Hey, Anirudh.Paul [00:35:54]: Anirudh's a man. He's a StageHand guy.swyx [00:35:56]: I mean, the interesting thing about each of these APIs is they're kind of each startup. Like, specifically extract, you know, Firecrawler is extract. There's, like, Expand AI. There's a whole bunch of, like, extract companies. They just focus on extract. I'm curious. Like, I feel like you guys are going to collide at some point. Like, right now, it's friendly. Everyone's in a blue ocean. At some point, it's going to be valuable enough that there's some turf battle here. I don't think you have a dog in a fight. I think you can mock extract to use an external service if they're better at it than you. But it's just an observation that, like, in the same way that I see each option, each checkbox in the side of custom GBTs becoming a startup or each box in the Karpathy chart being a startup. Like, this is also becoming a thing. Yeah.Paul [00:36:41]: I mean, like, so the way StageHand works is that it's MIT-licensed, completely open source. You bring your own API key to your LLM of choice. You could choose your LLM. We don't make any money off of the extract or really. We only really make money if you choose to run it with our browser. You don't have to. You can actually use your own browser, a local browser. You know, StageHand is completely open source for that reason. And, yeah, like, I think if you're building really complex web scraping workflows, I don't know if StageHand is the tool for you. I think it's really more if you're building an AI agent that needs a few general tools or if it's doing a lot of, like, web automation-intensive work. But if you're building a scraping company, StageHand is not your thing. You probably want something that's going to, like, get HTML content, you know, convert that to Markdown, query it. That's not what StageHand does. StageHand is more about reliability. I think we focus a lot on reliability and less so on cost optimization and speed at this point.swyx [00:37:33]: I actually feel like StageHand, so the way that StageHand works, it's like, you know, page.act, click on the quick start. Yeah. It's kind of the integration test for the code that you would have to write anyway, like the Puppeteer code that you have to write anyway. And when the page structure changes, because it always does, then this is still the test. This is still the test that I would have to write. Yeah. So it's kind of like a testing framework that doesn't need implementation detail.Paul [00:37:56]: Well, yeah. I mean, Puppeteer, Playwright, and Slenderman were all designed as testing frameworks, right? Yeah. And now people are, like, hacking them together to automate the web. I would say, and, like, maybe this is, like, me being too specific. But, like, when I write tests, if the page structure changes. Without me knowing, I want that test to fail. So I don't know if, like, AI, like, regenerating that. Like, people are using StageHand for testing. But it's more for, like, usability testing, not, like, testing of, like, does the front end, like, has it changed or not. Okay. But generally where we've seen people, like, really, like, take off is, like, if they're using, you know, something. If they want to build a feature in their application that's kind of like Operator or Deep Research, they're using StageHand to kind of power that tool calling in their own agent loop. Okay. Cool.swyx [00:38:37]: So let's go into Operator, the first big agent launch of the year from OpenAI. Seems like they have a whole bunch scheduled. You were on break and your phone blew up. What's your just general view of computer use agents is what they're calling it. The overall category before we go into Open Operator, just the overall promise of Operator. I will observe that I tried it once. It was okay. And I never tried it again.OpenAI's Operator and computer use agentsPaul [00:38:58]: That tracks with my experience, too. Like, I'm a huge fan of the OpenAI team. Like, I think that I do not view Operator as the company. I'm not a company killer for browser base at all. I think it actually shows people what's possible. I think, like, computer use models make a lot of sense. And I'm actually most excited about computer use models is, like, their ability to, like, really take screenshots and reasoning and output steps. I think that using mouse click or mouse coordinates, I've seen that proved to be less reliable than I would like. And I just wonder if that's the right form factor. What we've done with our framework is anchor it to the DOM itself, anchor it to the actual item. So, like, if it's clicking on something, it's clicking on that thing, you know? Like, it's more accurate. No matter where it is. Yeah, exactly. Because it really ties in nicely. And it can handle, like, the whole viewport in one go, whereas, like, Operator can only handle what it sees. Can you hover? Is hovering a thing that you can do? I don't know if we expose it as a tool directly, but I'm sure there's, like, an API for hovering. Like, move mouse to this position. Yeah, yeah, yeah. I think you can trigger hover, like, via, like, the JavaScript on the DOM itself. But, no, I think, like, when we saw computer use, everyone's eyes lit up because they realized, like, wow, like, AI is going to actually automate work for people. And I think seeing that kind of happen from both of the labs, and I'm sure we're going to see more labs launch computer use models, I'm excited to see all the stuff that people build with it. I think that I'd love to see computer use power, like, controlling a browser on browser base. And I think, like, Open Operator, which was, like, our open source version of OpenAI's Operator, was our first take on, like, how can we integrate these models into browser base? And we handle the infrastructure and let the labs do the models. I don't have a sense that Operator will be released as an API. I don't know. Maybe it will. I'm curious to see how well that works because I think it's going to be really hard for a company like OpenAI to do things like support CAPTCHA solving or, like, have proxies. Like, I think it's hard for them structurally. Imagine this New York Times headline, OpenAI CAPTCHA solving. Like, that would be a pretty bad headline, this New York Times headline. Browser base solves CAPTCHAs. No one cares. No one cares. And, like, our investors are bored. Like, we're all okay with this, you know? We're building this company knowing that the CAPTCHA solving is short-lived until we figure out how to authenticate good bots. I think it's really hard for a company like OpenAI, who has this brand that's so, so good, to balance with, like, the icky parts of web automation, which it can be kind of complex to solve. I'm sure OpenAI knows who to call whenever they need you. Yeah, right. I'm sure they'll have a great partnership.Alessio [00:41:23]: And is Open Operator just, like, a marketing thing for you? Like, how do you think about resource allocation? So, you can spin this up very quickly. And now there's all this, like, open deep research, just open all these things that people are building. We started it, you know. You're the original Open. We're the original Open operator, you know? Is it just, hey, look, this is a demo, but, like, we'll help you build out an actual product for yourself? Like, are you interested in going more of a product route? That's kind of the OpenAI way, right? They started as a model provider and then…Paul [00:41:53]: Yeah, we're not interested in going the product route yet. I view Open Operator as a model provider. It's a reference project, you know? Let's show people how to build these things using the infrastructure and models that are out there. And that's what it is. It's, like, Open Operator is very simple. It's an agent loop. It says, like, take a high-level goal, break it down into steps, use tool calling to accomplish those steps. It takes screenshots and feeds those screenshots into an LLM with the step to generate the right action. It uses stagehand under the hood to actually execute this action. It doesn't use a computer use model. And it, like, has a nice interface using the live view that we talked about, the iframe, to embed that into an application. So I felt like people on launch day wanted to figure out how to build their own version of this. And we turned that around really quickly to show them. And I hope we do that with other things like deep research. We don't have a deep research launch yet. I think David from AOMNI actually has an amazing open deep research that he launched. It has, like, 10K GitHub stars now. So he's crushing that. But I think if people want to build these features natively into their application, they need good reference projects. And I think Open Operator is a good example of that.swyx [00:42:52]: I don't know. Actually, I'm actually pretty bullish on API-driven operator. Because that's the only way that you can sort of, like, once it's reliable enough, obviously. And now we're nowhere near. But, like, give it five years. It'll happen, you know. And then you can sort of spin this up and browsers are working in the background and you don't necessarily have to know. And it just is booking restaurants for you, whatever. I can definitely see that future happening. I had this on the landing page here. This might be a slightly out of order. But, you know, you have, like, sort of three use cases for browser base. Open Operator. Or this is the operator sort of use case. It's kind of like the workflow automation use case. And it completes with UiPath in the sort of RPA category. Would you agree with that? Yeah, I would agree with that. And then there's Agents we talked about already. And web scraping, which I imagine would be the bulk of your workload right now, right?Paul [00:43:40]: No, not at all. I'd say actually, like, the majority is browser automation. We're kind of expensive for web scraping. Like, I think that if you're building a web scraping product, if you need to do occasional web scraping or you have to do web scraping that works every single time, you want to use browser automation. Yeah. You want to use browser-based. But if you're building web scraping workflows, what you should do is have a waterfall. You should have the first request is a curl to the website. See if you can get it without even using a browser. And then the second request may be, like, a scraping-specific API. There's, like, a thousand scraping APIs out there that you can use to try and get data. Scraping B. Scraping B is a great example, right? Yeah. And then, like, if those two don't work, bring out the heavy hitter. Like, browser-based will 100% work, right? It will load the page in a real browser, hydrate it. I see.swyx [00:44:21]: Because a lot of people don't render to JS.swyx [00:44:25]: Yeah, exactly.Paul [00:44:26]: So, I mean, the three big use cases, right? Like, you know, automation, web data collection, and then, you know, if you're building anything agentic that needs, like, a browser tool, you want to use browser-based.Alessio [00:44:35]: Is there any use case that, like, you were super surprised by that people might not even think about? Oh, yeah. Or is it, yeah, anything that you can share? The long tail is crazy. Yeah.Surprising use cases of BrowserbasePaul [00:44:44]: One of the case studies on our website that I think is the most interesting is this company called Benny. So, the way that it works is if you're on food stamps in the United States, you can actually get rebates if you buy certain things. Yeah. You buy some vegetables. You submit your receipt to the government. They'll give you a little rebate back. Say, hey, thanks for buying vegetables. It's good for you. That process of submitting that receipt is very painful. And the way Benny works is you use their app to take a photo of your receipt, and then Benny will go submit that receipt for you and then deposit the money into your account. That's actually using no AI at all. It's all, like, hard-coded scripts. They maintain the scripts. They've been doing a great job. And they build this amazing consumer app. But it's an example of, like, all these, like, tedious workflows that people have to do to kind of go about their business. And they're doing it for the sake of their day-to-day lives. And I had never known about, like, food stamp rebates or the complex forms you have to do to fill them. But the world is powered by millions and millions of tedious forms, visas. You know, Emirate Lighthouse is a customer, right? You know, they do the O1 visa. Millions and millions of forms are taking away humans' time. And I hope that Browserbase can help power software that automates away the web forms that we don't need anymore. Yeah.swyx [00:45:49]: I mean, I'm very supportive of that. I mean, forms. I do think, like, government itself is a big part of it. I think the government itself should embrace AI more to do more sort of human-friendly form filling. Mm-hmm. But I'm not optimistic. I'm not holding my breath. Yeah. We'll see. Okay. I think I'm about to zoom out. I have a little brief thing on computer use, and then we can talk about founder stuff, which is, I tend to think of developer tooling markets in impossible triangles, where everyone starts in a niche, and then they start to branch out. So I already hinted at a little bit of this, right? We mentioned more. We mentioned E2B. We mentioned Firecrawl. And then there's Browserbase. So there's, like, all this stuff of, like, have serverless virtual computer that you give to an agent and let them do stuff with it. And there's various ways of connecting it to the internet. You can just connect to a search API, like SERP API, whatever other, like, EXA is another one. That's what you're searching. You can also have a JSON markdown extractor, which is Firecrawl. Or you can have a virtual browser like Browserbase, or you can have a virtual machine like Morph. And then there's also maybe, like, a virtual sort of code environment, like Code Interpreter. So, like, there's just, like, a bunch of different ways to tackle the problem of give a computer to an agent. And I'm just kind of wondering if you see, like, everyone's just, like, happily coexisting in their respective niches. And as a developer, I just go and pick, like, a shopping basket of one of each. Or do you think that you eventually, people will collide?Future of browser automation and market competitionPaul [00:47:18]: I think that currently it's not a zero-sum market. Like, I think we're talking about... I think we're talking about all of knowledge work that people do that can be automated online. All of these, like, trillions of hours that happen online where people are working. And I think that there's so much software to be built that, like, I tend not to think about how these companies will collide. I just try to solve the problem as best as I can and make this specific piece of infrastructure, which I think is an important primitive, the best I possibly can. And yeah. I think there's players that are actually going to like it. I think there's players that are going to launch, like, over-the-top, you know, platforms, like agent platforms that have all these tools built in, right? Like, who's building the rippling for agent tools that has the search tool, the browser tool, the operating system tool, right? There are some. There are some. There are some, right? And I think in the end, what I have seen as my time as a developer, and I look at all the favorite tools that I have, is that, like, for tools and primitives with sufficient levels of complexity, you need to have a solution that's really bespoke to that primitive, you know? And I am sufficiently convinced that the browser is complex enough to deserve a primitive. Obviously, I have to. I'm the founder of BrowserBase, right? I'm talking my book. But, like, I think maybe I can give you one spicy take against, like, maybe just whole OS running. I think that when I look at computer use when it first came out, I saw that the majority of use cases for computer use were controlling a browser. And do we really need to run an entire operating system just to control a browser? I don't think so. I don't think that's necessary. You know, BrowserBase can run browsers for way cheaper than you can if you're running a full-fledged OS with a GUI, you know, operating system. And I think that's just an advantage of the browser. It is, like, browsers are little OSs, and you can run them very efficiently if you orchestrate it well. And I think that allows us to offer 90% of the, you know, functionality in the platform needed at 10% of the cost of running a full OS. Yeah.Open Operator: Browserbase's Open-Source Alternativeswyx [00:49:16]: I definitely see the logic in that. There's a Mark Andreessen quote. I don't know if you know this one. Where he basically observed that the browser is turning the operating system into a poorly debugged set of device drivers, because most of the apps are moved from the OS to the browser. So you can just run browsers.Paul [00:49:31]: There's a place for OSs, too. Like, I think that there are some applications that only run on Windows operating systems. And Eric from pig.dev in this upcoming YC batch, or last YC batch, like, he's building all run tons of Windows operating systems for you to control with your agent. And like, there's some legacy EHR systems that only run on Internet-controlled systems. Yeah.Paul [00:49:54]: I think that's it. I think, like, there are use cases for specific operating systems for specific legacy software. And like, I'm excited to see what he does with that. I just wanted to give a shout out to the pig.dev website.swyx [00:50:06]: The pigs jump when you click on them. Yeah. That's great.Paul [00:50:08]: Eric, he's the former co-founder of banana.dev, too.swyx [00:50:11]: Oh, that Eric. Yeah. That Eric. Okay. Well, he abandoned bananas for pigs. I hope he doesn't start going around with pigs now.Alessio [00:50:18]: Like he was going around with bananas. A little toy pig. Yeah. Yeah. I love that. What else are we missing? I think we covered a lot of, like, the browser-based product history, but. What do you wish people asked you? Yeah.Paul [00:50:29]: I wish people asked me more about, like, what will the future of software look like? Because I think that's really where I've spent a lot of time about why do browser-based. Like, for me, starting a company is like a means of last resort. Like, you shouldn't start a company unless you absolutely have to. And I remain convinced that the future of software is software that you're going to click a button and it's going to do stuff on your behalf. Right now, software. You click a button and it maybe, like, calls it back an API and, like, computes some numbers. It, like, modifies some text, whatever. But the future of software is software using software. So, I may log into my accounting website for my business, click a button, and it's going to go load up my Gmail, search my emails, find the thing, upload the receipt, and then comment it for me. Right? And it may use it using APIs, maybe a browser. I don't know. I think it's a little bit of both. But that's completely different from how we've built software so far. And that's. I think that future of software has different infrastructure requirements. It's going to require different UIs. It's going to require different pieces of infrastructure. I think the browser infrastructure is one piece that fits into that, along with all the other categories you mentioned. So, I think that it's going to require developers to think differently about how they've built software for, you know

Steve Jobs foi um empresário norte-americano do ramo de tecnologia, fundador da Apple Computer, hoje Apple Inc. Pioneiro da indústria de computadores pessoais, teve enorme influência na adoção e popularização da informática como item de consumo de massas. Mas foi muito além disso.  Jobs é, até hoje, quase 15 anos após seu falecimento, exemplo de empreendedorismo, sucesso e obstinação. Por isso, a história dele será contada neste episódio de Do Zero ao Topo - Personalidades. Este episódio faz parte de uma nova série do nosso podcast, que vai contar, em cada episódio, a história de um grande inovador de sucesso. Para saber mais sobre a história do 'gênio da Apple' acesse: https://www.infomoney.com.br/perfil/steve-jobs/

L'image du garage comme berceau d'Apple est un mythe largement répandu. On imagine souvent Steve Jobs et Steve Wozniak, deux jeunes génies bidouillant des circuits électroniques dans un modeste garage californien, donnant naissance à l'une des plus grandes entreprises technologiques du monde. En réalité, la création d'Apple ne s'est pas déroulée de cette façon.D'où vient le mythe du garage ?L'histoire du garage provient du fait que Steve Jobs et Steve Wozniak ont effectivement utilisé le garage des parents de Jobs, à Los Altos, mais pas pour concevoir les premiers ordinateurs d'Apple. Comme l'a expliqué Steve Wozniak lui-même, « Le garage, c'était un mythe. Nous n'avons rien conçu, rien fabriqué, rien vendu dans ce garage. C'était juste un bon endroit pour traîner. »L'idée d'Apple et le développement du premier ordinateur, l'Apple I, sont en réalité nés ailleurs :- Wozniak a conçu le premier prototype sur du papier et a fabriqué l'Apple I chez lui, en dehors du garage.- Jobs a trouvé les premiers financements et clients, notamment Paul Terrell, propriétaire du magasin Byte Shop, qui a commandé 50 unités.- Les premiers ordinateurs ont été assemblés dans un petit local industriel de Cupertino, bien plus adapté que le garage des Jobs.Pourquoi ce mythe persiste-t-il ?Le récit du garage correspond parfaitement au rêve américain : l'idée qu'une grande entreprise peut naître dans un lieu modeste, grâce au travail acharné et au génie de ses fondateurs. Ce mythe est aussi renforcé par d'autres success stories similaires, comme celle de Hewlett-Packard, qui, elle, a bien commencé dans un garage.De plus, Steve Jobs lui-même a parfois entretenu cette légende, sachant qu'elle rendait l'histoire d'Apple plus inspirante et accessible.L'importance réelle du garageMême si Apple n'a pas été inventée dans ce garage, il a quand même eu un rôle symbolique. C'était un lieu de rencontre, un espace où Jobs et Wozniak pouvaient rêver, discuter et planifier leurs ambitions. Mais la véritable naissance d'Apple s'est faite grâce aux compétences de Wozniak, à la vision de Jobs et aux premiers investisseurs, bien au-delà des murs d'un simple garage.Ainsi, Apple n'est pas née d'un garage, mais d'un mélange d'ingéniosité, de persévérance et d'opportunités saisies au bon moment. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

In this in-person episode recorded at Ashley Wozniak Designs' studio in Wexford, PA, I sit down with the incredible Ashley Wozniak. From her early days as a teacher to flipping homes and now running her thriving design business, Ashley shares the pivotal moments that shaped her career and creative vision. We dive into her passion for design, the challenges of transitioning careers, and her approach to creating stunning spaces. To wrap up, we embrace the holiday spirit with a lively chat about all things Christmas. Tune in for inspiration, insights, and festive fun!

In this week's North American Ag Spotlight podcast Chrissy Wozniak welcomes back Mindy Patterson, president and co-founder of The Cavalry Group and an unwavering advocate for agriculture. Mindy shares her perspective on the aftermath of the November election, discussing key government picks and their potential impact on agriculture, private property rights, and American livelihoods.Key Topics Covered:The Importance of Legislative Awareness: Mindy emphasizes how legislation at the local, state, and federal levels can significantly affect farmers, ranchers, and business owners, urging the agricultural community to stay vigilant and involved.The Sustains Act and Its Implications: A detailed breakdown of the Sustains Act, highlighting its potential threats to private property and rural communities under the guise of conservation and public-private partnerships.Defending Private Property Rights: The risks of government overreach, eminent domain misuse, and how these issues intertwine with controversial policies like CO2 pipelines and conservation easements.The Fight Against Animal Rights Extremism: Updates on The Cavalry Group's efforts to combat deceptive legislation targeting lawful businesses, including rodeo and horse-drawn carriage bans.Call to Action for Producers: Mindy passionately encourages agricultural producers to engage in policy discussions, attend town halls, and collaborate with advocacy groups to protect their industries.Mindy also shares insights into recent and upcoming legislation, The Cavalry Group's advocacy efforts, and strategies for pushing back against government overreach. This episode is a must-listen for those in agriculture, policy-making, and anyone concerned with private property rights.Additional Resources:Links to The Cavalry Group's legislative tracking tools and resources.Information on becoming a member of The Cavalry Group.Details on connecting with advocacy organizations like American Agri-Women.

Danny Boyle directed a good film that was written by Aaron Sorkin called "Steve Jobs". It's a biographical film depicting Apple Computers Co-Founder and Visionary Tech Giant, Steve Jobs. The film centers around three key moments in Jobs' life and in each of the periods shows us who this guy Steve Jobs is and we should care about him and the people who surround him. The scenes really give out a clear but complex picture of Steve Jobs. To be a visionary such as himself, you must some type of complication, something that stand out in your life. I dig the film for its intense dialog concerning the task at hand, which is basically making the unveiling of the future is as perfect as it can try to be. I dig the cinematography, where the space of a setting is used. Boyle gave us the feeling of a play of sorts because characters spent their time in closed doors in a public venue. Interesting to see how actors can use their space and setting for their effective skills. the use of editing where characters appear and disappear in the film and how we get the reaction shots from the characters which relates as how WE would react to a certain exchange of dialog and/or action. The flaw I would give for this film is partially on the type of character this version of Steve jobs is. Almost an egomaniac. It has a bit hard to swallow that pill.Three and a half out of four tokes.

INPUT (prompt), var1, var2! This week we read Apple computer inventor/Kathy Griffin's ex-boyfriend's memoir "iWoz: Computer Geek to Cult Icon: How I Invented the Personal Computer, Co-Founded Apple, and Had Fun Doing It." We create a code in order to discuss the evolution of Mac, insane tension between Woz and Steve Jobs, early Silicon Valley, scam-ass printers, how we used to fix our own TVs, Freemasons, and ask the ultimate question: does technology really help us or has it gone too far?Support the show: https://www.patreon.com/cbcthepodSee omnystudio.com/listener for privacy information.

Not since Gutenberg's printing press has one human being's inventions improved the quality of life for people as much as Apple co-founder and principle creator Steve Wozniak.    Fortunately for me the Woz loves jokes, humor and comedy in general so after sending him several heart felt e-mails requesting to chat with him he agreed, so last week while I was performing in San Francisco I drove down to Cupertino to record this conversation while him. This conversation was recorded at the Mandarin Oriental restaurant where Steve asked me to meet him. There is pleasant violin based classic music playing in the background because the owner politely delinked my request to turn off the music.    Steve Wozniak is not only a creative genius who has improved human life more than any other human being in the last 300 years, he also loves and cherishes humor and the story tellers who create the jokes.    He is exciting to talk to because he thinks so fast and can convey complicated information in a very simple way to be understood universally. His genius is not exclusively bound to his inventions that will lead the world to higher plains of consciousness and communications but it is the basic fact that he is a good person who genuinely cares about helping dreamer people like me wherever he can. It is my pleasure to present to you now the one and only Steve Wozniak!   Intro song: Cutting Room (Hot Pants) – Oceanliners Movie clip from YouTube: Her TRAILER 1 (2013) - Joaquin Phoenix, Scarlett Johansson Movie HD Movie clip from YouTube: Klaatu's warning Recorded in Cupertino, CA. January 2014.    [Original broadcast date: Jan 28 2015]    This is the output of OpenAI ChatGTP prompting to summarize the transcription:  This conversation with Steve Wozniak, co-founder of Apple, touches on humor, technology, and personal philosophies. Key highlights: Humor and Pranks Wozniak loves jokes and pranks, sharing stories about altering iPads, high school stunts, and making counterfeit $2 bills. Humor keeps him optimistic and happy. Thoughts on Technology AI Concerns: Wozniak shares concerns about AI surpassing human control, aligning with fears from Elon Musk and Stephen Hawking. He believes humanity's dependence on machines began with the Industrial Revolution. Privacy Advocacy: As a founder of the EFF, he champions internet freedom and user privacy, criticizing surveillance and censorship. Creativity Tools: Wozniak celebrates how Apple products empower creativity, describing computers as a "bicycle for the mind." Personal Insights Happiness: Optimism, humor, and calmness define his outlook. He avoids stress and focuses on enjoying life. Philosophy: Maintain youthful ideals, accept differences, and foster positive relationships. Closing Wisdom Stay curious, embrace creativity, and be kind to others. Humor and innovation are central to living a fulfilling life. Wozniak's blend of playfulness, intellect, and optimism offers both insight and inspiration.     Hooray for humanity! We're dropping new episodes every Thursday-ish. Connect! Be part of the Rhodesies team and get goodies: https://patreon.com/tomrhodessmartcamp More Tom  https://www.instagram.com/_TomRhodes More Ashna https://www.instagram.com/ashnarodjan   About Smart Camp podcast Tom Rhodes Smart Camp is a festival of ideas, knowledge, stories, books & adventures. Join us for  Smart Ramble (Tom talks) Smart Talk (Tom has a guest) Smart Bestie (Tom and Ashna Rodjan) Smart Books and Movies (Review on Books and Movies)