Podcasts about Sun Microsystems

Andrew shares his entrepreneurial journey, starting with working at a company that was later acquired by Sun Microsystems in 2005. He then launched a small business marketing firm which was sold to Reach Local, and later worked on SmartThings, which was acquired by Samsung in 2014. Currently, Andrew is the CEO of Contextual.io, a managed AI solutions provider that was recently sold to a private equity firm. Andrew and John discussed the differences between being owned by private equity firms versus large international or US companies, using Samsung's acquisition of a smart home platform as an example. Andrew explained that Samsung was interested in the platform not just for its current business but for its potential to connect Samsung's distributed devices. They explore how private equity firms prioritize returns for shareholders over cultural or human elements, which can lead to significant changes in the acquired business, including growth through organic or acquisitive means. John shares a story about a friend who sold his family business to private equity, who later regretted the decision due to how the people were treated during tough times. Andrew agreed and emphasized the importance of founders doing their own due diligence on the PE firm, including speaking with other sellers and understanding long-term expectations, as the financial excitement may fade over time. Both discussed the need for proper buyer due diligence, with Andrew expressing satisfaction with his current PE sponsor, Southfield Capital. Andrew shared his experience building businesses with a core team of co-founders, emphasizing the importance of trust and clear role definitions. He noted that while only a handful of employees have become entrepreneurs themselves, many team members remain willing to join new ventures due to their trust in the leadership team. He acknowledged that the quick success of early companies like SmartThings sometimes gave employees a misleading impression of entrepreneurship being easy. John MartinkaJessica MartinkaContact us via either website or give us a call and be sure to check out our blog pages with new posts weekly.https://nokomisadvisory.com/https://www.martinkaconsulting.com/https://www.gddpodcast.buzzsprout.comhttps://www.youtube.com/c/JohnAMartinka/videos 425-515-4903 

Surviving September 11 took more than courage. It took preparation, trust, and the ability to manage fear. I share my experience escaping from the 78th floor of the World Trade Center with my guide dog, Roselle, and the lessons that shaped how I responded that morning. You'll hear how years of learning my surroundings, trusting my training, and understanding my role as a leader helped me stay focused during the evacuation. I also explore blindness, the limits society places on blind people, and the power of teamwork between a guide dog and handler. Most of all, this story is about focusing on what you can control, trusting the relationships you've built, and preparing yourself to act when fear shows up. Highlights: 00:10 – Why Michael is revisiting September 11, 25 years later. 11:45 – How Michael learned that blindness itself isn't the limitation. 32:50 – Why preparation inside the World Trade Center mattered when crisis hit. 36:40 – How staying calm helped Michael lead others toward safety. 44:46 – The lesson Michael heard while running from the collapsing tower. 51:59 – What Roselle taught Michael about fear, trust, and moving forward. About the Host: Michael Hingson is a New York Times best-selling author, international lecturer, and Chief Vision Officer for accessiBe. Michael, blind since birth, survived the 9/11 attacks with the help of his guide dog Roselle. This story is the subject of his best-selling book, Thunder Dog. Michael gives over 100 presentations around the world each year speaking to influential groups such as Exxon Mobile, AT&T, Federal Express, Scripps College, Rutgers University, Children's Hospital, and the American Red Cross just to name a few. He is Ambassador for the National Braille Literacy Campaign for the National Federation of the Blind and also serves as Ambassador for the American Humane Association's 2012 Hero Dog Awards. https://michaelhingson.com https://www.facebook.com/michael.hingson.author.speaker/ https://twitter.com/mhingson https://www.youtube.com/user/mhingson https://www.linkedin.com/in/michaelhingson/ Thanks for listening! Thanks so much for listening to our podcast! If you enjoyed this episode and think that others could benefit from listening, please share it using the social media buttons on this page. Do you have some feedback or questions about this episode? Leave a comment in the section below! Subscribe to the podcast If you would like to get automatic updates of new podcast episodes, you can subscribe to the podcast on Apple Podcasts or Stitcher. You can subscribe in your favorite podcast app. You can also support our podcast through our tip jar https://tips.pinecast.com/jar/unstoppable-mindset . Transcript: Michael Hingson  00:04 Hi everyone, and welcome to another episode of Unstoppable Mindset. I am your host, Mike Hingson, and today we're doing something a little bit different. This is Friday, september 4, 20/26, and this is the first of four episodes commemorating all of the events that happened in and around September 11, 2001. As many of you know, I was in the World Trade Center working for a company. I had opened an office for them on the 78th floor of Tower One of the World Trade Center, and on September 11th, I was in my office because we were going to be doing some special sales training for people, and I was there getting prepared to do all of that when the terrorists attacked the towers, and then later the Pentagon. And as you may know, a fourth aircraft was crashed in Shanksville, Pennsylvania, because people on the aircraft took it over from the terrorists or tried to anyway, so one of the things that we thought would be helpful would be for me to give you again a taste of what I actually went through and what occurred on September 11, 2001, when we started this podcast back in August of 2021, I played a speech that talked about some of what happened to me in the World Trade Center. But today we're going to do a different speech. In April of 2024, I was invited to be a speaker at the Marshfield, Missouri Cherry Blossom Festival. Now that festival is a yearly event celebrating and commemorating different events in American history. In 2024, I was invited to come and speak and talk about my experience at the World Trade Center and to help put some of that into context. I thought it would be very relevant for all of you if we played that speech for you, so that you would again get a taste of what occurred with me, why I was able to survive and escape, and a little bit about the lessons that we should learn about not only September 11th, but frankly, from my perspective, being the fact that I have been blind since I was born in 1950, I want you to learn a little bit more about blindness. So we're going to present to you now my speech delivered in April on April 27, 2024, at the Marshfield, Missouri Cherry Blossom Festival. I hope that you'll enjoy it. I hope that it will teach you some things, and don't forget that we have other episodes coming up. We have another episode occurring on the eighth of September where I'm going to be interviewed by Michelle Abraham from Amplify You. Amplify You is the company that I work with to get these podcasts out twice a week, and Michelle has her own podcast, and she's going to interview me to talk about lessons we've learned, to talk a little bit about what happened on September 11th. But we won't give anything away for what's going to happen later in this series of episodes. On September 11th, I will be talking with Bob Ellis. Bob was at the Pentagon on September 11th and literally just walked out the door just before the aircraft hit the Pentagon. We're going to talk about that and again, hopefully, put some of things in perspective for you. Then on the 15th of September, I'm going to come back on episode 475 of our podcast, and talk a little bit more in detail about the lessons that I've learned, and talk about things that I hope people will take away and remember from september 11. I know many of you weren't even born when the World Trade Center terrorist attacks occurred, and so this episode 472, especially, I hope will give you a little bit better sense of what occurred, and from my perspective, why things occurred the way they did, and and how we proceed. So I hope you'll enjoy this episode. Hope that you'll enjoy what it brings, and we will definitely be moving forward to talk about some other things later on. Speaker 1  04:24 There are moments in American history that changed the national conscience. Yesterday, we heard about the assassination of President Kennedy. Some of you might be old enough to remember the attack of Pearl Harbor, and for most recently in American history, of course, the terrorist attacks September 11th. Today, you're going to hear a riveting account, a a heroic story of a man whose story I believe will really pull at your heartstrings. And to moderate that panel today, or that interview, to do is conduct our interview. Today is Mary Acher, who's no stranger to this stage, good friend, presidential historian, and a great interviewer. If you'll put your hands together for Miss Mary, Speaker 2  05:11 I just am so honored to met Michael Hinkson and Alamo. You know by what you see that he came down on the 78th floor of the North Tower with his guide dog Brosel, but I have a friend named Doug Weed who always told me, "You don't brag on yourself; you get somebody else to brag on you. And I want to brag on Michael before we start this. Before I ask him to tell this story, Michael was a premature baby, and at the time when he was born, they put the babies in pre in a the premature babies in a incubator sealed with 100% oxygen, and the doctors didn't know that then, but it blinded the children, and Michael was blinded at birth. So Michael was very fortunate that he had parents that refused to allow him to even think about being disabled. They mainstreamed him before mainstreaming was even known, and they taught him to ride a bicycle. They let him drive a car, and later in his life, he actually piloted an airplane. Is that amazing? He loved mathematics. He loved physics. He was taught geometry. He solved math problems in his head. He's got a master's degree in physics and another-not a master's, but a regular in in teaching. So that is why he is such an amazing man. He's never ever let this what enough people call a disability stop him at all? As a matter of fact, he has been such an amazing gift to the unsighted community in in the Braille and things that technology that blind people can utilize to be online and be all kinds of of things that they wouldn't ever have been allowed to do even 50 years ago. So anyway, I'm just so honored to have met you, Michael. It's just been amazing. I'm going to take him to Lambert's tomorrow. He says I have to catch the rolls, or somebody else will catch them and they'll eat them and he won't get it. I promised him I'd catch the rolls. All right, my dear Michael, would you start telling us about that horrendous day? I am Michael Hingson  08:00 going to not do what I said I was gonna do. I'm gonna stand up, and I'm gonna be very interested to go to Lambert's to see what they do with me, since normally they would throw the rolls, as I understand it. And I'm gonna point out that doesn't really work. So now, what are you gonna do? Because if they all fall on the floor and the dog gets them, and the dog gets sick, you guys are in trouble. So I'll be interested to see exactly what happens. No, I'm sure it will work out. Mary, thank you for those those kind words. I'd like to start by defining a couple things to help us in all of this. Mary is absolutely right about what my parents did in their position, the doctors told my parents when it was discovered I was blind at about four months of age that I should be sent to a home because no blind child could ever grow up to amount to anything or contribute to society. If you think that's bad, it was worse in other parts of the world where, when children were born who were blind, were just drowned in a bucket of water. So, in a sense, it wasn't as bad. Not every child who was born premature and put in an incubator did go blind, and it's unfortunate, in a sense, that at the time that I was born. Dr. Arnold Papps at the Wilmer Eye Institute at Johns Hopkins University had discovered that, in fact, oxygen could cause blindness, and even a few minutes a day of a non-oxygen environment would drop the incidence of blindness down to zero. But medical science didn't believe him because they said, "Well, too much oxygen can't be a problem. And what Dr. Arnold Pats essentially really proved is that too much of anything can be a problem. So it is it is an issue. I finally actually some time ago got to meet Dr. Pats. Before he passed, it was it was fascinating to talk with him about that. The condition at the time when I was born was called retroenterial fibroplasia. If you want to know how to spell that, I wrote a book called Thunderdog: The Story of a Blind Man, His Guide Dog, and the Triumph of Trust at Ground Zero, which we plan to have here, but the publisher messed up, so it wasn't. But you can go buy Thunderdog anywhere, and you can learn how to spell retrolateral fibroplegia. It is now called retinopathyoprematurity. I guess that's a little easier to spell. I don't know still why they changed the name, but they did. So fine, I don't care. I am blind. I don't care. Blindness isn't the problem. I've learned from my parents and growing up and being alive now for yep 74 years, blindness isn't the problem. The problem is our perception of blindness, what we believe blind people can and can't do, as opposed to what they truly can and can't do. If you want to really see a story or something about a blind person driving a car, there is a website www.blinddriverchallenge.org. Blinddriverchallenge.org. The president of the National Federation of the Blind in October of 2001 challenged private industry and universities to create a vehicle that a blind person could drive, not an autonomous vehicle, but truly a vehicle that would transmit to the blind person the information necessary for them to drive the vehicle. What you will see at blinddriverchallenge.org is a video of a gentleman named Mark Riccobono. Too many marks. Mark Riccobono driving a vehicle independently without any assistance around the Daytona Speedway, right before the 2011 Rolex 24 race, he will go through an obstacle course. He will pass boxes that are being thrown out of a van to try to block his way. He will pass the van and a number of things like that. The reality is, what is driving? It's all about you having the information necessary for you to control your vehicle, and as far as I'm concerned, given what Mark Riccobono did, and given the reality that the information is available to us, given the way most sighted drivers drive, I'll take me any day, especially where I live in Victorville. My gosh! But the the reality is, blindness isn't the problem. I grew up believing that I went to public school. I went to college. Michael Hingson  12:26 I did get a master's degree in physics. As I love to tell people, I'm as good as Doc Brown from Back to the Future in building reactors and nuclear bombs. The only difference between me and Doc Brown is I won't go steal fissionable material from some source that might come after me later. So you know, I think I was a little smarter than Doc Brown, but the fact is, again, it's not the problem. I was also the program director of the campus radio station for a while, and I worked at the campus radio station KUCI 89.9 on your FM dial for seven years. I did a show playing old radio shows every Sunday night from six to nine. Didn't even know what 60 minutes was. I heard about it, and one day finally somebody from the show or from the the Orange County Jail called and said, "We really got a situation. We want you to know about it here at the jail. People who heard about you, they've heard about 60 minutes, and on Sunday nights we have to divide the jail in half. Half of the people go up to a television room to watch 60 Minutes, and the other half, which is the bigger half, want to hear your show playing old radio shows on Sunday nights. So you know we must be doing something right. That even at the jail, they liked us. I went to work in 1976 for the National Federation of the Blind. It's the largest organization of blind consumers in the country. I was offered a position because I was in in the science world, one of the few at the time in that world. And the president of the federation, Dr. Jernigan, told me in late 74, early 75, we got a situation. There's a guy named Ray Kurzweil. You may have heard of Ray. He's a futurist. He's an inventor. He's invented the singularity. I'm not totally sure I agree with everything that Ray says. You know, Ray once said the only problem with God is we haven't invented it yet. I don't agree with that. And the other part about it is Ray says that we're really going to all become part of the world when chips are created that will allow us to directly interact with computers. Well, we'll see. I don't want to chip in my brain yet. But Ray at that time had developed a piece of technology that would actually look at a printed page. It actually had to build it up line by line, so it wasn't like snapping a picture. But it would learn to recognize all the characters on that page, no matter what their type styles or print styles were, and it would read it out loud, called the Kurzweil Reading Machine for the Blind. Just like with blindness and retro-entral fibroblasia, the government didn't believe he could do it because nobody else had been able to do it, and so they wouldn't help fund it. He came to the federation, and the federation said, "Tell you what we're going to do." Ray, I'm not sure they said it quite that way, but tell you what we're going to do, Ray. We're going to send somebody up there with a bunch of material, and if your machine reads what we bring up, not what you want to read, if it reads what we bring up, then we're going to help you get funding. And Ray, I'm sure again it wasn't quite the way he said it, but he said, "Bring it on. They did. It did, and a relationship began that exists to this day-a machine that literally would read print out loud. And Ray wanted the first application of omnivore optical character recognition to be a machine that would read print out loud for blind people. We created a project where we purchased several machines, and then for 18 months, from 1976, in October through June of 1978, I lived in suitcases or out of suitcases in hotels, traveling around the country where we put machines at places like the New York Public Library, the Iowa Commission for the Blind, the San Francisco Public Library, and some other agencies for the blind around the country. Michael Hingson  15:59 The idea being that we wanted blind people to come and use the machine, read whatever they wanted to read, and then give us information about what needed to go into a final production model of the machine. I wrote training curriculum. I wrote the the technical manuals for teaching people how to use the machine. I taught people to use it. I observed people using it. Sometimes grabbed my old soldering gun and fix things that broke on the machines. These were $50,000, 400 pound machines. They weren't little things like an app on an iPhone today, right? So anyway, we finally wrote the final recommendations, and then Ray said, "I want to hire you to come and do the same sort of thing within the company. So I went to work for Ray, moved to Cambridge, Massachusetts. Actually, I learned I moved to Winthrop, Massachusetts, learned how to go from Winthrop to Cambridge every day, and we began a relationship. And I worked at Kurzweil Computer Products, in and that started in again October of 1978. In May of 1978, I was called into the office of the VP of Marketing, and Andrew Parson said, "We're laying you off. What? We're laying you off. Why? Oh, it's not that you're doing a bad job or anything, but unfortunately, like a lot of engineering startup companies, we've hired too many people who aren't revenue producers, and we have to have more revenue producers. And so, as important as your job is, it's not as important as making money for the company. So we have to lay you off. Then he paused and he said, "Unless you'll go into sales. Now, I'm a science guy. However, I thought about it for a micro nanosecond, and I said, "Sure, I'll go into sales. As I love to tell people, I decided I would lower my standards and go from science to sales, and did. I said I don't know anything about sales. He said we'll send you to a Dale Carnegie sales course and all that. Well, I started selling, but not the reading machine for the blind. Instead, I sold a new product they had called the Kurzweil Data Entry Machine, and unlike the reading machine for the blind that sold for $50,000, if you want one, we might be able to find one of the old machines for you for 49 995. Instead, I sold a new product called the Kurzweil Data Entry Machine, which was only $125,000. I guess they had confidence in my ability, and I was very grateful for it. The real reason that I didn't want to refuse the sales position is I knew that at that time, and it's still somewhat today, the unemployment rate among employable blind people is close to 70. That is seven 0% It's not because we can't do the work; it's because people think we won't be able to do the work and don't give us the opportunity. So the bottom line is, I lowered my standards and went from science to sales, and did that for a while. And then in 1981, while Xerox was considering and actually working toward buying the product, I was asked by Ray and the VP of Sales to move back to California, where I was from, to help integrate Kurzweil into the Xerox West Coast environment, including their research center called Palo Alto Area Research Center Park, and I did. And my thanks for that was that after the the whole sale was consummated and Xerox completely took over. I was the last salesperson in June of 1984 to receive a FedEx letter saying thank you for your service, but we don't want you anymore. Goodbye, because all Xerox wanted was the technology. They didn't want the people. Now I was confronted with the situation. How am I going to find a job? What am I going to do? 70% unemployment. and I went out and I wrote lots of cover letters, sent out lots of resumes, and I even got a headhunter who called me and said, "Love your resume. We're going to have you interview with this company up in San Jose, California. We'll send you a ticket. They sent me the ticket the night before the flight. The guy called. Back and he says, "You know, I was just looking at your resume again. I see you do a lot of things with blind people. Michael Hingson  20:04 Is there somebody in your family who's blind? You notice that? And I said, "Yeah, I'm blind. You're blind? Well, I'm going to have to call them. They're not going to want to talk to you. I said, "Nothing has changed. My resume is still the same, but you're blind. It's all changed. No, it hasn't. There were no laws to stand on. The reservation was canceled, and I didn't do the interview. Their loss. If Speaker 3  20:30 you enjoy Unstoppable Mindset and would like to help us continue bringing these conversations to you each week, we've created a way for you to support the show. Your contribution helps us cover production costs and continue sharing stories, insights, and ideas that inspire people to live with purpose and possibility. If supporting the podcast feels right for you, you'll find the link in the show notes. Thank you for being part of the Unstoppable Mindset Community. Michael Hingson  21:02 Eventually, not finding a job, I started my own company selling computer-aided design systems to architects. A blind guy selling CAD systems? Why the heck not? I didn't need to work the machine. What I needed to know was how to work the machine, so I could describe it to architects, and I could sit them down in front of a machine and talk with them and talk them through it. We also hired people to demo CAD systems, and I did that for four years. And then I went back into the workforce. And when I went back into the workforce, my wife and I were talking one day, and she said, "You know, I got this great job I just discovered in the newspaper. It's selling high-end, new, revolutionary, hot, pluggable disc technology. It's perfect for you. You should apply. And I said to my wife Karen, who I had married in 1982. By the way, Karen also had a disability. She was in a wheelchair her whole life. She reads. I push. Worked out well. I said, so do I say in my cover letter I'm blind or not? Because typically, if you say you're blind, same thing will happen with the headhunter. You won't even get a call back if you don't say you're blind. You might get a callback, but then they're going to have all their defenses go up when you show up for the interview. And she said, "You're an idiot. Wives can do that, gentlemen, and it's fine. You're an idiot. Why? What's the most important thing you always said to every salesperson you ever hired, well, I wasn't quite sure which things she was thinking of. I had several things that I always said to salespeople I hired. She said, "You always told every salesperson you ever hired turn here's the operative word perceived liabilities into assets. You ever watch those little cartoons in the newspapers and all that, where the light bulb goes on over your head. Well, that's what happened, and I went and I wrote a cover letter to send with this resume to this company. And here are the last two paragraphs of the letter. The most important thing you need to know about me is that I am blind. As a blind person, I have had to sell all my life just to be able to function and survive. I've had to sell to take my guide dog on airplanes. I didn't tell them that we had to sue one airline because they violated their own policy because they wouldn't let me go on an airplane with my guide dog. I've had to sell to convince people to let me buy a house, move into apartments, sometimes take my guide dog into grocery stores, and do anything else because I was blind, I've always had to sell. So, second paragraph: When you're hiring someone for this job, do you want to hire somebody who comes in and works for eight or 10 hours a day, and then just goes home because the job is over, or do you want to truly hire somebody who understands sales for the science and art that it is, and who sells 24 hours a day as a way of life. Sent off the letter. Waited for two weeks, wondering if I'd get a call or an email. Well, no, not an email, not back then. But in late June 19 or May 1989, I got a call. This is Doug Cooper, head of marketing for Articon. We love your letter. Would you come for an interview? And I said sure. Next day we were down there. I was hired and started on july 2, 1989. Love to start on the second of July, or actually the third of July, because then I got the next day off. It was great. So I went to work for them, and we moved from where we were living in Mission Viejo down to Vista, California. The company was in Carlsbad. I began selling to the East Coast, selling our technologies and other technologies, Sun Microsystems products, and so on. And then in 1996, the owner of the company asked me to move to New York for them because we were selling to Wall Street. Michael Hingson  24:37 Wall Street was always good at getting and demanding and getting what they demanded, and they always said, "If you are a manufacturer and you're selling products to us, we want a representative, not an agent, but we want the company in Wall Street Arena to be able to to hold responsible and deal with. So we moved to New York. And I went to work on the 23rd floor of Tower Two of the World Trade Center, and was there for about a year, and then was recruited away by another company, and it wasn't hard because Articon did not figure out how to support a branch operation. So I was recruited away, and then in 1999 I was recruited away by Quantum Corporation, and now we're getting to what Mary asked about. But I needed to give you the background. Hope it was okay. So in 1999, I was hired to open an office for Quantum Corporation on well in New York City. Quantum was a company that made products called tape libraries. They were big boxes that consisted of tape drives and lots of tape cartridges, and you would attach them to computer networks, and then you would use software like one called Veritas, which is still used today. And what you would do is you would back up all of your data over the network into these tape libraries, onto tape cartridges, and then you would take the tape cartridges out and store them off-site. Now I gotta stop and be spiteful because in New Jersey they love to say that they stored them in a town called Mountainside Under a Mountain. You ever see a mountain in northern New Jersey? I came from California where we had mountains that were eight, 910, 1000 feet tall. They didn't even have decent hills, but they still called it a mountain. That was fine, whatever. They still were able to store the tapes in safe places. But the point is that all the data was backed up off-site, which is what they needed to do. We opened the actual office on august 1, 2000. I hired a staff, and we had a staff that came in and and sold, and we also worked with resellers. And in August of 2001, our main distributor Ingram Micro said, "You know, we got a lot of resellers who are selling your products, but they don't really know how to do it. Can we hold some seminars to teach our your reseller partners, our customers, the resellers, how to sell your product? I said, "You bet. We worked it out with the folks at Quantum. David Frank, who was in charge of pricing and distribution, said he wanted to come back to be a part of the seminars, and we set up doing the seminars. The idea was that we would teach them. I would be their main point of contact since I worked and lived there. David would be the person that I or they would contact without with any pricing issues, but I would be the technical point of contact contact. Master's degree in physics helps, and so we set up the seminars. And wouldn't you know it, we set them up to be held on september 11, 2001. The evening before, or the morning of September 11th, about 12:30, Roselle, my guide dog at the time, woke me up. She was very nervous and fidgety. I knew what it was like when she was fidgety. It was usually because it was a thunderstorm. She didn't like thunder, and we went down to my office. And of course, a thunderstorm did happen, and the storm literally came right over our house. I've never been in an environment where bombs went off around me, but I got to say that in this case, the thunder claps were, as I said, literally right over us, and it had to be like what a bomb sounds like going off. Anyway, it went on till about two, and then we went back up and got a couple more hours of sleep, three more hours of sleep. I got up. We went in and got to the office at about 7:40 in the morning on September 11th. As I came to the door, somebody came up with a cart. It turns out it was a guy from the Port Authority cafeteria. Michael Hingson  28:33 We were going to be providing breakfast and snacks for the first and second seminarians. We had seminars going all day, so we went in. I showed him where I wanted to set up everything in the conference room. I went in, got my laptop computer out of my backpack briefcase. I got my PowerPoint projector, and I went into the conference room and set everything up because I was going to be doing a PowerPoint show that day to give people all the information they needed about the ATLP 3000, the ATLP 1000, and so on. Yes, blind people can do PowerPoint, folks. It's not magic. You sighted bigots. So I had a script, and my wife and I had created the script, and I'd used it many times. The script was in Braille. I knew what was on every slide. We put a couple of things in addition on the script. We put all the wording from the slides on the script, and we also put on the script descriptions of the pictures, as well as where the picture would show up on the screen. So I would, for example, when we showed this to other customers around the city, I'd blow their minds because I would be doing the presentation. My sales guys loved it when I went out and did PowerPoint presentations because I could just point over my shoulder. On the left side of your screen, you'll see the ATLP 3000 with 16 cartridge, 16 drives, 326. Cartridges, and you see the label that says Prism Technology. We could hook five of them together. On the right side of your screen, you'll see the ATLP 1000, which was a single unit with 30 cartridges and one tape drive. And people would come up to me afterwards, and they say, "You know, we're ticked at you. I go, "Why? Well, first of all, your presentation was not boring, which usually they are. But second of all, you never turned and looked at the screen. You kept looking at us, even though you were pointing right to where everything was with your laser pointer. We didn't dare fall asleep. We forgot you were blind. And my response was, "You don't get it. My dog was down here taking notes. If you'd fallen asleep, we would have got you anyway. But that was what it was about. My responsibility was to be the leader of that office, and I had to do what anyone else would do. One of the main things that I did was spend hours, days walking around the World Trade Center, learning what the kiosks were in the shopping mall on the first floor, learning where different offices were, consulting with the Port Authority police and the fire prevention people learning what to do in case of an emergency because sometimes I might be in the office all by my little self. There would be nobody else around. I didn't want my staff in the office. I wanted them out selling and working and supporting customers. Not being in the office, of course, they did usually come in at least once a week. And and so I learned never watched The Sopranos, but I got to tell you, I learned more about the Sopranos from all the Italian Americans on my staff who talked about the Sopranos constantly. Bada bing, bada boom, and I learned a whole lot about Tony Soprano without ever watching the show. But the point is that I needed to know all that stuff. I needed to know where the restaurants were. Customers come into the office. Oh, you want to go out to lunch? What kind of food do you want? There's a great deli downstairs called Fine and Shapiro. Let me take you there. How would it have looked if I didn't know how to do that, and I had to say to someone, "You're going to have to let me take your arm and lead me there because I don't know how to get there, and two hours later we're supposed to be negotiating multi-million dollar contracts? No, I needed to know it. I didn't have the luxury, and I don't regard it as a luxury. I regard it as a disability of reading signs. I needed to know all of that stuff. What I didn't realize is that was creating a mindset in me, which I'll talk about in a moment. Michael Hingson  32:15 Anyway, got all the laptop projectors and everything set up. The only thing I knew I didn't know how to do extremely well is to get it exactly aimed right, but about 8o'clock, David Frank came in and I said, "Say, David, this is all set up, but let's aim the projector just exactly where you want it on the screen. And we did have to turn it just a little bit, but not too much. But anyway, at 845, I was in my office and David was with me. We were creating a final list of all the people who were going to be attending the seminars, because the Port Authority police, the security people, needed to know who was coming. There were two ways you could get into the building: either we faxed on letterhead a list of people who were coming on any given day, and then the people coming in would show their photo IDs, and it would be verified against the list. And if they were allowed in, then they would be given a badge that they would put over their neck, and they would carry that, and they could scan barcode and go into the appropriate elevator to come onto our floor, or they'd have to call us every time somebody came in. And I didn't want a lot of phone calls coming in, so we were faxing the list. I was reaching for Letterhead to fax to to print the list on Letterhead when suddenly I heard and felt kind of a muffled thump and a vibration. And then literally, if you any blind people in the room, well, I'll do it anyway. I'm holding up my hand, and what happened was that literally, as I'm now tipping my hand toward you, the building began to tip. We probably moved about 20 feet. The building kept tipping and tipping. David and I said together, "What's going on? I don't know. What's going on? What do you think? Was it an explosion? I said. David said, "Didn't sound like it. Is it an earthquake? David was from New York, and now he's living in California. He didn't know about earthquakes. I said, "No, the building wasn't shaking around. It was going in one direction. And finally, and I went over and I stood in the doorway between my office and the the outside lobby of our our offices, and I stood there. Roselle was asleep under my desk. David was just on the other side of my desk, holding it near our windows, looking out over Manhattan, the south side of Manhattan. And finally, David and I both said goodbye to each other because we thought we had moved so far that the building was going to take a 78 floor plunge to the street. And then the building slowed down, and it stopped, and it moved back. As soon as it got vertical, I started walking back into the office. I met Roselle coming around from under my desk. I took her leash. I said "heel, which meant to come around behind me to sit and lie down, which is what I would normally have Alamo do, but he's comfortable, so we'll just leave him there. Roselle sat down, and about that time. The building dropped straight down about six feet. Why did it drop down? Because tall buildings like that literally are springs. They're made to flex in windstorms and other things like that. An Empire, an airplane hit the Empire State Building in the 1940s because it got lost in a fog bank. Tall buildings are flexible. They have expansion joints, and when the building was hit, the expansion joints took up all of the the things that were going on. And then when the building got straight again, the expansion joints dropped back down to their normal configuration. I knew that because I had talked to people about stuff like that. I'd forgotten it until later, but I knew it. What I hadn't realized is that what was happening when I was learning so much stuff was that a mindset was being developed in me that said, "You know what to do in an emergency. And as soon as the building dropped, David turned and looked out the window and started shouting, "Oh my God, Mike! There's fire and smoke over us! There were millions of pieces of burning paper falling outside the windows. Michael Hingson  35:59 We got to get out of here right now! Slow down, David. No, we got to get out of here. The building's on fire. I could hear things rushing and brushing outside our windows, and now I knew what they were. David told me millions of pieces of burning paper, right? And I didn't smell any smoke. Roselle wasn't doing anything to indicate any concern, and David kept saying, "We got to get out of here. The building's on fire. And I kept saying, "Slow down. Our guests began to scream. We had like five or six who were in our conference room. Early arrivals. They started coming out, but then they heard me say, "Slow down, stop, David. Just wait. And they waited to see what was going to happen. And finally, David used the big line: "You don't understand. You can't see Speaker 4  36:37 it. The Michael Hingson  36:38 problem wasn't what I wasn't seeing, the problem was what David wasn't seeing-a dog sitting next to me, wagging her tail, yawning, going, "Who the heck woke me up? I was comfy, not giving any indication of fear. And I eventually got David to focus, and I said, "David, get our guests to the stairs. Don't let them take the elevators, because I knew if there's fire, especially because if there's fire, the elevators could become fire traps. The fire could get into the elevator shafts, which it did, and anybody in the cars would be burned. David left with our guests, got them to the stairs. Meanwhile, I called Karen and told her that there had been an explosion or something. We had no clue. There was no way to know. I love it. Reporters, even today, and other people say, "Well, of course you didn't know you couldn't see it. Excuse me, you numbskulls. The last time I checked, Superman and X-ray vision were fiction, and the airplane hit 18 floors above us on the other side of the building. No one knew. All the way down the stairs, we didn't know because no one saw it. No one knew. Anyway, I called and told Karen she wanted to know more. I said, "I don't know anything else. I've got to go because we're not staying here. We knew instantly that we had to leave, but we got our guests out. Then David came back. We swept the offices one last time. Went to the stairs and we started down. If I knew it was the last time I was going to be in the building, I would have taken a couple of things that I didn't take. Like I had a really neat talking scientific calculator that I couldn't replace. And if I had known that I wasn't coming back, I would have taken it. It would have been a little heavier, but I would have taken it anyway. We started down the stairs. There were other people, of course, on the stairs. We got down about four floors, and I was smelling an odor. I couldn't quite figure it out, and suddenly I realized I'm smelling the fumes from burning jet fuel. I traveled 100,000 miles a year for my company. I knew what the odor of jet fuel was like. I knew the kerosene smell, but it took a while to associate it with the World Trade Center because no one would have ever thought you would have smelled it there. When I realized what it was, I observed to the other people around me on the stairs, "I'm smelling the fumes from burning jet fuel. And they said, "Yeah, you're right. That's what it is. We must have been hit by an airplane. You understand? Nobody knew. We must have been hit because of what we're smelling, so we all accepted that that was what was going on, but we had no clue. We continued down the stairs, about 10 floors down. At one point, a woman stopped right behind me, and she said, "I can't go on. I can't breathe. We're not going to make it out. And I stopped and turned around and said, "Sure, we are. Come on, this is my guide dog Roselle. He's guiding me, and and she'll encourage you. Roselle gave her kisses, and this lady gave Roselle a few pets, and so on. And other people surrounded her, and we had a group hug, and the lady was able to keep going. A few burn victims passed us on the stairs as we went down. At about the 50th floor, David, who had gotten a little quiet. Suddenly said, "Mike, we're going to die. We're not going to make it out of here. Now you heard that I have a teaching credential. What you don't know, and teachers won't generally acknowledge it, but I'm going to tell you anyway. There's a secret class we take called Voice 101: How to Yell at Students. Didn't know that, did you? And anyway, as soon as David. Said Mike, "We're going to die. We're not going to make it out of here. I just said as sharply and with a snap into my voice that I could, "Stop it, David! If Rosella and I can go down these stairs, so can you. And David told me later that that brought him out of his funk. Michael Hingson  40:12 What he then said is, "I got to keep my mind off this. I want to walk a floor below you and shout up to you what I see on the stairs. Is that okay? And I said, sure. Did I really need him to do that? No. Did it matter? No, but it did to David. However, what I came to realize over time was, David doing that was one of the most important things that I experienced on that day. So I'm going down the stairs. I get to floor 49. David, I'm on the 48th floor. All's clear here, Mike. Going on down. I get to 48 floor, 47. We keep going down. Finally, I get to the 45th floor, David. I'm on the 44th floor. This is where the Port Authority cafeteria is. Not stopping. So David was obviously doing better, and he kept going down. Why do I say what I did about David and doing that? Because David became a focal point for anyone within the sound of his voice who could hear him say, "43rd floor, all's clear, everything is good. He had to have helped 1000s of people stay focused and not panic going down the stairs, and I think that was so cool that he did that all the way down 42nd floor, all good. We kept going down the stairs. We met firefighters on the 30th floor. They wanted to escort me down, and I finally convinced them that I was capable of going down without them. And I did it by playing the sight card. I said, "Look, my friend David is here. He can see we're good, and the firefighters let us go. I didn't want them to escort me. First of all, they don't know how to work with a blind guy and do sighted guide. But second of all, I didn't want to break up their team because I knew that each of those people were carrying the equipment that they had to use to fight the fire. You couldn't store it somewhere. Where would you store it? Oh, the 34th floor. And what happens if a fire broke out on the 33rd floor, you couldn't get to it. You had to carry the equipment, so we kept going down the stairs. Finally, got to the first floor. David got there, and I was at floor two. And he said, "Hey, there are water sprinklers running. You're going to have to run through a waterfall or a down torrent of water to get out of the stairwell. Why was there all that water? Because it wanted to keep fire either in or out of the stairs, if fire was around. David ran through. Then I got to the bottom. Roselle stood there, and I picked up her harness and said, "Rosel, forward, hop up, which is a command to speed up. We went through this torrential downpour. It was a waterfall, and we came out the other side, soaking. David was there, and there were voices. Hey, don't go outside! No, no, don't go that way. Go this way. A PA system, a guy on a bullhorn. No, no, no! Don't go outside. Don't go to the outside. Go this way. What we didn't know is, if they had let people go out, they might have been right below where people were jumping. And so that was one of the reasons they didn't want anyone out. They wanted people to go through the complex and get out at the far side, as far away from where everything was occurring that they could. This guy comes up to us and he goes, "I'm with the FBI. I'll get you where you need to go. And of course, I'm sitting there with my warped sense of humor, going, "I'm sorry, I only talked to McGarrett, and I didn't do it. I'm innocent. I just thought that I didn't say any of it out loud. Anyway, he got us through out to the outside of Tower One. We passed now the empty Ben and Jerry's ice cream kiosk that was there. Darn didn't get a chance for a scoop. Kept going. Finally, went up an escalator and got outside into the sunshine outside of Tower. Well, of the whole complex, as far away from the towers as we could be, we got outside. Michael Hingson  43:44 We were told to leave the area, but David looked around and he said, "Mike, I see fire in Tower Two. And I said, "What are you talking about? There's fire in Tower Two, really? What's that all about? We didn't feel a thing going down. We were in our own little cocoon, our own little cave. We had no clue. Anyway, we were told to leave, so we went to Broadway. We walked across the plaza to Broadway, turn left, going now north on Broadway. There was a building on my left. Broadway was on my right. We crossed several streets, crossed Fulton Street, finally got to Vetsy Street. David said, "I want to stop because I can see the fire in Tower Two really clearly from here, I want to take some pictures, and I said, "Great, I'll try to call my wife. I got out my phone. David was taking pictures, which I have today. I tried to call Karen. I couldn't get through. Later, of course, we learned that people were saying goodbye to loved ones, and that was why the circuits were busy. I had just put my phone away, and a police officer, and while David was putting his camera away, and a police officer yelled out of here! It's coming down now. We heard this rumble that became this deafening roar. I describe it as kind of a combination of a freight train and a waterfall. You could hear glass breaking and tinkling, and metal crashing down, and then this white noise sound as Tower Two, 100 yards away from. Pancake down. Everyone turned and ran. David ran. He was gone. I literally lifted Roselle by the harness, turned her 180 degrees, and started running back the way we came. And the first thing I remember saying in my mind was, "God, I cannot believe that you got us out of a building just to have it fall on us. And as soon as I thought that, I heard in my head as clearly as you hear me now, a voice that said, "Don't worry about what you can't control. Focus on running with Roselle, and the rest will take care of itself. Who is God? Absolutely no question. Don't worry about what you can't control. Focus on running with Roselle, and the rest will take care of itself. And so I also had this incredible sense of peace and calm that came over me. That said, you're okay if you work together. We kept running. We got back to Fulton Street, turned right on Fulton Street, and ran about 25 yards. And suddenly we caught up to David, who had apparently gone the same way. And David suddenly realized that he had left us behind and he was going to come back, but we caught up to him first, and he apologized. I said, "David, don't worry about it. Let's just keep going. The building's coming down, you know. And we both just started to run with Roselle, and suddenly we were engulfed in all the dirt and debris and the dust cloud from Tower Two. It was so thick that David said he couldn't see his hand six inches in front of his face, and all I can tell you is that every breath I took, I felt dirt and debris and junk going down my throat into my stomach, and we knew we had to get out of that. So I started telling Roselle, "Go right, right. There was a building on our right side, and I wanted her to find the nearest opening if she could even hear me, see my hand signals, or whatever. And I was also listening for openings. Yes, I can hear when I pass an opening, and I and I can tell it's there and deal with it accordingly. Like during a time when you're running away from a collapsing building, run into it. Suddenly, I heard an opening on the right, and Roselle must have known what I wanted. She must have been able to see my hand signals or something because she turned right, she took one step, she stopped, and she would not move. Come on, Roselle, keep going. She wouldn't move. Come on, Roselle. Nope, wouldn't do it. And I realized, focus on running with Roselle, and the rest will take care of itself. So I stuck out a foot. Michael Hingson  47:13 I trailed a hand along a wall, and realized that we were at the top of a flight of stairs. Roselle had done exactly what she was supposed to do, and I knew what I was supposed to do if I wanted to get her to move. But before I did that, I gave her a big hug, good girl, and then I said, "Roselle, forward! That's the command. And we went down the stairs into an arcade area that was the entrance to the Fulton Street subway station. There were a few other people down there. Then a guy came up from the subway system and saw about eight or nine of us there. He introduced himself as Lou, an employee of the subway system, and he took us down to an employee locker room where we could sit down and and kind of hack and cough and get the dust out of our lungs. There was a water fountain and there were fans. We were there about 10 minutes. Then a police officer came, and he said, "You got to get out of here right now. The air's clear up above. You can't stay here. And so we followed him. Of course, he probably had already been told that Tower One was going to collapse. the The officials knew that each building was going to collapse probably about a half hour before it actually did. At least that was their presumption, and that's what I've been told. Anyway, we followed him back up the stairs, through the arcade, up the last two flights of stairs. We got outside. David looked around and he goes, "Oh my God, Mike, there's no Tower Two anymore. And I said, "What do you see? And he said, "All I see are pillars of smoke, hundreds of feet tall. We stood there for a moment, and then we just turned, and we kept walking. Now west on Fulton Street, we walked about 10 minutes, and we were in this little plaza area when we heard that freight train waterfall sound again, and we knew it must be our tower collapsing. We saw a little retaining wall David did, and we got behind it and ducked down, and we waited until everything stopped, and then we stood back up. And David looked around and he said, "Oh my God, Mike, there's no World Trade Center anymore. And I said, "What do you see? And he said, "I just see fingers of fire and flame, hundreds of feet tall. We see, I see pillars of smoke. It's gone. Are you sure? Yeah, it's gone. It's not there. We stood there a moment, then I tried to call my wife Karen again. That was kind of my first thought. I need to tell her we're okay. This time I did get through because clearly the circuits were were free. And after some tears on both sides of the phone, she is the one who told us how two aircraft had deliberately been hijacked and crashed into the towers, one into the Pentagon, and a fourth at that time was still missing over Pennsylvania. Who would have thought? We spent the rest of that day getting up toward Midtown Manhattan, and eventually I got to Penn Station, learned that the trains were running, and went back. Out to New Jersey, David wanted to go back up to be with his sister, who he who he was staying with. She lived on the Upper East Side, so I got on trains and I went back over toward New Jersey. I called Karen and told her what was going on, and a friend of ours, a friend that Karen had known since high school out in California, Tom Painter, was also living in New Jersey, he had come down to be with her, not even knowing at the time whether I was in the World Trade Center or working from home that day or whatever. But he drove her to the station in our accessible van, and as I came off the train, I heard the van show up. I went downstairs, climbed and went up the ramp into the van, and got to hug Karen about 7o'clock that night, for the first time since leaving home, we got home. Tom drove us home. We all went inside. I was going to take Roselle outside because she hadn't been out since like five that morning. Michael Hingson  50:53 Well, I take that back about six that morning, and I took her harness off. But before I could do anything else, she was off like a shot. She went to her toy box, found her favorite tug bone, and started playing tug of war with my retired guide dog Linny. Why? Because it was over for her. And I talked to the guide dog people later, and I said, "Will any of this affect her? And they said, "Was she threatened? Did anything hit her or injure her in any way, and I said no. They said then no. It was over for her because dogs don't do what if. It was over. It was done. She was fine. Lesson to be learned. Lesson you will learn more about if you buy our new book, Live Like a Guide Dog: True Stories from a Blind Man and His Guide his dogs about being brave, overcoming adversity, and walking in faith. That that book is available for pre-order, and I've been signing bookmarks all day. I still even have a few with me. But the point is, you can pre-order it, and and it's about something that I learned later. I thought about during the pandemic. I've talked a lot about escaping and not being afraid because I developed a mindset that said you know what to do, but what I've not done is to teach others how they can learn to recognize that fear is not something that needs to blind or overwhelm you. You can use fear as a very powerful tool to guide you and steer you in the right direction if you know how to control it, and live like a guide dog is all about that. So I hope that you'll all get that when it comes out in August. But again, you can pre-order it now if you go to michaelhinkston.com. There's a link there where you can go to a web page to get information and to go to a link where you can pre-order it. And like I said, I have some bookmarked with a QR code on it, and and I'm and I yes I am plugging the book, but I'm also saying, look, folks, the bottom line is we operate in so many ways with misconceptions about things. I've talked about blindness. Anybody could have been in the World Trade Center, and and a lot of people were. The reality is, though, if you learn what to do and how to prepare for situations in general, when it becomes something specific, you'll know what to do. People have asked a number of times, "Well, wasn't your guide dog trained to operate in an emergency like the World Trade Center? How are we going to do that? No, the dog isn't trained to do that. The guide dog's job is not to lead. Guide dogs do not lead blind people. Guide dogs' jobs are to make sure that we walk safe. It's my job to know where to go and how to get there to give the dog direction. The dog depends and relies on me to give it direction. The dog's job, as I said, is to make sure we walk safely. It's a team effort. We each have a job to do, and we develop a trusting relationship when we learn to trust each other and respect the job the other member of the team is doing, which is what it's all about. Which is what happens on any team, trust is all around us. Trust is under attack in so many ways from our politicians, and in so many ways. But the reality is, trust is all around us. I think we all trust that the roof isn't going to fall in on the church. I think that we trust that the PA system is going to continue to work, and so on. Trust is all around us. The difference between dogs and people is that dogs, while they do love unconditionally, do not trust unconditionally. But dogs are open to trust unless some incredibly traumatic thing has happened to them where they lose that ability. But dogs are open to trust, dogs want humans to give them direction to establish rules, and all too often with our pets and so on, we don't do that. We don't really develop the relationship that we should and can with them. Michael Hingson  54:54 If we would, we would have so much stronger bond and relationships with them. It would be. Amazing for for all of us, but the bottom line is that's the relationship that I get with each guide dog. That's the relationship I have with Alamo. He trusts that I am going to feed him before too awfully long. He trusts that you guys are going to buy books, so he'll have kibbles for me to feed him. Just saying, but but seriously, the the trust has to be earned with a dog or with people or whatever, and if you find that you you discover you can't trust someone, don't wish them ill will, forgive them and move on. So you don't trust them, but you know what you have, and you go off and make new friends and learn other trusting relationships that you can develop. Focus on running with Roselle; the rest will take care of itself. The reality is, we worry so much about so many things. We are always doing what if we create most of the fears that we face in our lives, and we Don't need to do that. If we would focus on just the things that we have some control over and leave the rest alone, well, we might want to be aware of them, but we don't have to worry about them. We don't have control over them. Trust and deal with the things that you have to deal with, and let the rest take care of itself. And that was what I learned on September 11th, listening to the voice of God, absolutely, and that is something that I pass on to all of you, and I think that's the most important thing that I can leave you with. Hi again, everyone. This is Mike Hingson. I hope that you found that speech to be helpful and relevant and interesting. I hope that you learn some things from it. From a personal standpoint, I hope that you learn that blindness isn't really the big problem that I face. The challenge that I face really comes from the fact that people who have eyesight tend to believe that blind people are not capable of doing much because they can't see. Wrong thing to believe. I'm not going to spend a lot of time on that because we did it during the speech, but I just wanted to thank you for being here today, for listening and watching this episode. I hope that you will also tune in for our episode on Tuesday, where I'm in conversation with Michelle Abraham on next Friday, the 11th of September, that you will tune in to hear the conversation with Bob Ellis, and then episode 475, which will occur on the 15th of September, where we will talk about lessons to be learned and and give you some things to hopefully take away that maybe you haven't thought about. Thanks very much for being here with us. I really very much appreciate all of your support. If any of you have any questions or want to reach out to me, you are welcome to do so. Please feel free to email me at speaker@michaelhinkson.com. That's s p e a k e r at m i c h a e l h i n g s o n.com speaker@michaelhingson.com hope to hear from you and as you gather I do speak I continue to speak publicly I've been a keynote speaker since September 11 if anybody knows of anyone that needs a keynote speaker or you can use us in events that you have please reach out to me at speaker@michaelhingson.com let's talk about it. Let's see how we can help. I'm always looking for ways to inspire, but also to teach and help. And I'd like to be part of your world in that regard. Thanks again for being here. Thanks for listening, and come back next time for another episode of Unstoppable Mindset.

In this episode of Software People Stories, Gayathri Kalyanaraman speaks with Vasu Vadlamani, a technology leader, architect, entrepreneur and Professor of Practice, about a career that has evolved alongside the software industry itself. About his accidental start to an AI Era tech leader who's defining mantra has been Every role has an expiration date! Vasu takes us back to the early 1990s, when software meant client-server systems, handwritten notes and face-to-face communication. From his early work with Citibank to working with Sun Microsystems, building a professional services organization, experiencing the disruption that followed Oracle's acquisition of Sun, and later taking on technology and architecture roles at HCL and Cognizant, his journey reflects several waves of technology transformation.But perhaps the most interesting transition came later.While working at Cognizant, Vasu found himself asking a fundamental question: Why should the gap between college education and industry readiness be so large?This led him to work with educational institutions with a very practical goal — to make graduates industry-ready much sooner. Eventually, that became the driving force behind his move from corporate technology leadership to becoming a Professor of Practice.Today, Vasu sees himself less as a software professional and more as someone whose purpose is to help people do their best — in technology, in their careers and in their interactions with others.The conversation explores:The early days of software and how dramatically the industry has evolvedWhy business understanding helped Vasu become a better software professionalBuilding and scaling a technology services organization from zero to 150 peopleNavigating the difficult period when the Sun Microsystems ecosystem disappearedMoving from customer-facing roles to architecting internal enterprise systemsThe philosophy of making software development “zero maintenance”Why the gap between education and industry continues to matterMaking graduates “production ready” rather than simply degree readyWhy professors also need exposure to real-world engineeringCreating safe, sandboxed opportunities for faculty and students to work on real enterprise use casesWhat AI means for technology careersWhy roles will change, but technology itself isn't going awayThe importance of resilience, curiosity, teamwork and being “an engineer at heart”At the heart of the conversation is a simple message from Vasu:Don't worry about the future of technology. Keep learning, keep adapting, and keep building. There will always be a place for people who are willing to do the work and find their way.Quotable Quotes“Don't worry about AI. Roles will change. The industry will still be there.”“If you fail, use your knowledge to get up and rise again faster.”“IT is a team's play. One person alone cannot run the ship.”“The younger generation will always be smarter than me. If I can succeed, Gen Z will definitely succeed.”“If Vasu can find a way, you are much smarter than me. You will find a better way.”Vasu Vadlamani is an accomplished IT Professional offering 30 years of experience in integrating Technical and Domain expertise (Financial Services), focusing on Large Complex Digital Transformation Initiatives. An efficient Communicator possessing strong Coordination, Interpersonal, Mentoring and Team Management Skills. Cross Functional Services Leader managing multi geo, multi service line deliveries for over $440+M. Vasu was  CTO of ADM Insurance Domain, responsible to create and execute an Information Technology Strategy to modernize enterprise technological applications, moving away from their legacy apps to modern On Cloud tech stack. Co-authored the (C)ontain, (M)aintain (I)nvest philosophy so significantly enhance the business value of applications.His  research interests span Artificial Intelligence & Machine Learning, Cloud & Distributed Systems, Data Science, Software Engineering practices, and CS Education & Pedagogy. He is  particularly interested in how emerging technologies reshape both industry workflows and the way Computer Science itself should be taught at the graduate and postgraduate level.Vasu can be reached at https://www.linkedin.com/in/vasuvadlamani/

What happens when IoT finally gets the connectivity infrastructure it has been waiting for?In this episode of the Mr. Beacon Podcast, Steve talks with Alper Yegin, CEO of the LoRa Alliance, about LoRaWAN and why he believes it has become a fourth pillar of wireless connectivity alongside Bluetooth, Wi-Fi, and cellular.Alper explains what makes LoRaWAN different: long range, deep indoor coverage, extremely low power consumption, unlicensed spectrum, and infrastructure that can be deployed through private, public, community, and satellite networks. Devices can operate for more than ten years on a single battery, opening the door to applications where conventional connectivity simply does not work.The conversation explores where LoRaWAN fits and where it does not. It is not designed for streaming video or other high-bandwidth, real-time applications. Instead, it targets the enormous world of massive IoT, where sensors may only need to send small amounts of data regularly. That makes it particularly powerful for smart buildings, metering, industrial monitoring, agriculture, asset tracking, smart cities, and more.Alper also explains why he believes LoRaWAN's open-standard approach has been central to its success, and how an ecosystem of hundreds of companies has enabled the technology to evolve from a single protocol into a broader end-to-end architecture.The conversation then turns to the future: satellite connectivity, geolocation, digital product passports, plug-and-play infrastructure, and the emerging concept of physical AI. Alper describes IoT as the bridge between AI and the physical world, the "digital nervous system" connecting AI's intelligence to physical assets.Finally, Alper shares the career path that took him from TCP/IP development at Sun Microsystems and decades of standards work to leading the LoRa Alliance, along with three songs that have shaped his journey.A wide-ranging conversation about connectivity, standards, IoT, AI, and the infrastructure being built for the physical world.Alper's Top 3 Songs:“Fast Car” by Tracy Chapman: https://www.youtube.com/watch?v=uzOdm9w3J94“Rocket Man” by Elton John: https://www.youtube.com/watch?v=fOWCoRr-wqc“Storm” by Vanessa Mae: https://www.youtube.com/watch?v=oOSIAKbXzE8Mister Beacon is hosted by Steve Statler, CEO of ambientChat.ai — Using AI to connect people with places and products with an app that puts you in control of YOUR data.Our sponsor is Identiv https://www.identiv.com, whose IoT solutions create digital identities for physical objects, enhancing global connectivity for businesses, people, and the planet. We are also sponsored by Blecon http://www.blecon.net. Blecon who delivers asset tracking and condition monitoring using the devices your team already carries. Hosted on Acast. See acast.com/privacy for more information.

Ravi Soin has clear advice for anyone starting a security career today: don't be a risk manager, be a trust architect. In this episode, Steve Moore sits down with Ravi—CIO and CISO at Smartsheet—for a builder's-eye conversation on the modern CISO role, AI as an accelerant on old sins, and why the CISO who still says “no” is already obsolete.Ravi traces his path through Sun Microsystems, RealNetworks, a decade at Microsoft, and 15 years at healthcare software leader Edifecs to his eight months at Smartsheet. He explains what it means to think about security the way builders do—understanding where corners get cut under sprint pressure—and why that inside-out perspective changes how you defend.Steve and Ravi dig into how Smartsheet is deploying agentic AI across the enterprise: a centralized knowledge graph tied to every corporate system, Claude-powered threat models, DAST and SAST scans, SOC triage on the 80% phishing baseline, and MCP-connected asset and license management.They name the old culture directly. It was an era of risk registers where lows and mediums were quietly punted, tens of thousands of known vulnerabilities were accepted as compensating- control fiction, and time-to-exploit was assumed to be forgiving. Both push back on the panicked reaction to the Mythos disclosures, arguing AI has simply closed the exploit window on the trash environments were already ignoring.Ravi's core advice: build trust into the system, think about security through the customer's lens, and treat AI agents as first-class identities under the same IAM principles you apply to humans. He and Steve close on how incident response must be re-fit for the agentic era, why auditability is the non-negotiable foundation of AI governance, and why community remains the sharpest source of learning.Key Topics• Thinking about security like a builder, from the inside out• Why the CISO who still says “no” is already obsolete• Deploying agentic AI across engineering, SOC, and corporate systems• MCP-connected asset and license management• The old risk-register culture and how the industry was gambling• Why the Mythos reaction missed the bigger story• Advice to your 21-year-old self: be a trust architect• Building security through the customer's lensGuest BioRavi Soin is the CIO and CISO at Smartsheet, where he leads global IT and security strategy for the AI-enhanced enterprise work management platform. He brings more than two decades of security and IT leadership, including 15 years as CIO and CISO at healthcare software leader Edifecs and product roles at Microsoft, RealNetworks, and Sun Microsystems. Ravi serves on the SeattleCIO advisory board and was named Seattle CIO of the Year.GET A DEMO:

Greg Greeley was named CEO of Simon & Schuster a little more than 100 days ago, with a career that spans aerospace engineering, Sun Microsystems, and nearly two decades at Amazon — where he held senior leadership roles including heading up Amazon Prime. In this episode, Greg talks about how he spent his first 100 days at S&S, how he's approaching his new role, and why he took the job in the first place.

In this episode of High Net Purpose, Joe McCarthy sits down with Greg Greeley, CEO of Simon & Schuster and former Amazon and Airbnb leader, for a conversation about purpose, customer obsession, Amazon Prime, transformation, AI and legacy. Greg describes purpose as giving back to society more than you take by building companies that serve customers, suppliers, employees and stakeholders. The conversation moves from his childhood in a farming community and the bankruptcy that shaped his appetite for risk, through Amazon's dot-com-era pressure and the creation of Prime, to his current role leading Simon & Schuster through a period of change. Greg shares: Why his definition of purpose is simple: give back more than you take What he learned building Amazon Prime alongside Jeff Bezos and the team How childhood adversity and family bankruptcy shaped his appetite for risk Why the best leaders stay obsessed with customers, not competitors Why transformation requires builders, not just operators How AI is changing leadership, decision-making and long-term value creation If you're a senior operator, founder, family office principal, or leader navigating uncertainty, this episode will challenge how you think about purpose, growth and long-term impact. The practical test at the centre of the episode is simple: are you building something that will outlast you, and are you building the team that can carry it forward? Greg Greeley | BioGreg Greeley is Chief Executive Officer of Simon & Schuster, the 102-year-old publisher now operating as an independent company. He grew up in a small farming community, where his father moved from selling insurance to farmers into running restaurants - an entrepreneurial household whose later bankruptcy, just as Greg left for college, taught him self-reliance and shaped his appetite for doing hard things.Trained as an engineer with a computer systems degree and an MBA in finance, Greg began his career in aerospace before moving to Sun Microsystems in the mid-1990s. In 1999 he left Sun - then at the top of its game - to join Amazon, initially in finance for worldwide operations. Over nearly two decades at Amazon he led the worldwide media business through the digital transition, created Super Saver Shipping, and was central to the creation and global expansion of Amazon Prime. He went on to join Airbnb in a senior leadership role during its period of hyper-growth, and today applies that builder's playbook to publishing, where he is focused on making a century-old company “work like a 102-year-old startup”.He describes his purpose simply: to give back to society more than you take by building great companies - and to be remembered as a builder. Hosted on Acast. See acast.com/privacy for more information.

An audience is more than a follower count. For filmmakers and creators, building a direct relationship with the people who care about their work can be the foundation of a sustainable creative career. In this episode, Alex Stolz speaks with Jeffrey Kohn, founder and CEO of TopFan, about what filmmakers can learn from the creator economy—and why building an audience and “owning” that relationship are two very different things. Jeffrey explains why creators cannot afford to depend entirely on social platforms and algorithms for access to their fans. Instead, he argues for using those platforms as a point of discovery, while creating direct channels through which audiences can become part of a deeper and more enduring community. The conversation explores the power of superfans; why relatively small but highly engaged audiences can be more valuable than large follower counts; and how creators can turn moments of attention into long-term relationships. Alex and Jeffrey also discuss crowdfunding, audience participation and the ways a committed community can help creators finance projects, generate revenue and carry momentum from one story to the next. A practical conversation about moving beyond rented platforms, creating genuine connection and building an audience that can sustain your creative work over the long term. About Jeffrey Kohn Jeff Kohn is the founder and CEO of TopFan. Prior to TopFan, Jeff was a distinguished enterprise architect for Oracle, led global e-business operations for for Sun Microsystems, and space radiation analysis for NASAs Mission Control. At TopFan, Jeff focuses on solving the platform dependency problem in the creator economy. TopFan technology provides creators with a customized, white-labeled website and mobile app platform that unifies content, community and commerce into one place, and full ownership of their fan data. In turn, creators own their platform, and achieve long-term financial stability and equity in their business.

Welcome back to The Main Thing Podcast! The Teachers We Never Chose Sometimes our greatest teachers don't stand at the front of a classroom. They arrive disguised as hardship, disappointment, illness, financial pressure, failure or seasons we never would have chosen. When fellow podcaster Rick Barron accepted my invitation to join me on The Main Thing, I expected to hear great stories from his remarkable 42-year career in Silicon Valley. What I didn't expect was to come away thinking about failure, gratitude, resilience and the unexpected teachers that shape a life. Rick's journey takes us from a military hospital during the Vietnam War to Apple's original Macintosh launch, through a frightening battle with melanoma that nearly cost him his left arm, and into a retirement filled with curiosity, mentoring and meaningful conversations. It's an episode that reminds us wisdom is rarely learned in comfort.   Episode Summary Rick Barron has lived several remarkable chapters. He served our country during the Vietnam era. He helped manufacture the original Apple Macintosh. He spent 42 years working for technology leaders including Apple, Hewlett-Packard, Sun Microsystems, Motorola, Symantec and Intel. Today, he is a fellow podcaster whose curiosity and love of storytelling continue to give his retirement fresh purpose. Yet this conversation isn't ultimately about technology or career success. It's about what life teaches us. Rick shares unforgettable stories of watching Steve Jobs unveil Apple's legendary "1984" commercial, receiving a melanoma diagnosis that threatened his arm, facing financial uncertainty with only $53 left in his checking account and encouraging a young intern named Amy Wong toward the career she dreamed of pursuing.   Resources to Explore

Unlocking Marketing ROI with AI: Insights from Uptempo’s Marie Bahl Uptempo.io About the Guest(s): Marie Bahl is the Chief Marketing Officer (CMO) of Uptempo, a pioneering company focused on providing cutting-edge marketing technology solutions. With over two decades of diverse experience across technology-focused industries, Marie is renowned for her ability to demystify complex technologies and make them appealing to targeted audiences. Her expertise spans roles in marketing and sales within prominent tech companies such as Opower, Tendril Networks, Converge, Yahoo, Zoho, and Sun Microsystems. At Uptempo, Marie drives innovative marketing strategies and customer acquisition approaches, aiming to transform the marketing landscape by leveraging artificial intelligence and data analytics. Episode Summary: In this engaging episode of The Chris Voss Show, host Chris Voss is joined by Marie Bahl, CMO of Uptempo, for an insightful discussion about the transformative potential of AI in marketing and the critical importance of proving return on investment (ROI). Marie shares her expertise on how Uptempo helps brands bridge the gap between spending and strategic success by crafting detailed, data-oriented marketing solutions. The discussion highlights the essential need to reconcile various marketing data sets to achieve a comprehensive view of ROI, which is the holy grail for marketing professionals worldwide. Throughout the conversation, Marie and Chris delve into how marketing data, when properly harnessed, can lead to unprecedented optimization and decision-making capability. Marie emphasizes the importance of using artificial intelligence appropriately, underscoring that it should focus on analytics and data synthesis rather than replacing creative output. The episode explores the concept of AI’s “jailbreak” moment, offering a glimpse into how brands can harness AI-driven insights to optimize marketing budgets and strategies. Additionally, they discuss broader industry trends, including how large corporations are adapting to new technologies and the significant challenges faced by marketers in justifying their budgets. Key Takeaways: Importance of Proving ROI: Marie highlights that ROI is a crucial measure for marketing success and how Uptempo provides the tools to tie various marketing activities directly to revenue outcomes. Role of AI in Marketing: AI’s potential lies more in data processing and analytics, not replacing human creativity. AI in marketing should enhance decision-making, not detract from the human element. Structured Data Equals Success: Reconciled and organized data is paramount for effective AI application, ensuring accurate insights and decision-making capabilities. Marketing Challenges Over Time: Marketers are expected to do more with less, requiring efficient technology to validate their strategies and demonstrate tangible business outcomes. Evolving Marketing Tools: Uptempo stands out by focusing on ROI over proxy indicators, integrating various data points to provide a holistic understanding of marketing effectiveness. Notable Quotes: “It’s not enough just to get the money at the beginning of the year, apply, do the voodoo that we do, and then at the end of the year go, ‘Hey, we did a great job.'” “Applied well, and Uptempo happens to do it, but if you can’t get it through us, buy it, build it, find it, acquire it, get somebody to do it for you, you need to be able to prove your value.” “ROI is the holy grail of every marketing CMO I think across the world; it’s the only measure that matters, and it’s the only measure we can’t get to.” “Marketing was a cost center, and you threw money at it, and we weren’t really sure what happened. Magic. Voodoo happened in the background.” “We have been spreadsheet jockeys, stitching together 80 spreadsheets to validate our existence for the last 30 years.”

“We put the dot in .com” นี่คือสโลแกนของ Sun Microsystems ยักษ์ใหญ่เทคโนโลยีที่เคยขับเคลื่อนเว็บไซต์ดังๆ อย่าง eBay และ Yahoo ในยุคตื่นทองของอินเทอร์เน็ต ด้วยมูลค่าบริษัทพุ่งทะลุ 2 แสนล้านดอลลาร์ แต่รู้ไหมว่า ภายในเวลาไม่ถึง 30 ปี อาณาจักรนี้กลับล่มสลายและถูกขายทอดตลาดด้วยราคาไม่ถึง 4% ของจุดสูงสุด! หลายคนคิดว่าเพราะฟองสบู่แตก แต่จริงๆ แล้วเกิดจากความผิดพลาดเชิงโครงสร้างที่หยั่งรากลึกกว่านั้นมาก วันนี้เราจะแฉเบื้องลึกว่าทำไมยักษ์ใหญ่ที่แจก Java ให้คนใช้ฟรีทั่วโลกถึงพังครืน และมรดกที่เขาทิ้งไว้วันนี้ยังทำงานอยู่ในโทรศัพท์และธนาคารเกือบทุกแห่งที่คุณใช้ได้อย่างไร เลือกฟังกันได้เลยนะครับ อย่าลืมกด Follow ติดตาม PodCast ช่อง Geek Forever's Podcast ของผมกันด้วยนะครับ #SunMicrosystems #บทเรียนธุรกิจ #กรณีศึกษาธุรกิจ #สรุปธุรกิจ #การล่มสลายของธุรกิจ #ประวัติศาสตร์ไอที #ผู้สร้างJava #วิกฤตดอตคอม #ถอดบทเรียน #เรื่องเล่าธุรกิจ #ข่าวไอที #เทคโนโลยียุค90 #RiseAndFall #ธุรกิจเทคโนโลยี #geekstory #geekforeverpodcast

In this episode of Channel Chat Dubai, Marc Sumner sits down with Kinda Baydoun, Senior Director at Veeam, to discuss leadership, partnerships, trust, and the future of the IT channel across EMEA. From starting her career at Sun Microsystems to leading one of the industry's most influential channel organisations, Kinda shares the lessons that shaped her journey and why building trust remains the foundation of every successful partnership. The conversation explores: • How Veeam is transforming its partner strategy across EMEA • Why "connecting the dots" is critical for channel success • The role of trust, relationships, and face-to-face engagement in the Middle East • What separates high-growth partners from those standing still • The impact of AI, cyber security, cloud adoption, and data resilience • Building high-performing teams and the qualities Kindah looks for in future leaders • Women in technology, mentorship, and sponsorship • Veeam's vision for the future following the acquisition of Coveware One of the most respected channel leaders in the region, Kinda provides valuable insights for vendors, distributors, MSPs, resellers, and technology leaders looking to accelerate growth in an increasingly competitive market.

Subscribe to our Newsletter:https://theultimatepartner.com/ebook-subscribe/ Check Out UPX:https://theultimatepartner.com/experience/ https://youtu.be/j0TuosYDQe4?si=7mzUwBe4PrQ-eB2E In this insightful session from the Ultimate Partner Live event in Bellevue, Washington, Vince Menzione sits down with Stephen Boyle, Corporate Vice President for Enterprise Partners at Microsoft, to pull back the curtain on the tectonic shifts redefining the tech ecosystem. Boyle details Microsoft's massive organizational pivot into enterprise and SME/channel divisions , explaining how artificial intelligence acts as the foundational thread unifying systems integrators, software vendors, and digital natives. Moving past market noise surrounding competing foundational models , he highlights Microsoft's strategy to become the ultimate “platform of platforms” by prioritizing user choice, security, and trust. Emphasizing a shift away from infrastructure technicalities and toward practical business outcomes , Boyle delivers an urgent mandate for partners to scale technical talent, eliminate traditional operational silos, and brace for the incoming consumption-driven, agent-based future of enterprise computing. Key Takeaways Microsoft has restructured its global sales divisions into distinct Enterprise and SME/Channel organizations to better target its massive total addressable markets. Artificial intelligence is fundamentally altering the partner ecosystem by dismantling traditional software and systems integrator silos to build interconnected, multi-party solutions. Rather than forcing alignment to a singular model, Microsoft aims to be the definitive platform of platforms by offering extensive choice across over 1,100 language models. The enterprise landscape is rapidly moving past experimental AI pilot phases and entering production setups completely focused on transforming core business outcomes. Tomorrow's service organizations are aggressively evolving into software-minded operations that deploy repeatable, highly specialized internal autonomous agents. Managing tokens and monitoring usage metrics represents the emerging operational baseline for balancing efficiency against the scaling expenses of large language models. If you're ready to lead through change, elevate your business, and achieve extraordinary outcomes through the power of partnership—this is your community. At Ultimate Partner® we want leaders like you to join us in the Ultimate Partner Experience – where transformation begins. Key Tags AI frontier, platform of platforms, enterprise partners, global systems integrators, digital natives, language models, token consumption, agent sprawl, citizen developers, shadow IT, business outcomes, technical enablement, marketplace growth, hyper-scalers, processing fluency, sovereign AI, industry ecosystems, data governance. Transcript [00:00:00] Stephen Boyle: This is the biggest, most transformative, iterative change in technology we’ve ever seen, where, if you wanna call it a paradigm shift or whatever word comes after paradigm shift. [00:00:12] Vince Menzione: We just came back from Ultimate Partner live in Bellevue, Washington, where we hosted incredible leaders for two amazing days. Come join us for this next session where we explore the tectonic shifts we’ve all been seeing. Uh, I am thrilled to invite our next guest up on stage. I’ve known this gentleman for several years back in my days at Microsoft, and, um, we’ve been friends, actually Microsoft, and then we both went and did different things, came he’s come back to Microsoft in a big way. [00:00:46] Vince Menzione: Uh, Steven Boyle, for those of you don’t know, is recently a named the C. We will talk about it in a second, but I, I need to announce you properly. Is the corporate vice president, which by the way in Microsoft is a big deal for enterprise partners. He and Nicole De and I would say are the two Microsoft leaders in the organization. [00:01:06] Vince Menzione: Nicole is the channel chief. Steven has a, a big remit and we’ll talk about that up on stage. But I’m just so delightful for his support and for making the time in a very busy week at Microsoft ’cause this is CEO summit this week to make some time to come with us and be on stage with me. Please welcome my good friend Steven Boyle. [00:01:29] Vince Menzione: Good to see you, sir. To see. So I’m gonna put you on this side. [00:01:33] Stephen Boyle: Okay. [00:01:35] Vince Menzione: The hot seat. So I’m gonna, I, I didn’t do a justice and I, I wanted you to explain your role. I, I think I know, but I think for the, for the people in the room, uh, talk to us what Enterprise Partners means at Microsoft and what that role remit and remit looks like. [00:01:50] Stephen Boyle: Um, CVPs may or may not be important, but one thing they don’t do is get invites to the CEO summit. So I’m super pleased to be here with you guys. No, no, it’s totally cool. It’s totally cool if that phone rings. No, I’m kidding. Doesn’t. So what does it mean? So I’d like quickly, um. January last year, uh, we split the sales organization into enterprise and small to medium enterprise and channel. [00:02:15] Stephen Boyle: You guys probably familiar with that? Nicole is the, uh, chief partner officer lives in the SMA and C world and drives the channel, um, drives our marketplace business and, and a lot of other things. Um, for that 60 billion, um, you know, total addressable market that we have. Down there in SME and C. Um, at the same time, we established enterprise partner as part of Nick Parker’s overall organization. [00:02:40] Stephen Boyle: Um, but for most of 2025 we ran it as global systems integrators and advisories, ISVs and digital natives. So three separate footprints all focused entirely on, on, on enterprise. Um, in December, January, we talked about establishing an enterprise partner leader that would. You know, aggregate all of this stuff. [00:03:00] Stephen Boyle: Um, I was fortunate to come through, um, some frankly, pretty hairy, uh, experiences, I bet with some of our senior leaders. Um, I, I’ve loved to [00:03:08] Vince Menzione: been in the room for that [00:03:09] Stephen Boyle: questions like, why Steven Boyle and things like that, right? And really have to dig deep to, uh, to justify. Anyway, uh, I’m blessed and honored, uh, to run that entire portfolio of partners, uh, for the entirety of the enterprise partner world, which now from a chief revenue officer perspective, belongs to Deb. [00:03:25] Stephen Boyle: Deb Co. So Deb is the enterprise leader for all of our sales that we do into that space. Awesome. Um, I have three regional leaders, Nina Harding here in the United States, Ehab Ra in in Europe, and Heather Gordon in Asia that mirror and replicate and flow down the things that we decide to do from a strategy perspective for the, uh, for the core. [00:03:45] Vince Menzione: And we love Nina. She’s been, she was at our last event, [00:03:47] Stephen Boyle: super, super lady. And, uh, you know, the US is still 50% of our overall business. [00:03:53] Vince Menzione: Yeah. [00:03:53] Stephen Boyle: Too big to fabric. Every time I talk to Nina, I’m like, Nina, you’re too big to fail. We can’t cover you anywhere else. So you know, you’ve gotta be successful here in the Americas. [00:04:01] Vince Menzione: So I think just for breaking it up, I, ’cause I do want to like, it’ll lead to the next question, right? So you have the global systems integrators, all these systems integrators. Essentially you have all of the software companies we used to call ISVs, we now call SDCs or software development corporations. [00:04:17] Vince Menzione: And then you also have the AI stack, I’ll call it. Right? So under Jason Grafe. Yeah. Many, many might know. Jason’s been a guest on the podcast and was Satya’s chief of staff at one time, eight years. Eight years. Wow. I didn’t realize there was that many. [00:04:31] Stephen Boyle: Carry carried a lot of bags for Satya over the years. [00:04:34] Vince Menzione: Unbelievable. Well, let’s, I mean, so AI is an important component, right? And you saw Jay’s, Jay talking, just talking about AI and all these things. I would love to start here, right? Because, uh, you’re, you’re, I wanna get your perspective as Microsoft, your perspective as Microsoft on the biggest shifts you’re seeing in defining this we’ll call AI Frontier. [00:04:54] Vince Menzione: We’re seeing right now, how should partners translate that into how they position and go to market externally? How, how do we need to think about this time? [00:05:02] Stephen Boyle: Yeah, that is, uh, that is a huge question and I’m not sure we’ve got enough time to go into the, into all of the detail. Um, so let me sort of up level it a little bit for you. [00:05:10] Stephen Boyle: And I think, look, the move that we meet at made a couple of months ago and pulling together those three aspects. Nicole had already done it in SME and C. Right. One partner organization across the world with a very common set of goals. We were working closely together, Sandy Gupta, on ISV, Jason on ai, and myself on on si. [00:05:29] Stephen Boyle: But we were still working closely together across silos. So the opportunity for me, 60 days into this role is AI just allows you to wire the partner ecosystem together differently. Right? And even if you look at how we’re going to market an AI today, um. You know, with, with, with chat GPT, with Claude, with Anthropic, um, I think there’s something like 1100 different, you know, language models on Microsoft today. [00:05:55] Stephen Boyle: So the way I think about AI is we are absolutely gonna be the ultimate platform of platforms. Yeah, choice is incredibly important. Um. It’s, it’s, you know, turn the clock back 12 months, everybody was chat gpt five point x, you know, and then six months ago it was Gemini and now it seems to be clawed. And honestly I don’t know what it’s gonna be next quarter. [00:06:15] Stephen Boyle: So the only thing I can do is offer you choice. [00:06:18] Vince Menzione: Yeah. [00:06:18] Stephen Boyle: And from a partner perspective, I think that minimizes or reduces the risk that you have betting on the Microsoft platform because you can go in a multitude of different directions. I know we’re not in Europe, but if you were in Europe and you were worried about G-G-D-P-R and Jay mentioned sovereignty, you’d probably be like lining up really closely to Misra. [00:06:37] Stephen Boyle: Yeah. And a bunch of other Europe, European partners. So wherever you are in the globe, I wanna be that platform choice. Um, and we will lead with our own first party solutions. I hope they’re not coming for me. Um. I parked safely in the hotel. It can’t be me. Um, but you weren’t vibe coding in the room. Um, but you know, wherever you are in the world, in whichever industry you are in, um, it is our intent to, to offer that platform of platforms and to give the broadest set of partners the opportunity to engage with us. [00:07:07] Vince Menzione: I think that’s really important because I, I have found, especially in the last month or two, people are, it’s almost like a knee jerk. Don’t you feel like people don’t know what to do? There’s been so much noise in the press and the media and, and the markets around open AI and anthropic especially. Where do I go? [00:07:26] Vince Menzione: Seems to be like when I, when I sit, I watch everybody in the room here. I think they’re, they’ve all been thinking that as well. So you can, [00:07:31] Stephen Boyle: there’s a, a little bit of a deer in the headlights moment. Yes. And even I like, I get that. Yeah. Um, you know, I saw, uh, Jay slides. Jay, love the presentation. Love the slides, man. [00:07:40] Stephen Boyle: I’m gonna steal several of them. Um, we’ll talk about that later. We, we [00:07:43] Vince Menzione: have the deck, [00:07:45] Stephen Boyle: but, but in all seriousness, you know, this, this is like. It’s a new paradigm. I will date myself a little bit. Some of you might heard me say this. I sold many computers in the 1980s. Mini computers. Some of you in the room are going, what’s a mini computer? [00:07:59] Stephen Boyle: Um, I sold client server for Sun Microsystems in the nineties. I sold an awful lot of Oracle databases in the Auts, I think they’re called, and I’ve done two stints with Microsoft. This is the biggest, most transformative. Iterative change in technology we’ve ever seen. What, if you wanna call it a paradigm shift or whatever word comes after paradigm shift. [00:08:18] Stephen Boyle: Um, and we are building intelligent systems at scale faster than we’ve ever seen. Scalable, mission critical solutions being implemented today inside of Microsoft and with our most important customers. So, and we can’t do it without partners, right? There is absolutely nothing we can do in this industry. I will, I will put the, you know, the elephant in the room out there. [00:08:40] Stephen Boyle: Our ISD organization has between five and 7,000 people. Our forward deployed engineering organization is about a thousand people. [00:08:47] Vince Menzione: Yeah. [00:08:48] Stephen Boyle: So when you look at the scale of the total addressable market that Jay just talked about. We are gonna service directly like this much [00:08:55] Vince Menzione: used to be 5%. Was it even, is it even that high? [00:08:58] Stephen Boyle: I doubt it’s, I doubt it’s even that. And the billions of dollars that we spend every year helping our customers transform to what we’re now calling frontier firms is gonna be, have to be driven with every single person in this room in some way, shape, or form. Judson is not asking Marla to significantly increase ISD. [00:09:15] Stephen Boyle: Not asking John to significantly increase FDE, although we probably will hire in that area just because of the, the newness and the, you know, bright shiny object that everybody’s like, oh, FDE, I’ve gotta have those. We’ve got a thousand already today that have been around in John’s organization for 10 plus years doing the things that we are doing today. [00:09:32] Stephen Boyle: But we are gonna build out that muscle. But the real way we’re gonna build out that muscle is with all of you in this room. That’s like categorical. That is my like, probably number one goal for the next one to three years is make sure that, that story that Jay just told about Microsoft not being involved in AstraZeneca. [00:09:48] Stephen Boyle: I probably won’t tell Judson that Jay, but I love the story. Um, like if you could all do that for me, like win, um, that is so, you know, from our worldwide learning, through our skilling enablement through our cloud solution architects that I personally own. We are pivoting aggressively towards making sure that the partners understand our platforms better than any other job, number one for me right now, if you don’t understand what I’m selling, like I’m kind of dead in the water obviously. [00:10:15] Stephen Boyle: Well, [00:10:15] Vince Menzione: I was gonna ask you why now? Why Microsoft? Why now? Right? Because there is a lot of noise. You know, Google just announced, you all announced your results on the same day, which was astounding. That was freaky, wasn’t it? It was. It was the first time. And the, the total commitment, customer commitment is over a trillion dollars now, I think 1.2 trillion is what I counted up. [00:10:33] Stephen Boyle: Yeah. [00:10:34] Vince Menzione: But it’s saying a lot about like, what do I do now, like as these partners in the room. Um, how, I think you kind of already, and you’ve talked about this, about differentiating where Microsoft is, I think J Slide does a lot of justice there. It says how, uh, Microsoft Partners came into the room, surrounded the customer. [00:10:52] Vince Menzione: It feels like Microsoft has always leaned in big time on partners. Uh, more so I would say than any other organization out there. What would [00:10:59] Stephen Boyle: you say Joe Roses, my chief of staff, business manager and so many other things was telling me last night that, you know, we used to say 500,000 partners. [00:11:05] Vince Menzione: Yeah, [00:11:06] Stephen Boyle: it’s a, it’s a significantly higher number than that as well. [00:11:09] Stephen Boyle: So there’s an element of, you know, back to the deer in the headlights, which partners are, are more important. One of my other phrases that I say on a regular basis, the winners and losers are yet to be decided in this next wave. Like, I want all of us to on the right side of that argument. Right? But, but it’s gonna be a challenge and, and companies are going through shifts. [00:11:28] Stephen Boyle: You know, Accenture, maybe, possibly doesn’t need 750,000 employees in the not too distant future. Maybe TCS at 600,000 doesn’t need 600,000 human employees. So we’re going through this dramatic shift of, you know, what’s the right balance going forward. What I would say about Microsoft is notwithstanding the fact that we’ve figured this out for 51 years, which is a little bit mind blowing, um, that you know, all the way back in the seventies we’ve gone through so many iterative changes. [00:11:56] Stephen Boyle: People have questioned just like they’ve questions. A lot of other technology companies, are you gonna be around for the long haul? I think we’ve proven time and time again, and I love Jay’s story. I’ve used that myself about how many companies disappear on a, on a decade to decade, you know, business. 10 years ago I had the opportunity to listen to Craig Clayton Christensen, who’s sadly no longer with us. [00:12:15] Stephen Boyle: Yeah. But you know, the books that he wrote and the story that he told to Microsoft 2014, we were nowhere in cloud. [00:12:21] Vince Menzione: Yeah. [00:12:22] Stephen Boyle: AWS was so far ahead of us, it was crazy. And he came in and he’s like. You know what? You guys need to be successful. You need to figure out how to cross this chasm again, and we’ve done it time and time again. [00:12:32] Stephen Boyle: You can go back. You know, Microsoft used to be known as a fast follower in ai. I don’t think we’re a fast follower. I think we’re right up there. We’re right at the front, but that race is still being run and the winners are losers are yet to be decided. [00:12:44] Vince Menzione: I was in that room with Clayton Christensen with you, by the way. [00:12:46] Vince Menzione: I remember, I remember that. That was at a Prism conference. [00:12:49] Stephen Boyle: Yeah. Yeah. [00:12:50] Vince Menzione: You men, you touched on this with the GSIs a little bit. How do you see the roles evolving? You know, we, we, we bucketed all, we’ve always been. Fantastic about bucketing ISVs or SDCs and sis and digital natives. Yeah. How does it, how does that all come together? [00:13:06] Vince Menzione: Does it come together any differently in this new AI platform era, or is it the same? [00:13:11] Stephen Boyle: I look, I, I’ve said this for a long time, like if you go into AstraZeneca, the six plus, you know, frontline partners, there’s probably a whole board of second, third tier that, that we don’t know about doing, you know, things across the AstraZeneca group. [00:13:25] Stephen Boyle: It takes several villages and sometimes a small town, especially in my world, in the enterprise world, strategic five hundreds. Yeah. Um, you know, we, we ran some reports a few years ago and it is shocking how many global systems integrators have a footprint in Shell or Exxon or, you know, bank of America or whatever else. [00:13:44] Stephen Boyle: So I’ve always believed that partner to partner is critical. Yeah. I think it became even more critical in the, in the AI world, and I’ll take my new friends at Anthropic. So I went to the first Anthropic partner Summit. Some of you might have been down there in, in San Diego, um, just a couple of months ago. [00:13:59] Stephen Boyle: Same partners, same people from the same partners. In the room, you know, talking about what they’re gonna do together with Anthropic. Um, and I’m looking out across this audience going, okay, well I know him and I know her and I know those guys, and like, I need to figure out how I’m gonna weave this together. [00:14:14] Stephen Boyle: So it’s not just an Accenture and Anthropic or an NTT data and anthropic, but it’s an NTT data plus anthropic plus Microsoft. Story going forward. And then who’s best at delivering those services capabilities? So it’s it at every juncture that I see in the, in the partner community, and this is the, the reason why I argued vehemently with Nick, that it has to be one organization I’m gonna create maybe given a little bit away. [00:14:40] Stephen Boyle: So if you’re recording, stop now. Um, I’m gonna create an enablement organization that is partner agnostic. I don’t necessarily care. I do care about the digital natives, but I don’t care about how I train them. Right. What I’m more important of is how do I train the digital natives in what the sis are doing, and how do I train the sis and what the ISVs Plus digital Natives are doing. [00:15:01] Vince Menzione: Yeah. [00:15:01] Stephen Boyle: That is my, that’s my game plan. If I fail there, then I think we fail to raise the bar and be differentiated in an AI world, and I’m not set up like that today. [00:15:12] Vince Menzione: I wanna, I wanna ask you, uh, uh, because I was looking at Jay’s slide and the, the managed piece is. And we have a lot of managed service providers in this room today. [00:15:20] Vince Menzione: A lot of them, by the way, come from the old school of managed services. The managed piece seems to be like, if I’m doing something today with ai, we’re gonna talk about security next, uh, up on stage here. It seems like there’s a new set of skills or a different approach to the customer, don’t you? Don’t you agree? [00:15:37] Stephen Boyle: I I [00:15:37] Vince Menzione: think you need to keep your hands on the steering wheel at all [00:15:39] Stephen Boyle: times. I think what it boils down to is you can’t do AI unless you do certain other things. [00:15:44] Vince Menzione: Yeah. [00:15:44] Stephen Boyle: Right. You could be a modern work specialist and you could make a lot of money being a modern work specialist, or you could be a, a dynamic specialist. [00:15:52] Stephen Boyle: We just held our, uh, inner A in a circle conference last last week, which I was disappointed to miss for the first time in a few years. Those, those days are, are, are fast becoming over. [00:16:03] Vince Menzione: Yeah. [00:16:04] Stephen Boyle: Um, why? Because everything that I’ve just said is tied together by ai. Yes. And in order to do good ai, you need good data. [00:16:12] Stephen Boyle: And in order to trust everything that you’re getting, as Judson talks about trust and intelligence, you need to wrap that in a really secure [00:16:19] Vince Menzione: Yes. [00:16:19] Stephen Boyle: You know, en en environment. Now we will do our best to provide levels of security into how we deliver ai. But that’s not the end of the game, right? You have to take it all, all the way to the edge. [00:16:30] Stephen Boyle: So that’s why a siloed partner or a singular commercial solution area partner in Microsoft’s terms, has got to transform its business. ’cause if you’re gonna do ai, you’ve gotta do those other things as well. [00:16:41] Vince Menzione: Agreed. I must see the model changing, and in fact, I see like bigger organizations becoming managed service providers in many respects. [00:16:48] Stephen Boyle: Yeah. Yeah. I mean, look, there’s still, there’s still a role for all the old terminology you mentioned is SV to sdc. Yeah. I’m like, I’m been around long enough. Look, it’s ANB still anv, it’s still an isv. Thank you. Independent software vendor. Um, and it’s, you know, where, where AI is allowing software to be, you know, frankly developed in a number of different places. [00:17:07] Stephen Boyle: We are all citizen developers. Um, you know, I was on a call with our internal leadership yesterday, um, and you guys might have heard this story ’cause I think it came out at Ignite. When we turn the agent 365, around and on ourselves. We found 130,000 agents running across Microsoft that had been developed and deployed internally with, I mean, you could call it shadow it. [00:17:28] Stephen Boyle: I guess that would be one phrase that you would use for it, but the reality is if you, if you haven’t got something to do your job today, you have the tools. To build it really, really fast. Um, and that, you know, that’s, that’s a great opportunity for people to be able to do their work, you know, in a better and in a different way. [00:17:45] Stephen Boyle: But it’s also a huge opportunity to make sure that data governance and security and all the other things that we need to deliver are there out of, out of the gate and out of the platform that we deliver. So security’s absolutely critical. Not saying that managed services won’t grow, um, at, at some level as well, but only if they transform into this multifaceted way. [00:18:04] Stephen Boyle: Yeah. Thinking [00:18:05] Vince Menzione: about, well, that’s what I was, I was gonna lead to here with innovating. It’s happening across, I mean, we’re talking about chips, we’re talking about foundational models, LLMs, we’re talking about applications, we’re talking about agents. How should we think about where to play and how to differentiate as partners in this room? [00:18:22] Stephen Boyle: I think. [00:18:25] Stephen Boyle: So look, I mean, one, one of the ways that Judson talks about it is I think silicon’s gonna change over time. Yes. NVIDIA’s definitely the 800 pound gorilla, maybe the 8,000 pound gorilla. Yeah. Uh, but you know, if you read the press, there’s, there’s things happening in, in different places as first party silicon, which we clearly are, are developing, um, in a quantum direction for sure. [00:18:45] Stephen Boyle: Um, there’s lots of different language models that haven’t even been launched on, on, on the marketplace yet, so. You know, Judson’s trying to uplevel our conversations. You’ll hear us talking about conversations more and more as we go into FY 27, um, that obviate all of those layers. Just like even when I was selling Sun Microsystems, it was about the business outcome and the business solution that we were solving for not necessarily the fastest piece of hardware or the best client service solution on, on the market. [00:19:17] Stephen Boyle: So I think what’s gonna happen over the next 12 to 24 months is we’ll have so many different models to choose from. We’ll have more silicon to choose from, but those won’t be the real buying decisions. The real buying decisions of what? How am I trying to transform my finance organization, my HR organization, and my supply chain? [00:19:36] Stephen Boyle: Because the underlying technology, Judson says commodity I, I guess I can go with that. It will be commoditized and we’ll really start to focus back on what the important things are. We’re moving a lot from pilot to production. You guys have probably seen that. The numbers that Jay just showed about how many. [00:19:52] Stephen Boyle: Projects are failing, is getting less and less because we’re getting smarter and smarter about what it takes to actually drive the business outcome. And I need all of us to be talking that same language. Yeah. Having conversations with head of HR about how we’re gonna transform human capital management in the, in the age of agents, if you like, like the underlying platform. [00:20:14] Stephen Boyle: It’s not, don’t worry about it. You wanna be on a secure platform. Don’t get me wrong. But at the same time, I don’t think we, we spent too much time worrying about that. [00:20:21] Vince Menzione: Yeah. We’re not, what you’re saying is we’re not spending enough time on outcomes. On the business outcomes. Right. And that’s where we need to focus. [00:20:27] Vince Menzione: We’re, we’re focusing on, I, I feel like we’re, it’s a signal to, to noise ratio that we’re living through right now. There’s too much noise. [00:20:33] Stephen Boyle: Yeah. [00:20:34] Vince Menzione: And we’re not focusing on the signal. I think that’s what you’re saying. [00:20:36] Stephen Boyle: I, it’s got to be, I mean, to be honest with you, it’s always been, you know, even when I sold what I would perceive, you know, sun in the nineties was a rockman ship to the stars and, you know, kind of sad what happened to that company. [00:20:47] Stephen Boyle: Um, but we, we were, we were fixated on, we had the best client server. But, but nobody was buying, you know, a piece of Sun hardware as a room heater, which is all it did, you know, like for the longest. But if you had SAP, if you had Cybase, if you had Bond, remember Bond, I mean all of those applications that drove the business outcomes, we’ve gotta get back to that kind of mentality. [00:21:09] Stephen Boyle: Yes. And worrying a little bit less about the underlying architecture. Yeah. It needs to be, it needs to be part of the conversation. ’cause it needs to deliver trust and security and intelligence and everything else. Then you need to rapidly move to what are you trying to achieve and how can we ensure the, the, the success of, of your business outcome. [00:21:27] Stephen Boyle: And look, I mean, Palantir pri you know, sort of came out and said, well, the way we do that is through forward deployed engineering. Um, and they stole the show. And, and, you know, they’re, they’re doing very well as a result of doing that. Uh, but if you go and talk to, um, Tom Siebel’s organization at C3 ai. [00:21:43] Stephen Boyle: They’ve had FDS for quite a while. You know, I told you about John Chuchu 10 years ago. John Chu, Chuck’s job was to go and get all the applications that we needed on the Microsoft phone. Remember that? [00:21:54] Vince Menzione: Yes. Um, [00:21:55] Stephen Boyle: you know, so we’ve pivoted John o over the years to doing what he’s doing now, which is to go sometimes in partnership with, with partners into the customer and say, what is it you’re trying to achieve? [00:22:05] Stephen Boyle: Let me show you how I can build that for you in three weeks or three months. That might have taken you three years. We literally just did a hackathon with one partner last, last, last week with, uh, with our ISE organization, the, the, the forward deployed, uh, group that John runs. Um, and one of the big customers said, I’ve just done in three days what would’ve taken me three months. [00:22:26] Stephen Boyle: Now he hasn’t productized it and rolled it out and blah, blah, blah. But the reality is that is how fast things are changing. And this was not a small company. This was a very, very large oil company, and they were like blown away by how much we can achieve. We’ve gotta do that at scale. [00:22:41] Vince Menzione: Yeah. [00:22:42] Stephen Boyle: You know, we, we have a commitment to scale our FDE community through partnerships to touch all of the S 500 in a very personalized way. [00:22:51] Stephen Boyle: And then, you know, at a slightly, you know, lower ratios down through the, through the majors and into, into Nicole’s SME and C world as well. [00:22:59] Vince Menzione: Jay talks about the decade of the ecosystem. He coined that term back, back on a podcast way back in nine, in, uh, in 2020. Microsoft has been at the, for, we used to call partner to partner back, back in the day. [00:23:10] Vince Menzione: Mm-hmm. Do you remember those days? How do you think about this ecosystem evolving and what steps are you taking to help bring these organizations together? Because I, I, again, we look at the seven seats or 6.3 seats at the table. The customer has the power now that they didn’t have before. ’cause they have the commitment with like with Microsoft and they can buy off of the marketplace and pull together multiple organizations to go, go do that. [00:23:34] Vince Menzione: How do you think about helping to orchestrate that as the leader of the enterprise partner business? [00:23:39] Stephen Boyle: So I’ll start with a really big example, and I’ll try and sort of scale it down a little bit. But my friends at Accenture, with the Accenture, Microsoft Business Group, we spend an awful lot of time, you know, in, in each other’s pockets, in each other’s deals. [00:23:51] Stephen Boyle: We know everything that’s going on in the Accenture, Microsoft Business Group. And a couple of weeks, or maybe a month or so ago, I was told that the Microsoft Business Group is now larger than the SAP Business group. It probably flip flops. [00:24:03] Vince Menzione: Yeah, [00:24:04] Stephen Boyle: it won’t be too long before the Anthropic Business Group is bigger than both of those. [00:24:08] Stephen Boyle: So what I need my Microsoft team to do is to not spend all of their lives in the. A MBG, the Azure, the Accenture, Microsoft Business group, but to go make friends in the Anthropic Accenture Business group and frankly still to make friends in the SAP business group and maybe in the Oracle Business Group and the list goes on. [00:24:27] Stephen Boyle: So at a macro 11, in the very largest accounts where we haven multiple practices, where we haven’t spent time before, I’m gonna. Push my people into uncomfortable zones and I’m gonna push them to go into those other areas and I’m gonna load them up with technical talent and cloud solution architects and ai, you know, forward deployed engineers. [00:24:45] Stephen Boyle: And I’m gonna force different people to talk together that haven’t talked together. So I can do that in TCS. I can do that, Capgemini, I can do that. Um, you know, in Europe with Capgemini and Misra is a classic example. Um, with the, with the Indian sis, Indian based sis, they’re all big enough where I know all the practices exist. [00:25:04] Stephen Boyle: I just need to do a better job of, of talking to them. Now, when you downsize that into, you know, into a, a company that doesn’t have all of that scale, this the same truth still holds. I need to talk to people who aren’t necessarily motivated every single day to do something with Microsoft. I need to talk to people who are motivated to do something with an AI partner or even a traditional SaaS partner. [00:25:27] Stephen Boyle: I noticed yesterday, actually no, this morning I got a notification that we just passed, um, a billion dollars in revenue on the marketplace with ServiceNow. [00:25:35] Vince Menzione: Nice. [00:25:36] Stephen Boyle: Um, and I think AWS announced the same thing, by the way this month as well. Um, so thank you to the ServiceNow people. Yeah. Um, you know, that is that there’s a tremendous demonstration of how far we’ve come in marketplace. [00:25:48] Stephen Boyle: ’cause that’s another one where we trailed AWS quite significantly. But with the right partnerships. And driving the right motions, we can, you know, we can definitely catch up and we will continue to pass, uh, some of, some of the other hyperscalers in, in, in that way. So really the bottom line to your question is partner to partner is still real. [00:26:08] Vince Menzione: Yeah, [00:26:08] Stephen Boyle: how we do it and what we use to tie things together. And I know that compensation drives behavior and we’re not gonna get into a compensation about like how we get compensated and everything else, but the reality is I’ve gotta break down those barriers and those silos and I’ve gotta deliver real meaningful enablement and practice development so that, so that the people who sit in the Anthropic business group and the people who sit in the Microsoft Business Group are spending as much time together as they are with me. [00:26:34] Stephen Boyle: That makes sense. Simply put, that’s what I, I need to achieve at scale rapidly. [00:26:40] Vince Menzione: So to, we’re getting close to time here, but as you look forward, what would define the most successful partnerships in this ecosystem? Is it, is it what you described, the opening up the aperture or for the, for the leaders in the room here today, what should they go do better and differently? [00:26:58] Stephen Boyle: Um, so obviously we’re closing out this fiscal, we’ve got Microsoft start and Microsoft start for partners coming up in July. Um, I mentioned the fact that we’re, we’re driving. Cu customer engagement through the lens of conversations and how do we achieve business outcomes? I would encourage you to, to gravitate, if you like, above the commercial solution areas where you might have understood, this is how I interact with Microsoft today. [00:27:23] Stephen Boyle: Um, and abstract it up to that AI layer. You know, think about trust, think about intelligence, think about business outcomes, and how do I potentially weave together a story? If I’m in the dynamic space, how do I get better in data? If I’m in the data space, how do I get better in. In that modern work environment, but really use AI as the overlay to, to help tie that together. [00:27:44] Stephen Boyle: That’s one thing. The second thing is if we’re not training you in the right direction, it’s stevenBoyle@microsoft.com. Let me know. Awesome. Um, we’ve got programmatic stuff, um, you know, and we’ve got high touch stuff as well. So I think this is, this is another time where Microsoft is gonna over pivot on all of the training and enablement that we need to do to make sure that you’re, you know, you’re grounded in our platform. [00:28:07] Stephen Boyle: Um, I think there’s a huge opportunity with this agenda future to become more of a software partner. You know, even the deepest services organizations are going to need agents, and the more successful ones will be the ones that can turn on those agents in a repeatable way. So. Our agents, the new SaaS. I’m not exactly saying that, but I think that the agen future is one where even the more services oriented companies will, will have teams of agents that they’re deploying. [00:28:35] Stephen Boyle: In fact, I had a very, very large systems integrator, um, in, in the EBC just about a month ago, three weeks ago. Um, and I was sat next to their head of consulting and he showed me what he called his God dashboard. Uh, and right in the middle of his God dashboard there are like 450 accounts. All of whom I recognized, ’cause they were all in the enterprise, right in the middle of his dashboard was, how many tokens am I spending? [00:29:00] Vince Menzione: Yeah. [00:29:01] Stephen Boyle: Like, not like what’s my daily runway? You know, not am I making a profit on that account or anything else like that is like, how many tokens have I consumed? Yeah. Because there is an awful lot of, that is the new juice, if you like. That’s, that’s driving the success. You can have the smartest people on the planet, but you’ve got to still arm them with all the best tools that are available out there. [00:29:22] Stephen Boyle: So it’s fascinating to listen to him, how he had gone through that thing of, you know, agent sprawl, how many are really working, how many are not working? How can we prove that? You can prove it through, you know, managing your tokens. There’s a new version of. Finops for tokens, for want of a better phrase, that’s gonna be critical for us all to understand. [00:29:40] Stephen Boyle: ’cause they’re not cheap, they’re not free, that’s for sure. And, and they might not be cheap if you’re not, if you’re not managing them and using them effectively. Yeah. So that’s the other thing that I would really get on top of. And, you know, we’re gonna make some announcements in the not too distant future about the consumption driven future. [00:29:56] Stephen Boyle: Um, that, that we will, that we will deliver with our first party and third party platforms going forward. So that’s another. Another critical thing [00:30:03] Vince Menzione: sounds like some exciting announcements. Pretty soon. [00:30:06] Stephen Boyle: Yeah, could look close. Quarter four, help me close. Quarter four. Yes. That’s priority number one, two, and three right now. [00:30:12] Stephen Boyle: Uh, but get ready for some, you know, for some new announcements in July. Um, look, the future is incredibly bright with Microsoft. It’s incredibly bright in the industry as a whole, right? I mean, let, let’s be honest, the, the growth targets that we will have for ne next year are astronomical, and we will not make them without the partner community that we have, without training and enabling the partner community that we need for tomorrow. [00:30:34] Stephen Boyle: So like, stay close, you know, stay engaged. Talk to your partner development managers, talk to the talk to field reps, talk to the accounts that that, that you are in, and stay as close as you possibly can to our emerging strategy. And, um, you know, look, I, I think if I had fivefold or tenfold the people I have today, I still wouldn’t be able to touch everybody that I would like to touch in the partner community. [00:30:58] Stephen Boyle: So I’ll apologize in advance. Um, but we’re gonna have some, you know, some really cool ways of learning. Um, and we’re gonna make sure that they’re available to the widest possible audience. [00:31:07] Vince Menzione: Well, we bring the practitioners and the experts in the room to help with that as well. Right? Yeah. Because you can’t always have a partner development manager tied to everybody in the room. [00:31:14] Stephen Boyle: I, I would do hackathons on AI every week with every partner and every part of the world, but I can’t. [00:31:19] Vince Menzione: Yeah, exactly. Well, so good to have you today. Thank you. So good to see you again. I don’t know what your schedule is like. I, we didn’t, we don’t have enough time for questions. [00:31:28] Stephen Boyle: That’s cool. [00:31:28] Vince Menzione: From the audience. [00:31:29] Stephen Boyle: I’m gonna stay around for a little [00:31:30] Vince Menzione: while this [00:31:30] Stephen Boyle: morning and I’m coming back [00:31:31] Vince Menzione: for cocktails. Alright, terrific. So. Stephen Boyle will be here for cocktail hour. Thank you. Four 30 and uh, I wanna thank you, sir. So good to have you. Thank you. Good to see you. Absolutely. [00:31:42] Stephen Boyle: So much. Absolutely. Hey, thanks everybody. [00:31:43] Stephen Boyle: Thanks for what you do today, and hopefully thank you for what you do tomorrow as well. [00:31:46] Vince Menzione: Thank you. An incredible leader. [00:31:49] Stephen Boyle: Don’t forget, ultimate [00:31:51] Vince Menzione: partner Alive is coming soon, June 18th at our executive breakfast in New York. I hope to see you there.Description The Future of Tech is Here. Subscribe to our Newsletter:https://theultimatepartner.com/ebook-subscribe/ Check Out UPX:https://theultimatepartner.com/experience/ I

Welcome back to Liftoff with Keith, the show where we sit down with the founders, operators, and industry leaders building the future in real time.Today's guest is one of the most respected voices in digital infrastructure — Dean Nelson.Dean has spent nearly four decades at the center of the internet economy, helping build more than $10 billion in digital infrastructure across four continents for companies like Sun Microsystems, eBay, PayPal, and Uber.He's also the founder of Infrastructure Masons, a global community uniting the builders of the digital age, now celebrating its 10-year anniversary.In this episode, we unpack the explosive growth happening across AI infrastructure and data centers — including staggering projections that the industry could spend $500 billion this year alone, scale toward $3 trillion by 2028, and potentially hit $7 trillion by 2030.The conversation explores:Why the industry could spend $7 trillion by 2030The explosive rise of AI infrastructureThe shift toward inference and edge computingCommunity and environmental pressures facing data center growthThe labor and construction challenges slowing deploymentWhy Texas has become ground zero for AI infrastructure expansionAnd how power availability may become the defining constraint of the AI eraIf compute scaled like this but power didn't… are we effectively bottlenecking the AI era on energy infrastructure?This is a fascinating conversation about the future of AI, data centers, infrastructure, and the physical systems powering the next generation of innovation.Let's lift off.Connect with Dean Nelson: Website: https://imasons.org/ LinkedIn: https://www.linkedin.com/in/deannelson/ Publication: https://imasons.org/publications/ Sponsor Info: We are strategic business advisors with decades of leadership experience and a proven track record of driving businesses' growth. We specialize in creating custom-tailored strategies to introduce your company, drive growth, build leadership teams, and ensure companies implement appropriate compensation programs. Our mission is to utilize our expansive network to benefit your company https://www.compass-strategic-advisors.com/ Subscribe for more founder insights and hit the bell for notifications! Follow us on our channels for exclusive startup content and behind-the-scenes insights from interviews like this one. Spotify: https://open.spotify.com/show/3cFpLXfYvcUsxvsT9MwyAD?si=f5a14e779777487d Apple Podcasts: https://podcasts.apple.com/ca/podcast/liftoff-with-keith-newman/id1560219589 Substack: https://keithnewman.substack.com/ Newman Media Studios: https://newmanmediastudios.com/ LinkedIn: https://www.linkedin.com/company/liftoffwithkeith For sponsorship inquiries, please contact: sponsorships@wherewithstudio.comFrom the Host:A Special Shout out to our Great Host of the Ignite Studios: https://www.ignitegtm.com/ and Producers of AI Infra5 @ Plug and Play World HQ in Sunnyvale, CALiftoff is Sponsored by - Strategic Consulting firm and the M&A specialists at Compass Strategic Advisors - https://www.compass-strategic-advisors.com/ and The GTM Firm - https://www.thegtmfirm.com/ #AIinfrastructureexpansion #Digitalinfrastructuretrends #Datacentergrowth #Powerandenergyconstraints #Waterstewardship #Skilledlaborshortages #Communitypushback #Digitalsovereignty #dgecomputingandAIinference #PrivateAImodels #Largescaleinfrastructureconstruction

An airhacks.fm conversation with Arun Gupta (@arungupta) about: learning Basic, Pascal, COBOL and C in college, early Java applets connecting to databases via JDBC, joining Sun Microsystems in March 1999 as an RMI/CORBA test engineer, the Portable Object Adapter and IIOP wire protocol, RMI-IIOP for language interoperability, J2EE 1.2 alpha release, JAX-B and JAX-RS testing, J2EE technologies migrating into Java SE, GlassFish as the open-source reference implementation, growing GlassFish downloads from zero to five million in three years, OSGi modularization in GlassFish V3, single-jar Java EE deployment, the Sun Grid early cloud attempt, the Sun Cloud REST API designed by Tim Bray, Red Hat JBoss technical marketing, recording an early docker screencast at Red Hat, Couchbase and the move to Amazon, principal open source technologist role, making Amazon join CNCF, launching Amazon Corretto with James Gosling at Devoxx Belgium 2019, the corretto name meaning coffee with liquor, Apple Open Source Program Office and the internal Apple openJDK fork used across Apple Music and Siri, Intel VP of Open Ecosystem, joining JetBrains as VP of Developer Experience, the book Fostering Open Source Culture, MineCraft Modding with Forge co-authored with his son who keynoted JavaOne at age 10, Devoxx4Kids in the US with over 200 workshops and 5000 kids taught, the not-invented-here syndrome, the conference program committee bias toward new topics, normative JSR specifications using must, shall and must not as a basis for LLM code generation, TCK and reference implementation model, Quarkus modernization of legacy J2EE applications, AGENTS.md and skill files on top of coding agents, running and weight training for mindfulness. Arun Gupta on twitter: @arungupta

This week Nick talks to Scott Lane Scott is the Founder and CEO of Speeki and serves as its Principal Auditor. He brings more than 25 years of experience in governance, compliance, and ESG risk, having built and scaled international businesses focused on helping organisations strengthen risk management and stakeholder trust.  After working for Sun Microsystems and Hitachi, Scott founded The Red Flag Group in 2006, where he served as CEO and Chairman. Under Scott's leadership, the company became a globally recognised expert in risk and compliance, advising many of the world's largest organisations. Scott exited the business in 2020 when The Red Flag Group became part of London Stock Exchange Group following its acquisition by Refinitiv. Nick and Scott discuss how audit and assurance capabilities have expanded from governance and compliance into broader ESG and sustainability reporting. They explore the growing need for independent verification of ESG claims, alongside the evolving global debate around ESG regulation, reporting, and governance standards. Book Choice Good To Great by Jim CollinsMusic ChoiceBruno Mars, FKA twigs, Nine Inch Nails, BIGBANG, Karol G & David GuettaThis content is issued by Zeus Capital Limited (“Zeus”) (Incorporated in England & Wales No. 4417845), which is authorised and regulated in the United Kingdom by the Financial Conduct Authority (“FCA”) for designated investment business, (Reg No. 224621) and is a member firm of the London Stock Exchange. This content is for information purposes only and neither the information contained, nor the opinions expressed within, constitute or are to be construed as an offer or a solicitation of an offer to buy or sell the securities or other instruments mentioned in it. Zeus shall not be liable for any direct or indirect damages, including lost profits arising in any way from the information contained in this material. This material is for the use of intended recipients only.

(0:00) Intro (1:47) About the podcast sponsor: The American College of Governance Counsel (2:34) Start of interview  (4:12) Laurie's origin story (6:19) From Management Consulting (Accenture) to Product Innovation (Visa). "What they all had in common was that I got to start with a blank sheet of paper." (8:52) Toward Venture Capital and Board Governance. From Sun Microsystems to Packet Design to investing. (13:07) How she got interested in board governance. Her first board experience with Interactive Investor (cross-listed in US and UK) (14:27) Joining Playground Global in 2019 (16:16) Tesla's Day-Zero Board (20:15) Zoox and Autonomous Ambition (24:11) Boards Across Company Types: VC-backed companies and family businesses. Example of her time as board member at Bose. (27:57) Lessons from Church and Dwight. The roles of M&A and marketing. (30:37) Her co-authored paper on The Artificially Intelligent Boardroom (Stanford GSB)  (35:30) Private Markets and Trillion-Dollar Valuations (40:28) The role of private equity in this environment, and its distinctive board structure. (42:55) Geopolitics and Supply Chains (47:20) Cybersecurity Oversight in the AI Age (50:45) Courage in the Boardroom. “As board members, we have to be courageous enough to ask the right questions at the right time, rather than sit back and hope everything will be okay.” (52:22) Books that have greatly influenced her life: Night Train to Lisbon, by Pascal Mercier (2004) The Immortal Life of Henrietta Lacks, by Rebecca Skloot (2010) Sapiens: A Brief History of Mankind, by Yuval Noah Harari (2011) (54:14) Her mentors: Heidi Roizen  Scott McNealy Peggy Johnson (56:49) Quotes that she thinks of often or lives her life by. "It is easy enough to be pleasant, when life flows by like a song, but the man worth while is one who will smile, when everything goes dead wrong." Ella Wheeler Wilcox (57:32) An unusual habit or an absurd thing that she loves. Dancing, after following research from Kelly McGonigal. Hummingbird feeders. (59:39) The living person she most admires: her husband, Ben Lenail. Laurie Yoler is a venture capital investor at Playground Global, former board member at Tesla and Zoox, and a director or advisor to more than 25 boards. She currently serves on the boards of Church & Dwight and the NACD Northern California Chapter. You can follow Evan on social media at:X: @evanepsteinLinkedIn: https://www.linkedin.com/in/epsteinevan/ Substack: https://evanepstein.substack.com/__To support this podcast you can join as a subscriber of the Boardroom Governance Newsletter at https://evanepstein.substack.com/__Music/Soundtrack (found via Free Music Archive): Seeing The Future by Dexter Britain is licensed under a Attribution-Noncommercial-Share Alike 3.0 United States License

Dive into a special episode with Dato' Dr. Sean SEAH, a serial tech entrepreneur, satellite innovator, and global technology leader, as he shares insights on digital transformation, space technology, entrepreneurship, and leadership for the future of Malaysia and beyond.With experience spanning Silicon Valley companies such as Sun Microsystems and Netscape, Dato' Dr. Sean SEAH has played a key role in advancing Malaysia's digital and space ambitions. As the founder of Angkasa-X and Chairman of WITSA, he is passionate about using technology to create social inclusion, connect underserved communities, and inspire future generations to dream boldly and innovate fearlessly.

In this episode of the Digital Rapport® Podcast, I share the personal story behind why I chose to help coaches grow their businesses instead of becoming a coach myself.After starting my career in the corporate world with companies like Tetley Tea and Sun Microsystems, my passion for personal development led me into the worlds of NLP, hypnosis, emotional intelligence, and life coaching. But one powerful conversation changed the direction of my career forever.I realised that many talented coaches struggled not because they lacked skill or passion, but because they lacked the marketing systems, technology, and business infrastructure needed to grow successfully online.That insight led me to combine my background in IT and technology with my passion for personal development — helping coaches, consultants, authors, and experts build scalable online businesses through funnels, automation, email marketing, and digital strategy.In this episode, I talk about:• How I got started in the coaching industry• The moment that changed my perspective on coaching• Learning from mentors like Janet Schweitzer and Ron Holland• The early days of online funnels and email marketing• Why technology overwhelms many coaches• Building systems that help experts scale online• Merging passion, business, and technology into one missionIf you're a coach, consultant, entrepreneur, or expert trying to grow your business online, this episode offers valuable insights into the strategy and systems that support long-term growth.#CoachingBusiness #DigitalMarketing #PersonalDevelopment #OnlineBusiness #Funnels #MarketingAutomationhttps://www.digitalrapportpodcast.com

Vinod Khosla on Why AI Could End Human Labor and Change Capitalism ForeverVinod Khosla joins Newcomer to discuss AI, capitalism, freedom, education, religion, and why he believes technology will fundamentally reshape how humans live and work.The legendary venture capitalist behind Sun Microsystems and early bets on OpenAI shares his thoughts on why AI could eliminate the need for traditional jobs, how capitalism may evolve in an AI-driven world, and why future generations may no longer need careers purely for survival.He also discusses Silicon Valley's biggest blind spots, the future of education and creativity, human purpose after AI, why institutions are failing to adapt, and what comes next for entrepreneurship and innovation.Vinod also explains why he thinks most people underestimate the speed of AI progress, and what happens when intelligence becomes effectively unlimited.Subscribe for more conversations with the people shaping technology, media, startups, and culture.

▶️ Connect with Richard on LinkedIn: https://www.linkedin.com/in/richardatherton-firsthuman/   Have you ever thought that the hardest things you've faced might actually be preparing you for the life you're meant to live? In this episode of Being Human, Richard Atherton talks with Ali Mahlodji, CEO of futureOne, keynote speaker, five-time author, and guest lecturer at the University of Cambridge. As a toddler, Ali found himself in a refugee camp in Austria. At 13 he started stuttering and didn't stop until he was 22. He left school early, worked more than 40 jobs ranging from floor cleaner to carpenter, and taught himself software engineering using library books. After 70 application letters to OG Silicon Valley giant, Sun Microsystems, Ali lands himself his first tech role.  What made the difference for him was something his mother did every day, no matter how tough things got: she told him she loved him just as he was. Not for his grades or achievements, but simply for being himself. Now, through futureOne's Heroes programme, he helps people in 40 countries break free from old patterns. In this conversation, he shares why, with AI on the rise, doing this inner work is more important than ever.   We discuss: Escaping Iran aged 2 Dealing with his father's mental breakdown Getting his break in Tech Building a start-up and exiting Recovering from burnout and building futureOne Links:  Ali's Website futureOne

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubIan F. Darwin - Java, Android & Unix Developer, Trainer, Mentor & Author of "Java Cookbook"Jeanne Boyarsky - Oracle Java Champion, Co-Author of "Real-World Java" & "OCP 21 Java Cert Book"Check out more here:https://gotopia.tech/episodes/438RESOURCESIanhttps://fosstodon.org/@IanDarwinhttps://x.com/Ian_Darwinhttps://github.com/IanDarwinhttps://www.linkedin.com/in/idarwinhttps://www.darwinsys.comJeannehttps://bsky.app/profile/jeanneboyarsky.bsky.socialhttps://mastodon.social/@jeanneboyarskyhttps://x.com/jeanneboyarskyhttps://github.com/boyarskyhttps://www.linkedin.com/in/jeanne-boyarskyhttps://sites.google.com/view/jeanneboyarskyhttps://www.selikoff.netLinkshttps://javacookbook.orghttps://dev.java/community/jcsDESCRIPTIONIn this GOTO Book Club, Java Champion Jeanne Boyarsky interviews Ian F. Darwin — author of one of Java's most enduring reference books, Java Cookbook, now in its fifth edition covering up to Java 25. The conversation traces Ian's extraordinary journey: from writing Java's first commercial training course outside of Sun Microsystems, to meeting Tim O'Reilly at a Unix conference and handing him a chapter on lint, to delivering a class in Houston where the entire room had just been laid off and were using the course as their golden handshake into a new career. Ian talks about the philosophy behind the book — culling a peak 900-page beast down to a tight 600 pages, anchoring tool choices on proven, battle-tested picks like JUnit, Mockito, and logging — and shares his three favourite chapters: Regular Expressions, Object-Oriented Techniques, and Reflection.The conversation gets sharply honest about AI and the future of the industry. Ian — who uses Claude as his coding assistant and does vibe code — warns that his greatest fear isn't AI taking over the world, but something subtler and more dangerous: companies stopping junior hires because AI can do the work, leaving no one to grow into the deep expertise that retires with the current generation. The parallel risk for books is equally candid: AI was trained on older editions, so the fifth edition is genuinely new and un-scraped territory.His advice for anyone who has learned the basics of Java?Don't ask an AI — buy the cookbook, save yourself years of trial and error, and for goodness' sake, read the code before you deploy it. "It's like building an airplane and putting passengers on it without flight testing."RECOMMENDED BOOKSIan F. Darwin • Java Cookbook 5th ed. • https://amzn.to/3QH0NZyIan F. Darwin • Java Cookbook 1st ed. • https://amzn.to/4sUpPlLIan F. Darwin • Checking C Programs with Lint • https://amzn.to/3Q2C69YVictor Grazi & Jeanne Boyarsky • Real-World Java • https://amzn.to/4oCEeBRJeanne Boyarsky & Scott Selikoff • OCP 21 Java Cert Book • https://amzn.to/4lF8OICBlueskyInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

These episodes of #thePOZcast, live from Transform 2026 in Las Vegas, are proudly brought to you by our friends at Overalls What if your employees had one central hub to handle real life? Meet Overalls. A smarter way to support your team, combining expert human LifeConcierges™ with AI to solve everyday challenges across healthcare, caregiving, benefits, insurance, finances, life admin, and more. From start to finish, Overalls handles the details — using existing benefits where they fit, and filling in the gaps where they don't. So employees save time, reduce stress, and stay focused at work, while employers boost engagement and get more value from their benefits. Overalls is redefining how work supports life, helping employee teams from Reddit, Patreon, BeatBox, and more cross pesky to-dos off their lists every day. Learn more at https://getoveralls.com/?utm_source=podcast&utm_medium=podcast&utm_campaign=pozcast Thanks for listening, and please follow us on Insta @NHPTalent and www.youtube.com/thePOZcast For all episodes, please check out www.thePOZcast.com About:  Nancy Hauge , Chief People Experience Officer  Nancy oversees all "people" functions worldwide at Automation Anywhere, including talent acquisition, communication, total rewards, learning and development, engagement, DEI, and Social Impact. She brings more than 30 years of experience in senior leadership and management consulting roles. Prior to joining Automation Anywhere, she was the chief people officer at HotChalk, where she was responsible for all people functions, legal, and facilities. Before that, Nancy served as the SVP of global human resources and facilities at Silicon Image through its 2015 acquisition, and as SVP of human resources for K12 Inc. (STRIDE) through its 2007 IPO. She also has executive experience at Ruckus Network, Noah's New York Bagels, Gymboree Corporation and Sun Microsystems.  She was recognized by HRO Today as CHRO of the Year 2023, for Innovation.  Additional recognition includes being named by HR Leadership as one of the Top 100 HR Tech Influencers for 2021, by HRO Today as a Leader of Distinction in North America in 2019. She is also a recipient of the "Stevie Awards" for women in high tech and was named by the Silicon Valley Business Journal as one of the "100 Women of Influence" in Silicon Valley both in 2015. Nancy has served on the Board of Regents for Holy Names College and the Board of Advisors to The Cameron School of Business at The University of North Carolina, Wilmington.  What you didn't know: Nancy started her career in comedy. Writing and performing. Of course, Nancy admits that she is lucky she wasn't very good at that or she would not be here today. Key Takeaways: 1. People Are the Most Unpredictable — and That's the Point Nancy's reason for still loving HR after 45 years: no two days are ever the same, because people will always surprise you. That unpredictability isn't a bug in the people function — it's what makes it the most creative, human-centered role in any organization. 2. AI Agents Should Do the Work Humans Shouldn't Have to Do The real promise of AI in HR isn't efficiency for its own sake — it's freeing humans to do what humans are actually best at. Reviewing resumes, scheduling interviews, and answering repetitive benefit questions should be automated. Creativity, judgment, and connection should not. 3. The Referral Agent Changes How Jobs Get Designed Automation Anywhere's referral agent is a glimpse at the future of workforce planning: as a new job description is written, AI maps it to existing tools in the catalog and recommends what else needs to be built. Jobs are no longer just roles — they're a design challenge. 4. The Future of Benefits Is Bespoke, Not Bulk Volume-purchased, one-size-fits-many benefits packages are a legacy model. Millennials and Gen Z expect benefits that match their actual life — their family structure, their life stage, their specific needs. Companies that don't move toward personalization will lose the talent war to those that do. 5. Benefits Are How You Reach Into the Family Nancy's reframe: benefits aren't just a compensation component — they're the one place a company can make an employee's family a partner in retention. When a company helps with a night nurse, fertility support, or postpartum care, the family notices. And families influence career decisions. 6. The Night Nurse Benefit Generated the Most Emotional Response of Nancy's Career Of all the benefits Nancy has implemented across 45 years, a night nurse support service for new parents produced the most extraordinary emotional response she has ever received from employees. It's a reminder that the highest-impact benefits often aren't the most expensive — they're the most human. 7. AI Agents Can Surface Benefits at the Exact Moment They're Needed The awareness and adoption problem in benefits is real: employees don't think about benefits until they need them. AI agents that detect life changes — a new dependent added to insurance, a leave request filed — and proactively surface relevant benefits solve this problem at scale, without requiring HR to monitor or manage it manually. 8. People Share More With Agents Than With HR — and That's a Feature Employees are more willing to disclose sensitive, personal information to an AI agent than to a human HR representative, because there's no fear of judgment or career consequences. That confidentiality drives benefit utilization and gives companies a more accurate picture of what employees actually need. 9. Great Alumni Are Part of the Benefits ROI Nancy's two-vector framework for benefits ROI — retention and human wellness — includes something most people skip: the alumni experience. The goal isn't just to keep employees as long as possible. It's to make them feel so well-cared-for that when they leave, they become ambassadors. That has real, lasting value. CHAPTERS: 00:00 – Introduction: Adam welcomes Nancy Hauge — whose favorite color is puce — and sets up a conversation with one of the most experienced people leaders in the series. 02:00 – Meet Nancy & Automation Anywhere Nancy introduces herself as Chief People Experience Officer and describes Automation Anywhere's AI agent platform — built to help enterprises manage agentic solutions across their entire tech stack. 04:00 – Why 45 Years in HR Never Gets Old Nancy's answer to what keeps her energized after four-plus decades: people are the least predictable thing in the world, which makes HR the most creative function in any business. 06:30 – The Greatest Innovation in HR Tech Nancy's take on the biggest recent leap: AI agents that remove human bias from processes, hand repetitive work back to machines, and free people to do what they're actually best at — creativity and problem solving. 09:00 – The Referral Agent: AI Redesigning Job Descriptions A specific innovation at Automation Anywhere: an AI agent that, as a job description is written, maps it to existing agents in the catalog and recommends new ones to build — fundamentally changing how work gets designed. 12:00 – The Future of Benefits Is Bespoke Nancy's bold prediction: one-size-fits-many benefits are on the way out. The next generation of workers — Millennials and Gen Z — expect à la carte, concierge-level solutions tailored to their life and their family, not volume-purchased packages. 15:00 – Benefits Reach Into the Family A reframe that changes how you think about total rewards: benefits are the one place a company can reach into an employee's family and make them partners in retention. That's a responsibility — and an opportunity. 17:30 – The Night Nurse Benefit The benefit that generated the most emotional response Nancy has ever seen in her career — a post-birth night nurse support service — and why the reaction from employees was extraordinary. 21:00 – AI Agents Driving Benefits Awareness How Automation Anywhere uses AI agents to proactively surface the right benefits at the right moment — detecting life changes like a new baby on insurance and prompting employees with relevant support before they even think to ask. 24:00 – Confidentiality & the Trust Factor Why employees are more likely to share vulnerable, personal information with an AI agent than with HR — no judgment, no performance review implications, no office gossip. And why does that drive benefit utilization? 26:30 – Justifying Benefits ROI on Two Vectors Nancy's framework: retention is one vector, human wellness and happiness is the other. And the goal isn't just keeping people — it's creating great alumni who leave saying the company genuinely cared about them. 29:00 – The 5-Year Century Nancy previews her upcoming book, co-authored with Automation Anywhere's CEO, publishing May 19th via Wiley — about how rapidly everything is changing and how AI agents are going to help humanity tackle its biggest challenges.

In this episode of The People Dividend Podcast, host Mike Horne welcomes global leadership expert Mitchell Levy. They explore the themes of credibility, thought leadership, and executive abundance. Mitchell shares insights from his career, including his journey from Sun Microsystems to becoming an entrepreneur and thought leader. The conversation delves into the importance of clarity, credibility, and the concept of executive abundance, which focuses on bringing value to five stakeholder groups. Mitchell also discusses his upcoming book and the significance of understanding one's purpose and executing it with integrity and commitment.   Key Points: Mitchell Levy emphasizes the importance of credibility, defining it as being trusted, known, and liked, with integrity being a core value. The concept of executive abundance is introduced, focusing on bringing value to five stakeholder groups, including family, employees, customers, investors, and the community. Clarity is highlighted as a crucial element for both personal and professional success, serving as a compass for decision-making. Mitchell shares his journey from working at Sun Microsystems to becoming an entrepreneur, illustrating the rewards and challenges of pursuing one's passion. The discussion underscores the significance of understanding and executing one's purpose with integrity and commitment to achieve true fulfillment.   Links:  Learn more about Mike Horne on Linkedin Email Mike at mike@mike-horne.com Learn More About Executive and Organization Development with Mike Horne Twitter: https://twitter.com/mikehorneauthor  Instagram: https://www.instagram.com/mikehorneauthor/,  LinkedIn Mike's Newsletter: https://www.linkedin.com/newsletters/6867258581922799617/,  Schedule a Discovery Call with Mike: https://calendly.com/mikehorne/15-minute-discovery-call-with-mike     Learn More about Mitchell Levy: mitchellevy.com  Mitchell Levy's TEDx Talk: https://www.youtube.com/watch?v=Ge2zZhk766o  #peopledividendpodcast #podcastepisode #podcastrecommendations #Leadership #Credibility #ExecutiveAbundance #ThoughtLeadership #PersonalGrowth

This week, we interviewed Kristin Russell. Kristin is the CEO of CBTS and a member of its Board of Directors. Kristin shapes and drives the organization's strategic direction. A dynamic visionary, she is guiding CBTS's evolution from a traditional infrastructure and managed services firm into a market leader in AI-enabled digital transformation solutions. Kristin is a seasoned industry veteran with over 20 years of experience driving transformative growth at leading technology companies. Prior to joining CBTS, she served as the President of Arrow Electronics' Global Enterprise Computing Solutions (ECS) division.  Before joining Arrow, Kristin held key leadership roles at Deloitte Consulting, Oracle, and Sun Microsystems. She also served as the Secretary of Technology and Chief Information Officer for the State of Colorado. Kristin's leadership has earned her numerous industry accolades, including recognition on CRN's 'Top 100 Channel Leaders', the GTDC Innovator Award, Women We Admire's '100 Women in Technology', and CIO of the Year by the Denver Business Journal. Kristin excels at building strong, collaborative teams and fostering cultures grounded in accountability, innovation, and high performance.  A sought-after expert and engaging speaker, she has been featured in several publications, books, and events. A lifelong learner and tech enthusiast, Kristin thrives on helping others achieve their full potential. Outside of work, Kristin enjoys cooking, traveling, and spending time with her family. She holds a bachelor's degree in International Affairs from the University of Colorado.  

Seja membro deste canal e ganhe benefícios:https://www.youtube.com/channel/UCdmGjywrxeOPfC7vDllmSgQ/joinO programa de hoje destaca o suposto iPhone dobrável de US$ 2.000, a aliança bilionária entre Intel e Musk para chips de robótica e o erro de privacidade do Google Gemini. Veja também as ofertas do dia, de Soundbar Samsung a monitores gamer, e as recomendações de leitura e cinema.

A version of this essay has been published by firstpost.com at https://www.firstpost.com/opinion/shadow-warrior-drones-are-the-new-tanks-time-for-india-to-catch-up-13998019.htmlThe most important lesson (of many) from Gulf War 3 may have been foreshadowed by the Ukraine War and other conflicts: that a combination of a step-change in warfare (military strategy) and disruptive innovation (business strategy) could rewrite the rules. If so, we may need to rethink the value of much expensive hardware. Moreover, nations such as India may need to seriously revamp their arms procurement: to small, cheap, local maybe?The most disturbing aspect of this scenario is that it reduces the human factor, and human control, over warfare. It leads to the specter of robot warfare, of Skynet, of 2001: A Space Odyssey, where autonomous intelligences may take rational decisions that have grave consequences for humans, inflicting collateral damage on innocent bystanders in ways that nobody quite understands. We need a real-life version of Isaac Asimov's “Three Laws of Robotics”. But then humans too inflict unthinking collateral damage..Step-change in warfare, and disruptive innovationThere have been numerous instances where a settled and standardized war tactic was suddenly overturned by a new invention, rendering old military assets impotent. One or two examples will suffice: one was the eclipse of heavy cavalry after the invention of massed archers using longbow volleys to mow them down with thousands of synchronized arrows raining down, also inducing panic in their horses in mid-charge.Another example is how battle tanks overwhelmed the previous model of trench warfare. (Ironically, in turn, tanks are now being rendered sitting ducks by drones.)In both cases, long-held assumptions had to be rewritten practically overnight, and entirely new mechanisms had to be put in place. It is a good question (on which reasonable people may differ) as to whether the arrival of drone-and-missile-based warfare is rendering air power, including fighters, bombers and aircraft carriers, essentially obsolescent.Clayton Christensen articulated the theory of disruptive innovation in business, where an entrenched incumbent can be overthrown in short order by an insurgent attacking them from an unexpected direction, often based on lower-cost options. One example is that of Kodak and the film-camera business. Cheap and convenient digital photography dislocated Kodak et al practically overnight.I personally experienced this disruption in the 1990s when I had a key role in operating system strategy for Sun Microsystems, the runaway leader in engineering workstations and servers, which used the Unix operating system. Despite our best efforts, Microsoft+Intel coming in from the low end (as Windows systems became more capable) rapidly captured the key resource, which is third-party software vendors. This caused end users to desert in droves.There were other reasons, too: internecine warfare among firms using Unix, such as IBM, HP, Sun, AT&T, Toshiba, et al. While they bickered, Windows systems became more powerful. Lesson: the ecosystem has to be managed carefully, including supply chains.Putting these three together (step-change, disruptive innovation, and the ground realities of the Gulf War 3) one can speculate that future military doctrine will be vastly different. Here is Iran's military doctrine, for reference, from the substack NotesonGeopolitics (Disclaimer: I am neither endorsing it or criticizing it, just offering it as an example).The US is adjusting to this reality. There is a book titled “Project Maven”, based on 200+ interviews chronicling the US military's shift to AI-driven warfare, starting with a 2017 Pentagon project to automate drone footage analysis amid overwhelming data volumes.Project Maven evolved from error-prone early tools (such as misidentifying school buses as threats) to supporting autonomous systems like Goalkeeper drones and Whiplash naval units, now used in conflicts from Ukraine to the Caribbean by 25,000 personnel across 32 companies.Speaking of disruptive innovation, it is ironic to see the US reverse-engineering Iranian Shahed drones, and the Russians doing the same to Ukrainian drones: incumbents learning from insurgents.This is only the beginning, of course. There is a nightmare scenario: murmurating, autonomous drone swarms with a hive mind. A flock of starlings flying in perfect synchrony is a thing of beauty: they do not collide with each other, the entire swarm changes direction instantaneously, and there is emergent intelligence in the swarm, much greater than the intelligence of the individual bird. The same is true of beehives and ant colonies, too.A company called ShieldAI in fact has a product named Hivemind that does precisely this.Imagine a murmurating drone swarm of 1,000 or even 10,000: and since they cost so little make, this is not unrealistic. The enemy may shoot down 90% of them, but the 10% that gets through, especially if they are kamikaze drones fitted with explosives, can cause real damage. There is the old joke about quantity: “What do you do when you invade China? First day, you take 10,000 prisoners. Second day, you take 100,000 prisoners. Third day, you surrender!”But we don't have to go that far: just take two instances where inexpensive drones were able to penetrate the defenses of heavily secured military airports. The first was in Russia in June 2025. Using 117 low-cost drones, Ukrainians struck several airbases at once. There is video footage of FPV drones landing on Tu-95 bombers, destroying them. These are strategic long-range nuclear bombers from the Cold War era, and will be difficult to replace.And then, just last month: at Barksdale Air Force Base in the US, where B-52 nuclear bombers are deployed, there were repeated drone swarm overflights (of 12-15 drones) between March 9th and March 15th, 2026. They couldn't be jammed, and displayed “non-commercial signal characteristics”, although they did not actually attack the planes. Reconnaissance, it must be assumed. Superpower militaries are unable to contain them.Electronic warfare like jamming may be ineffective anyway as swarms self-repair. But it is true that there are air defense weapons that can shoot down the majority of drones. There are interceptors (but they are much more expensive than the drones themselves). Then new Directed Energy Weapons (including both lasers and high-powered microwaves) are in development. Rail guns, I understand, are overkill for them.Where is India in this arms race?India finds itself left behind in this transition, and remains committed to legacy platforms such as tanks, fighters, and other imported systems. It is true that there were battlefield successes in Operation Sindoor, where X-25 drones (towed on a 100 meter optical cable) emitted the radar signatures of Rafale fighter jets, thus drawing enemy missiles to themselves, without harming the planes. But these were Israeli products; also British-origin Banshee drones were used for spoofing Su-31 and Mig-29 signatures..Indigenous drone efforts lag China by 3-5 years in scale, AI integration, and mass production; reliance on Chinese components persists despite bans. It does not have to be this way: India should create Production Linked Incentives for drones and missiles, and harness Machine Learning and Artificial Intelligence at scale.India needs to promote this as a cottage industry, so that many individuals will get involved, as in the following post by a Ukrainian drone-maker, with a hashtag #MadebyHousewives. That country produces as many as 4.5 million cheap drones a year, often using 3d printing.While Ukraine and Iran improvise hive-mind swarms under fire, India's northeast and border regions face asymmetric threats from low-cost systems. The recent mercenary scandal in the Northeast illustrates the peril. Mercenaries, the Northeast and a new Christian enclave?The March 2026 arrests by India's National Investigation Agency (NIA) expose how this drone proliferation directly endangers the Seven Sisters. Six Ukrainians and American mercenary Matthew Aaron Van Dyke were detained across Indian airports. They had repeatedly crossed from restricted Mizoram into Myanmar since 2024, training ethnic insurgent groups in drone assembly, operation, jamming, and electronic warfare.They smuggled European drone consignments through India for insurgent networks, some linked to proscribed Indian groups operating in the northeast. This is no abstract threat: drones enable precision strikes on security forces, surveillance of remote terrain, and supply drops. These capabilities could ignite or sustain insurgencies in India's volatile borderlands.In the background is former Bangladesh Prime Minister Sheikh Hasina's explosive 2024 warning. Hasina alleged a “white man's” conspiracy to carve out a new “Christian nation” (akin to East Timor or South Sudan) from Bangladesh's Chittagong Hill Tracts, Myanmar's Rakhine and Chin regions, and India's Northeast. She cited foreign eyes on the Bay of Bengal and ethnic fault lines.Hasina's claim was dismissed as paranoia then; today, Ukrainian-American actors arming Myanmar's rebel groups lend credence to a broader destabilization playbook. A hive-mind-enabled drone campaign could empower separatists and create a Christian-majority enclave, exploiting Christian tribal demographics and porous borders. This is hybrid warfare at its most insidious: mercenaries as force multipliers for great-power proxies.If these insurgents can leverage drone swarms to close the Siliguri Corridor or target regional infrastructure, they can create a fait accompli on the ground for India.ConclusionThe drone-missile age demands urgent adaptation. Nations must invest in AI swarm doctrine, resilient EW, decentralized deployment, and indigenous mass production ecosystems. For India, the wake-up call is clear: clinging to legacy investments while insurgents import hive-mind precursors risks not just military irrelevance but territorial integrity. The Tu-95 pyres and B-52 overflights are warnings. The northeast drone pipeline is a direct threat. Warfare has changed; those who fail to swarm will be overrun.Here is the AI-generated audio podcast about this essay:1570 words, Apr 3, 2026 This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit rajeevsrinivasan.substack.com/subscribe

An airhacks.fm conversation with Daniel Terhorst-North (@tastapod.com) about: first computer experience with the ZX81 and its 1K memory, the 1K chess game on ZX81, the ZX Spectrum with 16K and later 48K memory, the Amstrad 128K, typing in game listings from computer magazines, Dan's brother John hacking ZX spectrum games using a hardware freeze device and memory peeking/poking, cracking game encryption and copy protection on 8-bit tape cassette games, the arms race between game publishers and hackers, cracking the Star Wars game security before its release, ZX Spectrum fan sites and retro gaming communities, classic games including 3D Monster Maze and Manic Miner and Jet Set Willy, sprite graphics innovation on the Z80 chip, first internship at Domark publishing Empire Strikes Back on ZX Spectrum and Commodore 64, second internship at IBM Hursley Park working on CICS in PL/1 and Rexx, the contrast between casual game studio culture and IBM corporate culture in the 1980s, IBM's role as a founding partner of J2EE Enterprise Java, JMS wrapping MQ Series, the reliability of MQ Series compared to later messaging technologies, finding and reporting a concurrency bug in MQ Series with JUnit tests and IBM's rapid response with an emergency patch, IBM alphaWorks portal and experimental technologies, IBM Aglets mobile Java agent framework compared to modern A2A agent protocols, Jini and JavaSpaces from Sun Microsystems with leasing and self-healing, JXTA peer-to-peer technology, IBM Jikes Compiler performance compared to javac, IBM's own JVM, JVM running on Palm Pilot around 1999, VisualAge for Java as a port of VisualAge for SmallTalk with its image-based architecture and no file system exposure, Java's coupling of class and package names to files and directories as a design weakness, the difficulty of refactoring without IDE support, Eclipse as the first IDE with proper refactoring, NetBeans IDE performance compared to Visual Studio Code, third internship writing X-ray machine control software in Turbo Pascal doing digital image processing, the pace of technological innovation slowing from kaikaku (abrupt change) to kaizen (continuous improvement), Douglas Adams quote about technology perception by age, DEC Alpha 64-bit Unix performance, commodity Linux hardware replacing exotic RISC machines, Apple M series chips rediscovering RISC Architecture and system-on-chip design, innovation fatigue and signal-to-noise ratio in modern tech, LLMs and the trillion-dollar bet on the wrong technology, electric cars as an example of ongoing innovation, Tailwind CSS shutting down due to AI-generated code replacing paid expertise, Stack Overflow in trouble due to AI summarization, open source innovation continuing with tools like Astral's uv replacing the python toolchain, cross-community collaboration between rust and Python and Ruby ecosystems, first graduate job at Crossfield (Fuji/DuPont joint venture) doing electronic pre-press and color transformation through 4D CMYK color cubes, writing a TIFF decoder from scratch in C, Raster Image Processor technology and its connection to Adobe, transition from C++ to Java feeling quirky, joining ThoughtWorks in 2002 for enterprise Java work Daniel Terhorst-North on twitter: @tastapod.com

Bryan Cantrill is the co-founder and CTO of Oxide Computer Company. We discuss why the biggest cloud providers don't use off the shelf hardware, how scaling data centers at samsung's scale exposed problems with hard drive firmware, how the values of NodeJS are in conflict with robust systems, choosing Rust, and the benefits of Oxide Computer's rack scale approach. This is an extended version of an interview posted on Software Engineering Radio. Related links Oxide Computer Oxide and Friends Illumos Platform as a Reflection of Values RFD 26 bhyve CockroachDB Heterogeneous Computing with Raja Koduri Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Bryan Cantrill. He's the co-founder and CTO of Oxide computer company, and he was previously the CTO of Joyent and he also co-authored the DTrace Tracing framework while he was at Sun Microsystems. [00:00:14] Jeremy: Bryan, welcome to Software Engineering radio. [00:00:17] Bryan: Uh, awesome. Thanks for having me. It's great to be here. [00:00:20] Jeremy: You're the CTO of a company that makes computers. But I think before we get into that, a lot of people who built software, now that the actual computer is abstracted away, they're using AWS or they're using some kind of cloud service. So I thought we could start by talking about, data centers. [00:00:41] Jeremy: 'cause you were. Previously working at Joyent, and I believe you got bought by Samsung and you've previously talked about how you had to figure out, how do I run things at Samsung's scale. So how, how, how was your experience with that? What, what were the challenges there? Samsung scale and migrating off the cloud [00:01:01] Bryan: Yeah, I mean, so at Joyent, and so Joyent was a cloud computing pioneer. Uh, we competed with the likes of AWS and then later GCP and Azure. Uh, and we, I mean, we were operating at a scale, right? We had a bunch of machines, a bunch of dcs, but ultimately we know we were a VC backed company and, you know, a small company by the standards of, certainly by Samsung standards. [00:01:25] Bryan: And so when, when Samsung bought the company, I mean, the reason by the way that Samsung bought Joyent is Samsung's. Cloud Bill was, uh, let's just say it was extremely large. They were spending an enormous amount of money every year on, on the public cloud. And they realized that in order to secure their fate economically, they had to be running on their own infrastructure. [00:01:51] Bryan: It did not make sense. And there's not, was not really a product that Samsung could go buy that would give them that on-prem cloud. Uh, I mean in that, in that regard, like the state of the market was really no different. And so they went looking for a company, uh, and bought, bought Joyent. And when we were on the inside of Samsung. [00:02:11] Bryan: That we learned about Samsung scale. And Samsung loves to talk about Samsung scale. And I gotta tell you, it is more than just chest thumping. Like Samsung Scale really is, I mean, just the, the sheer, the number of devices, the number of customers, just this absolute size. they really wanted to take us out to, to levels of scale, certainly that we had not seen. [00:02:31] Bryan: The reason for buying Joyent was to be able to stand up on their own infrastructure so that we were gonna go buy, we did go buy a bunch of hardware. Problems with server hardware at scale [00:02:40] Bryan: And I remember just thinking, God, I hope Dell is somehow magically better. I hope the problems that we have seen in the small, we just. You know, I just remember hoping and hope is hope. It was of course, a terrible strategy and it was a terrible strategy here too. Uh, and the we that the problems that we saw at the large were, and when you scale out the problems that you see kind of once or twice, you now see all the time and they become absolutely debilitating. [00:03:12] Bryan: And we saw a whole series of really debilitating problems. I mean, many ways, like comically debilitating, uh, in terms of, of showing just how bad the state-of-the-art. Yes. And we had, I mean, it should be said, we had great software and great software expertise, um, and we were controlling our own system software. [00:03:35] Bryan: But even controlling your own system software, your own host OS, your own control plane, which is what we had at Joyent, ultimately, you're pretty limited. You go, I mean, you got the problems that you can obviously solve, the ones that are in your own software, but the problems that are beneath you, the, the problems that are in the hardware platform, the problems that are in the componentry beneath you become the problems that are in the firmware. IO latency due to hard drive firmware [00:04:00] Bryan: Those problems become unresolvable and they are deeply, deeply frustrating. Um, and we just saw a bunch of 'em again, they were. Comical in retrospect, and I'll give you like a, a couple of concrete examples just to give, give you an idea of what kinda what you're looking at. one of the, our data centers had really pathological IO latency. [00:04:23] Bryan: we had a very, uh, database heavy workload. And this was kind of right at the period where you were still deploying on rotating media on hard drives. So this is like, so. An all flash buy did not make economic sense when we did this in, in 2016. This probably, it'd be interesting to know like when was the, the kind of the last time that that actual hard drives made sense? [00:04:50] Bryan: 'cause I feel this was close to it. So we had a, a bunch of, of a pathological IO problems, but we had one data center in which the outliers were actually quite a bit worse and there was so much going on in that system. It took us a long time to figure out like why. And because when, when you, when you're io when you're seeing worse io I mean you're naturally, you wanna understand like what's the workload doing? [00:05:14] Bryan: You're trying to take a first principles approach. What's the workload doing? So this is a very intensive database workload to support the, the object storage system that we had built called Manta. And that the, the metadata tier was stored and uh, was we were using Postgres for that. And that was just getting absolutely slaughtered. [00:05:34] Bryan: Um, and ultimately very IO bound with these kind of pathological IO latencies. Uh, and as we, you know, trying to like peel away the layers to figure out what was going on. And I finally had this thing. So it's like, okay, we are seeing at the, at the device layer, at the at, at the disc layer, we are seeing pathological outliers in this data center that we're not seeing anywhere else. [00:06:00] Bryan: And that does not make any sense. And the thought occurred to me. I'm like, well, maybe we are. Do we have like different. Different rev of firmware on our HGST drives, HGST. Now part of WD Western Digital were the drives that we had everywhere. And, um, so maybe we had a different, maybe I had a firmware bug. [00:06:20] Bryan: I, this would not be the first time in my life at all that I would have a drive firmware issue. Uh, and I went to go pull the firmware, rev, and I'm like, Toshiba makes hard drives? So we had, I mean. I had no idea that Toshiba even made hard drives, let alone that they were our, they were in our data center. [00:06:38] Bryan: I'm like, what is this? And as it turns out, and this is, you know, part of the, the challenge when you don't have an integrated system, which not to pick on them, but Dell doesn't, and what Dell would routinely put just sub make substitutes, and they make substitutes that they, you know, it's kind of like you're going to like, I don't know, Instacart or whatever, and they're out of the thing that you want. [00:07:03] Bryan: So, you know, you're, someone makes a substitute and like sometimes that's okay, but it's really not okay in a data center. And you really want to develop and validate a, an end-to-end integrated system. And in this case, like Toshiba doesn't, I mean, Toshiba does make hard drives, but they are a, or the data they did, uh, they basically were, uh, not competitive and they were not competitive in part for the reasons that we were discovering. [00:07:29] Bryan: They had really serious firmware issues. So the, these were drives that would just simply stop a, a stop acknowledging any reads from the order of 2,700 milliseconds. Long time, 2.7 seconds. Um. And that was a, it was a drive firmware issue, but it was highlighted like a much deeper issue, which was the simple lack of control that we had over our own destiny. [00:07:53] Bryan: Um, and it's an, it's, it's an example among many where Dell is making a decision. That lowers the cost of what they are providing you marginally, but it is then giving you a system that they shouldn't have any confidence in because it's not one that they've actually designed and they leave it to the customer, the end user, to make these discoveries. [00:08:18] Bryan: And these things happen up and down the stack. And for every, for whether it's, and, and not just to pick on Dell because it's, it's true for HPE, it's true for super micro, uh, it's true for your switch vendors. It's, it's true for storage vendors where the, the, the, the one that is left actually integrating these things and trying to make the the whole thing work is the end user sitting in their data center. AWS / Google are not buying off the shelf hardware but you can't use it [00:08:42] Bryan: There's not a product that they can buy that gives them elastic infrastructure, a cloud in their own DC The, the product that you buy is the public cloud. Like when you go in the public cloud, you don't worry about the stuff because that it's, it's AWS's issue or it's GCP's issue. And they are the ones that get this to ground. [00:09:02] Bryan: And they, and this was kind of, you know, the eye-opening moment. Not a surprise. Uh, they are not Dell customers. They're not HPE customers. They're not super micro customers. They have designed their own machines. And to varying degrees, depending on which one you're looking at. But they've taken the clean sheet of paper and the frustration that we had kind of at Joyent and beginning to wonder and then Samsung and kind of wondering what was next, uh, is that, that what they built was not available for purchase in the data center. [00:09:35] Bryan: You could only rent it in the public cloud. And our big belief is that public cloud computing is a really important revolution in infrastructure. Doesn't feel like a different, a deep thought, but cloud computing is a really important revolution. It shouldn't only be available to rent. You should be able to actually buy it. [00:09:53] Bryan: And there are a bunch of reasons for doing that. Uh, one in the one we we saw at Samsung is economics, which I think is still the dominant reason where it just does not make sense to rent all of your compute in perpetuity. But there are other reasons too. There's security, there's risk management, there's latency. [00:10:07] Bryan: There are a bunch of reasons why one might wanna to own one's own infrastructure. But, uh, that was very much the, the, so the, the genesis for oxide was coming out of this very painful experience and a painful experience that, because, I mean, a long answer to your question about like what was it like to be at Samsung scale? [00:10:27] Bryan: Those are the kinds of things that we, I mean, in our other data centers, we didn't have Toshiba drives. We only had the HDSC drives, but it's only when you get to this larger scale that you begin to see some of these pathologies. But these pathologies then are really debilitating in terms of those who are trying to develop a service on top of them. [00:10:45] Bryan: So it was, it was very educational in, in that regard. And you're very grateful for the experience at Samsung in terms of opening our eyes to the challenge of running at that kind of scale. [00:10:57] Jeremy: Yeah, because I, I think as software engineers, a lot of times we, we treat the hardware as a, as a given where, [00:11:08] Bryan: Yeah. [00:11:08] Bryan: Yeah. There's software in chard drives [00:11:09] Jeremy: It sounds like in, in this case, I mean, maybe the issue is not so much that. Dell or HP as a company doesn't own every single piece that they're providing you, but rather the fact that they're swapping pieces in and out without advertising them, and then when it becomes a problem, they're not necessarily willing to, to deal with the, the consequences of that. [00:11:34] Bryan: They just don't know. I mean, I think they just genuinely don't know. I mean, I think that they, it's not like they're making a deliberate decision to kind of ship garbage. It's just that they are making, I mean, I think it's exactly what you said about like, not thinking about the hardware. It's like, what's a hard drive? [00:11:47] Bryan: Like what's it, I mean, it's a hard drive. It's got the same specs as this other hard drive and Intel. You know, it's a little bit cheaper, so why not? It's like, well, like there's some reasons why not, and one of the reasons why not is like, uh, even a hard drive, whether it's rotating media or, or flash, like that's not just hardware. [00:12:05] Bryan: There's software in there. And that the software's like not the same. I mean, there are components where it's like, there's actually, whether, you know, if, if you're looking at like a resistor or a capacitor or something like this Yeah. If you've got two, two parts that are within the same tolerance. Yeah. [00:12:19] Bryan: Like sure. Maybe, although even the EEs I think would be, would be, uh, objecting that a little bit. But the, the, the more complicated you get, and certainly once you get to the, the, the, the kind of the hardware that we think of like a, a, a microprocessor, a a network interface card, a a, a hard driver, an NVME drive. [00:12:38] Bryan: Those things are super complicated and there's a whole bunch of software inside of those things, the firmware, and that's the stuff that, that you can't, I mean, you say that software engineers don't think about that. It's like you, no one can really think about that because it's proprietary that's kinda welded shut and you've got this abstraction into it. [00:12:55] Bryan: But the, the way that thing operates is very core to how the thing in aggregate will behave. And I think that you, the, the kind of, the, the fundamental difference between Oxide's approach and the approach that you get at a Dell HP Supermicro, wherever, is really thinking holistically in terms of hardware and software together in a system that, that ultimately delivers cloud computing to a user. [00:13:22] Bryan: And there's a lot of software at many, many, many, many different layers. And it's very important to think about, about that software and that hardware holistically as a single system. [00:13:34] Jeremy: And during that time at Joyent, when you experienced some of these issues, was it more of a case of you didn't have enough servers experiencing this? So if it would happen, you might say like, well, this one's not working, so maybe we'll just replace the hardware. What, what was the thought process when you were working at that smaller scale and, and how did these issues affect you? UEFI / Baseboard Management Controller [00:13:58] Bryan: Yeah, at the smaller scale, you, uh, you see fewer of them, right? You just see it's like, okay, we, you know, what you might see is like, that's weird. We kinda saw this in one machine versus seeing it in a hundred or a thousand or 10,000. Um, so you just, you just see them, uh, less frequently as a result, they are less debilitating. [00:14:16] Bryan: Um, I, I think that it's, when you go to that larger scale, those things that become, that were unusual now become routine and they become debilitating. Um, so it, it really is in many regards a function of scale. Uh, and then I think it was also, you know, it was a little bit dispiriting that kind of the substrate we were building on really had not improved. [00:14:39] Bryan: Um, and if you look at, you know, the, if you buy a computer server, buy an x86 server. There is a very low layer of firmware, the BIOS, the basic input output system, the UEFI BIOS, and this is like an abstraction layer that has, has existed since the eighties and hasn't really meaningfully improved. Um, the, the kind of the transition to UEFI happened with, I mean, I, I ironically with Itanium, um, you know, two decades ago. [00:15:08] Bryan: but beyond that, like this low layer, this lowest layer of platform enablement software is really only impeding the operability of the system. Um, you look at the baseboard management controller, which is the kind of the computer within the computer, there is a, uh, there is an element in the machine that needs to handle environmentals, that needs to handle, uh, operate the fans and so on. [00:15:31] Bryan: Uh, and that traditionally has this, the space board management controller, and that architecturally just hasn't improved in the last two decades. And, you know, that's, it's a proprietary piece of silicon. Generally from a company that no one's ever heard of called a Speed, uh, which has to be, is written all on caps, so I guess it needs to be screamed. [00:15:50] Bryan: Um, a speed has a proprietary part that has a, there is a root password infamously there, is there, the root password is encoded effectively in silicon. So, uh, which is just, and for, um, anyone who kind of goes deep into these things, like, oh my God, are you kidding me? Um, when we first started oxide, the wifi password was a fraction of the a speed root password for the bmc. [00:16:16] Bryan: It's kinda like a little, little BMC humor. Um, but those things, it was just dispiriting that, that the, the state-of-the-art was still basically personal computers running in the data center. Um, and that's part of what, what was the motivation for doing something new? [00:16:32] Jeremy: And for the people using these systems, whether it's the baseboard management controller or it's the The BIOS or UF UEFI component, what are the actual problems that people are seeing seen? Security vulnerabilities and poor practices in the BMC [00:16:51] Bryan: Oh man, I, the, you are going to have like some fraction of your listeners, maybe a big fraction where like, yeah, like what are the problems? That's a good question. And then you're gonna have the people that actually deal with these things who are, did like their heads already hit the desk being like, what are the problems? [00:17:06] Bryan: Like what are the non problems? Like what, what works? Actually, that's like a shorter answer. Um, I mean, there are so many problems and a lot of it is just like, I mean, there are problems just architecturally these things are just so, I mean, and you could, they're the problems spread to the horizon, so you can kind of start wherever you want. [00:17:24] Bryan: But I mean, as like, as a really concrete example. Okay, so the, the BMCs that, that the computer within the computer that needs to be on its own network. So you now have like not one network, you got two networks that, and that network, by the way, it, that's the network that you're gonna log into to like reset the machine when it's otherwise unresponsive. [00:17:44] Bryan: So that going into the BMC, you can are, you're able to control the entire machine. Well it's like, alright, so now I've got a second net network that I need to manage. What is running on the BMC? Well, it's running some. Ancient, ancient version of Linux it that you got. It's like, well how do I, how do I patch that? [00:18:02] Bryan: How do I like manage the vulnerabilities with that? Because if someone is able to root your BMC, they control the system. So it's like, this is not you've, and now you've gotta go deal with all of the operational hair around that. How do you upgrade that system updating the BMC? I mean, it's like you've got this like second shadow bad infrastructure that you have to go manage. [00:18:23] Bryan: Generally not open source. There's something called open BMC, um, which, um, you people use to varying degrees, but you're generally stuck with the proprietary BMC, so you're generally stuck with, with iLO from HPE or iDRAC from Dell or, or, uh, the, uh, su super micros, BMC, that H-P-B-M-C, and you are, uh, it is just excruciating pain. [00:18:49] Bryan: Um, and that this is assuming that by the way, that everything is behaving correctly. The, the problem is that these things often don't behave correctly, and then the consequence of them not behaving correctly. It's really dire because it's at that lowest layer of the system. So, I mean, I'll give you a concrete example. [00:19:07] Bryan: a customer of theirs reported to me, so I won't disclose the vendor, but let's just say that a well-known vendor had an issue with their, their temperature sensors were broken. Um, and the thing would always read basically the wrong value. So it was the BMC that had to like, invent its own ki a different kind of thermal control loop. [00:19:28] Bryan: And it would index on the, on the, the, the, the actual inrush current. It would, they would look at that at the current that's going into the CPU to adjust the fan speed. That's a great example of something like that's a, that's an interesting idea. That doesn't work. 'cause that's actually not the temperature. [00:19:45] Bryan: So like that software would crank the fans whenever you had an inrush of current and this customer had a workload that would spike the current and by it, when it would spike the current, the, the, the fans would kick up and then they would slowly degrade over time. Well, this workload was spiking the current faster than the fans would degrade, but not fast enough to actually heat up the part. [00:20:08] Bryan: And ultimately over a very long time, in a very painful investigation, it's customer determined that like my fans are cranked in my data center for no reason. We're blowing cold air. And it's like that, this is on the order of like a hundred watts, a server of, of energy that you shouldn't be spending and like that ultimately what that go comes down to this kind of broken software hardware interface at the lowest layer that has real meaningful consequence, uh, in terms of hundreds of kilowatts, um, across a data center. So this stuff has, has very, very, very real consequence and it's such a shadowy world. Part of the reason that, that your listeners that have dealt with this, that our heads will hit the desk is because it is really aggravating to deal with problems with this layer. [00:21:01] Bryan: You, you feel powerless. You don't control or really see the software that's on them. It's generally proprietary. You are relying on your vendor. Your vendor is telling you that like, boy, I don't know. You're the only customer seeing this. I mean, the number of times I have heard that for, and I, I have pledged that we're, we're not gonna say that at oxide because it's such an unaskable thing to say like, you're the only customer saying this. [00:21:25] Bryan: It's like, it feels like, are you blaming me for my problem? Feels like you're blaming me for my problem? Um, and what you begin to realize is that to a degree, these folks are speaking their own truth because the, the folks that are running at real scale at Hyperscale, those folks aren't Dell, HP super micro customers. [00:21:46] Bryan: They're actually, they've done their own thing. So it's like, yeah, Dell's not seeing that problem, um, because they're not running at the same scale. Um, but when you do run, you only have to run at modest scale before these things just become. Overwhelming in terms of the, the headwind that they present to people that wanna deploy infrastructure. The problem is felt with just a few racks [00:22:05] Jeremy: Yeah, so maybe to help people get some perspective at, at what point do you think that people start noticing or start feeling these problems? Because I imagine that if you're just have a few racks or [00:22:22] Bryan: do you have a couple racks or the, or do you wonder or just wondering because No, no, no. I would think, I think anyone who deploys any number of servers, especially now, especially if your experience is only in the cloud, you're gonna be like, what the hell is this? I mean, just again, just to get this thing working at all. [00:22:39] Bryan: It is so it, it's so hairy and so congealed, right? It's not designed. Um, and it, it, it, it's accreted it and it's so obviously accreted that you are, I mean, nobody who is setting up a rack of servers is gonna think to themselves like, yes, this is the right way to go do it. This all makes sense because it's, it's just not, it, I, it feels like the kit, I mean, kit car's almost too generous because it implies that there's like a set of plans to work to in the end. [00:23:08] Bryan: Uh, I mean, it, it, it's a bag of bolts. It's a bunch of parts that you're putting together. And so even at the smallest scales, that stuff is painful. Just architecturally, it's painful at the small scale then, but at least you can get it working. I think the stuff that then becomes debilitating at larger scale are the things that are, are worse than just like, I can't, like this thing is a mess to get working. [00:23:31] Bryan: It's like the, the, the fan issue that, um, where you are now seeing this over, you know, hundreds of machines or thousands of machines. Um, so I, it is painful at more or less all levels of scale. There's, there is no level at which the, the, the pc, which is really what this is, this is a, the, the personal computer architecture from the 1980s and there is really no level of scale where that's the right unit. Running elastic infrastructure is the hardware but also, hypervisor, distributed database, api, etc [00:23:57] Bryan: I mean, where that's the right thing to go deploy, especially if what you are trying to run. Is elastic infrastructure, a cloud. Because the other thing is like we, we've kinda been talking a lot about that hardware layer. Like hardware is, is just the start. Like you actually gotta go put software on that and actually run that as elastic infrastructure. [00:24:16] Bryan: So you need a hypervisor. Yes. But you need a lot more than that. You, you need to actually, you, you need a distributed database, you need web endpoints. You need, you need a CLI, you need all the stuff that you need to actually go run an actual service of compute or networking or storage. I mean, and for, for compute, even for compute, there's a ton of work to be done. [00:24:39] Bryan: And compute is by far, I would say the simplest of the, of the three. When you look at like networks, network services, storage services, there's a whole bunch of stuff that you need to go build in terms of distributed systems to actually offer that as a cloud. So it, I mean, it is painful at more or less every LE level if you are trying to deploy cloud computing on. What's a control plane? [00:25:00] Jeremy: And for someone who doesn't have experience building or working with this type of infrastructure, when you talk about a control plane, what, what does that do in the context of this system? [00:25:16] Bryan: So control plane is the thing that is, that is everything between your API request and that infrastructure actually being acted upon. So you go say, Hey, I, I want a provision, a vm. Okay, great. We've got a whole bunch of things we're gonna provision with that. We're gonna provision a vm, we're gonna get some storage that's gonna go along with that, that's got a network storage service that's gonna come out of, uh, we've got a virtual network that we're gonna either create or attach to. [00:25:39] Bryan: We've got a, a whole bunch of things we need to go do for that. For all of these things, there are metadata components that need, we need to keep track of this thing that, beyond the actual infrastructure that we create. And then we need to go actually, like act on the actual compute elements, the hostos, what have you, the switches, what have you, and actually go. [00:25:56] Bryan: Create these underlying things and then connect them. And there's of course, the challenge of just getting that working is a big challenge. Um, but getting that working robustly, getting that working is, you know, when you go to provision of vm, um, the, all the, the, the steps that need to happen and what happens if one of those steps fails along the way? [00:26:17] Bryan: What happens if, you know, one thing we're very mindful of is these kind of, you get these long tails of like, why, you know, generally our VM provisioning happened within this time, but we get these long tails where it takes much longer. What's going on? What, where in this process are we, are we actually spending time? [00:26:33] Bryan: Uh, and there's a whole lot of complexity that you need to go deal with that. There's a lot of complexity that you need to go deal with this effectively, this workflow that's gonna go create these things and manage them. Um, we use a, a pattern that we call, that are called sagas, actually is a, is a database pattern from the eighties. [00:26:51] Bryan: Uh, Katie McCaffrey is a, is a database reCrcher who, who, uh, I, I think, uh, reintroduce the idea of, of sagas, um, in the last kind of decade. Um, and this is something that we picked up, um, and I've done a lot of really interesting things with, um, to allow for, to this kind of, these workflows to be, to be managed and done so robustly in a way that you can restart them and so on. [00:27:16] Bryan: Uh, and then you guys, you get this whole distributed system that can do all this. That whole distributed system, that itself needs to be reliable and available. So if you, you know, you need to be able to, what happens if you, if you pull a sled or if a sled fails, how does the system deal with that? [00:27:33] Bryan: How does the system deal with getting an another sled added to the system? Like how do you actually grow this distributed system? And then how do you update it? How do you actually go from one version to the next? And all of that has to happen across an air gap where this is gonna run as part of the computer. [00:27:49] Bryan: So there are, it, it is fractally complicated. There, there is a lot of complexity here in, in software, in the software system and all of that. We kind of, we call the control plane. Um, and it, this is the what exists at AWS at GCP, at Azure. When you are hitting an endpoint that's provisioning an EC2 instance for you. [00:28:10] Bryan: There is an AWS control plane that is, is doing all of this and has, uh, some of these similar aspects and certainly some of these similar challenges. Are vSphere / Proxmox / Hyper-V in the same category? [00:28:20] Jeremy: And for people who have run their own servers with something like say VMware or Hyper V or Proxmox, are those in the same category? [00:28:32] Bryan: Yeah, I mean a little bit. I mean, it kind of like vSphere Yes. Via VMware. No. So it's like you, uh, VMware ESX is, is kind of a key building block upon which you can build something that is a more meaningful distributed system. When it's just like a machine that you're provisioning VMs on, it's like, okay, well that's actually, you as the human might be the control plane. [00:28:52] Bryan: Like, that's, that, that's, that's a much easier problem. Um, but when you've got, you know, tens, hundreds, thousands of machines, you need to do it robustly. You need something to coordinate that activity and you know, you need to pick which sled you land on. You need to be able to move these things. You need to be able to update that whole system. [00:29:06] Bryan: That's when you're getting into a control plane. So, you know, some of these things have kind of edged into a control plane, certainly VMware. Um, now Broadcom, um, has delivered something that's kind of cloudish. Um, I think that for folks that are truly born on the cloud, it, it still feels somewhat, uh, like you're going backwards in time when you, when you look at these kind of on-prem offerings. [00:29:29] Bryan: Um, but, but it, it, it's got these aspects to it for sure. Um, and I think that we're, um, some of these other things when you're just looking at KVM or just looks looking at Proxmox you kind of need to, to connect it to other broader things to turn it into something that really looks like manageable infrastructure. [00:29:47] Bryan: And then many of those projects are really, they're either proprietary projects, uh, proprietary products like vSphere, um, or you are really dealing with open source projects that are. Not necessarily aimed at the same level of scale. Um, you know, you look at a, again, Proxmox or, uh, um, you'll get an OpenStack. [00:30:05] Bryan: Um, and you know, OpenStack is just a lot of things, right? I mean, OpenStack has got so many, the OpenStack was kind of a, a free for all, for every infrastructure vendor. Um, and I, you know, there was a time people were like, don't you, aren't you worried about all these companies together that, you know, are coming together for OpenStack? [00:30:24] Bryan: I'm like, haven't you ever worked for like a company? Like, companies don't get along. By the way, it's like having multiple companies work together on a thing that's bad news, not good news. And I think, you know, one of the things that OpenStack has definitely struggled with, kind of with what, actually the, the, there's so many different kind of vendor elements in there that it's, it's very much not a product, it's a project that you're trying to run. [00:30:47] Bryan: But that's, but that very much is in, I mean, that's, that's similar certainly in spirit. [00:30:53] Jeremy: And so I think this is kind of like you're alluding to earlier, the piece that allows you to allocate, compute, storage, manage networking, gives you that experience of I can go to a web console or I can use an API and I can spin up machines, get them all connected. At the end of the day, the control plane. Is allowing you to do that in hopefully a user-friendly way. [00:31:21] Bryan: That's right. Yep. And in the, I mean, in order to do that in a modern way, it's not just like a user-friendly way. You really need to have a CLI and a web UI and an API. Those all need to be drawn from the same kind of single ground truth. Like you don't wanna have any of those be an afterthought for the other. [00:31:39] Bryan: You wanna have the same way of generating all of those different endpoints and, and entries into the system. Building a control plane now has better tools (Rust, CockroachDB) [00:31:46] Jeremy: And if you take your time at Joyent as an example. What kind of tools existed for that versus how much did you have to build in-house for as far as the hypervisor and managing the compute and all that? [00:32:02] Bryan: Yeah, so we built more or less everything in house. I mean, what you have is, um, and I think, you know, over time we've gotten slightly better tools. Um, I think, and, and maybe it's a little bit easier to talk about the, kind of the tools we started at Oxide because we kind of started with a, with a clean sheet of paper at oxide. [00:32:16] Bryan: We wanted to, knew we wanted to go build a control plane, but we were able to kind of go revisit some of the components. So actually, and maybe I'll, I'll talk about some of those changes. So when we, at, For example, at Joyent, when we were building a cloud at Joyent, there wasn't really a good distributed database. [00:32:34] Bryan: Um, so we were using Postgres as our database for metadata and there were a lot of challenges. And Postgres is not a distributed database. It's running. With a primary secondary architecture, and there's a bunch of issues there, many of which we discovered the hard way. Um, when we were coming to oxide, you have much better options to pick from in terms of distributed databases. [00:32:57] Bryan: You know, we, there was a period that now seems maybe potentially brief in hindsight, but of a really high quality open source distributed databases. So there were really some good ones to, to pick from. Um, we, we built on CockroachDB on CRDB. Um, so that was a really important component. That we had at oxide that we didn't have at Joyent. [00:33:19] Bryan: Um, so we were, I wouldn't say we were rolling our own distributed database, we were just using Postgres and uh, and, and dealing with an enormous amount of pain there in terms of the surround. Um, on top of that, and, and, you know, a, a control plane is much more than a database, obviously. Uh, and you've gotta deal with, uh, there's a whole bunch of software that you need to go, right. [00:33:40] Bryan: Um, to be able to, to transform these kind of API requests into something that is reliable infrastructure, right? And there, there's a lot to that. Uh, especially when networking gets in the mix, when storage gets in the mix, uh, there are a whole bunch of like complicated steps that need to be done, um, at Joyent. [00:33:59] Bryan: Um, we, in part because of the history of the company and like, look. This, this just is not gonna sound good, but it just is what it is and I'm just gonna own it. We did it all in Node, um, at Joyent, which I, I, I know it sounds really right now, just sounds like, well, you, you built it with Tinker Toys. You Okay. [00:34:18] Bryan: Uh, did, did you think it was, you built the skyscraper with Tinker Toys? Uh, it's like, well, okay. We actually, we had greater aspirations for the Tinker Toys once upon a time, and it was better than, you know, than Twisted Python and Event Machine from Ruby, and we weren't gonna do it in Java. All right. [00:34:32] Bryan: So, but let's just say that that experiment, uh, that experiment did ultimately end in a predictable fashion. Um, and, uh, we, we decided that maybe Node was not gonna be the best decision long term. Um, Joyent was the company behind node js. Uh, back in the day, Ryan Dahl worked for Joyent. Uh, and then, uh, then we, we, we. [00:34:53] Bryan: Uh, landed that in a foundation in about, uh, what, 2015, something like that. Um, and began to consider our world beyond, uh, beyond Node. Rust at Oxide [00:35:04] Bryan: A big tool that we had in the arsenal when we started Oxide is Rust. Um, and so indeed the name of the company is, is a tip of the hat to the language that we were pretty sure we were gonna be building a lot of stuff in. [00:35:16] Bryan: Namely Rust. And, uh, rust is, uh, has been huge for us, a very important revolution in programming languages. you know, there, there, there have been different people kind of coming in at different times and I kinda came to Rust in what I, I think is like this big kind of second expansion of rust in 2018 when a lot of technologists were think, uh, sick of Node and also sick of Go. [00:35:43] Bryan: And, uh, also sick of C++. And wondering is there gonna be something that gives me the, the, the performance, of that I get outta C. The, the robustness that I can get out of a C program but is is often difficult to achieve. but can I get that with kind of some, some of the velocity of development, although I hate that term, some of the speed of development that you get out of a more interpreted language. [00:36:08] Bryan: Um, and then by the way, can I actually have types, I think types would be a good idea? Uh, and rust obviously hits the sweet spot of all of that. Um, it has been absolutely huge for us. I mean, we knew when we started the company again, oxide, uh, we were gonna be using rust in, in quite a, quite a. Few places, but we weren't doing it by fiat. [00:36:27] Bryan: Um, we wanted to actually make sure we're making the right decision, um, at, at every different, at every layer. Uh, I think what has been surprising is the sheer number of layers at which we use rust in terms of, we've done our own embedded firmware in rust. We've done, um, in, in the host operating system, which is still largely in C, but very big components are in rust. [00:36:47] Bryan: The hypervisor Propolis is all in rust. Uh, and then of course the control plane, that distributed system on that is all in rust. So that was a very important thing that we very much did not need to build ourselves. We were able to really leverage, uh, a terrific community. Um. We were able to use, uh, and we've done this at Joyent as well, but at Oxide, we've used Illumos as a hostos component, which, uh, our variant is called Helios. [00:37:11] Bryan: Um, we've used, uh, bhyve um, as a, as as that kind of internal hypervisor component. we've made use of a bunch of different open source components to build this thing, um, which has been really, really important for us. Uh, and open source components that didn't exist even like five years prior. [00:37:28] Bryan: That's part of why we felt that 2019 was the right time to start the company. And so we started Oxide. The problems building a control plane in Node [00:37:34] Jeremy: You had mentioned that at Joyent, you had tried to build this in, in Node. What were the, what were the, the issues or the, the challenges that you had doing that? [00:37:46] Bryan: Oh boy. Yeah. again, we, I kind of had higher hopes in 2010, I would say. When we, we set on this, um, the, the, the problem that we had just writ large, um. JavaScript is really designed to allow as many people on earth to write a program as possible, which is good. I mean, I, I, that's a, that's a laudable goal. [00:38:09] Bryan: That is the goal ultimately of such as it is of JavaScript. It's actually hard to know what the goal of JavaScript is, unfortunately, because Brendan Ike never actually wrote a book. so that there is not a canonical, you've got kind of Doug Crockford and other people who've written things on JavaScript, but it's hard to know kind of what the original intent of JavaScript is. [00:38:27] Bryan: The name doesn't even express original intent, right? It was called Live Script, and it was kind of renamed to JavaScript during the Java Frenzy of the late nineties. A name that makes no sense. There is no Java in JavaScript. that is kind of, I think, revealing to kind of the, uh, the unprincipled mess that is JavaScript. [00:38:47] Bryan: It, it, it's very pragmatic at some level, um, and allows anyone to, it makes it very easy to write software. The problem is it's much more difficult to write really rigorous software. So, uh, and this is what I should differentiate JavaScript from TypeScript. This is really what TypeScript is trying to solve. [00:39:07] Bryan: TypeScript is like. How can, I think TypeScript is a, is a great step forward because TypeScript is like, how can we bring some rigor to this? Like, yes, it's great that it's easy to write JavaScript, but that's not, we, we don't wanna do that for Absolutely. I mean that, that's not the only problem we solve. [00:39:23] Bryan: We actually wanna be able to write rigorous software and it's actually okay if it's a little harder to write rigorous software that's actually okay if it gets leads to, to more rigorous artifacts. Um, but in JavaScript, I mean, just a concrete example. You know, there's nothing to prevent you from referencing a property that doesn't actually exist in JavaScript. [00:39:43] Bryan: So if you fat finger a property name, you are relying on something to tell you. By the way, I think you've misspelled this because there is no type definition for this thing. And I don't know that you've got one that's spelled correctly, one that's spelled incorrectly, that's often undefined. And then the, when you actually go, you say you've got this typo that is lurking in your what you want to be rigorous software. [00:40:07] Bryan: And if you don't execute that code, like you won't know that's there. And then you do execute that code. And now you've got a, you've got an undefined object. And now that's either gonna be an exception or it can, again, depends on how that's handled. It can be really difficult to determine the origin of that, of, of that error, of that programming. [00:40:26] Bryan: And that is a programmer error. And one of the big challenges that we had with Node is that programmer errors and operational errors, like, you know, I'm out of disk space as an operational error. Those get conflated and it becomes really hard. And in fact, I think the, the language wanted to make it easier to just kind of, uh, drive on in the event of all errors. [00:40:53] Bryan: And it's like, actually not what you wanna do if you're trying to build a reliable, robust system. So we had. No end of issues. [00:41:01] Bryan: We've got a lot of experience developing rigorous systems, um, again coming out of operating systems development and so on. And we want, we brought some of that rigor, if strangely, to JavaScript. So one of the things that we did is we brought a lot of postmortem, diagnos ability and observability to node. [00:41:18] Bryan: And so if, if one of our node processes. Died in production, we would actually get a core dump from that process, a core dump that we could actually meaningfully process. So we did a bunch of kind of wild stuff. I mean, actually wild stuff where we could actually make sense of the JavaScript objects in a binary core dump. JavaScript values ease of getting started over robustness [00:41:41] Bryan: Um, and things that we thought were really important, and this is the, the rest of the world just looks at this being like, what the hell is this? I mean, it's so out of step with it. The problem is that we were trying to bridge two disconnected cultures of one developing really. Rigorous software and really designing it for production, diagnosability and the other, really designing it to software to run in the browser and for anyone to be able to like, you know, kind of liven up a webpage, right? [00:42:10] Bryan: Is kinda the origin of, of live script and then JavaScript. And we were kind of the only ones sitting at the intersection of that. And you begin when you are the only ones sitting at that kind of intersection. You just are, you're, you're kind of fighting a community all the time. And we just realized that we are, there were so many things that the community wanted to do that we felt are like, no, no, this is gonna make software less diagnosable. It's gonna make it less robust. The NodeJS split and why people left [00:42:36] Bryan: And then you realize like, I'm, we're the only voice in the room because we have got, we have got desires for this language that it doesn't have for itself. And this is when you realize you're in a bad relationship with software. It's time to actually move on. And in fact, actually several years after, we'd already kind of broken up with node. [00:42:55] Bryan: Um, and it was like, it was a bit of an acrimonious breakup. there was a, uh, famous slash infamous fork of node called IoJS Um, and this was viewed because people, the community, thought that Joyent was being what was not being an appropriate steward of node js and was, uh, not allowing more things to come into to, to node. [00:43:19] Bryan: And of course, the reason that we of course, felt that we were being a careful steward and we were actively resisting those things that would cut against its fitness for a production system. But it's some way the community saw it and they, and forked, um, and, and I think the, we knew before the fork that's like, this is not working and we need to get this thing out of our hands. Platform is a reflection of values node summit talk [00:43:43] Bryan: And we're are the wrong hands for this? This needs to be in a foundation. Uh, and so we kind of gone through that breakup, uh, and maybe it was two years after that. That, uh, friend of mine who was um, was running the, uh, the node summit was actually, it's unfortunately now passed away. Charles er, um, but Charles' venture capitalist great guy, and Charles was running Node Summit and came to me in 2017. [00:44:07] Bryan: He is like, I really want you to keynote Node Summit. And I'm like, Charles, I'm not gonna do that. I've got nothing nice to say. Like, this is the, the, you don't want, I'm the last person you wanna keynote. He's like, oh, if you have nothing nice to say, you should definitely keynote. You're like, oh God, okay, here we go. [00:44:22] Bryan: He's like, no, I really want you to talk about, like, you should talk about the Joyent breakup with NodeJS. I'm like, oh man. [00:44:29] Bryan: And that led to a talk that I'm really happy that I gave, 'cause it was a very important talk for me personally. Uh, called Platform is a reflection of values and really looking at the values that we had for Node and the values that Node had for itself. And they didn't line up. [00:44:49] Bryan: And the problem is that the values that Node had for itself and the values that we had for Node are all kind of positives, right? Like there's nobody in the node community who's like, I don't want rigor, I hate rigor. It's just that if they had the choose between rigor and making the language approachable. [00:45:09] Bryan: They would choose approachability every single time. They would never choose rigor. And, you know, that was a, that was a big eye-opener. I do, I would say, if you watch this talk. [00:45:20] Bryan: because I knew that there's, like, the audience was gonna be filled with, with people who, had been a part of the fork in 2014, I think was the, the, the, the fork, the IOJS fork. And I knew that there, there were, there were some, you know, some people that were, um, had been there for the fork and. [00:45:41] Bryan: I said a little bit of a trap for the audience. But the, and the trap, I said, you know what, I, I kind of talked about the values that we had and the aspirations we had for Node, the aspirations that Node had for itself and how they were different. [00:45:53] Bryan: And, you know, and I'm like, look in, in, in hindsight, like a fracture was inevitable. And in 2014 there was finally a fracture. And do people know what happened in 2014? And if you, if you, you could listen to that talk, everyone almost says in unison, like IOJS. I'm like, oh right. IOJS. Right. That's actually not what I was thinking of. [00:46:19] Bryan: And I go to the next slide and is a tweet from a guy named TJ Holloway, Chuck, who was the most prolific contributor to Node. And it was his tweet also in 2014 before the fork, before the IOJS fork explaining that he was leaving Node and that he was going to go. And you, if you turn the volume all the way up, you can hear the audience gasp. [00:46:41] Bryan: And it's just delicious because the community had never really come, had never really confronted why TJ left. Um, there. And I went through a couple folks, Felix, bunch of other folks, early Node folks. That were there in 2010, were leaving in 2014, and they were going to go primarily, and they were going to go because they were sick of the same things that we were sick of. [00:47:09] Bryan: They, they, they had hit the same things that we had hit and they were frustrated. I I really do believe this, that platforms do reflect their own values. And when you are making a software decision, you are selecting value. [00:47:26] Bryan: You should select values that align with the values that you have for that software. That is, those are, that's way more important than other things that people look at. I think people look at, for example, quote unquote community size way too frequently, community size is like. Eh, maybe it can be fine. [00:47:44] Bryan: I've been in very large communities, node. I've been in super small open source communities like AUMs and RAs, a bunch of others. there are strengths and weaknesses to both approaches just as like there's a strength to being in a big city versus a small town. Me personally, I'll take the small community more or less every time because the small community is almost always self-selecting based on values and just for the same reason that I like working at small companies or small teams. [00:48:11] Bryan: There's a lot of value to be had in a small community. It's not to say that large communities are valueless, but again, long answer to your question of kind of where did things go south with Joyent and node. They went south because the, the values that we had and the values the community had didn't line up and that was a very educational experience, as you might imagine. [00:48:33] Jeremy: Yeah. And, and given that you mentioned how, because of those values, some people moved from Node to go, and in the end for much of what oxide is building. You ended up using rust. What, what would you say are the, the values of go and and rust, and how did you end up choosing Rust given that. Go's decisions regarding generics, versioning, compilation speed priority [00:48:56] Bryan: Yeah, I mean, well, so the value for, yeah. And so go, I mean, I understand why people move from Node to Go, go to me was kind of a lateral move. Um, there were a bunch of things that I, uh, go was still garbage collected, um, which I didn't like. Um, go also is very strange in terms of there are these kind of like. [00:49:17] Bryan: These autocratic kind of decisions that are very bizarre. Um, there, I mean, generics is kind of a famous one, right? Where go kind of as a point of principle didn't have generics, even though go itself actually the innards of go did have generics. It's just that you a go user weren't allowed to have them. [00:49:35] Bryan: And you know, it's kind of, there was, there was an old cartoon years and years ago about like when a, when a technologist is telling you that something is technically impossible, that actually means I don't feel like it. Uh, and there was a certain degree of like, generics are technically impossible and go, it's like, Hey, actually there are. [00:49:51] Bryan: And so there was, and I just think that the arguments against generics were kind of disingenuous. Um, and indeed, like they ended up adopting generics and then there's like some super weird stuff around like, they're very anti-assertion, which is like, what, how are you? Why are you, how is someone against assertions, it doesn't even make any sense, but it's like, oh, nope. [00:50:10] Bryan: Okay. There's a whole scree on it. Nope, we're against assertions and the, you know, against versioning. There was another thing like, you know, the Rob Pike has kind of famously been like, you should always just run on the way to commit. And you're like, does that, is that, does that make sense? I mean this, we actually built it. [00:50:26] Bryan: And so there are a bunch of things like that. You're just like, okay, this is just exhausting and. I mean, there's some things about Go that are great and, uh, plenty of other things that I just, I'm not a fan of. Um, I think that the, in the end, like Go cares a lot about like compile time. It's super important for Go Right? [00:50:44] Bryan: Is very quick, compile time. I'm like, okay. But that's like compile time is not like, it's not unimportant, it's doesn't have zero importance. But I've got other things that are like lots more important than that. Um, what I really care about is I want a high performing artifact. I wanted garbage collection outta my life. Don't think garbage collection has good trade offs [00:51:00] Bryan: I, I gotta tell you, I, I like garbage collection to me is an embodiment of this like, larger problem of where do you put cognitive load in the software development process. And what garbage collection is saying to me it is right for plenty of other people and the software that they wanna develop. [00:51:21] Bryan: But for me and the software that I wanna develop, infrastructure software, I don't want garbage collection because I can solve the memory allocation problem. I know when I'm like, done with something or not. I mean, it's like I, whether that's in, in C with, I mean it's actually like, it's really not that hard to not leak memory in, in a C base system. [00:51:44] Bryan: And you can. give yourself a lot of tooling that allows you to diagnose where memory leaks are coming from. So it's like that is a solvable problem. There are other challenges with that, but like, when you are developing a really sophisticated system that has garbage collection is using garbage collection. [00:51:59] Bryan: You spend as much time trying to dork with the garbage collector to convince it to collect the thing that you know is garbage. You are like, I've got this thing. I know it's garbage. Now I need to use these like tips and tricks to get the garbage collector. I mean, it's like, it feels like every Java performance issue goes to like minus xx call and use the other garbage collector, whatever one you're using, use a different one and using a different, a different approach. [00:52:23] Bryan: It's like, so you're, you're in this, to me, it's like you're in the worst of all worlds where. the reason that garbage collection is helpful is because the programmer doesn't have to think at all about this problem. But now you're actually dealing with these long pauses in production. [00:52:38] Bryan: You're dealing with all these other issues where actually you need to think a lot about it. And it's kind of, it, it it's witchcraft. It, it, it's this black box that you can't see into. So it's like, what problem have we solved exactly? And I mean, so the fact that go had garbage collection, it's like, eh, no, I, I do not want, like, and then you get all the other like weird fatwahs and you know, everything else. [00:52:57] Bryan: I'm like, no, thank you. Go is a no thank you for me, I, I get it why people like it or use it, but it's, it's just, that was not gonna be it. Choosing Rust [00:53:04] Bryan: I'm like, I want C. but I, there are things I didn't like about C too. I was looking for something that was gonna give me the deterministic kind of artifact that I got outta C. But I wanted library support and C is tough because there's, it's all convention. you know, there's just a bunch of other things that are just thorny. And I remember thinking vividly in 2018, I'm like, well, it's rust or bust. Ownership model, algebraic types, error handling [00:53:28] Bryan: I'm gonna go into rust. And, uh, I hope I like it because if it's not this, it's gonna like, I'm gonna go back to C I'm like literally trying to figure out what the language is for the back half of my career. Um, and when I, you know, did what a lot of people were doing at that time and people have been doing since of, you know, really getting into rust and really learning it, appreciating the difference in the, the model for sure, the ownership model people talk about. [00:53:54] Bryan: That's also obviously very important. It was the error handling that blew me away. And the idea of like algebraic types, I never really had algebraic types. Um, and the ability to, to have. And for error handling is one of these really, uh, you, you really appreciate these things where it's like, how do you deal with a, with a function that can either succeed and return something or it can fail, and the way c deals with that is bad with these kind of sentinels for errors. [00:54:27] Bryan: And, you know, does negative one mean success? Does negative one mean failure? Does zero mean failure? Some C functions, zero means failure. Traditionally in Unix, zero means success. And like, what if you wanna return a file descriptor, you know, it's like, oh. And then it's like, okay, then it'll be like zero through positive N will be a valid result. [00:54:44] Bryan: Negative numbers will be, and like, was it negative one and I said airo, or is it a negative number that did not, I mean, it's like, and that's all convention, right? People do all, all those different things and it's all convention and it's easy to get wrong, easy to have bugs, can't be statically checked and so on. Um, and then what Go says is like, well, you're gonna have like two return values and then you're gonna have to like, just like constantly check all of these all the time. Um, which is also kind of gross. Um, JavaScript is like, Hey, let's toss an exception. If, if we don't like something, if we see an error, we'll, we'll throw an exception. [00:55:15] Bryan: There are a bunch of reasons I don't like that. Um, and you look, you'll get what Rust does, where it's like, no, no, no. We're gonna have these algebra types, which is to say this thing can be a this thing or that thing, but it, but it has to be one of these. And by the way, you don't get to process this thing until you conditionally match on one of these things. [00:55:35] Bryan: You're gonna have to have a, a pattern match on this thing to determine if it's a this or a that, and if it in, in the result type that you, the result is a generic where it's like, it's gonna be either the thing that you wanna return. It's gonna be an okay that contains the thing you wanna return, or it's gonna be an error that contains your error and it forces your code to deal with that. [00:55:57] Bryan: And what that does is it shifts the cognitive load from the person that is operating this thing in production to the, the actual developer that is in development. And I think that that, that to me is like, I, I love that shift. Um, and that shift to me is really important. Um, and that's what I was missing, that that's what Rust gives you. [00:56:23] Bryan: Rust forces you to think about your code as you write it, but as a result, you have an artifact that is much more supportable, much more sustainable, and much faster. Prefer to frontload cognitive load during development instead of at runtime [00:56:34] Jeremy: Yeah, it sounds like you would rather take the time during the development to think about these issues because whether it's garbage collection or it's error handling at runtime when you're trying to solve a problem, then it's much more difficult than having dealt with it to start with. [00:56:57] Bryan: Yeah, absolutely. I, and I just think that like, why also, like if it's software, if it's, again, if it's infrastructure software, I mean the kinda the question that you, you should have when you're writing software is how long is this software gonna live? How many people are gonna use this software? Uh, and if you are writing an operating system, the answer for this thing that you're gonna write, it's gonna live for a long time. [00:57:18] Bryan: Like, if we just look at plenty of aspects of the system that have been around for a, for decades, it's gonna live for a long time and many, many, many people are gonna use it. Why would we not expect people writing that software to have more cognitive load when they're writing it to give us something that's gonna be a better artifact? [00:57:38] Bryan: Now conversely, you're like, Hey, I kind of don't care about this. And like, I don't know, I'm just like, I wanna see if this whole thing works. I've got, I like, I'm just stringing this together. I don't like, no, the software like will be lucky if it survives until tonight, but then like, who cares? Yeah. Yeah. [00:57:52] Bryan: Gar garbage clock. You know, if you're prototyping something, whatever. And this is why you really do get like, you know, different choices, different technology choices, depending on the way that you wanna solve the problem at hand. And for the software that I wanna write, I do like that cognitive load that is upfront. With LLMs maybe you can get the benefit of the robust artifact with less cognitive load [00:58:10] Bryan: Um, and although I think, I think the thing that is really wild that is the twist that I don't think anyone really saw coming is that in a, in an LLM age. That like the cognitive load upfront almost needs an asterisk on it because so much of that can be assisted by an LLM. And now, I mean, I would like to believe, and maybe this is me being optimistic, that the the, in the LLM age, we will see, I mean, rust is a great fit for the LLMH because the LLM itself can get a lot of feedback about whether the software that's written is correct or not. [00:58:44] Bryan: Much more so than you can for other environments. [00:58:48] Jeremy: Yeah, that is a interesting point in that I think when people first started trying out the LLMs to code, it was really good at these maybe looser languages like Python or JavaScript, and initially wasn't so good at something like Rust. But it sounds like as that improves, if. It can write it then because of the rigor or the memory management or the error handling that the language is forcing you to do, it might actually end up being a better choice for people using LLMs. [00:59:27] Bryan: absolutely. I, it, it gives you more certainty in the artifact that you've delivered. I mean, you know a lot about a Rust program that compiles correctly. I mean, th there are certain classes of errors that you don't have, um, that you actually don't know on a C program or a GO program or a, a JavaScript program. [00:59:46] Bryan: I think that's gonna be really important. I think we are on the cusp. Maybe we've already seen it, this kind of great bifurcation in the software that we writ

In this episode, I sit down with Prashant Sridharan, a 30-year veteran of developer marketing who has shaped go-to-market strategies for tech giants like Sun Microsystems, Microsoft, AWS, Facebook, and Twitter, and currently runs product marketing at Supabase. We dive deep into the origins of DevRel and how marketing to developers has evolved in an increasingly noisy, AI-saturated landscape.Topics covered:- Transitioning from massive tech companies to the fast-paced startup world - How to genuinely measure the success of Developer Relations without ruining communities - Using AI tools like Claude to accelerate mechanical marketing tasks while preserving authentic storytelling - The shift from traditional SEO to GEO (Generative Engine Optimization) for developer tools - The thrill of live, unscripted coding demos and stories from sharing the stage with Steve Ballmer - Prashant's upcoming fiction novel, The Midnight Coders Children, and the craft of writing Find more from Prashant at StrategicNerds.com and check out his non-fiction book, Picks and Shovels: https://amzn.to/4cJ2TRO

An airhacks.fm conversation with Simon Ritter (@speakjava) about: first computer experiences with TRS-80 and mainframe ALGOL68 programming via punched cards in the 1970s UK, one-week turnaround times for program execution, writing battleship games on mainframes, bbc micro with color graphics and dual floppy drives, father's influence as a tech enthusiast with a PDP-8 in his chemistry lab, early fascination with robotics and controlling machines through programming, writing card games and Mandelbrot set fractal generators in Basic, transition from BASIC to C programming through sponsored university degree, working at Rocc Computers on Unix device drivers and kernel debugging, the teleputer, memory leak debugging requiring half-inch mag tape transfers and two-week investigation periods, AT&T Unix source code license access and kernel modifications, Unix System V Release 4 and Bell Labs heritage, Motorola 68000 processor's flat memory model versus Intel's near/far pointers, Novell acquisition of Unix from AT&T in 1993, Unixware development and time spent in Utah, SCO's acquisition of Unix IP and subsequent IP trolling, joining Sun Microsystems in 1996 as Solaris sales engineer, transition to Java evangelism in 1997, working under Reggie Hutcherson and Matt Thompson for nearly 10 years, building Lego Mindstorms blackjack-dealing robot with Java speech recognition and computer vision, using Sphinx for voice recognition and FreeTTS for speech synthesis, JMF webcam integration for card recognition, JavaOne 2004 robot demonstration, Glassfish application server evangelism and reference implementation benefits, Sun's technology focus versus business development challenges, CDE desktop environment nostalgia, Oracle acquisition of Sun in 2010, Jonathan Schwartz's acquisition announcement email, Oracle's successful stewardship of Java through openJDK, praise for Brian Goetz Mark Reinhold John Rose and Stuart Marks, six-month release cycle benefits, Project Amber Loom Panama and Valhalla developments, OpenSolaris discontinuation leading to docker adoption for server containerization, Oracle's 2015 pivot to cloud focus, career-defining conversation in Japan about cloud versus Java evangelism, layoff during vacation in September 2015, joining Azul Systems after three-and-a-half-hour interview with Gil Tene, ten years at Azul working on high-performance JVM Platform Prime garbage collection and CRaC technology, comparison of Azul culture to Sun Microsystems innovation environment, commercial Java distribution value propositions and runtime inventory features Simon Ritter on twitter: @speakjava

We think that offering different sizes is serving our customers, but is it actually? Does standard sizing make it easier for the customer or does it just make it easier for the brand? Rick Levine and Steven Heard have thoughts. They've each run multiple manufacturing businesses in different industries and are currently partners of the made-to-measure development and manufacturing studio ApparelWerks. No matter the business, their goal with product design, fit, and sizing has been the same: make each customer insanely happy. It impacts how they see production, technology, entrepreneurship, craftsmanship, customer relationships, and more. In episode 130, we cover it all. Steven and Rick were introduced when Rick was looking into body scanning for a problem his daughter, an engineer, was trying to solve. "There's a guy in Portland who's been making customized clothing for decades. He knows all about scanners and measurement." They discovered a shared appreciation for manufacturing technology, a fascination with old sewing machines, and a view that tech is only a means to an end; their past businesses were focused on making customers happy. Both were also looking for something new and interesting to do, and the result was starting ApparelWerks, a manufacturing and product development studio in Portland creating made-to-measure clothing. Steven Heard has decades of experience making clothing, starting at the Levi Strauss factory on Valencia Street in San Francisco, at a time when all patterns and samples for the company were still created there. He was a senior pattern-maker for Levi's Dockers brand, and went on to spearhead the world's first large-scale bespoke jeans production, leveraging body scanning technology to craft custom jeans for thousands of consumers. He founded pattern service bureau Clinton Park, doing garment development and pattern work for numerous national and start-up brands, and developed a reputation for being the go-to patternmaker for denim development. He went on to found Japanese-inspired San Francisco denim and workwear brand Dillon Montara in 2014, and was the development and manufacturing partner behind Portland's Ship John brand. Rick Levine is the engineering black sheep in a family of artists. His father was a ceramist and designer, making and using tools to create mid-century ceramic tile and lamps on a large scale. Rick spent a lot of his time growing up around clay and machinery. Rick started his career as a producer and editor for film and video, and stepped sideways into programming tools and user interfaces for computer systems. He worked at Sun Microsystems early in its existence, and then at a series of start-ups. In 2006, Rick followed his interest in manufacturing automation to found chocolate brand Sun Cups. He repurposed industrial-scale chocolate techniques to create artisanal, organic, nut-free chocolates and made them available in thousands of stores. In 2013, he and his brother, designer Neil Levine, founded sock company XOAB, focusing on creating comfortable socks with a broad palette of Merino wool and Supima® cotton colors. They created a domestic supply chain, and used modified knitting machines and pattern analysis software to take new designs from sketch to shelf in less than a week, a capability unique in the hosiery industry. This episode explores: Fitting the customer Why the garment won't fit unless you've had a conversation with the customer The difference between solving fit for your brand versus solving fit for your customer The advantages and limitations of 3D body scanning for apparel development How they know when they got the fit right Fitting the lifestyle Scaling on-demand production How one-piece production flow changes the way you see efficiency How Rick's and Steven's background lead to their perspectives on manufacturing The tools Rick and Steven use to systemetize custom clothing Fitting the values Why there's value in both craft and technology Why Rick has a “healthy disrespect” for tools People and resources mentioned in this episode: ApparelWerks website Dillon Montara website ApparelWerks Instagram Do you want fashion business tips and resources like this sent straight to your inbox? Sign up for the How Fitting newsletter to receive new podcast episodes plus daily content on creating fashion that fits your customer, lifestyle, and values.

Corey Zumar is a Product Manager at Databricks, working on MLflow and LLM evaluation, tracing, and lifecycle tooling for generative AI.Jules Damji is a Lead Developer Advocate at Databricks, working on Spark, lakehouse technologies, and developer education across the data and AI community.Danny Chiao is an Engineering Leader at Databricks, working on data and AI observability, quality, and production-grade governance for ML and agent systems.MLflow Leading Open Source // MLOps Podcast #356 with Databricks' Corey Zumar, Jules Damji, and Danny ChiaoJoin the Community: https://go.mlops.community/YTJoinInGet the newsletter: https://go.mlops.community/YTNewsletterShoutout to Databricks for powering this MLOps Podcast episode.// AbstractMLflow isn't just for data scientists anymore—and pretending it is is holding teams back. Corey Zumar, Jules Damji, and Danny Chiao break down how MLflow is being rebuilt for GenAI, agents, and real production systems where evals are messy, memory is risky, and governance actually matters. The takeaway: if your AI stack treats agents like fancy chatbots or splits ML and software tooling, you're already behind.// BioCorey ZumarCorey has been working as a Software Engineer at Databricks for the last 4 years and has been an active contributor to and maintainer of MLflow since its first release. Jules Damji Jules is a developer advocate at Databricks Inc., an MLflow and Apache Spark™ contributor, and Learning Spark, 2nd Edition coauthor. He is a hands-on developer with over 25 years of experience. He has worked at leading companies, such as Sun Microsystems, Netscape, @Home, Opsware/LoudCloud, VeriSign, ProQuest, Hortonworks, Anyscale, and Databricks, building large-scale distributed systems. He holds a B.Sc. and M.Sc. in computer science (from Oregon State University and Cal State, Chico, respectively) and an MA in political advocacy and communication (from Johns Hopkins University)Danny ChiaoDanny is an engineering lead at Databricks, leading efforts around data observability (quality, data classification). Previously, Danny led efforts at Tecton (+ Feast, an open source feature store) and Google to build ML infrastructure and large-scale ML-powered features. Danny holds a Bachelor's Degree in Computer Science from MIT.// Related LinksWebsite: https://mlflow.org/https://www.databricks.com/~~~~~~~~ ✌️Connect With Us ✌️ ~~~~~~~Catch all episodes, blogs, newsletters, and more: https://go.mlops.community/TYExploreJoin our Slack community [https://go.mlops.community/slack]Follow us on X/Twitter [@mlopscommunity](https://x.com/mlopscommunity) or [LinkedIn](https://go.mlops.community/linkedin)] Sign up for the next meetup: [https://go.mlops.community/register]MLOps Swag/Merch: [https://shop.mlops.community/]Connect with Demetrios on LinkedIn: /dpbrinkmConnect with Corey on LinkedIn: /corey-zumar/Connect with Jules on LinkedIn: /dmatrix/Connect with Danny on LinkedIn: /danny-chiao/Timestamps:[00:00] MLflow Open Source Focus[00:49] MLflow Agents in Production[00:00] AI UX Design Patterns[12:19] Context Management in Chat[19:24] Human Feedback in MLflow[24:37] Prompt Entropy and Optimization[30:55] Evolving MLFlow Personas[36:27] Persona Expansion vs Separation[47:27] Product Ecosystem Design[54:03] PII vs Business Sensitivity[57:51] Wrap up

An airhacks.fm conversation with Alvaro Hernandez (@ahachete) about: discussion about LLMs generating Java code with BCE patterns and architectural rules, Java being 20-30% better for LLM code generation than python and typescript, embedding business knowledge in Java source code for LLM context, stackgres as a curated opinionated stack for running Postgres on kubernetes, Postgres requiring external tools for connection pooling and high availability and backup and monitoring, StackGres as a Helm package and Kubernetes operator, comparison with oxide hardware for on-premise cloud environments, experimenting with Incus for system containers and VMS, limitations of Ansible for infrastructure automation and code reuse, Kubernetes as an API-driven architecture abstracting compute and storage, Custom Resource Definitions (CRDs) for declarative Postgres cluster management, StackGres supporting sharding with automated multi-cluster deployment, 13 lines of YAML to create 60-node sharded clusters, three interfaces for StackGres including CRDs and web console and REST API, operator written in Java with quarkus unlike typical Go-based operators, Google study showing Java faster than Go, GraalVM native compilation for 80MB container images versus 400-500MB JVM images, fabric8 Kubernetes client for API communication, reconciliation cycle running every 10 seconds to maintain desired state, pod local controller as Quarkus sidecar for local Postgres operations, dynamic extension installation without rebuilding container images, grpc bi-directional communication between control plane and control nodes, inverse connection pattern where nodes initiate connections to control plane, comparison with Jini and JavaSpaces leasing concepts from Sun Microsystems, quarter million lines of Java code in the operator mostly POJOs predating records, PostgreSQL configuration validation with 300+ parameters, automated tuning applied by default in StackGres, potential for LLM-driven optimization with clone clusters for testing, Framework Computer laptop automation with Ubuntu auto-install and Ansible and Nix, five to ten minute full system reinstall including BIOS updates Alvaro Hernandez on twitter: @ahachete

In this conversation, Ben Bajarin and Jay Goldberg engage with Benedict Evans to explore the current state of AI development, its historical context, and future predictions. They discuss the potential for an AI bubble, the importance of productization for user adoption, and the varying levels of AI integration across different industries. The conversation also touches on the comparison between Nvidia and Sun Microsystems, highlighting the challenges and opportunities in the AI landscape.

This podcast is brought to you by Outcomes Rocket, your exclusive healthcare marketing agency. Learn how to accelerate your growth by going to⁠ outcomesrocket.com AI security is no longer optional; it's the foundation that determines whether innovation in healthcare will thrive or fail. In this episode, Steve Wilson, Chief AI & Product Officer for Exabeam and author, discusses the hidden vulnerabilities inside modern AI systems, why traditional software assumptions break down, and how healthcare must rethink safety, trust, and security from the ground up. He explains the risks of prompt injection and indirect prompt injection, highlights the fragile nature of AI “intuition,” and compares securing AI to training unpredictable employees rather than testing deterministic code. Steve also explores issues such as supply chain integrity, output filtering, trust boundaries, and the growing need for continuous evaluation rather than one-time testing. Finally, he shares stories from his early career at Sun Microsystems, Java's early days, startup lessons from the 90s, and how modern AI agents are reshaping cybersecurity operations. Tune in and learn how today's most advanced AI systems can be both powerful and dangerously gullible, and what it takes to secure them! Resources Connect with and follow Steve Wilson on LinkedIn. Follow Exabeam on LinkedIn and visit their website! Buy Steve Wilson's book The Developer's Playbook for Large Language Model Security here.

Jeffrey Allen, a respected energy healer and Mindvalley author, is known for his teachings on personal transformation and spiritual awakening.  His ‘Duality' training with Mindvalley and ‘Spirit Mind' training with his wife Hisami assist people worldwide in transforming their lives and reconnecting with their true essence. Prior to entering the world of spirituality, Jeffrey had a 15 year career as software engineer with the US Department of Energy and Sun Microsystems. Since then he has spent over 15 years teaching clairvoyance, healing, and mediumship studies around the world.  Jeffrey has studied with world renowned teachers Michael Tamura, Mary Bell Nyman, Jim Self, John Fulton, and Nassim Haramein of the Resonance Project. We discuss: The Spirit Body Why men don't feel energy like women Types of energy healing Insight on the current energy right now How to recognize your natural gifts Follow Jeffrey Allen on Instagram @iamjeffreyallen Explore Jeffrey's Duality or Unlocking Transcendence classes with Mindvalley https://www.mindvalley.com Learn more about Jeffrey Allen  www.IAMJeffreyAllen.com www.SpiritMind.com Follow Chef Whitney Aronoff on Instagram at @whitneyaronoff and @starseedkitchen Learn more about High Vibration Living with Chef Whitney Aronoff on www.StarseedKitchen.com  Get 10% off your order of Chef Whitney's organic spices with code STARSEED on www.starseedkitchen.com  Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of The Segment, host Raghu Nandakumara sits down with one of the most influential technology leaders of our time: Tony Scott, President & CEO of Intrusion and former U.S. Federal CIO under President Obama. With CIO roles at Microsoft, VMware, Disney, General Motors, Bristol Myers Squibb, and Sun Microsystems, Tony brings a rare, decades-wide perspective on how enterprise technology evolves—and where it's heading next.Tony shares his journey through some of the world's most complex organizations, offering a candid look at the forces that drive digital transformation, why organizational silos still shape most architectures, and how AI may finally help dissolve them. He breaks down how cybersecurity models must shift in an era of ubiquitous AI, legacy infrastructure, and escalating regulatory complexity—and explains why continuous monitoring and long-term institutional memory are now essential.We also dive into Tony's leadership philosophy, how he balances transformation with cyber risk, and what he's learned transitioning from CIO to CEO of a cybersecurity company tackling some of today's hardest problems. Key themes discussed:The evolution of the CIO role across decades of transformation Managing cyber risk amid AI proliferation, legacy systems, and modern architectures The importance of “useful life” frameworks for tech modernization Leadership lessons from navigating both public and private sector tech at scale A must-listen for CIOs, CISOs, tech leaders, and anyone preparing their organization for what's next in AI-driven transformation and cybersecurity.

It began in the 1970s, with rumors rumbling from the outskirts of the American technology giant, IBM. A new chip architecture capable of revolutionary processing speeds. It was called RISC. The RISC Wars were fought over nearly 20 years, with the most intensive battles in the late 1980s and early 1990s. At its peak, it involved a mix of young chip upstarts and old giants across the world throwing around benchmark results. Sun Microsystems. MIPS Computer. PA-RISC. IBM. PowerPC. DEC Alpha. Fujitsu and NEC in Japan. Siemens and Philips in Europe. And of course, looming over them all: Intel and the burgeoning Wintel Death Machine. It was a time of shifting alliances, leaps of inspiration, wild technical claims, and the Iron Fist of Intel. Today, we delve into legends of the RISC Wars.

It began in the 1970s, with rumors rumbling from the outskirts of the American technology giant, IBM. A new chip architecture capable of revolutionary processing speeds. It was called RISC. The RISC Wars were fought over nearly 20 years, with the most intensive battles in the late 1980s and early 1990s. At its peak, it involved a mix of young chip upstarts and old giants across the world throwing around benchmark results. Sun Microsystems. MIPS Computer. PA-RISC. IBM. PowerPC. DEC Alpha. Fujitsu and NEC in Japan. Siemens and Philips in Europe. And of course, looming over them all: Intel and the burgeoning Wintel Death Machine. It was a time of shifting alliances, leaps of inspiration, wild technical claims, and the Iron Fist of Intel. Today, we delve into legends of the RISC Wars.

What if the real key to exploding your business isn't just innovation—but mastering the art of pivoting through change?   In this episode of Sharkpreneur, Seth Greene interviews Blair LaCorte, CEO at LaCorte Ventures. Blair is a leader who has guided multiple companies from startup to IPO and through major industry disruptions. Blair's career includes C-level roles at ExoJet Vista, TPG, Autodesk, Sun Microsystems, and the world's largest live entertainment production company. He's currently training as an astronaut for Virgin Galactic, serves as Vice Chairman of the Buck Institute for Research on Aging, and has collaborated with icons like Richard Branson, Elon Musk, and Bill Clinton. In this candid conversation, Blair shares how to recognize when to pivot versus double down, why change is the ultimate business opportunity, and how to build lasting connections that fuel personal and professional growth.   Key Takeaways: → The two essential skills every entrepreneur needs: fact-finding and quick-start decision-making. → How to tell if you're pivoting too much—or not enough. → Why change should be viewed as a profit opportunity, not a threat. → The biggest mistakes leaders make when reacting to disruption—and how to avoid them. → Why restructuring and scaling have more in common than most think.   Blair LaCorte is a dynamic business executive with a diverse career spanning entertainment, aviation, AI, technology, aerospace, consulting, investing, and military logistics. Raised by entrepreneurs, he has held CEO and C-level roles at major companies like PRG, XOJET/Vista, TPG, Autodesk, and Sun Microsystems/Oracle. Blair has helped lead multiple startups to successful IPOs, including AEye Technologies and VerticalNet. Currently, he is an astronaut-in-training for Virgin Galactic and serves as Vice Chairman of the Buck Institute, a leader in longevity research. He also co-founded and facilitates a Mastermind group of 40 global CEOs. Known for his engaging leadership and strategic vision, Blair has served on nonprofit boards alongside luminaries like Steve Kerr, Phil Jackson, Richard Branson, Elon Musk, and Bill Clinton.   Connect With Blair LaCorte: Website: https://mastermindinnovate.com/ LinkedIn: https://www.linkedin.com/in/blair-lacorte-68084/ Learn more about your ad choices. Visit megaphone.fm/adchoices

What if the real key to exploding your business isn't just innovation—but mastering the art of pivoting through change?   In this episode of Sharkpreneur, Seth Greene interviews Blair LaCorte, CEO at LaCorte Ventures. Blair is a leader who has guided multiple companies from startup to IPO and through major industry disruptions. Blair's career includes C-level roles at ExoJet Vista, TPG, Autodesk, Sun Microsystems, and the world's largest live entertainment production company. He's currently training as an astronaut for Virgin Galactic, serves as Vice Chairman of the Buck Institute for Research on Aging, and has collaborated with icons like Richard Branson, Elon Musk, and Bill Clinton. In this candid conversation, Blair shares how to recognize when to pivot versus double down, why change is the ultimate business opportunity, and how to build lasting connections that fuel personal and professional growth.   Key Takeaways: → The two essential skills every entrepreneur needs: fact-finding and quick-start decision-making. → How to tell if you're pivoting too much—or not enough. → Why change should be viewed as a profit opportunity, not a threat. → The biggest mistakes leaders make when reacting to disruption—and how to avoid them. → Why restructuring and scaling have more in common than most think.   Blair LaCorte is a dynamic business executive with a diverse career spanning entertainment, aviation, AI, technology, aerospace, consulting, investing, and military logistics. Raised by entrepreneurs, he has held CEO and C-level roles at major companies like PRG, XOJET/Vista, TPG, Autodesk, and Sun Microsystems/Oracle. Blair has helped lead multiple startups to successful IPOs, including AEye Technologies and VerticalNet. Currently, he is an astronaut-in-training for Virgin Galactic and serves as Vice Chairman of the Buck Institute, a leader in longevity research. He also co-founded and facilitates a Mastermind group of 40 global CEOs. Known for his engaging leadership and strategic vision, Blair has served on nonprofit boards alongside luminaries like Steve Kerr, Phil Jackson, Richard Branson, Elon Musk, and Bill Clinton.   Connect With Blair LaCorte: Website: https://mastermindinnovate.com/ LinkedIn: https://www.linkedin.com/in/blair-lacorte-68084/ Learn more about your ad choices. Visit megaphone.fm/adchoices

BONUS: The Evolution of Agile - From Project Management to Adaptive Intelligence, With Mario Aiello In this BONUS episode, we explore the remarkable journey of Mario Aiello, a veteran agility thinker who has witnessed and shaped the evolution of Agile from its earliest days. Now freshly retired, Mario shares decades of hard-won insights about what works, what doesn't, and where Agile is headed next. This conversation challenges conventional thinking about methodologies, certifications, and what it truly means to be an Agile coach in complex environments. The Early Days: Agilizing Before Agile Had a Name "I came from project management and project management was, for me, was not working. I used to be a wishful liar, basically, because I used to manipulate reports in such a way that would please the listener. I knew it was bullshit." Mario's journey into Agile began around 2001 at Sun Microsystems, where he was already experimenting with iterative approaches while the rest of the world was still firmly planted in traditional project management. Working in Palo Alto, he encountered early adopters discussing Extreme Programming and had an "aha moment" - realizing that concepts like short iterations, feedback loops, and learning could rescue him from the unsustainable madness of traditional project management. He began incorporating these ideas into his work with PRINCE2, calling stages "iterations" and making them as short as possible. His simple agile approach focused on: work on the most important thing first, finish it, then move to the next one, cooperate with each other, and continuously improve. The Trajectory of Agile: From Values to Mechanisms "When the craze of methodologies came about, I started questioning the commercialization and monetization of methodologies. That's where things started to get a little bit complicated because the general focus drifted from values and principles to mechanisms and metrics." Mario describes witnessing three distinct phases in Agile's evolution. The early days were authentic - software developers speaking from the heart about genuine needs for new ways of working. The Agile Manifesto put important truths in front of everyone. However, as methodologies became commercialized, the focus shifted dangerously away from the core values and principles toward prescriptive mechanisms, metrics, and ceremonies. Mario emphasizes that when you focus on values and principles, you discover the purpose behind changing your ways of working. When you focus only on mechanics, you end up just doing things without real purpose - and that's when Agile became a noun, with people trying to "be agile" instead of achieving agility. He's clear that he's not against methodologies like Scrum, XP, SAFe, or LeSS - but rather against their mindless application without understanding the essence behind them. Making Sense Before Methodology: The Four-Fit Framework "Agile for me has to be fit for purpose, fit for context, fit for practice, and I even include a fourth dimension - fit for improvement." Rather than jumping straight to methodology selection, Mario advocates for a sense-making approach. First, understand your purpose - why do you want Agile? Then examine your context - where do you live, how does your company work? Only after making sense of the gap between your current state and where the values and principles suggest you should be, should you choose a methodology. This might mean Scrum for complex environments, or perhaps a flow-based approach for more predictable work, or creating your own hybrid. The key insight is that anyone who understands Agile's principles and values is free to create their own approach - it's fundamentally about plan, do, inspect, and adapt. Learning Through Failure: Context is Paramount "I failed more often than I won. That teaches you - being brave enough to say I failed, I learned, I move on because I'm going to use it better next time." Mario shares pivotal learning moments from his career, including an early attempt to "agilize PRINCE2" in a command-and-control startup environment. While not an ultimate success, this battle taught him that context is paramount and cannot be ignored. You must start by understanding how things are done today - identifying what's good (keep doing it), what's bad (try to improve it), and what's ugly (eradicate it to the extent possible). This lesson shaped his next engagement at a 300-person organization, where he spent nearly five months preparing the organizational context before even introducing Scrum. He started with "simple agile" practices, then took a systems approach to the entire delivery system. A Systems Approach: From Idea to Cash "From the moment sales and marketing people get brilliant ideas they want built, until the team delivers them into production and supports them - all that is a system. You cannot have different parts finger-pointing." Mario challenges the common narrow view of software development systems. Rather than focusing only on prioritization, development, and testing, he advocates for considering everything that influences delivery - from conception through to cash. His approach involved reorganizing an entire office floor, moving away from functional silos (sales here, marketing there, development over there) to value stream-based organization around products. Everyone involved in making work happen, including security, sales, product design, and client understanding, is part of the system. In one transformation, he shifted security from being gatekeepers at the end of the line to strategic partners from day one, embedding security throughout the entire value stream. This comprehensive systems thinking happened before formal Scrum training began. Beyond the Job Description: What Can an Agile Coach Really Do? "I said to some people, I'm not a coach. I'm just somebody that happens to have experience. How can I give something that can help and maybe influence the system?" Mario admits he doesn't qualify as a coach by traditional standards - he has no formal coaching qualifications. His coaching approach comes from decades of Rugby experience and focuses on establishing relationships with teams, understanding where they're going, and helping them make sense of their path forward. He emphasizes adaptive intelligence - the probe, sense, respond cycle. Rather than trying to change everything at once and capsizing the boat, he advocates for challenging one behavior at a time, starting with the most important, encouraging adaptation, and probing quickly to check for impact of specific changes. His role became inviting people to think outside the box, beyond the rigidity of their training and certifications, helping individuals and teams who could then influence the broader system even when organizational change seemed impossible. The Future: Adaptive Intelligence and Making Room for Agile "I'm using a lot of adaptive intelligence these days - probe, sense, respond, learn and adapt. That sequence will take people places." Looking ahead, Mario believes the valuable core of Agile - its values and principles - will remain, but the way we apply them must evolve. He advocates for adaptive intelligence approaches that emphasize sense-making and continuous learning rather than rigid adherence to frameworks. As he enters retirement, Mario is determined to make room for Agile in his new life, seeking ways to give back to the community through his blog, his new Substack "Adaptive Ways," and by inviting others to think differently. He's exploring a "pay as you wish" approach to sharing his experience, recognizing that while he may not be a traditional coach or social media expert, his decades of real-world experience - with its failures and successes - holds value for those still navigating the complexity of organizational change. About Mario Aiello Retired from full-time work, Mario is an agility thinker shaped by real-world complexity, not dogma. With decades in VUCA environments, he blends strategic clarity, emotional intelligence, and creative resilience. He designs context-driven agility, guiding teams and leaders beyond frameworks toward genuine value, adaptive systems, and meaningful transformation. You can link with Mario Aiello on LinkedIn, visit his website at Agile Ways.

In this episode, we sit down with Peter Schein, co-founder and CEO of the Organizational Culture and Leadership Institute, to explore the power of asking the right questions and building open, trusting relationships. Peter, who contributed to the second and third editions of Humble Inquiry: The Gentle Art of Asking Instead of Telling (originally written by his father, Edgar), discusses how curiosity in leadership is more important than ever in today's fast-paced, innovation-driven world. Join us to discover: ·       How to effectively ask open-ended questions to foster trust and curiosity. ·       The key differences between inquiry and interrogation, and why they matter. ·       The transformative power of asking instead of telling. ·       How to navigate and overcome challenges in the modern workplace with humble inquiry. With over 30 years of leadership experience in the technology sector, including roles at Apple, SGI, and Sun Microsystems, Peter brings invaluable insights into organizational culture, leadership development, and communication. His work offers a fresh perspective on leadership, emphasizing trust and inquiry over command and control. Learn more about Peter and his work by visiting his website today! Episode also available on Apple Podcasts: https://apple.co/38oMlMr Keep up with Peter Schein socials here: Facebook: https://www.facebook.com/pschein/  X: https://x.com/scheinocli 

Merriam-Webster's Word of the Day for October 10, 2025 is: obviate • AHB-vee-ayt • verb To obviate something (usually a need for something, or a necessity) is to anticipate and prevent it. A formal word, obviate can also mean "to make an action unnecessary." // The new medical treatment obviates the need for surgery. // Allowing workers flexibility should obviate any objections to the change. See the entry > Examples: "In 1987, a new kind of computer workstation debuted from Sun Microsystems. These workstations, as well as increasingly powerful desktop computers from IBM and Apple, obviated the need for specialized LISP machines. Within a year, the market for LISP machines evaporated." — Jeremy Kahn, Fortune, 3 Sept. 2025 Did you know? It's most often needs that get obviated. And a need that's obviated is a need that's been anticipated and prevented. That sentence may obviate your need to consult the definition again, for example. Obviate comes ultimately from the Latin adjective obviam, meaning "in the way," and obviating does often involve figuratively putting something in the way, as when an explanatory sentence placed just so blocks a need to consult a definition. (Obviam is also an ancestor of our adjective obvious.) Obviate has a number of synonyms in English, including prevent, preclude, and avert, which all can mean "to hinder or stop something." Preclude often implies that a degree of chance was involved in stopping an event, while avert always implies that a bad situation has been anticipated and prevented or deflected by the application of immediate and effective means. Obviate generally suggests the use of intelligence or forethought to ward off trouble.

Blair LaCorte is the Vice Chair of the Board of Directors at the Buck Institute for Research on Aging—the world's first biomedical research institution dedicated solely to understanding aging and age-related diseases, and the largest independent scientific institute in the Bay Area. A seasoned leader and strategist, Blair has a track record of transforming companies across five industries, leveraging his expertise in change management to drive operational alignment, scale, and market leadership. Most recently, he led AEye's $1.5B IPO, advancing the company's mission to enable safe, reliable vehicle autonomy. Prior to that, Blair served as Global President of PRG, the world's largest live event technology and services company; CEO of XOJET, one of the fastest-growing aviation companies in history; and Senior Advisor and Operating Partner at TPG, a leading private equity firm managing over $97 billion in global investments. His earlier career includes executive roles at technology innovators such as VerticalNet, Savi Technologies, Autodesk, and Sun Microsystems. Blair is an active board member and advisor to organizations spanning science, business, and education, including the Positive Coaching Alliance, the Kairos Society, the Graduate Business Foundation, and alma maters Dartmouth College and the University of Maine. His leadership has been recognized by Fast Company, Ad Age, NASA, and the ITAS “100 Most Influential Leaders in Transportation” list. His insights have been featured in Forbes, Fortune, The Wall Street Journal, and on major networks including ABC, Bloomberg, CNN, and CNBC. Holding multiple patents across hardware, software, communications, security, and defense, Blair is also an astronaut-in-training and is scheduled to fly with Virgin Galactic. Outside of his professional pursuits, he is a dedicated father to three sons and the owner of a slightly anxious Weimaraner named Bella. Work With Us: Arétē by RAPID Health Optimization Links: Blair LaCorte on LinkedIn Anders Varner on Instagram Doug Larson on Instagram Coach Travis Mash on Instagram  

Simon Ritter has been in the IT industry for 40 years. He went from university to work on Unix in the early days, employed by AT&T and programming in the C language. In 1996, he switched gears to join Sun Microsystems, programming in Java. Years later, after the Oracle transition, he started to dig into what might be next. Outside of tech, he is married with an older son. He is a complete petro-head - meaning, he is really into cars. In fact, in the last few years, he and his son re-built a classic mini from the ground up.While Simon was at Oracle, he started to crave a different opportunity, but still in the Java space. He stumbled upon a company digging into powering the Java platform, to make it the most secure, efficient and trusted platform on the planet - and he, and the company, found a great fit.This is Simon's creation story at Azul.SponsorsFull ScalePaddle.comSema SoftwarePropelAuthPostmanMeilisearchLinkshttps://www.azul.com/https://www.linkedin.com/in/siritter/Support this podcast at — https://redcircle.com/code-story-insights-from-startup-tech-leaders/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

Join us in this episode as we dive into the art of building open and trusting relationships with Peter Schein. In 2013, Peter's father, Edgar wrote Humble Inquiry: The Gentle Art of Asking Instead of Telling. Since then, Peter has contributed to the second and third edition of the book to bring a fresh perspective on how to see human conversational dynamics and relationships, presented in a compact, personal, and eminently practical way.  Why do we need Humble Inquiry more than ever? Peter sits down to explain… Join in to discover: How to curiously ask people what's going on in their world. The key differences between inquiry and interrogation.  The power of asking instead of telling. How to confidently navigate challenges inherent in today's workplace. Peter is the co-founder and CEO of the Organizational Culture and Leadership Institute in Menlo Park, California. He contributed to the 5th edition of Organizational Culture and Leadership (2017) and brings more than 30 years of experience in the technology sector. His career spans leadership roles in marketing, corporate development, and strategy at both emerging startups and global IT leaders such as Apple, SGI, and Sun Microsystems.  In driving new strategies and integrating smaller ventures into larger enterprises, Peter developed a deep expertise in the organizational and cultural challenges that innovation-driven companies face. Want to learn more about Peter and his work? Click here now!

Andrew Casey remembers a moment when colleagues truly looked to him for leadership. At ServiceNow, a then‑$400 million company with little go‑to‑market infrastructure, the team faced a long list of missing elements: no functioning comp plan, no partner ecosystem, and no clear strategy for scaling sales. “Whenever people said they didn't know how,” Casey recalls, “I started raising my hand and said, I don't know either, but I know what we're going to go do… and then we're going to adjust as we go.” That willingness to lead through uncertainty became a turning point in his career.ServiceNow would grow from $400 million to $4.5 billion during his tenure, and colleagues still use the pricing and deal frameworks he created, he tells us. The experience cemented his approach: chase experiences, not titles, and transform finance into a partner that drives business outcomes.That mindset carried into his first CFO role at WalkMe in 2020, where, just two weeks in, COVID forced an immediate office shutdown. “We didn't even have a work‑from‑home policy,” he tells us. The sudden disruption forced him to navigate crisis management, team alignment, and IPO preparation simultaneously.His journey through Sun Microsystems, Symantec, Oracle, HP, ServiceNow, and Lacework sharpened his ability to guide transformation and scale. Today, as CFO of Amplitude, Casey draws on those lessons to help a smaller public company grow with discipline. Each chapter—from orchestrating 37 acquisitions at Oracle to steering turnarounds—reflects a career built on stepping into complexity, listening first, and leading change with confidence.

Despite being the son of a pharmacist turned wine professional, I did not know the purpose of an Entheogen. Ross Halleck set me straight,so much so, that after defining an entheogen, the value of the consumption of wine became clearer. Ross Halleck doesn't just make wine—he might just ask you to close your eyes and seek the divine within a single glass. In this episode of Wine Talks, you'll be swept past the typical vineyard tales and deep into the spiritual and mystical roots of wine itself. You'll learn how Ross stumbled into the wine trade not through family legacy or grand ambition, but with the curiosity of a seeker and a penchant for unearthing life's mysteries. Paul and Ross unravel why, for some, wine is more than a social lubricant or status symbol; it's an “entheogen”—a conduit to something sacred. Discover how the trappings of wine culture, from magazine scores to over-intellectualization, can miss the magic entirely, and why Ross is on a mission to return wine to its ancient role: bringing people together, not driving them apart. You'll step inside his West Sebastopol vineyard and hear why he believes winning top awards means little if you can't connect with people's hearts. The conversation flows from digital reviews and the democratization of taste, to the pitfalls of marketing wine as pure commerce, to modern-day plant medicine ceremonies designed to foster self-discovery, belonging, and reverence. As the layers peel back, you'll come away with a fresh perspective on wine—not just as a beverage, but as a timeless link to the sacred, the mysterious, and the collective human story. And if you've ever wondered why a certain glass makes you feel something inexplicable, or why wine alone among drinks is revered across cultures and epochs, this episode offers more than an explanation—it offers an invitation to experience the “vine intervention” for yourself. Halleck Vineyard Website: halleckvineyard.com (Ross Halleck's winery, mentioned as halleckvineyard.com under events for wine ceremonies.) Starbucks Website: starbucks.com Hewlett-Packard (HP) Website: hp.com Apple Website: apple.com Sun Microsystems (company no longer independent; acquired, but for historical reference): Website: oracle.com (redirects to Oracle) Wine Spectator Website: winespectator.com Robert Parker/Wine Advocate Website: robertparker.com Wine of the Month Club Website: wineofthemonthclub.com Michelin (Michelin Guide for restaurants) Website: guide.michelin.com Yelp Website: yelp.com Foursquare Website: foursquare.com Kosta Brown  Website: kostabrowne.com Kendall-Jackson Website: kj.com Rombauer Vineyards Website: rombauer.com Cheval Blanc Website: chateau-cheval-blanc.com #wine #winetalks #paulkalemkiarian #rosshalleck #halleckvineyard #winepodcast #wineindustry #pinotnoir #sonomacounty #wineandspirit #wineculture #enthiogen #wineexperience #winelover #winecommunity #wineclub #winemarketing #winepassion #spiritualwine #wineceremony