Podcasts about Microsoft Office

The Blockchain Syndicate: A Contemporary Thriller by Robbie Bach https://www.amazon.com/Blockchain-Syndicate-Contemporary-Thriller/dp/B0F9GYKTL9 https://theblockchainsyndicate.com/ A dead man blackmails a United States senator. A Russian assassin leaves a trail of bodies. A cryptic criminal syndicate unleashes financial chaos. A courageous war hero races to save her family—and her country. Set amid the turbulence of today's headlines, this gripping techno thriller—the second in Bach's series to feature Tamika Smith—pulses with high-stakes intrigue and razor-edged political drama. Senator Tamika Smith's new year begins in shambles. First she receives an email threatening to expose her past—a threat from someone she knows is dead. Then her boyfriend, Johnny Humboldt, is kidnapped in broad daylight after his daughter is wounded in a California school shooting. Someone is desperate to take Tamika down and damage the country she loves. The attacks are professional, the delivery is flawless, and the message unmistakable: America is broken, and someone is determined to fix it their way. Standing in the eye of the storm, Tamika must navigate a political landscape riddled with betrayal, misinformation, and moral decay to rescue Johnny and uncover the group behind the web of conspiracy. As the country spirals toward financial Armageddon and democracy itself begins to unravel, Tamika must decide what she is willing to sacrifice to save her family and pull the nation back from the brink. With its sharp blend of shadowy villains and morally torn heroes, The Blockchain Syndicate dares you to question everything—right up to the final, breathless moment. About the author Robbie Bach is best known for founding and leading the team that created the Xbox. Today he is an entertaining storyteller and catalyzing voice who writes books and speaks to audiences on leadership, creativity, strategy, and civic issues. Robbie joined Microsoft in 1988. Over the next twenty-two years, he worked in various marketing and business management roles—including supporting the successful launch and expansion of Microsoft Office. As Chief Xbox Officer, he led the creation and development of the Xbox business, including the launch of the Xbox, and its highly popular successor, Xbox 360, as well as the Xbox Live gaming platform. Then as Microsoft's President of the Entertainment and Devices Division, he was responsible for the company's worldwide gaming, music, video, phone, and retail sales businesses until he retired in 2010. In his current role as a civic engineer, Robbie works with corporate, philanthropic, and civic organizations to help drive positive change in our communities. He guest-lectures extensively at a variety of colleges and universities and speaks to corporate, civic, nonprofit, and trade association audiences across the country. In 2015, he published his first book, “Xbox Revisited: A Game Plan for Corporate and Civic Renewal.” His first thriller novel, “The Wilkes Insurrection,” was published in 2021. The sequel thriller, “The Blockchain Syndicate” featuring Senator Tamika Smith, was published in 2025.

U.S. Secretatry of State Marco Rubio says a Biden-era switch to the font Calibri — meant to be more accessible to more readers — was another instance of too much focus on DEI. He has ordered a return to Times New Roman, the old Microsoft Office classic. We'll talk about that with Ellen Lupton, the author of a definitive, bestselling book on typographic design.

I don't want to ask what America is thinking, but what are they thinking? As more details of their social media information requests to enter the States came to light yesterday, the less I wanted to go there. To get in I need to supply a wealth of personal information, including DNA and all my social media links. Now I love America and its people, but if I have to jump through all those hoops my first reaction is "forget it". The Land of the Free is no longer the Land of the Free Speech. Say the wrong thing on social media and they may cancel you. This is worse than anything under Biden or Obama, it's cancel culture writ large. And the irony is that it's so dumb. If you're really an enemy of the States, you've already cancelled all your social media. This will cancel the tourists, not the terrorists. Righto: here's the most bonkers thing I heard yesterday out of Trump's America Secretary of State Marco Rubio halted the State Department's official use of the typeface Calibri, calling the Biden-era move “wasteful,” and ordered the return of Times New Roman. He called it a part of a push to stamp out diversity. Now how does that work? Well in 2023, Secretary of State Antony Blinken ordered the typeface change to Calibri to improve accessibility for readers with disabilities, such as low vision and dyslexia, and people who use assistive technologies, such as screen readers. Now that was true, it was invented for people with low vision, and by the way it's Microsoft Office's default font and apparently it works, but apparently that's woke. So back to Times New Roman we go, and the left are saying it tallies with MAGA's obsession with all things Roman. And it would all be just a funny margin in history if it wasn't so expensive and therefore wasteful. You'd think that you'd just ask everyone to change their default and off we go. But no. Teams are going to have to check every little unit. Apparently, that's $145 thousand an agency, and there's a lot of agencies in American bureaucracy. And here's the real rub: Times New Roman takes more ink. And then when you calculate the sheer volume of wordage coming out of the American state, the cost actually mounts into the many millions. The right often complains about the cost of crazy left-wing ideology, seemingly blissfully unaware that they're just as ideologically crazy.See omnystudio.com/listener for privacy information.

This Week In Startups is made possible by:Goldbelly - Goldbelly.comEvery.io - http://every.io/Zite - zite.com/twistToday's show:Today, Zapier's a multi-billion company helping enterprises integrate AI agents and other time-saving shortcuts into their workflows… but we had the founder on TWiST when they were just getting started!In a 2016 chat, founder Wade Foster walked JCal through their 2012 seed round, running a small entirely remote team with no HQ, the complexities of building a tool that relies on third-party APIs, and why Microsoft Office was the “Holy Grail” for his integration software.PLUS we've got a new entrant in your Gamma Pitch Deck competition! Tour CEO/CTO Amulya Parmer tells us how his app is saving property managers time and grief, while eliminating “looky-loos” and increasing their “hit rate.”FINALLY, Alex chats with Tomas Puig of TWiST 500 marketing analysis startup Alembic. It turns out, LLMs aren't ideal for scrutinizing marketing campaigns because they lack the requisite historical data. Find out how they're using Spiking Neural Networks (SNN) to dig deeper than GPT and Claude can go.Timestamps:(02:40) Amulya from Tour opens the show with praise for Jason(03:34) Tour's 2-minute Gamma pitch: automated property tours for managers(06:47) Why Jason thinks Tour is an ideal tool for Gen Z(10:01) Goldbelly - Goldbelly ****ships America's most delicious, iconic foods nationwide! Get 20% off your first order by going to Goldbelly.com and using the promo code TWiST at checkout.(13:32) How Tour can eliminate “looky-loos” and increase the “hit rate”(14:38) Why Tour prices based on individual properties and apartments(19:13) Every.io - For all of your incorporation, banking, payroll, benefits, accounting, taxes or other back-office administration needs, visit every.io.(20:23) Jason wants to sprinkle some AI into Tour(24:29) Welcoming Tomas Puig from Alembic(25:12) Does epic-scale brand marketing actually pay off for these brands?(27:27) The hardest thing about being a marketer…(28:31) Alembic's origins: organizing huge unstructured data sets(30:18) Zite - Zite is the fastest way to build business software with AI. Go to zite.com/twist to get started.(31:27) Case Study: making sense of Delta's Olympics data(33:37) Applying simulation models and supercomputers to marketing data(35:48) How Spiking Neural Networks (SNN) help Alembic spot trends and link causal relationships(41:13) The key advantage of training models on private data(43:16) Building their own clusters vs. renting(44:41) “You don't ask if you have Product Market Fit… You hold on for dear life.”(46:28) Flashback with Alex and Lon to Jason's 2016 chat with Wade Foster of Zapier(54:48) The dangers of building atop other platform's APIs(01:03:00) What Zapier learned pre-pandemic about leading remote teams(01:13:12) Why MS Office was the “Holy Grail” for early ZapierSubscribe to the TWiST500 newsletter: https://ticker.thisweekinstartups.comCheck out the TWIST500: https://www.twist500.comSubscribe to This Week in Startups on Apple: https://rb.gy/v19fcpFollow Lon:X: https://x.com/lonsFollow Alex:X: https://x.com/alexLinkedIn: ⁠https://www.linkedin.com/in/alexwilhelmFollow Jason:X: https://twitter.com/JasonLinkedIn: https://www.linkedin.com/in/jasoncalacanisThank you to our partners:(10:01) Goldbelly - Goldbelly ****ships America's most delicious, iconic foods nationwide! Get 20% off your first order by going to Goldbelly.com and using the promo code TWiST at checkout.(19:13) Every.io - For all of your incorporation, banking, payroll, benefits, accounting, taxes or other back-office administration needs, visit every.io.(30:18) Zite - Zite is the fastest way to build business software with AI. Go to zite.com/twist to get started.Follow TWiST:Twitter: https://twitter.com/TWiStartupsYouTube: https://www.youtube.com/thisweekinInstagram: https://www.instagram.com/thisweekinstartups

In this week's episode, we take a look at six software tools for indie authors to help them write and improve their workflow. This coupon code will get you 50% off the audiobook of Cloak of Blades, Book #4 in the Cloak Mage series, (as excellently narrated by Hollis McCarthy) at my Payhip store: BLADES2025 The coupon code is valid through December 15, 2025. So if you need a new audiobook this winter, we've got you covered! TRANSCRIPT [This episode's content is not sponsored. Jonathan has not received any compensation for these reviews and has not received any free products or services from the companies mentioned in this episode. He does not currently use affiliate links for the products mentioned.] 00:00:00 Introduction and Writing Updates Hello, everyone. Welcome to Episode 280 of The Pulp Writer Show. My name is Jonathan Moeller. Today is a very snowy December 5th, 2025, and today I'm discussing six software tools that are useful for indie authors. Before we get into that, we will have Coupon of the Week and then an update on my current writing, publishing, and audiobook projects. So first up, Coupon of the Week. This week's coupon code will get you 50% off the audiobook of Cloak of Blades, Book #4 in the Cloak Mage series (as excellently narrated by Hollis McCarthy), at my Payhip store. And that is BLADES2025. And as always, the coupon code and the link to my Payhip store will be available in the show notes for this episode. This coupon code will be valid through December the 15th, 2025. So if you need a new audiobook for this winter or for your Christmas travels, we have got you covered. And now for an update on my current writing and publishing projects. As I mentioned last week, Blade of Shadows is out and it's available at Amazon, Barnes and Noble, Kobo, Google Play, Apple Books, Smashwords, and my Payhip store, and it's been doing quite well and gotten a good response from everyone. So thank you for that and I am looking forward to continuing that series. Now that Blade of Shadows is done, my main project is the fifth book in the Half-Elven Thief series, which is Wizard-Assassin. I had originally planned to name it Elven-Assassin, but decided Wizard-Assassin sounded a bit punchier, so I went with that instead. I am 46,000 words into it, which puts me on chapter 10 of 16. The final draft will have more chapters because one of the chapters is 11,000 words. I'm going to have to cut it up. I've also noticed that readers in general these days seem to prefer shorter chapters, so I've been trying to lean more into doing that and having books with shorter chapters. I think the rough draft is going to be about 70 to 75,000 words, give or take. So I'm hoping I can finish that next week, and I am cautiously optimistic I can have the book published before Christmas. If I can't get it published before Christmas, it is going to slip to my first book of 2026. But at the moment, and of course, barring our old unwelcome friend unexpected developments, I am cautiously optimistic I can have it out by Christmas 2025. So watch my website and listen to this space for additional news. My secondary project is Blade of Storms, which will be the third book in the Blades of Ruin series and the direct sequel to Blade of Shadows. I am about 6,000 words into that, and once Wizard-Assassin is done, that will be my main project. I'm hoping to have that out at the end of January, but if Wizard-Assassin slips to January, then Blade of Storms will [of necessity] slip to February. In audiobook news, Blade of Flames, the audiobook of the first book in the Blades of Ruin series, is now out and you can get that at Audible, Amazon, Apple, Kobo, Google Play, my own Payhip store, Spotify, and all the other usual audiobook stores. So if you're looking for something else to listen to during your Christmas travels this year, I suggest checking out Blade of Flames (as excellently narrated by Brad Wills). Cloak of the Embers, the 10th book in the Cloak Mage series (as excellently narrated by Hollis McCarthy)…the recording of that is done and it is being proofed right now, so I am hopeful we can hopefully have that out before Christmas (if all goes well). In fact, after I record this podcast episode, I'm going to have to convert the ebook cover of Cloak of Embers into an audiobook cover for Cloak of Embers. So that is where I'm at with my current writing and publishing projects. There is definitely a lot going on. 00:03:40 Main Topic: 6 Helpful Writing Tools for Indie Authors in 2025 [All Prices referenced are USD.] Now we're going to move on to our main topic this week, which is six helpful writing tools for indie authors in 2025. Last year in 2024, I did a roundup of popular software tools for writers and I thought I would give a quick update for it. Some of these tools like Calibre and LibreOffice I use, while others like Scrivener and Notion just aren't great fit for my workflow, I still want to talk about them anyways since just because I don't use them doesn't mean that they're not good and a lot of writers do in fact use them. Many writers also have complex systems for organizing their files and would benefit from tools like that. Without further ado, here are six pieces of software used for writing and writing adjacent tasks. I should mention before we get going as well that none of these tools are explicitly generative AI tools because as you know, if you've listened to the podcast over the years is my opinion of generative AI remains mostly negative. I have and continue to do some marketing experiments with generative AI elements, but I remain overall unimpressed by the technology. So with that in mind, none of these software tools I'm going to mention are explicitly AI tools. Some of them do have AI elements that you can plug in and use if you want to, but they aren't part of the core functionality of the application unless you specifically seek it out. With that in mind, let's get to it. #1: The first one we will talk about is Scrivener. Scrivener is of course essentially a word processor and project management system specifically designed for creative or nonfiction writing, unlike a traditional word processor like Microsoft Word, LibreOffice Writer, or Apple Pages. It features tools for outlining, for breaking documents into chapters, tracking word count goals and et cetera. One of the major benefits of it is a one-time cost instead of as a subscription because it seems like everything is a subscription nowadays, but Scrivener is still $60 a pop. They also offer a free trial and student discount and occasionally [it will] go on sale during peak times like the holidays. The downside of this is that Scrivener has a sharp learning curve. For myself when I write, I write either in Microsoft Word or Libre Office and I just sit down and write. When I write an outline, it's one Word document and the rough draft is another document that I write until I'm done. Scrivener is definitely a more complex software application, which I have to admit is funny to say because Microsoft Word is ridiculously complicated and has, in my opinion, far more functionality stuffed into it than it really needs. But Scrivener is a different kind of functionality and therefore the learning curve could be quite high for that. Additionally, this may not be the right software tool to work with your style of writing or how you organize your files. A couple extra thoughts with that is it's important to know yourself. Will you actually use the extra features included with Scrivener or do they just look cool and shiny? Scrivener probably is best for those who take extensive notes on their work, especially if trying to organize research based on chapters where it's needed. So if you're a nonfiction writer or if you're a historical fiction writer or a thriller writer who is very concerned about accuracy in your books, this may be useful for you so you can put in notes about the proper way to address a duke in 19th century England or what caliber of ammunition your thriller hero's preferred firearm takes. It's maybe the best for the kind of people who enjoy curating their Notion and Trello accounts and are able to think about their book in a very visual way without letting that process be an excuse to keep them from writing. I'd also say it's good for people who extensively revise blocks of text within a chapter and move chapters around a lot. #2: Canva. Canva has been around for a long time and it is a platform that makes it easy to create visual content using a drag and drop interface that provides a variety of templates, fonts, and designs to use for things like social media posts. They currently have two tiers for individuals, a limited free option, and Canva Pro, which is $12.99 a month. Some of the pros for Canva are it is well-suited for using templates for writers to create images for social media posts and book marketing material. The learning curve is not very steep, especially compared with something like Photoshop. If you've used PowerPoint before, you can definitely handle Canva. The cons: although some people use it to create book covers, many books have been flagged by Kindle Direct Publishing (KDP) and some of the other publishing platforms for doing so. I would advise you to avoid Canva for creating book covers because of the potential for issues that could keep your book out of ebook stores. At the very least, read Canva's terms of use and the rules of KDP and the other ebook publishers very, very carefully before you would even begin to consider using Canva for this purpose. Many of the free features have been folded into the pro version such as sharing template links. The editing and design features are basic compared to something like Photoshop, though that may change as we're going to discuss a little bit here. Because Canva is so popular, there's a certain amount of snobbery out there about using its designs without significant modification. You may have encountered on social media or the Internet people who react very negatively to the presence of AI generated images and this exists to a lesser extent with Canva templates. "Looks like it was made in Canva" is sometimes used as an insult. If you want a unique style and look for your images, you'll have to work a little more to achieve that using Canva. Canva is quick for great one-time things like Facebook or BookBub ads, but I wouldn't recommend using it for book creation or book covers at this time because of the potential problems that can arise from that. For myself, I don't usually use Canva. I've had enough practice with Photoshop that I'm pretty confident in making whatever I want in terms of ad images or book covers in Photoshop, and I use Photoshop for that. However, since I organized the notes for this episode, there is a major caveat to that. Recently, Canva acquired a program called Affinity Photo Editor, which is essentially a much lower cost alternative to Photoshop. When this happened, there was a great deal of negativity around it because people thought Canva was going to jack up the price or make it into an overpriced subscription. But what Canva did surprised a great many people in that they made Affinity totally free and essentially are using a freemium model with it where you can use Affinity Photo Editor for free. It used to be, I believe like $79, possibly $69, and then any of the other features like downloading additional content from Canva would cost part of your Canva subscription. So I have to admit, I'm sufficiently curious about this, that when I write the tie in short story for Wizard-Assassin, I may use Affinity Photo Editor to assemble the cover for it just to see if it would work for that or not, because as I've said, I use Photoshop, but Photoshop is very expensive, Adobe frequently does business practices that are a bit shifty, and the idea of a freemium alternative to Photoshop is not necessarily a bad idea. So when I write a tie in short story for Wizard-Assassin later this month, I think I will attempt to make the cover in Affinity Photo Editor and see if that is something that would be good for my workflow or not, and I will report on that later. #3: Number three is Notion, which can be used to organize information, links, calendars, and reminders into one central dashboard. They have two plans for individuals, a free plan and a Plus plan, which is currently $10 to $12 per month (depending on whether you want a monthly or an annual plan). The Plus version offers unlimited file uploads, greater customizations, and integrations with Slack and Google Drive. The pros for using Notion is that it is popular with writers and content creators for being able to have project planning tools, notes, lists, links, trackers, and reminders all in one dashboard. If you enjoy customization and getting something set up exactly the way you want, you might enjoy setting up your lists, calendars, trackers, and notes through Notion. You can add images and adjust the layout and colors for a more "aesthetic" experience. It is easy to find customized templates [online], especially for writers and for things like storyboarding, word counts, and keeping tracks of sources for nonfiction writing. These Notion templates are shared by individuals, not the company and can be free or paid. Now, some of the cons with Notion. It didn't used to use very much AI, but the company is leaning increasingly heavy into AI, both as a company and in its features on the boards, if that is a concern. The amount of customization options and detail can be absolutely overwhelming. Someone who gets decision fatigue easily or doesn't want to customize a lot and might not enjoy using it. Some people are increasingly complaining that the software is getting too overloaded with features and is slow. For people who value being organized and love having complex and highly visual systems, Notion might be helpful. The downside is that maintaining your Notion boards can easily turn into what I call a "writing-adjacent activity" that gives you the illusion of productivity because of the time you spend managing and updating it aside from the business of getting actual writing done. So once again, this is a good example of "know thyself." If this is something that would be helpful for you, go ahead and pursue it. But if it's something that could turn into a tool for procrastination, it's probably better to avoid it. For myself, I am old enough that when I need to make lists and keep track of things, I have a yellow legal pad on my desk that I write things down on. #4: The next piece of software we're going to look at is LibreOffice. It is an open source piece of software that closely matches Microsoft Office, including Microsoft Word. Pros: It's free and open source. There's a minimal learning curve for those already familiar with Microsoft Word. The interface is a little different, but it's pretty easy to figure things out if you're familiar with Word or Excel. Some swear that that LibreOffice is faster than Word. It depends on the kind of document you're working on and the kind of computer you're using. So that's an area where your mileage may vary. It is also the best word processing option for privacy advocates, especially for those who are concerned about Microsoft and Google storing their work and possibly harvesting it for AI because by default, LibreOffice doesn't work with any AI elements. If you want it to work with any AI elements, plugins are available but they are not included. It's great for the writer who doesn't want to support Microsoft for any reason but still wants to be able to easily save documents in Microsoft file formats like .docx. It works. I've written entire books using it. I wrote all of Soul of Serpents and Soul of Dragons in it, and that was 13 years ago now, and the software has only improved since then. I wrote Silent Order: Eclipse Hand [using it] in 2017 and was very happy with the results, and I still use it for various projects every week, and I found a couple times if something was screwed up in the formatting of Microsoft Word, if I opened it up in LibreOffice, I could fix it pretty easily and much easier than I could in Word. It does have a few cons. The user interface compared to Word or something like Apple Pages does look a bit dated, but it's still navigable. It doesn't have any cloud storage functionality. You would need to piece it together with another storage option if you want to be able to backup stuff to the cloud. But overall, if you can't afford the Microsoft Office Suite, don't want to support Microsoft, and value your privacy, this is your best bet for word processing. Some people may not like its interface, but it's still an extremely solid piece of free software. #5: And now let's move on to our fifth software tool, which is Calibre. Calibre is a tool for ebook management. It can be used for file formatting, changing your books' metadata, or changing file formats. Many use it to create a custom ebook library. Pros include: the product is free and open source. It is easy to generate different file formats for book publication. Do you want to categorize and organize your books in a very specific way? Calibre works for that. The cons: some people find the interface a little clunky and it comes with a bit of a learning curve. To be honest, the interface does look like it came from Windows 2000 and some of the features rely on knowledge of HTML and CSS. Editing and formatting of the book itself is better done using other software. Final thoughts on that? The software is trustworthy, reliable, and has been maintained over the years. It does exactly what it says it does, without any real style but plenty of substance. And I've been a regular Calibre user for like 15 years now, and whenever I get a new computer Calibre is usually one of the very first things I install on it. #6: And now for our sixth and final tool, Inkarnate. Inkarnate is a very useful piece of software that is designed for creating maps. I believe it was originally intended to create maps for role-playing games like Dungeons and Dragons and Pathfinder and so forth. But it's also very useful for creating maps for fantasy novels. As I may have mentioned on the podcast a few times before, I really don't like making maps. I find it constraining and it makes the writing feel a bit crabbed at times. That said, I write primarily in the fantasy genre and people in the fantasy genre love maps, so I'm kind of on the hook for making maps. I used to draw the maps by hand and then import it into Photoshop and add all the locations and add colors and so forth. But that is a lot of work, I have to admit. Inkarnate makes it a lot easier, and I've used it for the last couple of maps I've made. The map of the city of Tar-Carmatheion in the Half-Elven Thief books came from Inkarnate. The map of Owyllain for Blades of Ruin came from Inkarnate, and the map of New Kyre and adjoining regions for Ghost Armor also came from Inkarnate. It's very affordable too. The subscription, I believe, is only $30 a year, and I've been using for a few years now and have never regretted it. So I'd say all the pros are all the ones I've already listed. The cons are that the learning curve is a little bit sharp, but there are excellent YouTube videos and tutorials for that. So, final thoughts. If you find yourself needing to make maps and don't enjoy the process of making maps, then Inkarnate is the software product for you. So those are six tools, software tools for indie authors that I hope will make you more productive and make your work easier. So that is it for this week. Thank you for listening to the Pulp Writer Show. I hope you found the show useful. A reminder that you can listen to all the backup episodes at https://thepulpwritershow.com. If you enjoyed the podcast, please leave your review on your podcasting platform of choice. Stay safe and stay healthy and see you all next week.  

This week's episode is a full ride — from raging at Microsoft Office subscriptions, to questioning why politicians love “executive sessions,” to discovering Jim's newest life hack: drinking hot water like it's a religion. We also dive into a spicy Malibag about exes, boundaries, and why you deserve more than being someone's “escape.”It's messy, it's honest, and it's very us.Send letters to jimandsaab.com/malibag

Hannah Murray will start by looking at the bestseller lists on Amazon.co.uk and The Sunday Times, the oldest and most influential book sales chart in the UK, and seeing what new entries there are. Carolyn Kirby is an award-winning novelist who studied at Oxford University. Her latest novel 'Ravenglass' plunges the reader into a turbulent 18th century adventure over land and sea.  Tim Robinson was a BBC Director and producer, asking many documentaries. He now divides his time between Camden Town and Andalucia. 'The Difficult Life' is a haunting tale of love, art and madness. It's about talented painter Lucy Lake, who questions her sanity as she navigates the complexities of her marriage to Morten Andersen, a man haunted by his past, and the ex-wife whose soul remains to haunt them both.  Jamie Mustard is an artist, a futurist, and a writer with a focus on perception in the physical world. Growing up in severe poverty and illiteracy in inner city Los Angeles, Jamie now works as a strategic multi-media consultant. 'Hybred' is a graphic novel about childhood poverty, co-written with Francesca Filomena. Set in a future-adjacent Los Angeles, it's a story of staggering poverty, drugs and violence, and of an artistic child who finds beauty in the ugly and sublime hope in our conflicts.  ... James Campbell is married to E.H.Shepherd's great-granddaughter and has had responsibility for the oversight of E.H. Shepard's artistic and literary estate since 2010. 'The Men Who Created Winnie-The-Pooh' looks at the lives of author A.A.Milne and his illustrator E.H.Shepard. In celebration of 100 years of Winnie-The-Pooh, this beautiful books looks at the men behind the creation of the much-loved characters. Robbie Bach joined Microsoft in 1988. Over the next twenty-two years, he worked in various roles including supporting the successful launch and expansion of Microsoft Office. As Chief Xbox officer, he led the creation and development of the Xbox business. He retired from Microsoft as the president of the Entertainment and Devices Division in 2010. His debut novel 'The Wilkes Insurrection' introduced readers to Senator Tamika Smith. His latest 'The Blockchain Syndicate' follows Tamika as she faces a cryptic criminal syndicate threatening America's financial and political foundations.  William Coles has been a journalist for 30 years and has worked for a number of papers including The Sun, The Express, The Mail and The Wall Street Journal. His latest novel 'Movie Rogue' is based on the true story of how in 1996 a Sun reporter became an extra in one of the most searingly graphic scenes in movie history. Along the way - it's said - he also befriended both Tom Cruise and Stanley Kubrick.  Julie Caplin is the international bestselling author of the Romantic Escapes series. Her uplifting romantic comedies are set in gorgeous destinations across the globe, providing her readers with the ultimate escape. 'Christmas on Fifth Avenue' sees Evie Green's Christmas dream turn into a nightmare when a viral video makes her the laughing stock of the internet.

EP 269. In this week's update:Organized crime syndicates are now recruiting skilled hackers to orchestrate sophisticated digital hijackings of entire truckloads of high-value cargo.A bizarre Windows preview update has turned the password field invisible, leaving Microsoft advising users to blindly click where the button once appeared.Australia's $62 million weather-service overhaul launched on one of the hottest days of the year—only to deliver a slower, less functional site that enraged farmers and the public alike.The FTC has slammed edtech provider Illuminate Education for egregious security failures that allowed a single hacker to steal sensitive records of over 10 million students.A startling new study reveals that simply rearranging sentence syntax—not content—can trick major language models into ignoring their own safety guardrails.The company behind America's sprawling network of AI-powered license-plate cameras quietly relies on low-wage overseas freelancers to label footage of U.S. drivers and pedestrians.In a major blow to cybercrime, Europol and partners have seized servers, €25 million in Bitcoin, and shut down one of the world's largest cryptocurrency money-laundering services.European Parliament members are demanding the institution ditch Microsoft Office 365 and U.S. hardware in favor of homegrown alternatives to reclaim digital sovereignty.Let's jump in the cab and take this week's rig for an adventure!Find the full transcript to this week's podcast here.

Hello and welcome to The Rob Burgess Show. I am, of course, your host, Rob Burgess. On this our 288th episode, our guest is Robbie Bach. Robbie Bach is a bestselling author and former tech executive who helped lead Microsoft through some of its most dynamic years. As the Chief Xbox Officer, he spearheaded the creation of the iconic Xbox and Xbox 360. After retiring from Microsoft, he shifted his focus to philanthropy, civic advocacy and storytelling. Robbie Bach joined Microsoft in 1988. Over the next 22 years, he worked in various marketing, general management and business leadership roles, including supporting the successful launch and expansion of Microsoft Office. As Chief Xbox Officer, he led the creation and development of the Xbox business, including the launch of the Xbox and its highly popular successor, the Xbox 360. He retired from Microsoft as the president of the Entertainment and Devices Division in 2010. In his new role as a civic engineer, Robbie works with corporate, philanthropic and civic organizations that are driving positive change in our communities. He guest lectures extensively at various colleges and universities and speaks to corporate, civic and trade association audiences across the country. In 2015, he published his first book, “Xbox Revisited: A Game Plan for Corporate and Civic Renewal.” His debut novel featuring Tamika Smith, “The Wilkes Insurrection,” was published in 2021. He is the former chairman and current board member at the Bipartisan Policy Center. He serves on the national board of governors for Boys and Girls Clubs of America and was the chairman of that board from 2009 to 2011. He is also a board member for Habitat for Humanity International and Genius Sports. He previously served as a board member of the United States Olympic and Paralympic Committee, Sonos, Brooks Running Company, the Space Needle, Magic Leap and Year Up Puget Sound. He is the co-owner of Manini's, a company specializing in gluten-free foods. He was an Arjay Miller Scholar at the Stanford Graduate School of Business, where he earned his MBA, and a Morehead Scholar at the University of North Carolina, where he earned his degree in economics. He and his wife, Pauline, reside in Washington state, with their yellow lab, Roscoe. They have three grown children and two grandchildren. His first novel, “The Wilkes Insurrection,” introduced readers to Senator Tamika Smith in a high-stakes battle against a domestic terror conspiracy. In his latest novel, “The Blockchain Syndicate,” Bach continues the gripping saga as Tamika faces a cryptic criminal syndicate threatening America's financial and political foundations. Follow me on Mastodon: newsie.social/@therobburgessshow Check out my Linktree: linktr.ee/therobburgessshow Follow me on Bluesky: bsky.app/profile/robaburg.bsky.social

From flying to online shopping to using social media, everything seems to be getting worse. It's all — pardon our language here — shittier. According to today's Lever Time guest, that's no accident. Cory Doctorow is the author of Enshittification: Why Everything Suddenly Got Worse and What to Do About It. In this episode, Doctorow explains how enshittification works, how it's infected our online spaces, and what we can do to stop it. Plus, as an exclusive bonus to our paid subscribers, click here for the rest of David's conversation with Cory Doctorow. They talk about why Americans are trapped on Facebook or Microsoft Office and how Donald Trump is using tech companies as weapons in his trade war. Doctorow also offers a few simple solutions to stop our world from going to shit. Not yet a paid subscriber? Click here for a special membership offer exclusive to Lever Time listeners. To leave a tip for The Lever, ⁠click here⁠. It helps us do this kind of independent journalism. ⁠Click here⁠⁠ for a transcript of this episode. Learn more about your ad choices. Visit megaphone.fm/adchoices

Vanaf volgend jaar kunnen Nederlandse onderwijs- en onderzoeksinstellingen experimenteren met het Duitse samenwerkingsplatform Nextcloud, een Europees alternatief voor diensten van Amerikaanse techbedrijven zoals Google en Microsoft. De Nederlandse ICT-coöperatie SURF maakt dat mogelijk door het platform breed beschikbaar te stellen binnen het hoger onderwijs en onderzoeksdomein. SURF, dat verantwoordelijk is voor de ICT-diensten van universiteiten, hogescholen en onderzoeksinstellingen, voerde het afgelopen jaar al enkele kleinere pilots uit met Nextcloud. Die proefperiode is volgens de organisatie positief verlopen. Daarom wil SURF nu op grotere schaal ervaring opdoen, door instellingen aan te moedigen het platform intern te testen. Zo moet duidelijk worden hoe teams in de praktijk kunnen samenwerken en of Nextcloud een volwaardig alternatief kan zijn voor bestaande platforms. Nextcloud biedt functionaliteiten die vergelijkbaar zijn met diensten die veel instellingen nu gebruiken, zoals clouddiensten, e-mail, videobellen en online documentbewerking. Daarmee bestrijkt het vrijwel dezelfde basistaken als Word, Excel, Gmail en Google Docs. Het platform wordt in eerste instantie een jaar lang naast de bestaande Amerikaanse oplossingen aangeboden. Uit een recente interessepeiling van SURF blijkt dat er brede belangstelling is voor het gebruik van Nextcloud. Meerdere universiteiten, hogescholen, umc’s en onderzoeksinstellingen hebben zich gemeld om mee te doen met de testfase. Volgens SURF groeit het draagvlak voor een Europees platform, omdat de afhankelijkheid van Amerikaanse techbedrijven steeds meer als een risico wordt gezien. Een volledig Nederlands alternatief is er vooralsnog niet, maar met Nextcloud lijkt Europa in elk geval een serieuze optie in handen te hebben.See omnystudio.com/listener for privacy information.

L’Etat français est-il toujours souverain, c’est la question que l’on peut se poser pour plusieurs raisons. Souveraineté numérique de la France L’intégration de la France dans l’ensemble européen impose de renoncer à des compétences régaliennes. Le niveau de dette rend la politique française dépendante de ses créanciers. Mais le destin numérique de la France est-il bien protégé. Un rapport récent de la cour des comptes nous éclaire sur ce sujet. L’Etat français est-il toujours souverain On imagine que l’État protège jalousement ses données les plus sensibles, les enfermant dans des forteresses numériques impénétrables. La souveraineté numérique est devenue un mot d’ordre politique, une promesse de contrôle et d’indépendance face aux géants technologiques étrangers. Ceux que l’on nomme les GAFAM. Le paradoxe standard du marché ou souveraineté Il faut garder en tête que les standard du marché sont américains et ensuite Chinois. L’Europe arrive ensuite en ordre dispersé. Sur le plan analytique, il existe une tension concernant la politique numérique française : d’un côté, l’ambition affichée de souveraineté ; de l’autre, le besoin des administrations de disposer d’outils performants, modernes et à un coût maîtrisé. J’ajoute aussi que les agents de l’Etat veulent utiliser des outils qu’ils connaissent car ils ont été formés dessus avec ou en disposent chez eux. Bien souvent, c’est le second impératif qui l’emporte. Le cas le plus notable est celui du nouveau système d’information de ressources humaines du ministère de l’Éducation nationale, Virtuo, pour lequel le ministère a choisi une solution cloud opérée par une entreprise américaine. Ce choix a été fait en passant outre les recommandations initiales de la doctrine “Cloud au centre”, car aucune offre souveraine ne répondait aux exigences de performance et de coût. Le ministère estime a posteriori que sa décision est conforme à la version finale de la loi SREN, qui a restreint le champ d’application de l’obligation de souveraineté en exigeant non seulement que les données soient sensibles, mais aussi que leur violation présente un risque direct pour l’ordre public. Quand la loi se met elle même une balle dans le pied et fait de la vertu un vice. Circulaire Cloud au centre Revenons sur ce texte important, la circulaire cloud au centre. La doctrine « Cloud au centre » est une orientation édictée par le Premier ministre pour que les administrations privilégient les infrastructures cloud (informatique en nuage) pour leurs nouveaux projets numériques. Le cloud est appelé à devenir l'environnement par défaut de tout nouveau projet informatique de l’État. Cette doctrine est la déclinaison opérationnelle de la Stratégie nationale pour le cloud lancée en mai 2021, qui vise à encourager l’utilisation du cloud tout en assurant l’autonomie de l’État, la maîtrise de ses données et le respect des règles européennes en matière de protection des données à caractère personnel. Version de juillet 2021 : La première version de la circulaire, diffusée en juillet 2021, stipulait que toute application manipulant des données d'une sensibilité particulière, notamment les données personnelles des citoyens français, devait être hébergée sur une infrastructure souveraine. Voir mon article sur ce sujet ici Version de mai 2023 : La doctrine a été mise à jour en mai 2023 (circulaire n° 6404/SG). Cette version a restreint l'obligation de recourir à une offre souveraine, ne l’exigeant que lorsque deux critères sont cumulativement observés : Les données doivent relever de secrets protégés par la loi. Leur violation doit être susceptible « d'engendrer une atteinte à l'ordre public, à la sécurité publique, à la santé et à la vie des personnes, ou à la protection de la propriété intellectuelle ». Voilà comment faire entrer le loup dans la bergerie. Loi SREN : Ces critères cumulatifs ont été élevés au niveau législatif par l’Article 31 de la loi du 21 mai 2024 visant à sécuriser et à réguler l'espace numérique (dite loi SREN). La restriction du champ d’application de cette obligation visait notamment à consolider la doctrine sur le plan juridique en limitant les risques de recours par des opérateurs étrangers au regard des règles du marché intérieur européen et du principe de non-discrimination de l'OMC. Le Cloud de confiance et SecNumCloud Le concept de « cloud de confiance » remplace la notion initiale de « cloud souverain ». Il repose sur deux solutions jugées équivalentes en termes de sécurité pour les données sensibles : Les clouds internes de l'État (dits du 1er cercle), comme Nubo (opéré par la DGFiP) et Pi (opéré par le ministère de l'Intérieur). Les offres commerciales qualifiées SecNumCloud. La qualification SecNumCloud est un référentiel d'exigences techniques, opérationnelles et juridiques élaboré par l'Agence nationale de la sécurité des systèmes d'information (Anssi). Il garantit le plus haut niveau de sécurité pour les services de l'État et les opérateurs d'importance vitale (OIV). Un apport essentiel de ce référentiel est l’accent mis sur la souveraineté. Il garantit une immunité aux lois non européennes à portée extraterritoriale, telles que le Cloud Act ou le Foreign Intelligence Surveillance Act (Fisa) américain. Cela impose notamment que le siège social du prestataire soit situé dans l'Union européenne et qu’une entité non européenne ne détienne pas, à elle seule, plus de 24 % du capital et des droits de vote du prestataire. Les limites de la mise en œuvre Cloud au centre Malgré l’ambition politique affichée, la mise en œuvre de la doctrine « Cloud au centre » rencontre des difficultés. Bien que la commande publique en services cloud soit passée de 1 M€ en 2020 à 52 M€ en 2024, atteignant 120 M€ au total sur cette période, cela reste très modeste par rapport aux dépenses informatiques annuelles de l'État, de l'ordre de 3 Md€. De plus, le recours aux solutions qualifiées SecNumCloud induit un surcoût par rapport aux offres cloud non qualifiées, estimé entre +25 % et +40 %. Ce point est à challenger car, pour avoir fait le travail de passer tout une entreprise SECNUMCLOUD, cela à pu être fait à ISO cout en partant d’un système déjà Cloud. C’est sur que si on part de On premise, on a ce surcout. Mais on ne compare pas la même solution. Cloud au centre L'échec des clouds internes Face à la domination des géants américains, l’État a tenté de construire ses propres solutions Cloud souverain. Deux clouds interministériels ont ainsi vu le jour : Nubo, porté par le ministère des Finances, et Pi, porté par celui de l’Intérieur. L’ambition était de fournir une alternative sûre et maîtrisée pour les données les plus sensibles. La réalité est cependant bien loin des ambitions affichées. Les chiffres sont sans appel : “la part d'interministériel pour les clouds Pi et Nubo plafonne à 5 %”. En clair, ces solutions sont très peu utilisées en dehors des ministères qui les ont créées. La raison principale ? Un sous-investissement chronique. Le rapport note que Nubo a coûté 55 millions d’euros en neuf ans, une somme modeste au regard des dépenses numériques annuelles de l’État qui s’élèvent à environ 3 milliards d’euros. En conséquence, la gamme de services offerts reste limitée et la tarification est jugée inadaptée. Cet échec à attirer les utilisateurs empêche Nubo et Pi d’atteindre la “taille critique” nécessaire pour justifier de nouveaux investissements, créant ainsi un cercle vicieux de sous-performance et de sous-utilisation qui les rend non compétitifs. Peut être aussi la stratégie n’est pas bonne de vouloir créer son propose cloud plutôt qu’externaliser cela à un hyperscaler souverain qui pourra mutualiser les couts. La souveraineté SECNUMCLOUD un coût : jusqu’à 40 % plus cher Qu’est-ce qu’une solution numérique “vraiment” souveraine ? En France, le plus haut standard est défini par la qualification SecNumCloud, délivrée par l’Agence nationale de la sécurité des systèmes d’information (ANSSI). Ce label garantit non seulement un très haut niveau de sécurité technique, mais aussi une immunité juridique contre les lois extraterritoriales, comme le fameux Cloud Act américain. Cette loi qui permet aux autorités américaines de contraindre les fournisseurs de services américains à livrer des données, où qu’elles soient stockées dans le monde. Services secnumcloud Cette garantie a un prix. Le rapport de la Cour des comptes met un chiffre précis sur ce coût, une donnée rarement rendue publique : le surcoût d’une infrastructure qualifiée SecNumCloud par rapport à une offre cloud traditionnelle est estimé “entre +25 et +40 %”. De nouveau, je pense que ce montant est un maximum et que en faisant appels à un hyperscaler et en optimisant, on peut le faire à iso cout. Marché public cloud Vos logiciels de bureautiques sont un enjeu stratégique majeur D’un point de vue politique, le débat sur la souveraineté devient le plus tangible lorsqu’il touche aux outils quotidiens des agents publics. Exemple très concret des suites bureautiques pour illustrer ce défi. La dépendance historique de l’administration française à la suite Microsoft Office est devenue un problème stratégique lorsque l’entreprise a commencé à pousser agressivement son offre cloud, Microsoft 365. Face à ce mouvement, la Direction interministérielle du numérique (DINUM) a demandé aux ministères de ne pas y souscrire, afin de protéger la souveraineté des communications électroniques. La réponse de l’État a été pour le moins fragmentée. D’un côté, le ministère de l’Éducation nationale, le plus grand employeur de France, a entrepris de remplacer la suite Office par une solution basée sur un logiciel libre (Collabora Online). De l’autre, la DINUM, l’autorité numérique de l’État, développe sa propre alternative (“La Suite”) en coopération avec l’Allemagne et les Pays-Bas. Cette divergence entre le plus grand ministère et l’autorité interministérielle illustre un manque de stratégie unifiée, même sur un sujet aussi fondamental que l’outil de travail quotidien de ses agents. La France, une voix isolée dans la bataille pour la souveraineté en Europe Le combat pour la souveraineté numérique ne se joue pas seulement à l’échelle nationale. C’est au niveau européen que se dessinent les règles du jeu, et sur ce terrain, la France peine à imposer sa vision exigeante. Le cas du projet de certification européen des services cloud (EUCS) est emblématique. La France a plaidé pour y inclure un niveau de sécurité maximal, inspiré de son propre label SecNumCloud, afin de garantir une immunité totale face aux lois extraterritoriales. La conclusion de la Cour des comptes est sans équivoque : “La démarche de la France est restée jusqu'à présent isolée au sein de l'UE.” Cet isolement n’est pas purement idéologique ; il est alimenté par de dures réalités économiques. Comme le note le rapport, la position de l’Allemagne s’est considérablement assouplie après l’annonce par Amazon Web Services d’un investissement de 7,8 milliards d’euros dans un cloud “souverain” sur son territoire, démontrant comment la puissance d’investissement des géants américains de la tech peut directement influencer la politique européenne. La quête de souveraineté numérique de la France n’est pas une stratégie assez coordonnée. Comme souvent c’est une série de compromis tactiques où la performance prime sur le principe, où les solutions internes échouent à se déployer à l’échelle, et où l’ambition européenne est contrecarrée par la réalité économique. Le parfait exercice des missions de service public peut être garanti sans nécessairement aligner les spécifications des systèmes d'information sur le plus haut niveau technologique dès lors qu'un degré trop élevé de performance à court terme peut constituer un double écueil : par la mise en cause de la souveraineté sur les données et par une dépendance de l'administration vis-à-vis de la politique commerciale d'un éditeur dominant.The post L'Etat français est-il toujours souverain ? first appeared on XY Magazine.

You know that preparing students for the contemporary workforce looks dramatically different than it did even a few years ago. Today's students need to be prepared to succeed in an even more demanding environment.  We sat down with two educators (Noam Bonkowski and Vladimir Noda) to talk about today's workforce demands and how you can make sure your students are prepared.  Noam is a CTE teacher, work-based learning (WBL) coordinator, and Project Management Professional in Queens, NY. In his role, he creates a classroom that models a professional PMO work environment, all while teaching project management foundations and key business skills. He certifies his students using the PMI Project Management Ready certification program. Noam also extends his influence beyond the classroom in his role as WBL coordinator. He fosters partnerships with businesses and develops opportunities for students to work as interns for key work experience and educational credit.  Vladimir is an enthusiastic educator, instructional coach, and advocate for business education with over a decade of experience enhancing student success. Throughout his career, he has assisted countless students in obtaining industry-recognized certifications in Microsoft Office, Adobe, and the Entrepreneurship and Small Business (ESB) exam. As an instructional coach, he is dedicated to building a top-tier business program and enhancing his school's presence through strategic marketing efforts. With a dynamic approach to curriculum development and certification preparation, Vladimir aims to empower educators with the tools and strategies necessary to boost student achievement, expand their programs, and cultivate future business leaders.  In this episode, we talk with Noam and Vladimir all about skills needed for the managers of tomorrow's workforce. We discuss everything from soft skills, classroom architecture, the role of certification, helping students practice their abilities in real-world scenarios, and inclusivity for marginalized students. Whether you're focusing on project management, communication, or an entrepreneurial mindset, we know you'll learn something to help your students master the skills required of tomorrow's business leaders. Learn more about our episode sponsors: The PMI Project Management Ready certification and Entrepreneurship and Small Business certification programs.  Interested in learning from educators like Noam and Vladimir? Join our CERTIFIED Academy program. Get all the details here.   Connect with other educators in our CERTIFIED Educator Community here.        Don't miss your chance to register for our annual CERTIFIED Educator's Conference here.    

Landing a job in Australia is increasingly competitive, with AI reshaping workplaces. New SEEK data reveals the top ten human skills employers want most, from customer service and Microsoft Office know-how to leadership and relationship management. Success coach Nim Gholkar shares practical tips on volunteering, networking, gaining local qualifications, and overcoming barriers often faced by South Asian professionals.

In this Blind Abilities episode, Jeff Thompson talks with Jeff Bishop, president of BITS—Blind Information Technology Specialists—an all-volunteer organization empowering blind and low-vision individuals through accessible technology, community, and hands-on learning. Bishop outlines BITS' rapid growth, affordable memberships, and expanding reach across platforms like WhatsApp, Facebook, email lists, and mentoring channels. BITS offers high-impact training, including Python programming, Microsoft Office, Google Workspace, NVDA, and AI immersion courses—all with fully accessible materials and strong completion rates. Their partnerships with APH, Bookshare, NLS, Microsoft, and others ensure free resources and meaningful industry feedback opportunities, including paid participation in Microsoft's Project Empower. With free Remote Incident Manager (RIM) support, active mentoring, and a welcoming culture, BITS serves beginners and experts alike. As the group considers rebranding the "S" in BITS to Solutions, the mission remains clear: meeting people where they are and helping them thrive in their digital lives. Link to BITS

What if your carefully crafted training course could become a content campaign that actually drives behavior change? Most L&D professionals create amazing content that gets consumed once and forgotten. But what if that single course could spawn dozens of touchpoints that reinforce learning over time?We're seeing a shift where smart L&D teams are borrowing from marketing playbooks, and it's working. The secret isn't creating more content; it's strategically repurposing what you already have.Joining this episode is Mike Taylor, Learning Consultant at Nationwide and co-author of "Think Like a Marketer, Train Like an L&D Pro."Mike's been pioneering the campaign approach to learning, and shows us how one webinar recording can become email sequences, infographics, GIFs, and micro-learning moments.He explains why thinking in campaigns rather than courses changes everything, introduces the SURE model for creating content that sticks, and shows how to overcome the "we don't have time" objection with smart repurposing strategies.Learning points from the episode include:00:00 - 02:22 Introduction to repurposing and spawning multiple content pieces02:22 - 05:15 Why repurposing isn't more work and how to expand your reach05:15 - 06:56 Think campaigns not courses: the hero content pyramid06:56 - 09:19 Leaving breadcrumb trails across multiple channels09:19 - 11:51 Setting hooks and the SURE model for relevant content11:51 - 12:39 Why content creates feelings whether you know it or not12:39 - 14:23 Turning annual compliance into year-round micro-learning14:23 - 16:37 Using AI and A/B testing data to sell repurposing internally16:37 - 17:58 Finding small experiments to build credibility17:58 - 21:13 Visual repurposing: webinars to GIFs, polls to graphics21:13 - 23:13 Using Camtasia for Microsoft Office tips and animated GIFs23:13 - 25:00 Why even simple content benefits from repurposing25:00 - 26:53 Making subject matter expert content digestible26:53 - 31:15 OutroImportant links and mentions:Connect with Mike Taylor on LinkedIn: https://www.linkedin.com/in/miketaylor/Find out more about Train Like a Marketer: https://trainlikeamarketer.com/Camtasia: https://www.techsmith.com/camtasia/  Snagit: https://www.techsmith.com/snagit/Audiate: https://www.techsmith.com/camtasia/audiate/

In this episode of Hashtag Trending, Jim Love discusses Geoffrey Hinton's views on AI replacing human labor for big tech profits, Google Cloud's internal competition with YouTube, and the International Criminal Court's switch from Microsoft Office to an open-source alternative. The episode also covers YouTube's controversial removal of Windows 11 installation videos on unsupported systems. 00:00 Introduction and Sponsor Message 00:29 AI's Impact on Jobs and Economy 02:35 Google Cloud's Rise and Internal Competition 04:36 ICC's Shift from Microsoft to Open Source 06:10 YouTube's Controversial Content Removals 07:40 Conclusion and Sponsor Message

Während andere Medienhäuser ihre Artikel durch KI überarbeiten lassen reden wir wieder unkontrolliert daher und liefern ein wenig Feedback, sprechen ausführlich über den Ausfall der AWS-Infrastruktur und was das für die Welt so bedeutet, unterstützen den Internationalen Strafgerichtshof bei dem Versuch, sich von Microsoft Office zu befreien, geben ein kurzes Update zur Chatkontrolle, erklären warum die Flughäfen auch alle nicht ganz so datensouverän sind und bedauern die Unterzeichnung der Cybercrime Convention. Zum Schluß noch ein paar Tips zum 39C3. Mehr gibt's nicht – abgesehen von ein paar Belehrungen und schlechten Witzen. Also alles wie immer.

Anna Bicker, heise-online-Chefredakteur Dr. Volker Zota und Malte Kirchner sprechen in dieser Ausgabe der #heiseshow unter anderem über folgende Themen: - Big Teams is watching you: Microsoft Teams prüft künftig Büroanwesenheit – Ab Dezember kann Microsoft Teams die Anwesenheit von Mitarbeitern im Büro erfassen. Welche Funktionen bietet das neue Feature genau? Wie reagieren Datenschützer auf diese Überwachungsmöglichkeit? Und welche Auswirkungen könnte das auf die Vertrauenskultur in Unternehmen haben? - Zurückhacken erlaubt? Bundesinnenministerium prüft Abwehrschläge gegen Cyberangriffe – Das Bundesinnenministerium erwägt, aktive Abwehrmaßnahmen gegen Cyberangriffe zu ermöglichen. Wo verläuft die Grenze zwischen Verteidigung und Angriff im digitalen Raum? Welche rechtlichen und technischen Herausforderungen bringt eine solche Strategie mit sich? Und wie könnten andere Staaten auf deutsche Cyber-Gegenschläge reagieren? - Musks neue Wissenswelt: Wie gut ist die Grokipedia? – Elon Musk hat mit Grokipedia eine Wikipedia-Alternative mit 885.000 Artikeln gestartet. Was unterscheidet Grokipedia von Wikipedia und wie funktioniert die KI-gestützte Plattform? Kann eine von Musks X-Plattform betriebene Enzyklopädie neutral und verlässlich sein? Und welche Chancen hat Grokipedia gegen den etablierten Platzhirsch Wikipedia? Außerdem wieder mit dabei: ein Nerd-Geburtstag, das WTF der Woche und knifflige Quizfragen.

Co-hosts Mark Thompson and Steve Little explore how Google's Nano Banana photo restoration tool will revolutionize image restoration by integrating with Adobe Photoshop. This move will greatly reduce unintended changes to historical photos when editing them with AI.Next, they unpack OpenAI's move to make ChatGPT Projects available to free-tier users, making research organization more accessible for genealogists.This week's Tip of the Week provides essential guidance on the responsible use AI when editing historical photos using AI tools like Nano Banana, ensuring transparency and trust in historical photographs.In RapidFire, they cover OpenAI's new Sora 2 AI-video social media platform, Claude's new ability to create and edit Microsoft Office files, memory features in Claude Projects, advancements in local language models, and how OpenAI's massive infrastructure deals are changing the AI landscape.Timestamps:In the News:02:43 Adobe improves historical photo restoration by adding Nano Banana to Photoshop09:34 ChatGPT Projects are Now FreeTip of the Week:13:36 Citations for AI-Restored Images Build Trust in AI-Modified PhotosRapidFire:21:24 Sora 2 Goes Social27:23 Claude Adds Microsoft Office Creation and Editing34:26 Memory Features Come to Claude Projects38:32 Apple and Amazon both create Local Language Model tools44:47 OpenAI's Big Data Centre Deal with Oracle Resource LinksOpenAI announces free access to ChatGPT Projectshttps://help.openai.com/en/articles/6825453-chatgpt-release-notesEngadget: OpenAI Rolls Out ChatGPT Projects to Free Usershttps://www.engadget.com/ai/openai-rolls-out-chatgpt-projects-to-free-users-215027802.htmlForbes: OpenAI Makes ChatGPT Projects Freehttps://www.forbes.com/sites/quickerbettertech/2025/09/14/small-business-technology-roundup-microsoft-copilot-does-not-improve-productivity-and-openai-makes-chatgpt-project-free/Responsible AI Photo Restorationhttps://makingfamilyhistory.com/responsible-ai-photo-restoration/Claude now has memory, but only for certain usershttps://mashable.com/article/anthropic-claude-ai-now-has-memory-for-some-usersNew Apple Intelligence features are available todayhttps://www.apple.com/newsroom/2025/09/new-apple-intelligence-features-are-available-today/Introducing Amazon Lens Livehttps://www.aboutamazon.com/news/retail/search-image-amazon-lens-live-shopping-rufusAmazon Lens Live Can Scan and Pull Up Matcheshttps://www.pcmag.com/news/spot-an-item-you-wish-to-buy-amazon-lens-live-can-scan-and-pull-up-matchesA Joint Statement from OpenAI and Microsoft About Their Changing Partnershiphttps://openai.com/index/joint-statement-from-openai-and-microsoft/The Verge: OpenAI and Oracle Pen $300 Billion Compute Dealhttps://www.theverge.com/ai-artificial-intelligence/776170/oracle-openai-300-billion-contract-project-stargateReuters: OpenAI and Oracle Sign $300 Billion Computing Dealhttps://www.reuters.com/technology/openai-oracle-sign-300-billion-computing-deal-wsj-reports-2025-09-10/?utm_source=chatgpt.comTagsArtificial Intelligence, Genealogy, Family History, Photo Restoration, AI Tools, OpenAI, Google, Adobe Photoshop, ChatGPT Projects, Nano Banana, Image Editing, AI Citations, Sora 2, Video Generation, Claude, Microsoft Office, Apple Intelligence, Amazon Lens, Oracle, Cloud Computing, Local Language Models, AI Infrastructure, Responsible AI, Historical Photos

In this episode, Josh discusses his perspective on how AI and advanced technologies in platforms like Google Workspace and Microsoft Office could potentially render general-purpose legal CRMs like Clio and PracticePanther obsolete.  Josh shares insights from his experience in family law and how he's been able to automate numerous tasks using these workstations. He highlights the cost-effectiveness and efficiency of using integrated features like e-signature, custom workflows with AI support, and booking links.  Josh also talks about the niche legal tech tools that will still be necessary and offers examples from his practice to demonstrate these concepts. Tune in to hear his predictions and learn more about his tech-driven approach to legal practice. Never miss an update on my journey by joining my substack here: https://joshschachnow.substack.com/ 00:00 Introduction and Overview 00:36 Balancing Tech and Law Practice 02:19 The Rise of AI in Legal Workspaces 05:25 Cost Efficiency of Google Workspace 07:43 Future of Legal CRMs and AI Integration 09:38 Niche Legal Tech Tools 10:46 Conclusion and Call to Action

Think about your digital life for a moment. What do you actually OWN anymore? Microsoft Office? Music? Movies? Your social media accounts? WRONG! In all of those spaces (and more), you're just a digital sharecropper. Americans have become more like the coal miners and sharecroppers we read about it history - not really owning much of anything and trapped in cycles of debt. God never wanted His people to be trapped in cycles of debt - and God has a lot to say about it. In this message, Max Vanderpool offers practical advice for handling debt.

Discover how blind tech enthusiasts can upgrade from Windows 10, harness Apple's new Braille Access features, and get involved with the powerful Bits community for learning and support. This episode is supported by Pneuma Solutions. Creators of accessible tools like Remote Incident Manager and Scribe. Get $20 off with code dt20 at https://pneumasolutions.com/ and enter to win a free subscription at doubletaponair.com/subscribe!Steven Scott hosts a lively discussion with Michael Babcock and Jeff Bishop about technology for blind users, starting with questions about device compatibility and upgrading from Windows 10 as end-of-life approaches. The episode explores tools like Rufus for accessible updates, the role of screen readers like JAWS, NVDA, and Narrator, and the importance of choosing the right solution for different computing needs. The conversation shifts into Apple's new Braille Access, highlighting features like BRF note creation, multitasking with braille displays, and sharing files via iCloud. Steven shares his personal training experience, while the team reflects on the impact of this feature for education, productivity, and collaboration. Listeners also get an in-depth look at BITS (Blind Information Technology Specialists), a global community empowering blind users to learn everything from Microsoft Office and Google tools to Python coding and AI. The team explains Project Empower, mentorship, and on-demand educational resources that help blind users upskill and even provide paid accessibility feedback to tech companies.Relevant LinksBITS (Blind Information Technology Specialists): https://joinbits.orgYour Tech Report: https://yourtechreport.com Find Double Tap online: YouTube, Double Tap Website---Follow on:YouTube: https://www.doubletaponair.com/youtubeX (formerly Twitter): https://www.doubletaponair.com/xInstagram: https://www.doubletaponair.com/instagramTikTok: https://www.doubletaponair.com/tiktokThreads: https://www.doubletaponair.com/threadsFacebook: https://www.doubletaponair.com/facebookLinkedIn: https://www.doubletaponair.com/linkedin Subscribe to the Podcast:Apple: https://www.doubletaponair.com/appleSpotify: https://www.doubletaponair.com/spotifyRSS: https://www.doubletaponair.com/podcastiHeadRadio: https://www.doubletaponair.com/iheart About Double TapHosted by the insightful duo, Steven Scott and Shaun Preece, Double Tap is a treasure trove of information for anyone who's blind or partially sighted and has a passion for tech. Steven and Shaun not only demystify tech, but they also regularly feature interviews and welcome guests from the community, fostering an interactive and engaging environment. Tune in every day of the week, and you'll discover how technology can seamlessly integrate into your life, enhancing daily tasks and experiences, even if your sight is limited. "Double Tap" is a registered trademark of Double Tap Productions Inc. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

The Blockchain Syndicate: A Contemporary Thriller by Robbie BachSet amid the turbulence of today's headlines, this gripping techno thriller—the second in Bach's series to feature Tamika Smith—pulses with high-stakes intrigue and razor-edged political drama.Senator Tamika Smith's new year begins in shambles. First she receives an email threatening to expose her past—a threat from someone she knows is dead. Then her boyfriend, Johnny Humboldt, is kidnapped in broad daylight after his daughter is wounded in a California school shooting. Someone is desperate to take Tamika down and damage the country she loves. The attacks are professional, the delivery is flawless, and the message unmistakable: America is broken, and someone is determined to fix it their way.Standing in the eye of the storm, Tamika must navigate a political landscape riddled with betrayal, misinformation, and moral decay to rescue Johnny and uncover the group behind the web of conspiracy. As the country spirals toward financial Armageddon and democracy itself begins to unravel, Tamika must decide what she is willing to sacrifice to save her family and pull the nation back from the brink. With its sharp blend of shadowy villains and morally torn heroes, The Blockchain Syndicate dares you to question everything—right up to the final, breathless moment.Robbie Bach joined Microsoft in 1988. Over the next twenty-two years, he worked in various marketing, general management, and business leadership roles, including supporting the successful launch and expansion of Microsoft Office. As Chief Xbox Officer, he led the creation and development of the Xbox business, including the launch of the Xbox and the highly popular successor product, Xbox 360. He retired from Microsoft as the president of the Entertainment and Devices Division in 2010.In his new role as a civic engineer, Robbie works with corporate, philanthropic, and civic organizations who are driving positive change in our communities. He guest lectures extensively at a variety of colleges and universities and speaks to corporate, civic, and trade association audiences across the country. In 2015, he published his first book, Xbox Revisited: A Game Plan for Corporate and Civic Renewal. His debut novel featuring Tamika Smith, The Wilkes Insurrection, was published in 2021. to 2011. He is the previous chairman and current board member at the Bipartisan Policy Center. He serves on the national board of governors for Boys and Girls Clubs of America and was the chairman of that board from 2009AMAZONhttps://theblockchainsyndicate.com/www.RobbieBach.com    http://www.bluefunkbroadcasting.com/root/twia/10925rbtr.mp3    The Wilkes Insurrection: A Contemporary Thriller by Robbie BachAMAZON

A dead man blackmails a U.S. senator. A shadowy syndicate unleashes financial chaos. Awar hero must risk everything to save her family and the country she swore to protect. From Robbie Bach, former Chief Xbox Officer at Microsoft and author of The Wilkes Insurrection, comes a riveting new contemporary thriller that blends cutting-edgetechnology with political danger in a way only he can. The Blockchain Syndicateimagines a world alarmingly close to our own, and it's just one wrong move away from collapse.Bach's insider knowledge of the tech world and his deep involvement in civic and policy circles lends a chilling authenticity to this thriller. With themes ripped from current headlines, AI, disinformation, political extremism, and digital vulnerability, The Blockchain Syndicate is not just a suspenseful read; it's a wake-up call. Robbie Bach joined Microsoft in 1988. Over the next twenty-two years, he worked in business leadership roles, including supporting the successful launch and expansion of MicrosoftOffice. As Chief Xbox Officer, he led the creation and development of the Xbox business, including the launch of the Xbox and its highly popular successor, the Xbox 360.In 2015, he published his first book, Xbox Revisited: A Game Plan for Corporate and Civic Renewal. His debut novel featuring Tamika Smith, The Wilkes Insurrection, was published in 2021.

"PC-as-a-Service makes fast, secure deployments possible without having to contract with a series of vendors for devices, connectivity, support, and replacement services — all with a competitive, predictable monthly payment," says John Tonthat, CRO of Cellhub, in a new Technology Reseller News podcast. Cellhub, a premier primary agent in T-Mobile's Channel Partner program, has teamed with Lifetime Endpoint Resources (EPR) to introduce a first-to-market PC-as-a-Service (PCaaS) program. Powered by T-Mobile's industry-leading 5G network and anchored by Lenovo® ThinkPad™ devices, the program is designed to give MSPs and solution providers a full-stack, fixed-price computing environment to deliver to end-users. Key features of the program include: Lenovo ThinkPad T14 Gen 6 laptops – ready-to-go, preconfigured Built-in 5G connectivity – 75 to 125 GB/month for mobile-first access Embedded security agent and remote wipe – enterprise-grade protection 24/7/365 help desk support – powered by distributor D&H Distributing Advanced exchange – replacement devices shipped before the old ones return Fixed 36-month pricing – predictable IT costs in volatile markets Microsoft 365 + Copilot – AI-enhanced productivity Tonthat explains that Cellhub's mission is to represent and advance T-Mobile solutions, but this launch also positions the company as a systems integrator and lifecycle enabler for MSPs. By unifying connectivity, devices, support, and software in one bundle, PCaaS helps partners offer a premium 5G-enabled workplace while creating new streams of recurring revenue. The program is aimed squarely at small and mid-sized businesses, helping them gain enterprise-grade computing power without the burden of upfront capital expenditures. “Cellhub is thrilled to provide a superior, comprehensive 5G solution that can accelerate outcomes for small businesses, especially those who might not be able to maintain their own in-house IT teams,” Tonthat adds. Listen to the full conversation with John Tonthat of Cellhub on Technology Reseller News. Connect with Cellhub & John Tonthat John Tonthat on LinkedIn cellhub.com Cellhub on LinkedIn Cellhub, a premier primary agent in T-Mobile's Channel Partner program, is working with asset lifecycle management provider Lifetime EndPoint Resources to launch a first-to-market PC-as-a-Service (PCaaS) program for the channel, powered by T-Mobile. This end-to-end 5G connectivity solution provides high-performance Lenovo® ThinkPad™ computing devices connected by T-Mobile, the largest 5G network, bundling 24-hour help desk services, advanced exchange services, and Microsoft Office 365 and Copilot for the devices. Cellhub considers PCaaS a next-gen model for comprehensive device lifecycle management in the channel, positioned to drive the category forward. The PCaaS program is delivered over a 36-month term at a competitive (and tariff-resistant) monthly recurring fee as opposed to an up-front capital expenditure. PCaaS allows MSPs to offer a fully-managed, set-price computing bundle, complete with cutting edge 5G connectivity, Lenovo-branded devices,  “always-there” support, and expedited exchange of devices when issues arise. It's ideal for a variety of modern workplaces, especially companies whose employees are distributed among different locations, like visiting nurses services or attorneys' offices, translating to reliable, consistent connectivity with minimal downtime and long-term optimized computing.

In this week's episode, we take a look at creating good backstories for characters and how that can advance the plot. We also discuss two articles about the problems of generative AI. This coupon code will get you 25% off the ebook versions of books in the Sevenfold Sword series at my Payhip store: SEVENBOOKS The coupon code is valid through October 13, 2025. So if you need a new ebook this fall, we've got you covered! Here are links to the articles mentioned in the episode. Writer Beware: https://writerbeware.blog/2025/08/01/return-of-the-nigerian-prince-a-new-twist-on-book-marketing-scams/ Ed Zitron: https://www.wheresyoured.at/the-haters-gui/ TRANSCRIPT 00:00:00 Introduction and Writing Updates Hello, everyone. Welcome to Episode 271 of The Pulp Writer Show. My name is Jonathan Moeller. Today is October 3, 2025, and today we are looking at how to create character backstories. We'll also look at some good articles about the problems created by generative AI technology. If you hear occasional drumming noise in the background, it seems like the elementary school a few blocks from here is practicing their marching band. Hopefully it won't be too disruptive. First off, let's start with Coupon of the Week. This week's coupon code will get you 25% off the ebook versions of books in the Sevenfold Sword Series in my Payhip store, and that coupon code is SEVENBOOKS. And as always, the coupon code and the link to my Payhip store will be available in the show notes. This coupon code will be valid through October the 13th, 2025. If you need a new ebook for this fall, we have got you covered. Now let's have a progress update on my current writing projects. As of this recording, I am 83,000 words into Cloak of Worlds, which will be the 13th book in the Cloak Mage series. I'm thinking the book will end up about 110,000 words, so hopefully I will finish up the rough draft next week. We'll see how things go. I'm also 8,000 words into Blade of Shadows, which will be the sequel to Blade of Flames from last month, and that will be my main project once Cloak of Worlds is published (hopefully by the end of October, if all goes well). In audiobook news, I'm very pleased to report that recording and all the work is done on Ghost in the Siege (as excellently narrated by Hollis McCarthy) and we will actually close out this episode with a preview from that audiobook. It's currently up on my Payhip store and probably Google Play as of this recording, but it should be showing up on all the other stores before too much longer. 00:01:52 Generative AI Now onto our next topic, which is two very good articles about the problems of generative AI I read recently. The first (and I'll have the links to both articles in the show notes) is from Writer Beware, which talks about how generative AI is causing a new round of super targeted scammers. These scammers feed your book into the chatbot, which then generates a highly personalized email praising the book and offering marketing services. I got a ton of these scam emails after Stealth and Spells Online, Ghost in the Siege, and Blade of Flames came out in the past couple months and a bunch more after Malison: The Complete Series did well on BookBub at the end of August. So if you are a writer and you publish a book and a few days later or perhaps even the very same day, you get a very detailed email praising the book with very specific plot points and offering marketing services, beware, it's probably a scam that will give you no value whatsoever for your money. Journalist Edward Zitron wrote a great article explaining in extensive detail why generative AI is a bad idea that's probably going to cause a serious market crash in the next few years. I admit I started out with a mildly negative opinion of LLM based generative AI tools in 2022 and 2023, but I wanted my opinion to be an informed one. I've experimented with them on and off and read a good bit about them and as I've experimented with them, my opinion has moved from mildly negative to highly negative and finally arriving at completely anti-AI this year. I never used AI for any of my books, short stories, or cover images. I experimented a bit with using AI images for Facebook ads, but people generally hated them, so I stopped entirely with that. In fact, Facebook ads have become far less effective this year because of all the AI stuff Meta has crammed into them, but more on that later. So why did I arrive at a highly negative opinion of AI? It's because these tools do not actually do what their advocates promise, they're hideously expensive to run, and the enormous costs and downsides significantly outweigh any benefits. In addition to the problems mentioned in the Zitron article like cost, false promises, economic bubbles, and the companies blatantly lying about their capabilities, I think the fundamental difficulty with generative AI is that it's essentially a cognitive mirror for its users, like a Narcissus Machine like I've called it before. What do I mean by this? In Greek myth Narcissus was enraptured by the beauty of his own reflection. LLM based AI is essentially very fancy autocomplete, which means it guesses the most likely response to your prompt based on a statistical likelihood. In other words, it ends up mirroring your own thoughts back at you. So I think LLMs are highly prone to inducing an unconscious confirmation bias in the user. Confirmation bias is a logical fallacy where one interprets new information as confirming one's preexisting beliefs. It's healthier to reevaluate one's beliefs based on new information that comes in, but with confirmation bias, you warp any incoming information to fit a preexisting belief. For example, let's say you have the preexisting belief that you're immortal and nothing can kill you, and then you accidentally shoot yourself in the arm with a nail gun and you bleed. The correct interpretation of this is no, you are not in fact immortal and you can in fact die. Someone suffering under confirmation bias would say the fact that they accidentally shot themselves in the nail gun in the arm with a nail gun and didn't die is proof that they're immortal. That's obviously a logical fallacy, but you see why it's called a confirmation bias. I think even highly intelligent people using LLMS are prone to this kind of confirmation bias because the AI model settles on what is the most statistically likely response to the prompt, which means that consciously or not, you are guiding the LLM to give you the responses that please you. This is why you see on the tragically hilarious side, people who are convinced they've invented a new level of physics with the LLM or taught it to become self-aware or think that the LLM has fallen in love with them. And on the outright tragic side, people who have serious mental breakdowns or blow up their lives in destructive ways because of their interaction with the LLM. Grimly enough, I suppose the problem is going to sort itself out when the AI bubble crashes, whether in a few months or a few years. As one of the linked articles mentioned, AI companies have no clear path to profitability, save for chaining together infinite NVIDIA graphics cards and hoping they magically stumble into an artificial general intelligence or a super intelligence. They're not going to and it's all going to fall apart. The downside is that this is going to cause a lot of economic disruption when it crashes. I know I'm very negative about AI, but in the end I see hardly any good results or actual benefits from the technology. Lots of technology products are becoming worse from having AI stuffed into them (like Windows 11 and Microsoft Office) and what a few good results have come about will not last because the data centers are burning cash like there's no tomorrow. So again, you can see the links to these articles in the show notes and those are my thoughts on generative AI at the moment. 00:07:04 Writing Backstory for Characters [Note: Contains some mild spoilers for early books in the Frostborn, Half-Elven Thief, The Ghosts, and Cloak Games series] Now let's move on to a happier and frankly more interesting topic and that is writing backstory for characters. I will define it, talk about why backstory is important, give three tips about writing effective backstories, and share examples of good backstories from my own work and other media. First of all, what is a backstory? It's what happens to a character before the story begins or details of situation that happens before the story begins. Very often you'll have characters who have preexisting pasts before the story begins. It's very rare the story will begin when the main character is born and go from there. Even if that is the case, then some of the supporting characters obviously will have backstories. One example of a backstory could be a detective who had a twin sister who is kidnapped, which explains why he gets overly invested when a similar case happens. An example of a location's backstory would be knowing that a particular country was once part of another one and split off after revolution or war. That detail influences how people in that country currently treat people in the other nation. And you can see that a backstory is also an important component of world building as well, especially for fantasy and science fiction novels, though even novels set in in the contemporary world like mysteries and contemporary romance will often have backstories as well that require world building, because the location is very often fictional or will have fictional elements to it. Now, why is backstory important? For one thing, it makes a story feel more realistic and “lived in”, for lack of a better word. It's not realistic that absolutely nothing of interest happened to the protagonist before the story begins, or that nothing from their past would influence their current beliefs, behavior, and decisions. Backstory also gives characters clearer reasons for doing things. Returning to the earlier example of detective who had a younger sister who was kidnapped. What if the detective was a very procedural and by the book until a sudden similar case happened? Backstory can explain his unorthodox methods and willingness to solve the case at any cost. Backstory can also drive the plot in many ways. Continuing with the detective example, the detective's knowledge of his little sister's case leads him to find similar patterns in the new case and sends him on a search to prove that the cases are connected. As we can see from that, backstory is also a good way to set up plot hooks for later characters, such as we could have our detective here with his twin sister who disappeared in circumstances similar to his current case. It could be a fantasy hero who had previous battles with orcs and explains why he doesn't like seeing orcs. It could be a contemporary romance heroine who is reencountering her old flame, in which case the backstory would be central towards the plot, essentially. And now for three tips for writing backstory. First, it's important to not stop the plot to reveal backstory. Infodumping is generally something to be avoided when you are writing a novel. A little bit of it is unavoidable, but you want to avoid infodumping as much as possible and to reveal only as much information as necessary, partly because that creates a less cumbersome read for the reader and partly because that can also inspire a sense of mystery that sort of helps hook the reader and propels them forward into the story. It's also good to only reveal backstory that serves the plot or provides key information. For example, you could have in your detective's backstory that he went to high school and he was only a mediocre student and graduated with a GPA of 2.9 while doing well in athletics. Unless that's actually relevant to the story or has some significance to the plot, it's probably best to not include that. You can always tell when a writer has done a lot of research on a particular topic like firearms or travel or the history of a particular country because they are going to put that information in the book whether you want it or not. And if you're inventing an elaborate backstory for your character, it's best to avoid that impulse and only bring in details from the backstory as necessary. It's also important not to have the characters tell each other backstory that they would already know. For example, if you have two characters who've been married for 20 years, it would not be good to have them appear in dialogue as, “As you know, beloved wife, we have been married for 20 years this Tuesday.” It would be better if it's important to the plot to reveal that information like they're going out to a 20th anniversary party or their friends are throwing them a 20th anniversary party, that kind of thing, rather than having it come out in sort of a cumbersome conversation like that. Additionally, it's also important to only do as much backstory as necessary. For your main character, you may need a good deal of backstory or for the antagonist, but for supporting characters, it's less important to have a fully realized background. You need just enough so that they feel realistic and can contribute to the plot without overburdening the plot with too many details. Now, a few examples from my own books, mild spoilers here, nothing major but mild spoilers. I have written characters who have one key backstory element that influenced the plot. Ridmark Arban from Frostborn would be one and his major backstory point is that he was unable to save his wife Aelia from being killed five years before the story starts. Later on, there would be additional backstory that comes out for him in relation to his father and his brothers, but that is the main backstory point that defines his character for easily the first half of the series. Another example would be Morigna, whose parents were killed by the dvargir and then she was raised by a mysterious sorcerer who called himself the old man. And that is a major defining part of her character, that backstory that happened before we meet her in the narrative. I've also written characters with a lot of backstory, and the chief example of that would be Calliande from Frostborn as well, where she wakes up in the first book with no memory of her past and discovering what her backstory actually is a major driving force in the first eight books of the series. So that is a good example. Not to toot my own horn or anything, but that is a good example of using backstory as a mysterious narrative hook to pull the characters forward. Rivah from Half-Elven Thief is another character of mine who has a lot of backstory. In the backstory, she was raised in a noble household, her mother died, her father was about to sell her into slavery, so she fled into the streets and then she met Tobell and became part of his thieving crew. Tobell suffered a serious injury, and the thieving crew broke up and Rivah had to sort of strike out on her own while coming under debt to the procurator Marandis. So there is a lot of backstory there and all of it is important to Rivah's character and I think I've done my best to sort of feed that into the story as necessary to drive the plot rather than hopefully unloading it all in a massive infodump. And I have written characters with very little backstory, and the prime example of those would be Caina and Nadia. In Caina's series, the series starts when she's 11 years old and living with her parents and we develop Caina as she goes along and follow her she grows to adulthood and then increasing prominence in her world. With Nadia, the very first scene in the book is her first day of kindergarten pledging allegiance to the flag, the United States, and the High Queen of the Elves, which is the first indicator that Nadia's world, while very similar as to ours, is nonetheless very different. Like Caina, the book's narrative starts when Nadia is very young and then we see her develop along the course of the books. In a good example of backstory used well from another book would be Aragorn from J.R.R. Tolkien's Lord of the Rings, where Aragorn's backstory is extremely important because when the hobbits first meet him at The Prancing Pony in Bree, he's just this mysterious wanderer known as Strider. But later on, we learn that he's actually the last heir of Gondor and Arnor and the rightful king of Gondor. His desire to reclaim his heritage and fulfill the role destiny has prepared for him is a major part of his character and that actually grows organically out of his backstory. I'm not usually fond of prequels, but a good example of a prequel using backstory effectively would be the combination of the Andor TV show and the Rogue One movie, where they create this excellent backstory for the Star Wars movie [Episode IV]. They do it through good characterization so you can see all the motivations of the characters as they go about their various missions and errands. So hopefully that gives you a good look into the process of creating backstory and how best to use it for writing your own stories. So that is it for this week. Thank you for listening to The Pulp Writer Show. I hope you found this show useful. A reminder that you can listen to all the back episodes of the show at https://thepulpwritershow.com. If you enjoyed the podcast, please leave a review on your podcasting platform of choice. Stay safe and stay healthy and see you all next week. And now let's close out with a preview of the audiobook of Ghosts in the Siege, as excellently narrated by Hollis McCarthy [audiobook excerpt follows].    

Elizabeth Figura is a Wine developer at Code Weavers. We discuss how Wine and Proton make it possible to run Windows applications on other operating systems. Related links WineHQ Proton Crossover Direct3D MoltenVK XAudio2 Mesa 3D Graphics Library Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Elizabeth Figuera. She's a wine developer at Code Weavers. And today we're gonna talk about what that is and, uh, all the work that goes into it. [00:00:09] Elizabeth: Thank you Jeremy. I'm glad to be here. What's Wine [00:00:13] Jeremy: I think the first thing we should talk about is maybe saying what Wine is because I think a lot of people aren't familiar with the project. [00:00:20] Elizabeth: So wine is a translation layer. in fact, I would say wine is a Windows emulator. That is what the name originally stood for. it re implements the entire windows. Or you say win 32 API. so that programs that make calls into the API, will then transfer that code to wine and and we allow that Windows programs to run on, things that are not windows. So Linux, Mac, os, other operating systems such as Solaris and BSD. it works not by emulating the CPU, but by re-implementing every API, basically from scratch and translating them to their equivalent or writing new code in case there is no, you know, equivalent. System Calls [00:01:06] Jeremy: I believe what you're doing is you're emulating system calls. Could you explain what those are and, and how that relates to the project? [00:01:15] Elizabeth: Yeah. so system call in general can be used, referred to a call into the operating system, to execute some functionality that's built into the operating system. often it's used in the context of talking to the kernel windows applications actually tend to talk at a much higher level, because there's so much, so much high level functionality built into Windows. When you think about, as opposed to other operating systems that we basically, we end up end implementing much higher level behavior than you would on Linux. [00:01:49] Jeremy: And can you give some examples of what some of those system calls would be and, I suppose how they may be higher level than some of the Linux ones. [00:01:57] Elizabeth: Sure. So of course you have like low level calls like interacting with a file system, you know, created file and read and write and such. you also have, uh, high level APIs who interact with a sound driver. [00:02:12] Elizabeth: There's, uh, one I was working on earlier today, called XAudio where you, actually, you know, build this bank of of sounds. It's meant to be, played in a game and then you can position them in various 3D space. And the, and the operating system in a sense will, take care of all of the math that goes into making that work. [00:02:36] Elizabeth: That's all running on your computer and. And then it'll send that audio data to the sound card once it's transformed it. So it sounds like it's coming from a certain space. a lot of other things like, you know, parsing XML is another big one. That there's a lot of things. The, there, the, the, the space is honestly huge [00:02:59] Jeremy: And yeah, I can sort of see how those might be things you might not expect to be done by the operating system. Like you gave the example of 3D audio and XML parsing and I think XML parsing in, in particular, you would've thought that that would be something that would be handled by the, the standard library of whatever language the person was writing their application as. [00:03:22] Jeremy: So that's interesting that it's built into the os. [00:03:25] Elizabeth: Yeah. Well, and languages like, see it's not, it isn't even part of the standard library. It's higher level than that. It's, you have specific libraries that are widespread but not. Codified in a standard, but in Windows you, in Windows, they are part of the operating system. And in fact, there's several different, XML parsers in the operating system. Microsoft likes to deprecate old APIs and make new ones that do the same thing very often. [00:03:53] Jeremy: And something I've heard about Windows is that they're typically very reluctant to break backwards compatibility. So you say they're deprecated, but do they typically keep all of them still in there? [00:04:04] Elizabeth: It all still It all still works. [00:04:07] Jeremy: And that's all things that wine has to implement as well to make sure that the software works as well. [00:04:14] Jeremy: Yeah. [00:04:14] Elizabeth: Yeah. And, and we also, you know, need to make it work. we also need to implement those things to make old, programs work because there is, uh, a lot of demand, at least from, at least from people using wine for making, for getting some really old programs, working from the. Early nineties even. What people run with Wine (Productivity, build systems, servers) [00:04:36] Jeremy: And that's probably a good, thing to talk about in terms of what, what are the types of software that, that people are trying to run with wine, and what operating system are they typically using? [00:04:46] Elizabeth: Oh, in terms of software, literally all kinds, any software you can imagine that runs on Windows, people will try to run it on wine. So we're talking games, office software productivity, software accounting. people will run, build systems on wine, build their, just run, uh, build their programs using, on visual studio, running on wine. people will run wine on servers, for example, like software as a service kind of things where you don't even know that it's running on wine. really super domain specific stuff. Like I've run astronomy, software, and wine. Design, computer assisted design, even hardware drivers can sometimes work unwind. There's a bit of a gray area. How games are different [00:05:29] Jeremy: Yeah, it's um, I think from. Maybe the general public, or at least from what I've seen, I think a lot of people's exposure to it is for playing games. is there something different about games versus all those other types of, productivity software and office software that, that makes supporting those different. [00:05:53] Elizabeth: Um, there's some things about it that are different. Games of course have gotten a lot of publicity lately because there's been a huge push, largely from valve, but also some other companies to get. A lot of huge, wide range of games working well under wine. And that's really panned out in the, in a way, I think, I think we've largely succeeded. [00:06:13] Elizabeth: We've made huge strides in the past several years. 5, 5, 10 years, I think. so when you talk about what makes games different, I think, one thing games tend to do is they have a very limited set of things they're working with and they often want to make things run fast, and so they're working very close to the me They're not, they're not gonna use an XML parser, for example. [00:06:44] Elizabeth: They're just gonna talk directly as, directly to the graphics driver as they can. Right. And, and probably going to do all their own sound design. You know, I did talk about that XAudio library, but a lot of games will just talk directly as, directly to the sound driver as Windows Let some, so this is a often a blessing, honestly, because it means there's less we have to implement to make them work. when you look at a lot of productivity applications, and especially, the other thing that makes some productivity applications harder is, Microsoft makes 'em, and They like to, make a library, for use in this one program like Microsoft Office and then say, well, you know, other programs might use this as well. Let's. Put it in the operating system and expose it and write an API for it and everything. And maybe some other programs use it. mostly it's just office, but it means that office relies on a lot of things from the operating system that we all have to reimplement. [00:07:44] Jeremy: Yeah, that's somewhat counterintuitive because when you think of games, you think of these really high performance things that that seem really complicated. But it sounds like from what you're saying, because they use the lower level primitives, they're actually easier in some ways to support. [00:08:01] Elizabeth: Yeah, certainly in some ways, they, yeah, they'll do things like re-implement the heap allocator because the built-in heap allocator isn't fast enough for them. That's another good example. What makes some applications hard to support (Some are hard, can't debug other people's apps) [00:08:16] Jeremy: You mentioned Microsoft's more modern, uh, office suites. I, I've noticed there's certain applications that, that aren't supported. Like, for example, I think the modern Adobe Creative Suite. What's the difference with software like that and does that also apply to the modern office suite, or is, or is that actually supported? [00:08:39] Elizabeth: Well, in one case you have, things like Microsoft using their own APIs that I mentioned with Adobe. That applies less, I suppose, but I think to some degree, I think to some degree the answer is that some applications are just hard and there's, and, and there's no way around it. And, and we can only spend so much time on a hard application. I. Debugging things. Debugging things can get very hard with wine. Let's, let me like explain that for a minute because, Because normally when you think about debugging an application, you say, oh, I'm gonna open up my debugger, pop it in, uh, break at this point, see what like all the variables are, or they're not what I expect. Or maybe wait for it to crash and then get a back trace and see where it crashed. And why you can't do that with wine, because you don't have the application, you don't have the symbols, you don't have your debugging symbols. You don't know anything about the code you're running unless you take the time to disassemble and decompile and read through it. And that's difficult every time. It's not only difficult, every time I've, I've looked at a program and been like, I really need to just. I'm gonna just try and figure out what the program is doing. [00:10:00] Elizabeth: It takes so much time and it is never worth it. And sometimes you have to, sometimes you have no other choice, but usually you end up, you ask to rely on seeing what calls it makes into the operating system and trying to guess which one of those is going wrong. Now, sometimes you'll get lucky and it'll crash in wine code, or sometimes it'll make a call into, a function that we don't implement yet, and we know, oh, we need to implement that function. But sometimes it does something, more obscure and we have to figure out, well, like all of these millions of calls it made, which one of them is, which one of them are we implementing incorrectly? So it's returning the wrong result or not doing something that it should. And, then you add onto that the. You know, all these sort of harder to debug things like memory errors that we could make. And it's, it can be very difficult and so sometimes some applications just suffer from those hard bugs. and sometimes it's also just a matter of not enough demand for something for us to spend a lot of time on it. [00:11:11] Elizabeth: Right. [00:11:14] Jeremy: Yeah, I can see how that would be really challenging because you're, like you were saying, you don't have the symbols, so you don't have the source code, so you don't know what any of this software you're supporting, how it was actually written. And you were saying that I. A lot of times, you know, there may be some behavior that's wrong or a crash, but it's not because wine crashed or there was an error in wine. [00:11:42] Jeremy: so you just know the system calls it made, but you don't know which of the system calls didn't behave the way that the application expected. [00:11:50] Elizabeth: Exactly. Test suite (Half the code is tests) [00:11:52] Jeremy: I can see how that would be really challenging. and wine runs so many different applications. I'm, I'm kind of curious how do you even track what's working and what's not as you, you change wine because if you support thousands or tens thousands of applications, you know, how do you know when you've got a, a regression or not? [00:12:15] Elizabeth: So, it's a great question. Um, probably over half of wine by like source code volume. I actually actually check what it is, but I think it's, i, I, I think it's probably over half is what we call is tests. And these tests serve two purposes. The one purpose is a regression test. And the other purpose is they're conformance tests that test, that test how, uh, an API behaves on windows and validates that we are behaving the same way. So we write all these tests, we run them on windows and you know, write the tests to check what the windows returns, and then we run 'em on wine and make sure that that matches. and we have just such a huge body of tests to make sure that, you know, we're not breaking anything. And that every, every, all the code that we, that we get into wine that looks like, wow, it's doing that really well. Nope, that's what Windows does. The test says so. So pretty much any code that we, any new code that we get, it has to have tests to validate, to, to demonstrate that it's doing the right thing. [00:13:31] Jeremy: And so rather than testing against a specific application, seeing if it works, you're making a call to a Windows system call, seeing how it responds, and then making the same call within wine and just making sure they match. [00:13:48] Elizabeth: Yes, exactly. And that is obviously, or that is a lot more, automatable, right? Because otherwise you have to manually, you know, there's all, these are all graphical applications. [00:14:02] Elizabeth: You'd have to manually do the things and make sure they work. Um, but if you write automateable tests, you can just run them all and the machine will complain at you if it fails it continuous integration. How compatibility problems appear to users [00:14:13] Jeremy: And because there's all these potential compatibility issues where maybe a certain call doesn't behave the way an application expects. What, what are the types of what that shows when someone's using software? I mean, I, I think you mentioned crashes, but I imagine there could be all sorts of other types of behavior. [00:14:37] Elizabeth: Yes, very much so. basically anything, anything you can imagine again is, is what will happen. You can have, crashes are the easy ones because you know when and where it crashed and you can work backwards from there. but you can also get, it can, it could hang, it could not render, right? Like maybe render a black screen. for, you know, for games you could very frequently have, graphical glitches where maybe some objects won't render right? Or the entire screen will be read. Who knows? in a very bad case, you could even bring down your system and we usually say that's not wine's fault. That's the graphics library's fault. 'cause they're not supposed to do that, uh, no matter what we do. But, you know, sometimes we have to work around that anyway. but yeah, there's, there's been some very strange and idiosyncratic bugs out there too. [00:15:33] Jeremy: Yeah. And like you mentioned that uh, there's so many different things that could have gone wrong that imagine's very difficult to find. Yeah. And when software runs through wine, I think, Performance is comparable to native [00:15:49] Jeremy: A lot of our listeners will probably be familiar with running things in a virtual machine, and they know that there's a big performance impact from doing that. [00:15:57] Jeremy: How does the performance of applications compare to running natively on the original Windows OS versus virtual machines? [00:16:08] Elizabeth: So. In theory. and I, I haven't actually done this recently, so I can't speak too much to that, but in theory, the idea is it's a lot faster. so there, there, is a bit of a joke acronym to wine. wine is not an emulator, even though I started out by saying wine is an emulator, and it was originally called a Windows emulator. but what this basically means is wine is not a CPU emulator. It doesn't, when you think about emulators in a general sense, they're often, they're often emulators for specific CPUs, often older ones like, you know, the Commodore emulator or an Amiga emulator. but in this case, you have software that's written for an x86 CPU. And it's running on an x86 CPU by giving it the same instructions that it's giving on windows. It's just that when it says, now call this Windows function, it calls us instead. So that all should perform exactly the same. The only performance difference at that point is that all should perform exactly the same as opposed to a, virtual machine where you have to interpret the instructions and maybe translate them to a different instruction set. The only performance difference is going to be, in the functions that we are implementing themselves and we try to, we try to implement them to perform. As well, or almost as well as windows. There's always going to be a bit of a theoretical gap because we have to translate from say, one API to another, but we try to make that as little as possible. And in some cases, the operating system we're running on is, is just better than Windows and the libraries we're using are better than Windows. [00:18:01] Elizabeth: And so our games will run faster, for example. sometimes we can, sometimes we can, do a better job than Windows at implementing something that's, that's under our purview. there there are some games that do actually run a little bit faster in wine than they do on Windows. [00:18:22] Jeremy: Yeah, that, that reminds me of how there's these uh, gaming handhelds out now, and some of the same ones, they have a, they either let you install Linux or install windows, or they just come with a pre-installed, and I believe what I've read is that oftentimes running the same game on both operating systems, running the same game on Linux, the battery life is better and sometimes even the performance is better with these handhelds. [00:18:53] Jeremy: So it's, it's really interesting that that can even be the case. [00:18:57] Elizabeth: Yeah, it's really a testament to the huge amount of work that's gone into that, both on the wine side and on the, side of the graphics team and the colonel team. And, and of course, you know, the years of, the years of, work that's gone into Linux, even before these gaming handhelds were, were even under consideration. Proton and Valve Software's role [00:19:21] Jeremy: And something. So for people who are familiar with the handhelds, like the steam deck, they may have heard of proton. Uh, I wonder if you can explain what proton is and how it relates to wine. [00:19:37] Elizabeth: Yeah. So, proton is basically, how do I describe this? So, proton is a sort of a fork, uh, although we try to avoid the term fork. It's a, we say it's a downstream distribution because we contribute back up to wine. so it is a, it is, it is a alternate distribution fork of wine. And it's also some code that basically glues wine into, an embedding application originally intended for steam, and developed for valve. it has also been used in, others, but it has also been used in other software. it, so where proton differs from wine besides the glue part is it has some, it has some extra hacks in it for bugs that are hard to fix and easy to hack around as some quick hacks for, making games work now that are like in the process of going upstream to wine and getting their code quality improved and going through review. [00:20:54] Elizabeth: But we want the game to work now, when we distribute it. So that'll, that'll go into proton immediately. And then once we have, once the patch makes it upstream, we replace it with the version of the patch from upstream. there's other things to make it interact nicely with steam and so on. And yeah, I think, yeah, I think that's, I got it. [00:21:19] Jeremy: Yeah. And I think for people who aren't familiar, steam is like this, um, I, I don't even know what you call it, like a gaming store and a [00:21:29] Elizabeth: store game distribution service. it's got a huge variety of games on it, and you just publish. And, and it's a great way for publishers to interact with their, you know, with a wider gaming community, uh, after it, just after paying a cut to valve of their profits, they can reach a lot of people that way. And because all these games are on team and, valve wants them to work well on, on their handheld, they contracted us to basically take their entire catalog, which is huge, enormous. And trying and just step by step. Fix every game and make them all work. [00:22:10] Jeremy: So, um, and I guess for people who aren't familiar Valve, uh, softwares the company that runs steam, and so it sounds like they've asked, uh, your company to, to help improve the compatibility of their catalog. [00:22:24] Elizabeth: Yes. valve contracted us and, and again, when you're talking about wine using lower level libraries, they've also contracted a lot of other people outside of wine. Basically, the entire stack has had a tremendous, tremendous investment by valve software to make gaming on Linux work. Well. The entire stack receives changes to improve Wine compatibility [00:22:48] Jeremy: And when you refer to the entire stack, like what are some, some of those pieces, at least at a high level. [00:22:54] Elizabeth: I, I would, let's see, let me think. There is the wine project, the. Mesa Graphics Libraries. that's a, that's another, you know, uh, open source, software project that existed, has existed for a long time. But Valve has put a lot of, uh, funding and effort into it, the Linux kernel in various different ways. [00:23:17] Elizabeth: the, the desktop, uh, environment and Window Manager for, um, are also things they've invested in. [00:23:26] Jeremy: yeah. Everything that the game needs, on any level and, and that the, and that the operating system of the handheld device needs. Wine's history [00:23:37] Jeremy: And wine's been going on for quite a while. I think it's over a decade, right? [00:23:44] Elizabeth: I believe. Oh, more than, oh, far more than a decade. I believe it started in 1990, I wanna say about 1995, mid nineties. I'm, I probably have that date wrong. I believe Wine started about the mid nineties. [00:24:00] Jeremy: Mm. [00:24:00] Elizabeth: it's going on for three decades at this rate. [00:24:03] Jeremy: Wow. Okay. [00:24:06] Jeremy: And so all this time, how has the, the project sort of sustained itself? Like who's been involved and how has it been able to keep going this long? [00:24:18] Elizabeth: Uh, I think as is the case with a lot of free software, it just, it just keeps trudging along. There's been. There's been times where there's a lot of interest in wine. There's been times where there's less, and we are fortunate to be in a time where there's a lot of interest in it. we've had the same maintainer for almost this entire, almost this entire existence. Uh, Alexander Julliard, there was one person starting who started, maintained it before him and, uh, left it maintainer ship to him after a year or two. Uh, Bob Amstat. And there has been a few, there's been a few developers who have been around for a very long time. a lot of developers who have been around for a decent amount of time, but not for the entire duration. And then a very, very large number of people who come and submit a one-off fix for their individual application that they want to make work. [00:25:19] Jeremy: How does crossover relate to the wine project? Like, it sounds like you had mentioned Valve software hired you for subcontract work, but crossover itself has been around for quite a while. So how, how has that been connected to the wine project? [00:25:37] Elizabeth: So I work for, so the, so the company I work for is Code Weavers and, crossover is our flagship software. so Code Weavers is a couple different things. We have a sort of a porting service where companies will come to us and say, can we port my application usually to Mac? And then we also have a retail service where Where we basically have our own, similar to Proton, but you know, older, but the same idea where we will add some hacks into it for very difficult to solve bugs and we have a, a nice graphical interface. And then, the other thing that we're selling with crossover is support. So if you, you know, try to run a certain application and you buy crossover, you can submit a ticket saying this doesn't work and we now have a financial incentive to fix it. You know, we'll try to, we'll try to fix your, we'll spend company resources to fix your bug, right? So that's been so, so code we v has been around since 1996 and crossover, I don't know the date, but it's crossover has been around for probably about two decades, if I'm not mistaken. [00:27:01] Jeremy: And when you mention helping companies port their software to, for example, MacOS. [00:27:07] Jeremy: Is the approach that you would port it natively to MacOS APIs or is it that you would help them get it running using wine on MacOS? [00:27:21] Elizabeth: Right. That's, so that's basically what makes us so unique among porting companies is that instead of rewriting their software, we just, we just basically stick it inside of crossover and, uh, and, and make it run. [00:27:36] Elizabeth: And the idea has always been, you know, the more we implement, the more we get correct, the, the more applications will, you know, work. And sometimes it works out that way. Sometimes not really so much. And there's always work we have to do to get any given application to work, but. Yeah, so it's, it's very unusual because we don't ask companies for any of their code. We don't need it. We just fix the windows API [00:28:07] Jeremy: And, and so in that case, the ports would be let's say someone sells a MacOS version of their software. They would bundle crossover, uh, with their software. [00:28:18] Elizabeth: Right? And usually when you do this, it doesn't look like there's crossover there. Like it just looks like this software is native, but there is soft, there is crossover under the hood. Loading executables and linked libraries [00:28:32] Jeremy: And so earlier we were talking about how you're basically intercepting the system calls that these binaries are making, whether that's the executable or the, the DLLs from Windows. Um, but I think probably a lot of our listeners are not really sure how that's done. Like they, they may have built software, but they don't know, how do I basically hijack, the system calls that this application is making. [00:29:01] Jeremy: So maybe you could talk a little bit about how that works. [00:29:04] Elizabeth: So there, so there's a couple steps to go into it. when you think about a program that's say, that's a big, a big file that's got all the machine code in it, and then it's got stuff at the beginning saying, here's how the program works and here's where in the file the processor should start running. that's, that's your EXE file. And then in your DLL files are libraries that contain shared code and you have like a similar sort of file. It says, here's the entry point. That runs this function, this, you know, this pars XML function or whatever have you. [00:29:42] Elizabeth: And here's this entry point that has the generate XML function and so on and so forth. And, and, then the operating system will basically take the EXE file and see all the bits in it. Say I want to call the pars XML function. It'll load that DLL and hook it up. So it, so the processor ends up just seeing jump directly to this pars XML function and then run that and then return and so on. [00:30:14] Elizabeth: And so what wine does, is it part of wine? That's part of wine is a library, is that, you know, the implementing that parse XML and read XML function, but part of it is the loader, which is the part of the operating system that hooks everything together. And when we load, we. Redirect to our libraries. We don't have Windows libraries. [00:30:38] Elizabeth: We like, we redirect to ours and then we run our code. And then when you jump back to the program and yeah. [00:30:48] Jeremy: So it's the, the loader that's a part of wine. That's actually, I'm not sure if running the executable is the right term. [00:30:58] Elizabeth: no, I think that's, I think that's a good term. It's, it's, it's, it starts in a loader and then we say, okay, now run the, run the machine code and it's executable and then it runs and it jumps between our libraries and back and so on. [00:31:14] Jeremy: And like you were saying before, often times when it's trying to make a system call, it ends up being handled by a function that you've written in wine. And then that in turn will call the, the Linux system calls or the MacOS system calls to try and accomplish the, the same result. [00:31:36] Elizabeth: Right, exactly. [00:31:40] Jeremy: And something that I think maybe not everyone is familiar with is there's this concept of user space versus kernel space. you explain what the difference is? [00:31:51] Elizabeth: So the way I would explain, the way I would describe a kernel is it's the part of the operating system that can do anything, right? So any program, any code that runs on your computer is talking to the processor, and the processor has to be able to do anything the computer can do. [00:32:10] Elizabeth: It has to be able to talk to the hardware, it has to set up the memory space. That, so actually a very complicated task has to be able to switch to another task. and, and, and, and basically talk to another program and. You have to have something there that can do everything, but you don't want any program to be able to do everything. Um, not since the, not since the nineties. It's about when we realized that we can't do that. so the kernel is a part that can do everything. And when you need to do something that requires those, those permissions that you can't give everyone, you have to talk to the colonel and ask it, Hey, can you do this for me please? And in a very restricted way where it's only the safe things you can do. And a degree, it's also like a library, right? It's the kernel. The kernels have always existed, and since they've always just been the core standard library of the computer that does the, that does the things like read and write files, which are very, very complicated tasks under the hood, but look very simple because all you say is write this file. And talk to the hardware and abstract away all the difference between different drivers. So the kernel is doing all of these things. So because the kernel is a part that can do everything and because when you think about the kernel, it is basically one program that is always running on your computer, but it's only one program. So when a user calls the kernel, you are switching from one program to another and you're doing a lot of complicated things as part of this. You're switching to the higher privilege level where you can do anything and you're switching the state from one program to another. And so it's a it. So this is what we mean when we talk about user space, where you're running like a normal program and kernel space where you've suddenly switched into the kernel. [00:34:19] Elizabeth: Now you're executing with increased privileges in a different. idea of the process space and increased responsibility and so on. [00:34:30] Jeremy: And, and so do most applications. When you were talking about the system calls for handling 3D audio or parsing XML. Are those considered, are those system calls considered part of user space and then those things call the kernel space on your behalf, or how, how would you describe that? [00:34:50] Elizabeth: So most, so when you look at Windows, most of most of the Windows library, the vast, vast majority of it is all user space. most of these libraries that we implement never leave user space. They never need to call into the kernel. there's the, there only the core low level stuff. Things like, we need to read a file, that's a kernel call. when you need to sleep and wait for some seconds, that's a kernel. Need to talk to a different process. Things that interact with different processes in general. not just allocate memory, but allocate a page of memory, like a, from the memory manager and then that gets sub allocated by the heap allocator. so things like that. [00:35:31] Jeremy: Yeah, so if I was writing an application and I needed to open a file, for example, does, does that mean that I would have to communicate with the kernel to, to read that file? [00:35:43] Elizabeth: Right, exactly. [00:35:46] Jeremy: And so most applications, it sounds like it's gonna be a mixture. You're gonna have a lot of things that call user space calls. And then a few, you mentioned more low level ones that are gonna require you to communicate with the kernel. [00:36:00] Elizabeth: Yeah, basically. And it's worth noting that in, in all operating systems, you're, you're almost always gonna be calling a user space library. That might just be a thin wrapper over the kernel call. It might, it's gonna do like just a little bit of work in end call the kernel. [00:36:19] Jeremy: [00:36:19] Elizabeth: In fact, in Windows, that's the only way to do it. Uh, in many other operating systems, you can actually say, you can actually tell the processor to make the kernel call. There is a special instruction that does this and just, and it'll go directly to the kernel, and there's a defined interface for this. But in Windows, that interface is not defined. It's not stable. Or backwards compatible like the rest of Windows is. So even if you wanted to use it, you couldn't. and you basically have to call into the high level libraries or low level libraries, as it were, that, that tell you that create a file. And those don't do a lot. [00:37:00] Elizabeth: They just kind of tweak their parameters a little and then pass them right down to the kernel. [00:37:07] Jeremy: And so wine, it sounds like it needs to implement both the user space calls of windows, but then also the, the kernel, calls as well. But, but wine itself does that, is that only in Linux user space or MacOS user space? [00:37:27] Elizabeth: Yes. This is a very tricky thing. but all of wine, basically all of what is wine runs in, in user space and we use. Kernel calls that are already there to talk to the colonel, to talk to the host Colonel. You have to, and you, you get, you get, you get the sort of second nature of thinking about the Windows, user space and kernel. [00:37:50] Elizabeth: And then there's a host user space and Kernel and wine is running all in user, in the user, in the host user space, but it's emulating the Windows kernel. In fact, one of the weirdest, trickiest parts is I mentioned that you can run some drivers in wine. And those drivers actually, they actually are, they think they're running in the Windows kernel. which in a sense works the same way. It has libraries that it can load, and those drivers are basically libraries and they're making, kernel calls and they're, they're making calls into the kernel library that does some very, very low level tasks that. You're normally only supposed to be able to do in a kernel. And, you know, because the kernel requires some privileges, we kind of pretend we have them. And in many cases, you're even the drivers are using abstractions. We can just implement those abstractions kind of over the slightly higher level abstractions that exist in user space. [00:39:00] Jeremy: Yeah, I hadn't even considered the being able to use hardware devices, but I, I suppose if in, in the end, if you're reproducing the kernel, then whether you're running software or you're talking to a hardware device, as long as you implement the calls correctly, then I, I suppose it works. [00:39:18] Elizabeth: Cause you're, you're talking about device, like maybe it's some kind of USB device that has drivers for Windows, but it doesn't for, for Linux. [00:39:28] Elizabeth: no, that's exactly, that's a, that's kind of the, the example I've used. Uh, I think there is, I think I. My, one of my best success stories was, uh, drivers for a graphing calculator. [00:39:41] Jeremy: Oh, wow. [00:39:42] Elizabeth: That connected via USB and I basically just plugged the windows drivers into wine and, and ran it. And I had to implement a lot of things, but it worked. But for example, something like a graphics driver is not something you could implement in wine because you need the graphics driver on the host. We can't talk to the graphics driver while the host is already doing so. [00:40:05] Jeremy: I see. Yeah. And in that case it probably doesn't make sense to do so [00:40:11] Elizabeth: Right? [00:40:12] Elizabeth: Right. It doesn't because, the transition from user into kernel is complicated. You need the graphics driver to be in the kernel and the real kernel. Having it in wine would be a bad idea. Yeah. [00:40:25] Jeremy: I, I think there's, there's enough APIs you have to try and reproduce that. I, I think, uh, doing, doing something where, [00:40:32] Elizabeth: very difficult [00:40:33] Jeremy: right. Poor system call documentation and private APIs [00:40:35] Jeremy: There's so many different, calls both in user space and in kernel space. I imagine the, the user space ones Microsoft must document to some extent, but, oh. Is that, is that a [00:40:51] Elizabeth: well, sometimes, [00:40:54] Jeremy: Sometimes. Okay. [00:40:55] Elizabeth: I think it's actually better now than it used to be. But some, here's where things get fun, because sometimes there will be, you know, regular documented calls. Sometimes those calls are documented, but the documentation isn't very good. Sometimes programs will just sort of look inside Microsoft's DLLs and use calls that they aren't supposed to be using. Sometimes they use calls that they are supposed to be using, but the documentation has disappeared. just because it's that old of an API and Microsoft hasn't kept it around. sometimes some, sometimes Microsoft, Microsoft own software uses, APIs that were never documented because they never wanted anyone else using them, but they still ship them with the operating system. there was actually a kind of a lawsuit about this because it is an antitrust lawsuit, because by shipping things that only they could use, they were kind of creating a trust. and that got some things documented. At least in theory, they kind of haven't stopped doing it, though. [00:42:08] Jeremy: Oh, so even today they're, they're, I guess they would call those private, private APIs, I suppose. [00:42:14] Elizabeth: I suppose. Uh, yeah, you could say private APIs. but if we want to get, you know, newer versions of Microsoft Office running, we still have to figure out what they're doing and implement them. [00:42:25] Jeremy: And given that they're either, like you were saying, the documentation is kind of all over the place. If you don't know how it's supposed to behave, how do you even approach implementing them? [00:42:38] Elizabeth: and that's what the conformance tests are for. And I, yeah, I mentioned earlier we have this huge body of conformance tests that double is regression tests. if we see an API, we don't know what to do with or an API, we do know, we, we think we know what to do with because the documentation can just be wrong and often has been. Then we write tests to figure out what it's supposed to behave. We kind of guess until we, and, and we write tests and we pass some things in and see what comes out and see what. The see what the operating system does until we figure out, oh, so this is what it's supposed to do and these are the exact parameters in, and, and then we, and, and then we implement it according to those tests. [00:43:24] Jeremy: Is there any distinction in approach for when you're trying to implement something that's at the user level versus the kernel level? [00:43:33] Elizabeth: No, not really. And like I, and like I mentioned earlier, like, well, I mean, a kernel call is just like a library call. It's just done in a slightly different way, but it's still got, you know, parameters in, it's still got a set of parameters. They're just encoded differently. And, and again, like the, the way kernel calls are done is on a level just above the kernel where you have a library, that just passes things through. Almost verbatim to the kernel and we implement that library instead. [00:44:10] Jeremy: And, and you've been working on i, I think, wine for over, over six years now. [00:44:18] Elizabeth: That sounds about right. Debugging and having broad knowledge of Wine [00:44:20] Jeremy: What does, uh, your, your day to day look like? What parts of the project do you, do you work on? [00:44:27] Elizabeth: It really varies from day to day. and I, I, a lot of people, a lot of, some people will work on the same parts of wine for years. Uh, some people will switch around and work on all sorts of different things. [00:44:42] Elizabeth: And I'm, I definitely belong to that second group. Like if you name an area of wine, I have almost certainly contributed a patch or two to it. there's some areas I work on more than others, like, 3D graphics, multimedia, a, I had, I worked on a compiler that exists, uh, socket. So networking communication is another thing I work a lot on. day to day, I kind of just get, I, I I kind of just get a bug for some program or another. and I take it and I debug it and figure out why the program's broken and then I fix it. And there's so much variety in that. because a bug can take so many different forms like I described, and, and, and the, and then the fix can be simple or complicated or, and it can be in really anywhere to a degree. [00:45:40] Elizabeth: being able to work on any part of wine is sometimes almost a necessity because if a program is just broken, you don't know why. It could be anything. It could be any sort of API. And sometimes you can hand the API to somebody who's got a lot of experience in that, but sometimes you just do whatever. You just fix whatever's broken and you get an experience that way. [00:46:06] Jeremy: Yeah, I mean, I was gonna ask about the specialized skills to, to work on wine, but it sounds like maybe in your case it's all of them. [00:46:15] Elizabeth: It's, there's a bit of that. it's a wine. We, the skills to work on wine are very, it's a very unique set of skills because, and it largely comes down to debugging because you can't use the tools you normally use debug. [00:46:30] Elizabeth: You have to, you have to be creative and think about it different ways. Sometimes you have to be very creative. and programs will try their hardest to avoid being debugged because they don't want anyone breaking their copy protection, for example, or or hacking, or, you know, hacking in sheets. They want to be, they want, they don't want anyone hacking them like that. [00:46:54] Elizabeth: And we have to do it anyway for good and legitimate purposes. We would argue to make them work better on more operating systems. And so we have to fight that every step of the way. [00:47:07] Jeremy: Yeah, it seems like it's a combination of. F being able, like you, you were saying, being able to, to debug. and you're debugging not necessarily your own code, but you're debugging this like behavior of, [00:47:25] Jeremy: And then based on that behavior, you have to figure out, okay, where in all these different systems within wine could this part be not working? [00:47:35] Jeremy: And I, I suppose you probably build up some kind of, mental map in your head of when you get a, a type of bug or a type of crash, you oh, maybe it's this, maybe it's here, or something [00:47:47] Elizabeth: Yeah. That, yeah, there is a lot of that. there's, you notice some patterns, you know, after experience helps, but because any bug could be new, sometimes experience doesn't help and you just, you just kind of have to start from scratch. Finding a bug related to XAudio [00:48:08] Jeremy: At sort of a high level, can you give an example of where you got a specific bug report and then where you had to look to eventually find which parts of the the system were the issue? [00:48:21] Elizabeth: one, one I think good example, that I've done recently. so I mentioned this, this XAudio library that does 3D audio. And if you say you come across a bug, I'm gonna be a little bit generics here and say you come across a bug where some audio isn't playing right, maybe there's, silence where there should be the audio. So you kind of, you look in and see, well, where's that getting lost? So you can basically look in the input calls and say, here's the buffer it's submitting that's got all the audio data in it. And you look at the output, you look at where you think the output should be, like, that library will internally call a different library, which programs can interact with directly. [00:49:03] Elizabeth: And this our high level library interacts with that is the, give this sound to the audio driver, right? So you've got XAudio on top of, um. mdev, API, which is the other library that gives audio to the driver. And you see, well, the ba the buffer is that XAudio is passing into MM Dev, dev API. They're empty, there's nothing in them. So you have to kind of work through the XAudio library to see where is, where's that sound getting lost? Or maybe, or maybe that's not getting lost. Maybe it's coming through all garbled. And I've had to look at the buffer and see why is it garbled. I'll open up it up in Audacity and look at the weight shape of the wave and say, huh, that shape of the wave looks like it's, it looks like we're putting silence every 10 nanoseconds or something, or, or reversing something or interpreting it wrong. things like that. Um, there's a lot of, you'll do a lot of, putting in print fs basically all throughout wine to see where does the state change. Where was, where is it? Where is it? Right? And then where do things start going wrong? [00:50:14] Jeremy: Yeah. And in the audio example, because they're making a call to your XAudio implementation, you can see that Okay, the, the buffer, the audio that's coming in. That part is good. It, it's just that later on when it sends it to what's gonna actually have it be played by the, the hardware, that's when missing. So, [00:50:37] Elizabeth: We did something wrong in a library that destroyed the buffer. And I think on a very, high level a lot of debugging, wine is about finding where things are good and finding where things are bad, and then narrowing that down until we find the one spot where things go wrong. There's a lot of processes that go like that. [00:50:57] Jeremy: like you were saying, the more you see these problems, hopefully the, the easier it gets to, to narrow down where, [00:51:04] Elizabeth: Often. Yeah. Especially if you keep debugging things in the same area. How much code is OS specific?c [00:51:09] Jeremy: And wine supports more than one operating system. I, I saw there was Linux, MacOS I think free BSD. How much of the code is operating system specific versus how much can just be shared across all of them? [00:51:27] Elizabeth: Not that much is operating system specific actually. so when you think about the volume of wine, the, the, the, vast majority of it is the high level code that doesn't need to interact with the operating system on a low level. Right? Because Windows keeps putting, because Microsoft keeps putting lots and lots of different libraries in their operating system. And a lot of these are high level libraries. and even when we do interact with the operating system, we're, we're using cross-platform libraries or we're using, we're using ics. The, uh, so all these operating systems that we are implementing are con, basically conformed to the posix standard. which is basically like Unix, they're all Unix based. Psic is a Unix based standard. Microsoft is, you know, the big exception that never did implement that. And, and so we have to translate its APIs to Unix, APIs. now that said, there is a lot of very operating system, specific code. Apple makes things difficult by try, by diverging almost wherever they can. And so we have a lot of Apple specific code in there. [00:52:46] Jeremy: another example I can think of is, I believe MacOS doesn't support, Vulkan [00:52:53] Elizabeth: yes. Yeah.Yeah, That's a, yeah, that's a great example of Mac not wanting to use, uh, generic libraries that work on every other operating system. and in some cases we, we look at it and are like, alright, we'll implement a wrapper for that too, on top of Yuri, on top of your, uh, operating system. We've done it for Windows, we can do it for Vulkan. and that's, and then you get the Molten VK project. Uh, and to be clear, we didn't invent molten vk. It was around before us. We have contributed a lot to it. Direct3d, Vulkan, and MoltenVK [00:53:28] Jeremy: Yeah, I think maybe just at a high level might be good to explain the relationship between Direct 3D or Direct X and Vulcan and um, yeah. Yeah. Maybe if you could go into that. [00:53:42] Elizabeth: so Direct 3D is Microsoft's 3D API. the 3D APIs, you know, are, are basically a way to, they're way to firstly abstract out the differences between different graphics, graphics cards, which, you know, look very different on a hardware level. [00:54:03] Elizabeth: Especially. They, they used to look very different and they still do look very different. and secondly, a way to deal with them at a high level because actually talking to the graphics card on a low level is very, very complicated. Even talking to it on a high level is complicated, but it gets, it can get a lot worse if you've ever been a, if you've ever done any graphics, driver development. so you have a, a number of different APIs that achieve these two goals of, of, abstraction and, and of, of, of building a common abstraction and of building a, a high level abstraction. so OpenGL is the broadly the free, the free operating system world, the non Microsoft's world's choice, back in the day. [00:54:53] Elizabeth: And then direct 3D was Microsoft's API and they've and Direct 3D. And both of these have evolved over time and come up with new versions and such. And when any, API exists for too long. It gains a lot of croft and needs to be replaced. And eventually, eventually the people who developed OpenGL decided we need to start over, get rid of the Croft to make it cleaner and make it lower level. [00:55:28] Elizabeth: Because to get in a maximum performance games really want low level access. And so they made Vulcan, Microsoft kind of did the same thing, but they still call it Direct 3D. they just, it's, it's their, the newest version of Direct 3D is lower level. It's called Direct 3D 12. and, and, Mac looked at this and they decided we're gonna do the same thing too, but we're not gonna use Vulcan. [00:55:52] Elizabeth: We're gonna define our own. And they call it metal. And so when we want to translate D 3D 12 into something that another operating system understands. That's probably Vulcan. And, and on Mac, we need to translate it to metal somehow. And we decided instead of having a separate layer from D three 12 to metal, we're just gonna translate it to Vulcan and then translate the Vulcan to metal. And it also lets things written for Vulcan on Windows, which is also a thing that exists that lets them work on metal. [00:56:30] Jeremy: And having to do that translation, does that have a performance impact or is that not really felt? [00:56:38] Elizabeth: yes. It's kind of like, it's kind of like anything, when you talk about performance, like I mentioned this earlier, there's always gonna be overhead from translating from one API to another. But we try to, what we, we put in heroic efforts to. And try, try to make sure that doesn't matter, to, to make sure that stuff that needs to be fast is really as fast as it can possibly be. [00:57:06] Elizabeth: And some very clever things have been done along those lines. and, sometimes the, you know, the graphics drivers underneath are so good that it actually does run better, even despite the translation overhead. And then sometimes to make it run fast, we need to say, well, we're gonna implement a new API that behaves more like windows, so we can do less work translating it. And that's, and sometimes that goes into the graphics library and sometimes that goes into other places. Targeting Wine instead of porting applications [00:57:43] Jeremy: Yeah. Something I've found a little bit interesting about the last few years is [00:57:49] Jeremy: Developers in the past, they would generally target Windows and you might be lucky to get a Mac port or a Linux port. And I wonder, like, in your opinion now, now that a lot of developers are just targeting Windows and relying on wine or, or proton to, to run their software, is there any, I suppose, downside to doing that? [00:58:17] Jeremy: Or is it all just upside, like everyone should target Windows as this common platform? [00:58:23] Elizabeth: Yeah. It's an interesting question. I, there's some people who seem to think it's a bad thing that, that we're not getting native ports in the same sense, and then there's some people who. Who See, no, that's a perfectly valid way to do ports just right for this defacto common API it was never intended as a cross platform common API, but we've made it one. [00:58:47] Elizabeth: Right? And so why is that any worse than if it runs on a different API on on Linux or Mac and I? Yeah, I, I, I guess I tend to, I, that that argument tends to make sense to me. I don't, I don't really see, I don't personally see a lot of reason for, to, to, to say that one library is more pure than another. [00:59:12] Elizabeth: Right now, I do think Windows APIs are generally pretty bad. I, I'm, this might be, you know, just some sort of, this might just be an effect of having to work with them for a very long time and see all their flaws and have to deal with the nonsense that they do. But I think that a lot of the. Native Linux APIs are better. But if you like your Windows API better. And if you want to target Windows and that's the only way to do it, then sure why not? What's wrong with that? [00:59:51] Jeremy: Yeah, and I think the, doing it this way, targeting Windows, I mean if you look in the past, even though you had some software that would be ported to other operating systems without this compatibility layer, without people just targeting Windows, all this software that people can now run on these portable gaming handhelds or on Linux, Most of that software was never gonna be ported. So yeah, absolutely. And [01:00:21] Elizabeth: that's [01:00:22] Jeremy: having that as an option. Yeah. [01:00:24] Elizabeth: That's kind of why wine existed, because people wanted to run their software. You know, that was never gonna be ported. They just wanted, and then the community just spent a lot of effort in, you know, making all these individual programs run. Yeah. [01:00:39] Jeremy: I think it's pretty, pretty amazing too that, that now that's become this official way, I suppose, of distributing your software where you say like, Hey, I made a Windows version, but you're on your Linux machine. it's officially supported because, we have this much belief in this compatibility layer. [01:01:02] Elizabeth: it's kind of incredible to see wine having got this far. I mean, I started working on a, you know, six, seven years ago, and even then, I could never have imagined it would be like this. [01:01:16] Elizabeth: So as we, we wrap up, for the developers that are listening or, or people who are just users of wine, um, is there anything you think they should know about the project that we haven't talked about? [01:01:31] Elizabeth: I don't think there's anything I can think of. [01:01:34] Jeremy: And if people wanna learn, uh, more about the wine project or, or see what you're up to, where, where should they, where should they head? Getting support and contributing [01:01:45] Elizabeth: We don't really have any things like news, unfortunately. Um, read the release notes, uh, follow some, there's some, there's some people who, from Code Weavers who do blogs. So if you, so if you go to codeweavers.com/blog, there's some, there's, there's some codeweavers stuff, uh, some marketing stuff. But there's also some developers who will talk about bugs that they are solving and. And how it's easy and, and the experience of working on wine. [01:02:18] Jeremy: And I suppose if, if someone's. Interested in like, like let's say they have a piece of software, it's not working through wine. what's the best place for them to, to either get help or maybe even get involved with, with trying to fix it? [01:02:37] Elizabeth: yeah. Uh, so you can file a bug on, winehq.org,or, or, you know, find, there's a lot of developer resources there and you can get involved with contributing to the software. And, uh, there, there's links to our mailing list and IRC channels and, uh, and, and the GitLab, where all places you can find developers. [01:03:02] Elizabeth: We love to help you. Debug things. We love to help you fix things. We try our very best to be a welcoming community and we have got a long, we've got a lot of experience working with people who want to get their application working. So, we would love to, we'd love to have another. [01:03:24] Jeremy: Very cool. Yeah, I think wine is a really interesting project because I think for, I guess it would've been for decades, it seemed like very niche, like not many people [01:03:37] Jeremy: were aware of it. And now I think maybe in particular because of the, the Linux gaming handhelds, like the steam deck,wine is now something that a bunch of people who would've never heard about it before, and now they're aware of it. [01:03:53] Elizabeth: Absolutely. I've watched that transformation happen in real time and it's been surreal. [01:04:00] Jeremy: Very cool. Well, Elizabeth, thank you so much for, for joining me today. [01:04:05] Elizabeth: Thank you, Jeremy. I've been glad to be here.

Guest: Shawn Villaron, Vice President of Customer and Strategic Initiatives, Office Product Group at Microsoft | Former VP & GM of PowerPoint | Bay Area Site Leader | Executive Sponsor of HOLA   Episode Overview In this episode, we sit down with Shawn Villaron, a 29-year veteran at Microsoft who has helped shape some of the company's most widely used products and strategies. Now serving as Vice President of Customer and Strategic Initiatives in the Office Product Group, Shawn partners with Microsoft's most important customers to better understand their needs around AI, workplace modernization, and productivity—insights that directly shape the future of Microsoft Office. Previously, Shawn was Vice President & General Manager for PowerPoint, where he led teams across multiple platforms—Windows, Mac, Web, iPad, Android, and iOS—reimagining how billions of people create and deliver stories. He also serves as Engineering Site Leader for Microsoft Bay Area, working across commercial, consumer, hardware, and AI platforms, while championing diversity and inclusion as executive sponsor of HOLA (Hispanic & Latinx Organization of Leaders in Action). Shawn brings a rare perspective: spending nearly three decades at a single company, driving innovation from the inside, and now exploring how AI and agents are reshaping the way we work, create, and build businesses. What You'll Learn in This Episode The positives and challenges of building an entire career at one company in the fast-moving tech world. How PowerPoint and Office are being reimagined for the AI storytelling era. Practical ways companies can encourage employees to use AI responsibly and effectively. How leaders can use AI to boost both creativity and productivity within teams. When employees might be using too much AI—or not enough. What it means to become an “AI Agent Boss” and how agents can give startups enterprise-level capabilities. Whether the concept of the one-person unicorn is realistic, and what's still missing. How recent graduates can stand out in an AI-driven job market. The emerging technologies Microsoft's Bay Area teams are most excited about right now. One piece of advice Shawn would give to founders and technologists building the next generation of workplace tools. Key Questions We Discuss What are the upsides and downsides of staying at one company for nearly three decades? How is Microsoft rethinking storytelling with AI in PowerPoint and Office? How can leaders balance productivity and creativity when adopting AI tools? What role will AI Agents play in empowering both startups and enterprises? Are we truly heading toward the era of the one-person unicorn? What advice would you give to graduates entering an AI-powered job market? Which emerging technologies are your Bay Area teams most focused on right now? About Shawn Villaron Shawn Villaron is Vice President of Customer and Strategic Initiatives in the Microsoft Office Product Group, where he drives strategy by working closely with top customers to shape the future of AI and productivity. Previously, he served as Vice President & GM of PowerPoint, guiding the product across every platform and ensuring seamless experiences for millions of users. He also serves as Engineering Site Leader for Microsoft Bay Area and as executive sponsor of HOLA, advancing diversity and inclusion at Microsoft. Resources & Links LinkedIn: Shawn Villaron | LinkedIn Microsoft Bay Area Blog: Microsoft Bay Area Blog Microsoft Work Trend Index: The 2025 Annual Work Trend Index: The Frontier Firm is Born   The views expressed on this podcast are for informational purposes only and do not constitute financial or legal advice. Please consult with a professional for guidance on your specific situation. The opinions shared are my own and do not necessarily reflect the views of Finalis Inc. or Finalis Securities LLC, Member FINRA/SIPC.

A story about passing lucrative deals to competitors—and building something users refuse to give upThis episode is for SaaS founders exhausted from chasing every opportunity—and wondering if extreme focus actually works.Most SaaS companies don't fail because of bad tech. They fail because they can't stop building.Ray Meiring, CEO of QorusDocs, discovered this during a meeting with a bank CIO. While trying to find use cases for their generic document tool, Ray realized they had it backwards—they were hunting for problems to fit their solution instead of solving a specific problem.That realization changed everything. Ray narrowed QorusDocs from "any document" to proposals to specific verticals. He even developed a system for passing lucrative but wrong-fit customers directly to competitors.And this inspired me to invite Ray to my podcast. We explore how narrowing from documents to proposals to law firms and engineering firms created users who'd "pry QorusDocs from their cold dead hands." Ray shares why moving 10,000 miles to Seattle transformed their network, how building inside Microsoft Office became their differentiator, and why consistency beats constant pivoting. You'll discover how saying no to features actually accelerated growth.We also zoom in on three of the 10 traits that define remarkable software companies:Acknowledge you can't please everyoneAim to be different, not just betterFocus on the essenceRay's story shows how narrowing your focus can multiply your impact.Here's one of Ray's quotes that captures his philosophy:"We were trying to be everything to everyone and just build this very generic product. But as we worked with more customers, we started to see a pattern around a very specific set of documents that were challenging—proposal documents."By listening to this episode, you'll learn:Why the A-B-Z framework beats traditional segmentationWhat happens when you deprecate features instead of adding themWhen proximity to customers trumps remote efficiencyWhy integration beats innovation for enterprise retentionFor more information about the guest from this week:Guest: Ray Meiring, CEO QorusDocsWebsite: qorusdocs.com

The Power of Partnership: Upskilling for Eastern KentuckyGuests:- Dottie Nolan: EKCEP Training Coordinator- Linda Chen & Donnie Grimes: The Center for Professional Development, University of the CumberlandsEpisode Highlights:The Need: Dottie discusses why EKCEP saw a need for new, customized certification courses to make job seekers more employable.The Partnership: The team explains the collaborative process of creating custom, asynchronous training programs that clients can complete on their own time.The Courses: We break down the key skills covered in four certification programs:Financial Literacy: Budgeting, credit, and banking basics.Customer Service: Skills for customer-facing roles across various industries.Digital Literacy: Computer skills, online safety, and software like Microsoft Office.Real-World Impact: We hear a success story and discuss how these certifications demonstrate a candidate's value to potential employers.The Future: Our guests share what's next for this successful partnership and potential new course offerings.Get Involved: Dottie explains how EKCEP clients can sign up for these exclusive, no-cost training opportunities.Thank you to our guests! To learn more about EKCEP's services or to find a job, visit ekcep.org or your local Kentucky Career Center.

Moving your business email from one system to another sounds straightforward until it isn't. Susan learned this the hard way during a weekend-long migration that revealed every hidden complexity you never think to ask about upfront. In this episode, she breaks down the five critical questions every business owner must answer before switching email systems - questions that could save you from your own technical nightmare and budget explosion. The 5 Questions That Prevent Email Migration Disasters How big are your mailboxes, and where is your old mail stored? Large mailboxes with years of Sent/Deleted items cause export failures. You need to know mailbox sizes and whether users keep local PST files before you can estimate the timeline. Who will be available during the actual migration for testing and approvals? Migrations require live client participation for password resets, login approvals, and testing. Without committed availability, projects stall. How do your users actually access their email today? Classic Outlook, new Outlook, web-only, mobile apps - each requires different configuration steps. Mixed environments multiply complexity. What domains and aliases are tied to your current email system? Hidden alias domains and Microsoft's "ownership" of domains can prevent a clean cutover to Google. You need the complete domain picture upfront. Do you need to keep Microsoft Office apps or other integrations? Many businesses use Microsoft 365 for more than email. Licensing decisions affect migration approach and ongoing costs. Subscribe to Susan's blog for a series on this topic.  Blog series on the topic of tech stacks and email migration.

In this episode, I'm joined by Microsoft Office maestro Shelley Fishel, founder of Tomorrow's VA. Shelley has spent decades training assistants to get brilliant results with Word, Excel, PowerPoint, Outlook and now, of course, Microsoft Copilot. We dig into what's genuinely useful right now, what's coming next, and how EAs can lead the conversation on AI without losing sight of the fundamentals.Shelley shares how she uses Copilot daily (from redrafting tricky emails to prioritising the inbox and summarising meetings), why core skills like slide masters and brand-safe templates still matter, and how to make the most of lesser-known gems across Microsoft 365. We also talk mindset—staying curious, learning out loud, and saying “yes” then figuring it out—plus the big question: Will AI replace EAs? (Short answer: no. Nuance, judgment, and calendar strategy still need a human.)What you'll learn:Practical ways EAs can use Copilot today in Outlook, Teams, Word and beyondWhy knowing the basics (formatting, slide masters, rules/quick steps) saves hours every weekHow to make a case for Copilot licences—and the security benefits of using it inside your tenantMindset shifts to keep pace with fast-moving tech (without chasing every shiny thing)Where Microsoft 365 is quietly evolving—and the features most assistants overlookTools, features & terms mentioned:Microsoft Copilot across Outlook, Word, Teams (meeting summaries), and forthcoming Excel capabilities (including =COPILOT)Outlook: Quick Steps, Rules, prioritising the inboxPowerPoint: Slide Master, custom layouts, brand-safe decksMicrosoft Loop (pages & live components), Copilot PagesMicrosoft Sway (lightweight, web-style internal newsletters)Microsoft Forms, Microsoft Lists, Microsoft BookingsSecurity/Tenant awareness (enterprise data protection vs. pasting data into public AI tools)Other AI tools touched on: ChatGPT, Claude, PerplexityPerfect for: Executive Assistants who want clear, real-world ways to work smarter with Microsoft 365 and lead on AI - without the hype.

News and Updates: The Republican-led FCC is moving to kill its 1Gbps broadband speed goal, arguing that such benchmarks unfairly disadvantage satellite and fixed wireless services like Starlink and T-Mobile Home Internet. Chair Brendan Carr says the current 100/25 Mbps standard is more "technologically neutral," though critics warn the move could hinder fiber rollout and inflate broadband availability stats. Microsoft Office 2024 is now available as a one-time $149 purchase with no feature updates, while Microsoft 365 remains a subscription service ($70–$100/year) offering cloud storage, constant updates, mobile access, and AI tools. Office 2024 suits offline users or regulated industries, while 365 is better for collaboration, flexibility, and long-term value. A single weak password allowed hackers to take down 158-year-old UK transport firm KNP. Ransomware gang Akira encrypted all company data and demanded a multi-million-pound ransom. Without backups or sufficient protection, KNP collapsed, laying off 700 workers. UK officials say ransomware incidents are rising rapidly, with 35–40 attacks per week and growing concern over underreporting and ransom payments. Tesla was forced to refund a customer $10,000 after an arbitrator ruled the company failed to deliver its Full Self-Driving (FSD) package. The buyer couldn't access FSD due to eligibility restrictions and noted that the software didn't perform as promised. Tesla provided a poorly prepared witness in arbitration and had to cover both the refund and $8,000 in arbitration fees. The decision highlights ongoing doubts about Tesla's ability to fulfill its long-standing autonomous driving claims.

Choosing between Google Docs and Microsoft 365? They look similar, but there are differences in cost, features, and how they work. I'll help you decide which fits your needs best.

Join Brian and Mike Cohn as they unpack the five essential pillars that take Agile from “just the motions” to meaningful, measurable impact. Plus, get a behind-the-scenes look at their revamped course built for real team transformation. Overview In this episode of the Agile Mentors Podcast, Brian is joined by longtime collaborator and Agile thought leader Mike Cohn for a deep dive into what really makes Agile stick. They explore the five foundational pillars—mindset, practices, roles, teamwork, and support beyond the team—and share stories of what happens when teams get them wrong (like obsessing over story point math or demoing a copyright update in a sprint review). Along the way, they introduce the newly available Working on a Scrum Team public course and explain why it’s designed for entire teams, not just isolated roles. Whether you're new to Agile or knee-deep in transformation, this episode will help you rethink how to build an Agile approach that actually works. References and resources mentioned in the show: Mike Cohn #80: From Struggling to Success: Reviving Agile Teams with Mike Cohn Scrum Team Roles and Responsibilities Working on a Scrum Team Course Mountain Goat Software Certified Scrum and Agile Training Schedule Subscribe to the Agile Mentors Podcast Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Mike Cohn, CEO of Mountain Goat Software, is a passionate advocate for agile methodologies. Co-founder of Agile Alliance and Scrum Alliance, he thrives on helping companies succeed with Agile and witnessing its transformative impact on individuals' careers. Mike resides in Northern Idaho with his family, two Havanese dogs, and an impressive hot sauce collection. Auto-generated Transcript: Brian Milner (00:00) Welcome in, Agile Mentors. We're back for another episode of the Agile Mentors podcast. Thanks for joining us. I'm with you, as always, Brian Milner. And today, I have the one and only Mike Cohn back with us. Welcome in, Mike. Mike (00:12) Thanks, Brian. Good to be here. Brian Milner (00:14) Always happy to have Mike on the show and really appreciate Mike making time to come on. Wanted to have Mike on because there's some things Mike's been talking about recently that are really interesting and people have been asking a little bit about this and I thought maybe it'd be just a good opportunity to talk through some of the stuff that Mike's been writing about. I know you spent, Mike, a lot of time helping teams to not just do Agile but to really get solid results from it. to see impact from it. And I know the topic you've been talking about recently is sort of these five pillars of supporting real agile improvements, the mindset, practices, roles, teamwork, and support beyond the team. So I thought maybe we could just dig in and drive through those and maybe learn a little bit about those as we go. Obviously also to talk a little bit about the exciting new course that's being launched here, the working on a Scrum team course, because I know that was originally just for private classes, right? And now it's being open to the public. Mike (01:23) Yeah, we've done working on a Scrum team as a private class for probably 20 plus years. It's been kind of our main offering to private clients. But we're hearing from a lot of people that they have one team and they can't really get a private class approved with the budget and such. So what we're doing is going ahead and making that course available as a public course. So two people from your company, five people from another company all in the same class the way we've done our certified courses for decades. And so we're going to start offering this as a public course. And the exciting thing there is that it's really meant to be a team-based class, where things like Scrum Master training, great class, but it's really meant for the Scrum Master, right? And working on a Scrum team is really designed, and you and I helped you and I design this course together, but it's designed to be something that is a whole team training, right? So good for anybody on a team. Brian Milner (02:16) Yeah, yeah, it's been really great teaching those in the private classes and I'm excited to think about the public being able to come in and take that now. Let's talk a little bit about these pillars and, I think people are gonna be really intrigued by the concept here. The first one is mindset, I think, and just wanna start there and say, what does it actually mean to... think Agile and what is the found, why is that kind of the foundation for successful transformations? Mike (02:43) Remember the kind of the early days of agile and there was a lot of conversation about could you be agile without understanding the principles, right? If you just did the practices, were you agile? Other people were saying, no, you have to start with the principles, right? And so do you start with principles? Do you start with practices? And I remember these early debates and they often devolved into a discussion of the karate kid movie, right? Remember that one, right? And, you know, can you just wax on? Brian Milner (03:12) Ha Mike (03:12) for long enough, just do the practices. And then all of a sudden, your karate instructor or your agile coach is, OK, you're agile. And it's like, wait, all I know how to do is wax a car, right? And so there were these discussions about practices versus principles. And I was kind of always on the side where you better understand the principles to do this. Just knowing the practices, waxing on all day, is kind of just going through the motions. And so you have to understand the principles. And the idea that I wanted was that if a team truly understood all of the principles underneath Agile, I don't just mean just the manifesto, but all the principles that are there from Lean, from Kanban, from everything, that if you really understood those, you'd kind of invent the practices, right? You do those and you go eventually to go, hey, we should probably meet every day. Or hey, if we tested first, that might be a really good thing. Brian Milner (03:57) Yeah. Mike (04:05) So you'd invent the practices if you really had that type of agile mindset. And so for me, when we're working with organizations to get them truly agile, and I don't mean like more agile than less agile, but agile in a way that's going to stick, you got to change mindsets, right? You've got to do more than just the wax on. So people have to get the mindset. Brian Milner (04:27) Yeah, I love that. I know that I've experienced some things in the course of working with people that's it's sort of like you, if you're not on the same page with the principles, then you start to talk through the practices and you run up against a problem. And really what you find out the core of it was, well, we weren't aligned on really the principle behind this. So why would I want the practices then, right? ⁓ Mike (04:49) Yeah. Well, that's where you also end up then with a lot of team debates about things, right? Because you're arguing about the practice. if you'll say you and I are arguing about the benefit of some practice, if we agree on the principle, we might just have different views on it. But deep down, we'll probably agree on some practice, or we might find an alternative one. But if you don't agree on the principles, you end up with a lot more of these kind of annoying. mean, team debates are great. I mean, I love. Brian Milner (04:54) Yeah. Mike (05:12) you know, having a team debate, arguing stuff like that, but not about pointless things, right? And not without some sort of foundation. They just kind of get in the way. It's just frustrating for everybody. Brian Milner (05:21) Yeah. Well, I'm kind of curious, what kind of signs or signals do you think teams should look out for to kind of clue in and let them know that what might actually be going on here is more of a mindset issue? Mike (05:36) think sometimes it's when you hear the appeal to authority, right? Somebody says, you know, well, we got to do it this way because the scrum guide says, right? Or the one that annoys me is we have to do it this way because Mike Cohn says, ⁓ you know, that was like, no, I, somewhere else also said, think, right? Don't just, you know, don't just, you know, blindly do story points or something. Cause I say they're a good thing. I want you to think too. Brian Milner (05:50) You You Mike (06:01) And so I think that kind of appeal to authority when teams are debating things. It's where we also see teams who think they're agile because they do a set of practices. We use a particular agile tool, so we must be agile. We do daily meetings. We must be agile. And those are not the things that make you agile. Those are artifacts of being agile. If you're agile, you're going to meet a lot. You're not going meet a lot, but you're going to talk a lot. Um, and so those are the artifacts of behaving in an agile way. And so I want to understand why we're doing those things. So I look for those kind of appeals to authority. Um, you know, emphasis on that type of stuff in an argument talking about how this is the right way saying there's only one right way to do something. Brian Milner (06:49) Yeah, yeah, that's great. How does working on the Scrum team deal with this? How does that address it? Mike (06:55) Well, one of the things we do, it was actually one of my favorite exercises. We do this exercise at the start of the class where we ask people to kind of map out how the organization talks about certain adsel principles and then how does the organization behave. And so for example, if a company says, people are our greatest asset, and then they treat people like dirt, we've got this kind of problem between what we say and what we do. And so I like to kind of map this out. And so we do this with the principles in the Agile Manifesto. And once we map those out and we start to see things that we say we value, but we don't behave that way, really helps us understand if we've really embraced that mindset. Or are we just doing things because an Agile coach told us to, or a boss told us to, or we did it that way in our prior company. Those are all bad reasons to do something. Brian Milner (07:48) Y eah. So this is great. So I agree. The mindset's really foundational. And there is this symbiotic relationship between mindset and practices, which came first and which comes first, as we talked about. I know a lot of teams get stuck doing Agile, though, in really only name only. So when we talk about practices, what makes the difference between going through the motions? Mike (08:00) Mm-hmm. Brian Milner (08:11) and actually doing things that work. Mike (08:13) Well, practices is kind of our second pillar, right? You have to have the mindset, right? But you also have to have the practices that come from having that mindset. so, again, I try to think of that team on a desert island, right? And they're isolated from the world. They've never talked to anybody, but they have an agile mindset. What practices are they going to invent, right? And I think those are kind of the core practices. We see a lot of problems with as an example, teams that misunderstand sprint planning. And I know when I first started teaching about sprint planning, I'd have a slide up there to have a picture of a sprint backlog. And the sprint backlog listed tasks like code this, design this, test this. And then there were estimates next to code this. It's going to take four hours testing. It's going to take three. And so we were able see all these numbers and think the point of a sprint planning was these numbers. And Even in the early days of this, I was always saying, no, it's not about those numbers. It's about deciding what product backlog items you can pick. if taking a, I don't even want to call it an estimate, but taking a wild guess about, it probably can take four hours to code. If that helps you decide how many backlog items you can commit to, great, put those numbers up there. But it was never about the numbers. And it's one of the most common problems that I see with teams in sprint planning is they get obsessed with How many hours did we bring in? How many points did we bring in? And I remember one team I worked with where we did sprint planning. Having those estimates were helpful for them on their sprint back. They were helping. And we finished the meeting. And we're using Google Sheets in a meeting to do this. We've got a row with the estimates in there. And as we start to wind down the meeting, I deleted that column that they'd spent so much time talking about. They're all kind of pissed off at me. Why'd you delete that? We spent all this time talking about it. I said, because we got the benefit, right? You got the benefit of those numbers. The benefit isn't a week from now remembering that you said five hours, because it's going to take what it takes. The benefit was the discussion that it led to of can we take more or are we already full? So I see teams get obsessed with that. This is one example, but that's one of the problems with sprint planning as a practice. Brian Milner (10:25) Yeah. Yeah. I think you're absolutely right. And that's one of the things I know I've talked about with people going through the course is sort of understanding the purpose behind the things. Just going back to, know, harkening back to what you said about, don't just do it because someone told you, you know, understand why the purpose behind it. And, know, otherwise we, I'm sure we've all had that experience before where someone just tells you to do something and says, you know, why? Cause I told you so, you know, that, that doesn't, that's not very convincing. Mike (10:52) Thanks, Mom. Brian Milner (10:53) Right, right, thanks mom. Yeah, not very convincing, but it's much more convincing when they can tell you, well, no, you do this because this is what we're trying to do. And I think you're right, that makes all the difference there. ⁓ Mike (11:05) It just, don't know anybody that responds well to being told what to do, right? My instant reaction is no, right? mean, you it could be, you know, a really, you it could be a really good thing. Eat more vegetables, you spend more time outside. No, right? Don't tell me what to do. So. Brian Milner (11:09) Right. Right. Yeah. It's almost like our default response is no until you convince me. Are there other common practices? We talked about sprint planning. Are there other kind of practices you see teams struggle with? Mike (11:28) Yeah, yeah, for a lot of people. think a huge one is product backlog refinement. I don't know what a better word would be than refinement. refinement is about making the backlog better. It's not about making it perfect. And I see teams that get stuck on backlog refinement and feel like they have to resolve every open issue, that everything has to be tiny and answered and buttoned up before we can start a sprint. And that's not the case. For me, the goal in refinement is to make sure things are small enough and sufficiently well understood. I don't want to bring in a backlog that's bigger than my velocity. If our velocity is 25, I don't want bring in a 50-point story. how about the problems of a 50-point story anyway? But I don't want to bring in some massive epic like that into a sprint. And so refinement is about making it small, making sure it's sufficiently well understood. Sufficiently well understood, not perfectly. And so Brian Milner (12:18) Yeah. Mike (12:28) The problem is these teams, and I know you've seen this, but teams who get in there, want to resolve every open issue. It's like, no, we can resolve that during the sprint. If we think about the goal and planning to make sure we know what to bring into the sprint, not too much, not too little, we're fine just enough that you're at that point. Is the button blue or red? Who cares? If it's a log in story, we're going to lock people out after some number of failed attempts. Who cares how many? Figure that out during the sprint. If it's five or three or eight, who cares? Figure that out later. So I think refinements won. Another big one would be reviews, ⁓ where sometimes teams demo too much in a sprint review. And they feel like they have to justify their existence, show everything you did during the sprint. And the most egregious example of that was this was a handful of years ago. But I literally remember a team showing Brian Milner (12:58) Yeah. Yeah. Mike (13:18) how they had updated the copyright notice on the footer of the web page, know, copyright, you know, whatever year our company, right? And it's like, my God, you didn't need to show that to stakeholders, right? We all either know there's a copyright notice on the bottom of the web page or we've seen one before. I don't need you to bring it up and scroll down to it. Now only took 15 seconds of the meeting, but that was 15 seconds of people's lives. They were never going to get back. you know, show stuff that you need feedback on, right? If you'd... Brian Milner (13:41) Right. Mike (13:45) You fixed a bug and you fixed it only way it could be fixed. Mention it perhaps, but you don't need to show it, right? Brian Milner (13:51) Yeah, yeah, know teams I've been on often it's just it's suffice it to have a list sometimes and just say here's a list of things if you want to know more about these come talk to us but we're move on to the stuff you care about. Mike (14:02) Yeah, I always have like a will show, will not show list. you know, I often, if I'm writing the meetup present, that'll put that up on Zoom or, you know, show it on a screen if we're in person. And often somebody wants to see something that's on the will not show list. Or they just want me to describe what bug was that again? What was that? You know, and I'll explain it really quickly. But if nobody wants to see it, don't bother showing it. So. Brian Milner (14:26) Yeah, I know we talk about these scrum practices quite a bit in the working on the scrum team class, but if someone signed up to take this class, what can they expect to hear or what can they expect to learn about these practices in the course? Mike (14:39) Well, I think one of the things that you and I did together in creating the newest version of the course was to look at what do you actually need to practice doing, and it's feasible to practice doing in a classroom setting, versus what should you just kind of talk through. And not everything needs to be practiced to get the hang of it, right? Everybody in the world has taken something big and split it up into smaller things before, right? I need to make. spaghetti dinner tonight. What do need to buy? Right? OK. Well, that's that's that's test decomposition by noodles, by sauce, by tomatoes. Let's make it from scratch. Right. By some garlic. Right. So everybody in the world has done decomposition. We've broken a big thing into small things. And I remember, you know, iterating over I'm still on sprint planning, I guess. But I remember iterating over exercises in sprint planning and in courses over the decades by now. And I would have one where you're planning a party for your kid, break it down into tasks. It's like, nobody learns anything from this. And so that's one where I'd rather say, OK, this problem occurs in sprint planning. How could you solve it? Other things like, let's say, splitting user stories or splitting job stories, that's a skill worth practicing together, getting feedback on. And so those type of things we try to practice in the course. other things we just talk about. mean, I'm curious on your thoughts on that. What do you think about some things being worth practicing, some things worth being better talked about? Brian Milner (16:01) Yeah, I agree. I agree fully. it's, it's, you know, there's some things, it's kind of like what you said before, there's some things that's not worth spending the time on, and it's better to just have a discussion and move on. Mike (16:13) Yeah. Yeah. I guess that's one of the things we always talked about. We always talked about return on investment of the exercise. What's the return on the exercise? And if you're going to have a one hour exercise, cool. One hour exercise. But it better have a pretty healthy return because that's a lot of time in class. And so what's the return on exercise? Is this worth a practice? Is it worth just a discussion? And if we can discuss two hard problems and give people advice on two common problems, they're probably going to face. Brian Milner (16:21) Yeah. Mike (16:41) Might be better than spending 20 minutes practicing something that they've probably done before. Brian Milner (16:45) Yeah, I completely agree. Let's move to the third pillar then, because I know this is a big one, just thinking and talking about the roles. And just as far as communication issues are concerned, even outside of Scrum, I know that's part of the big problem with teams and organizations just not being clearly defined about who does what and who's responsible for each thing. So those misunderstandings are really common failure points. ⁓ Mike (17:09) Mm-hmm. Brian Milner (17:10) How do you see teams getting that wrong and how's that derailing a Scrum team? Mike (17:15) Well, think we see it all the time on Scrum teams between Scrum Master and Product Owner and even the development team, right? Who does what? I was responding to some comments on LinkedIn this morning on some post I'd made last week and somebody had some comments. And it had to do with whether the Scrum Master or Product Owner does something. And it was interesting because in the comments on that post, I... I don't remember which one it was, but I shared a certain perspective. I feel pretty strongly that I have it right. I mean, I this is how we do it. But there were other people saying the opposite, right? And so, you know, these are people that are probably fairly experienced with Scrum, if they're following me on LinkedIn and feel comfortable commenting on a post, probably feel comfortable with it. And so there's a lot of confusion about what role does what thing. And I don't think this is something where the Scrum guy is going to have the answers for you. I think it's, I mean, you can look at the Scrum guy, oh, this. Here's my starting point answer, but we always want to play to people's strengths, right? And if you've got a scrum master who's got a lot of skill in one area, maybe they shift a little work from the PO to themselves, right? With the PO's permission, right? And the opposite, right? Between maybe PO and team. So it's fine to have default starting positions on who does what, but you always want to play to people's strengths. So I think PO scrum master, I think we see it with project managers and scrum masters, roll confusion on those type of roles as well. Brian Milner (18:38) Yeah, completely agree. A lot of those roles that are not named Scrum team roles and how they interact with the team, that's often a source of confusion as well. What are maybe some signs or symptoms that teams might be having confusion or problems in this area that maybe they don't even recognize or realize they're having an issue with roles? Mike (18:59) Any sort of conflicts, right? You know, you and I arguing over which one of us should do something. The other one would be kind of the opposite, which would be like a dropped ball. I was watching some YouTube video. I love baseball. I was watching some YouTube video the other day of like missed catches or something like that. And some team hit a baseball way up in the air and it was landing near three players, right? Three players are all looking at it. Brian Milner (19:12) You Mike (19:23) One guy waves the other two off, he's going to catch the ball and he must have been blinded by the sun because he's like six feet from the ball when it lands on the ground, right? And, you know, if we have a responsibility to catch the ball, run this meeting, right, right the backlog, the kids dropped, right? And so I think either arguing over who does something, two of us trying to do the same thing or neither of us doing it. I don't mean trying to get out of the work, right? All three players have been happy to catch the ball, but I think you've got it. You think I've got it, right? Those type of things are pretty good signs. think getting clarity around these roles can really optimize how a team works. And I think a really key thing here is that it changes over time. So I'll go back to my example of maybe the Scrubmaster has some skills that can help the product owner early on. Because maybe the product owner is new to the company. The product owner doesn't know the product as well. So they might rely on the Scrubmaster for guidance on things. Well, a year from now, we might shift responsibilities a little bit because now the PO is the expert on all things related to the product. So it's not like we want to establish clarity on roles one time and leave it forever. It's going to change. We get a new tester on the team, things might change. Product owner moves. It's going to change again. So we need to realize these responsibilities are dynamic. Brian Milner (20:39) Yeah, that's a great point. Your point about baseball just made me think about how, when you watch any youth sport in the world, when you go watch your kids play a sport, what's the one thing you always hear people scream from the sideline? Talk to each other. Call the ball. Well, that too. That too. Ump your blind. Those kinds of things. Well, let's talk a little bit about Mike (20:52) I thought you were going say, put my kid in. Brian Milner (21:00) I know this course addresses the roles and how would you say this course really helps address that issue of role confusion? Mike (21:07) think a big part of it is that we designed it to be for everybody on the team, right? Suppose you send a scrum master to a class, and it's a great class. Scrum master is going to back to the certain set of impressions about their role. Product owner goes to an equally good class about the product. They might have different impressions. Even if they took the course from the same instructor, they're hearing it a little differently. They're hearing it through their filters, right? And so when they're in a course together, there's more opportunities to clarify their understanding about those things, especially in the classes designed as we did with this one to bring out some of those differences. So I think the course helps with that. we've also designed it to mention the rules we haven't talked about, like managers and things like that. Brian Milner (21:53) Yeah, yeah, I think those are so important. And there's a lot of great discussions that come out when we have those topics. ⁓ Let's talk about the fourth pillar then, teamwork, because this, I think, builds really well on what we just talked about. And the idea that there's actually, Scrum is a team sport. ⁓ So beyond just normal human personality conflict type issues, what do you see that gets in the way of teams actually Mike (21:58) Mm-hmm. Mm-hmm. Brian Milner (22:18) working as a team. Mike (22:19) think ego is probably one, right? I can do everything better, just leave me alone. There's an old book that says basically, beware of a lone developer in a room, right? You know, it was referring to the developer who wants to close their door and say, I'll it done in a month, trust me, right? And one of the companies I worked with, and this one's going back like 15 years ago, but it was a really good story. Brian Milner (22:36) Yeah. Mike (22:43) is they would literally grab one unit of work. Each person on the team would grab a unit of work and take anywhere from three to 12 months to do the thing. So they were big things, but the person would do everything on it. They'd coded, tested everything. And the organization was putting out very little because of this. When they moved to Scrum in the first year, by their estimate, they said they delivered 540 % more work. over five times the amount of new features delivered. And that was through the collaboration, through the short iterations, those type of things. But it was about getting people to collaborate more. So I think there's huge opportunities to do that. One of the problems I see is when we don't overlap work. If we think about that organization I just described, you grab your thing, you're done in six months. I grab mine, I'm done in seven months. If we'd work together on those things, what's not make us any faster? No faster. But you and I could have worked on your one thing and been done in three months. OK, we're delivering value in three months, right? And so one of the things I look for a lot is how much teams are overlapping work, right? And if we're not overlapping work, there's huge opportunities to improve at that. I'll a little example of this. One of my favorite restaurants is, I don't know, barely call it a restaurant. It's a fast food deli. It's called Jimmy John's. Have you been to Jimmy John's, Yeah. Yeah, there's one near my house where I can go there and the wine will be out the door. Right. And you know, normally you see a wine out the door and it's like, crap, I'm going somewhere else. Right. These guys are so fast. They're so fast. When I get to the front, I place my order. I play this little game of can I fill up my cup? You know, I get an iced tea and they give me an empty cup and can I go fill up ice and put the tea in before they hand me my sandwich? And it's about 50-50. Right. It doesn't take long to fill up your iced tea. But the way they do that is the overlap work. As soon as I order my Italian club sandwich, somebody's already got the bread open, somebody's got a slab of meat they're ready to drop on there, somebody else has their hands over the vegetables and they're dropping the vegetables on there, and then a fourth person wraps it up. And so like four or five people touch my sandwich. Hopefully their hands are clean, but four or five people touch my sandwich as opposed to like most delis where I go and it's like you watch one person plod along making the sandwich, right? Overlap work is huge. Brian Milner (25:07) Yeah. Yeah, this episode sponsored by, no, just kidding. Use code Mike Cohn when you go to, no, just kidding. Yeah, I agree. And yeah, yeah, I'm familiar with Jimmy John's. Probably too familiar. ⁓ Yes, yeah, no, that's, I think that's part of their shtick is that they're, you know, they're known for being fast. So yeah. Mike (25:10) You Is yours just as fast? Yeah. Yeah. They call it Freaky Fast. They actually have a competition. I've seen YouTube videos of this where they get like the best teams at various restaurants race, right? And so they have like the Jimmy John sandwich making Olympics or something, but it's a skill. Brian Milner (25:36) wow, wow, yeah. You should pair that up with the hot dog eating challenge in some way and see if we could have a team sport going there. ⁓ Mike (25:48) Well, that's a good point because think about the hot dog eating. That's one guy, right? That's Joey Chesnett shoving hot dogs down. The Jimmy Johns is a team. They get the best crew at a restaurant and it's a team, right? How fast can the team go? Not how fast can one guy make a sandwich, right? Brian Milner (25:51) Yeah. Yeah, yeah. That's awesome. So what are some tips? What are some ways that you can really unite a team, especially those new teams? Because that's the fascination point for me is, how do you take this group of humans that really don't know each other and haven't worked together in the past and unite them together and have them gel as a team? How do you do that? Mike (26:21) I'll give you a couple. One, I think having really crisp sprint goals helps. So we all know exactly what we're trying to get done in the sprint. We don't lose sight of that because sometimes in the middle of a sprint, you lose sight of it. And you get myopic and you just focus on a list of tasks. And I'm going to say that it's probably similar to the team doing sprint planning and just getting them assessed with the numbers. It's not about the numbers. It's not about the tasks. It's about the backlog items that lead to some goal. So crisp sprint goals help. That's a hard phrase. Crisp Sprinkles helps. The other one I'd say is having a shared vision about where you're headed over a little bit longer term. Probably the biggest change to the Scrum Guide ever that I've liked is the inclusion of a product goal. And that was something I'd been talking about forever. mean, literally since I started doing Scrum was that sprinkles are great, but they're pretty short, right? You want to have something bigger. Brian Milner (26:52) It is. Mike (27:14) And so I like having product goals that are a few months out there. And one of the things I like doing for product goals is have teams do something like write a press release that describes their goal or create a vision in some way, write a review that you want to see come out on the App Store, Play Store, and a magazine. And one of my clients made software and they were reviewed by a major magazine and they were given an editor's choice runner up award. And they actually estimated that being runners up for that was probably worth about $10 million. First place, first time was worth about $10 million a year to them. And so they decided to get serious about this and they wrote a review. Their scrum master, she was actually combo scrum master product owner, Erin. She had the team write a review and she said, let's go earn this review. And I literally remember the email I got from her three months later. It was because it was Halloween night. I just like, you know, brought in the candy from outdoors. We're done trick or treating. And I checked my email. I a three word email from her from Erin. said we did it. And the magazine had let her know, hey, we're reviewing you. be out on, you know, like Tuesday's edition. And the review had quotes in there that were from their vision review, right? The things that they had wanted to achieve. Brian Milner (28:22) Ha ha. Mike (28:35) And that team had just really jelled around that and just became so much more productive and collaborated so much better because of that shared vision. Brian Milner (28:43) Yeah, that's amazing. getting back to the course then, I know in the course we're trying to kind of some of those collaboration muscles. What are some of the ways that the course helps to build that? Mike (28:56) think one of the key things that we're doing, and I'm excited about this, is that we're, you know, we of course use Zoom breakout rooms, right? You you go talk about this, we'll see you in eight minutes or something like that. And for this course, we're doing something where a group of three or more, when they register, can have a private breakout room. And this to me is exciting because people get the benefit of having a private breakout room. They can have sensitive discussions if they want. They can talk very specifically about. you know, what do we do about our jerk product owner? mean, whatever it is, right? You know, they can talk about their specific issues, yet have the context of a broader class. Because I think in one of the benefits of any public class is hearing how other teams are doing things. And sometimes that's because you get a good advice, you know, how did you solve that problem? We have that problem. Other times, it's just feeling that you're not alone in the world. they've got that problem too, right? And they don't have any solution for me, but I know I'm not alone in the world with this. And so I like these private breakout rooms for three or more. I think it's a novel thing we're doing with this class. And it's with the intent of combining the best of both worlds of private and public training for this. I'd the other thing is probably consistency, having everybody on the team hear the same message, having those discussions with an experienced instructor like you or me in the room to provide guidance when they have questions. know, go back to the role clarity, right? You know, they can talk about it and they're there. Then they're back in the main room with you or me and we can kind of answer questions. So I think that consistency will be huge as well. Brian Milner (30:25) Yeah, yeah, I love that idea of the private private breakout rooms that that's that's gonna be huge for a lot of people I know. ⁓ Mike (30:31) I'm excited to try it with this. This will be the first classes we do that for. I'm excited about it. Brian Milner (30:36) Yeah, yeah. Well, let's bring it home then and talk about the fifth pillar because the fifth pillar is really interesting as well. It talks about support beyond the team and teams can only do so much. Every team struggles when they're not supported well. And there's lots of studies that show leadership support is one of the biggest hurdles or obstacles to the adoption. Mike (30:46) Mm-hmm. Brian Milner (30:59) What does that support look like from outside the team and how can a team influence that? Mike (31:06) Yeah, if you're trying to be agile and your HR group has quarterly reviews of personnel that are all based on individual performance and has nothing to do about teamwork in there, it's going to be hard to focus on collaboration. So we have to kind of fix these issues. I think what we have to do here is to have team members educate those outside the organization. And we have information that we share about, you here's how to talk to a boss that's maybe mandating deadlines, things like that. And so we try to coach people through having some of those challenging conversations. And one of things I want teams to do is kind of become an example of what good agile looks like. And if you have a team that's excelling with agile and they're doing it from a kind of principles first, that mindset first approach. You're going to see other groups look at that and let's say the marketing group. They're going to look at that go, hey, that's an interesting way to work. I wonder how we could do that, right? And it's going look different for a marketing group than a tech team. the mindset is going to be the same. Principles will still be the same. And so when we get teams to do really well with this, other parts of the organization start to get interested. And then they stop being as much in our way. Brian Milner (32:20) Yeah. I know one of the most important aspects here and that we talk about is, is that you don't need to, to wait, right? If you're the team level, you don't have to just sit around and wait for the organization to make changes. you, you have opportunities to make changes as well. So how does that happen? How's the team change, you know, bring about those changes that, improve the agile process, the results. Mike (32:42) I think that's by being the example so that people see it. I think it's by having those conversations. You know, one of the things that we'll get is, you know, it's so common is the product owner that wants to change their mind all the time. I was reading something, I guess this is in our Agile mentors community, I think is where it was, but it was about the, you know, the product owner who said his favorite thing about Agile is that he can reprioritize every week. ⁓ And it's like, you can, you know. Brian Milner (33:05) Hmm. Yeah Mike (33:10) I'm not sure it's good. And I think about that, a team gets momentum, right? And you're working on a certain feature. Next sprint, it would be nice to work in that same area of this system, right? Your head's there. Just kind of keep going a little bit. And I've often described this as like, let's say you're working on three backlog items that are in a certain area of this system. Let's make it concrete. Let's say it's the spell checker in Microsoft Office, right? And you do three backlog items related to the spell checker this sprint. Next sprint, maybe your top priority is not more spell checker stuff, but maybe items, I don't know, 25, 26, and 27 on the backlog are still in the spell checker. You know what? It might be better to do those. There are probably two or three sprints away. Let's bring them into this sprint. Just get them done while my head's into spell checking. And so getting product owners or stakeholders to stop doing that, one of the ways that I like to talk about doing that is using an example of ordering a meal at a restaurant. I can order, let's say, the chicken entree. And then as the waiter is taking the orders around the table, I change from chicken, no, bring me the fish. Not a big deal. The waiter is going to cross off chicken and write down fish. If the waiter goes away, brings me back my salad, and I change my mind then, I say, hey, bring me the fish. Might not be a big deal. It's going to be a big deal if I've already taken three bites of the chicken. right? Or if he brings me the chicken. So yeah, we can change our mind, but there's a cost, right? And we want to educate stakeholders about that cost. They don't overdo it. Brian Milner (34:31) Yeah. Yeah. Well, speaking of the leaders and the organization, managers, leaders, do you think this course is appropriate for managers and leaders to attend as well? you feel like they might need to in order to really have this be an impact? Mike (34:55) Yeah, that's a good question. Is it appropriate? Yeah, I think it's appropriate. When we do this privately, we've had plenty of leaders and managers attend. I think it's great. I don't think that's required because they're not on the Scrum team. You said the name of the course is working on a Scrum team. And so they're not on the Scrum team. They benefit by knowing more how their Scrum team works. But I think what we found is that having just a key subset of people who hear the same message work through the training together, and then go back to the organization. That's enough to bring the passion, conviction, and skills that we want. So we don't truly need leaders. They're great. I would never talk a leader out of going, but I wouldn't. If I were a team and I could take the class this month or with my leader next month, I would just get the class done, right? And educate the leader afterwards. Brian Milner (35:41) Yeah. Yeah, yeah, I think that's a good plan. All right, well then we've made our way through the five pillars and for people who have come this far with us and are at this point, if they're listening and they're recognizing some of these problems we've been talking about, what would you recommend to them as next steps here? Mike (35:49) if Well, take a look at our website. If you go to mountaingoatsoftware.com. And then I think there's a courses link on the top. You can go up there and find the link to this course. It's an exciting one that we're doing. I've literally been teaching this, I think the first time I taught a class called Working on a Scrum Team was 2003 or 2004. it's a time tested course. You and I kind of redesigned it a couple of months ago to make it appropriate for public. or little better just in general and more appropriate for public. But it's a time-tested course that's now designed to be available for public settings instead of, you know, have to have 25 people or something. Brian Milner (36:36) Yeah, yeah, that's really exciting. I can't wait to see kind of how people are in, you know, react and interact in the course to some of these concepts and ideas. And we'll, we'll of course link to all these things that we've talked about in our show notes and make it easy for everyone to find the course listing and, and, you know, where the dates and everything that we're going to offer them. So make sure to check that out. Mike, thanks so much for coming on. This has been really enlightening and I appreciate you making time for it. Mike (37:01) Of course, thanks for having me, Brian. Always a pleasure.

Co-hosts Mark Thompson and Steve Little explore OpenAI's groundbreaking ChatGPT Agent, demonstrating how this autonomous tool can research, analyze, and perform complex tasks on your behalf.Next, they address important security concerns to consider in the new world of AI agents, introducing practical guidelines for protecting sensitive family data and avoiding prompt injection attacks.This week's Tip of the Week provides a back-to-basics guide on what AI is and its four core strengths: summarization, extraction, generation, and translation.In RapidFire, they discuss OpenAI's rumored office suite, Microsoft and Google's own efforts to integrate AI into their office suites, and recently announced AI infrastructure investments, including; Meta's Manhattan-sized data center and President Trump's new AI Action Plan.The hosts also announce their new Family History AI Show Academy, a five-week course beginning in October of 2025. See https://tixoom.app/fhaishow/ for more details.Timestamps:In the News:05:20 ChatGPT Agent: Autonomous Research Assistant for Genealogists22:49 Safe and Secure in the Age of AITip of the Week:36:20 What is AI and What is it Good For? Back to BasicsRapidFire:50:57 OpenAI's Office Suite Rumors53:56 Microsoft and Google Bring AI to Their Office Suites60:17 Big AI Infrastructure: Manhattan-Sized Data CentersResource Links:Introduction to Family History AIhttps://tixoom.app/fhaishow/Do agents work in the browser?https://www.bensbites.com/p/do-agents-work-in-the-browserIntroducing ChatGPT agent: bridging research and actionhttps://openai.com/index/introducing-chatgpt-agent/OpenAI's new ChatGPT Agent can control an entire computer and do tasks for youhttps://www.theverge.com/ai-artificial-intelligence/709158/openai-new-release-chatgpt-agent-operator-deep-researchOpenAI's New ChatGPT Agent Tries to Do It Allhttps://www.wired.com/story/openai-chatgpt-agent-launch/Agent demo posthttps://x.com/rowancheung/status/1945896543263080736OpenAI Quietly Designed a Rival to Google Workspace, Microsoft Officehttps://www.theinformation.com/articles/openai-quietly-designed-rival-google-workspace-microsoft-officeOpenAI Is Quietly Creating Tools to Take on Microsoft Office and Google Workspacehttps://www.theglobeandmail.com/investing/markets/stocks/MSFT/pressreleases/33074368/openai-is-quietly-creating-tools-to-take-on-microsoft-office-and-google-workspace-googl/What's new in Microsoft 365 Copilot?https://techcommunity.microsoft.com/blog/microsoft365copilotblog/what%E2%80%99s-new-in-microsoft-365-copilot--june-2025/4427592Google Workspace enables the future of AI-powered work for every businesshttps://workspace.google.com/blog/product-announcements/empowering-businesses-with-AIGoogle Workspace Review: Will it Serve My Needs?https://www.emailtooltester.com/en/blog/google-workspace-review/Tags:Artificial Intelligence, Genealogy, Family History, AI Agents, ChatGPT Agent, OpenAI, Computer Use, AI Security, Prompt Injection, Database Analysis, RootsMagic, Cemetery Records, AI Office Suite, Microsoft 365 Copilot, Google Workspace, Data Centers, AI Infrastructure, Natural Language Processing, Large Language Models, Context Windows, AI Education, Family History AI Show Academy, AI Reasoning Models, Autonomous Research, AI Ethics

What do cloud backups, two-factor authentication, and “turn it off and back on again” have in common? They're all part of the world Jose Velazquez navigates every day as co-owner of Carriage Trade Solutions, a Bridgeport-based managed services provider helping small and medium-sized businesses master the technology they need to thrive.This week on MissionCTRL, Ramon and Jorge sit down with Jose to hear how he built a business around making IT simple, affordable, and accessible. From his early days in infantry and marksmanship instruction for the Marine Corps, to working his way through project management and IT support roles, Jose shares how his passion for technology - and a lot of hustle - paved the way for Carriage Trade Solutions, which he co-founded in 2018 with an equally driven business partner.Jose opens up about why great IT isn't just about fixing broken computers - it's about education, empowerment, and bridging the massive “knowledge gap” many business owners face when it comes to tools like Microsoft Office and cloud services. He explains why cloud backups are non-negotiable, when it's time to retire old hardware, and how Carriage Trade Solutions provides enterprise-level support - email management, hardware lifecycles, vendor relationships - at a price point small businesses can actually afford.From music promotion roots to chamber of commerce networking, and from partnership challenges to delivering top-tier customer service (“we're not here to fix issues - we're here to help you succeed”), this conversation is packed with lessons for any entrepreneur looking to build a business that truly serves its clients.If you've ever wondered what IT really means for your business - or how to turn a passion for tech into a mission-driven company - this episode is for you.•••Find full episodes of Mission CTRL on Anchor, Apple Podcast, Spotify, and our website.Mission CTRL aims to ignite the innovative spirit inside us all through providing budding and successful entrepreneurs and community leaders with a platform to share their stories and inspire others. Tune in every Wednesday and catch up with the team at Peralta Design as we unleash the origin stories behind some exceptional leaders, share marketing/branding insights, and navigate the ever-changing currents of pop culture.Subscribe for more weekly branding and entrepreneurial content here! To learn more about Peralta Design's work visit peraltadesign.com.#welaunchbrands #launchyourbrand #BrandU #missionctrl #mctrl #digitalagency #mbeagency #mbe #digital #branding #marketing #web #creative #contentcreator #contentstrategy #marketingstrategy #leadership #leader #entrepreneur #entrepreneurs #entrepreneurship #entrepreneurial #startup #startups #business #businessowner #businesstips #scalingyourbusiness #smallbusiness #w2 #fulltime #9to5 #office #officelife #corporate #podcast #podcasts #podcastshow #businesspodcast #lifestory #lifestories #personalstory #personalstories

ChatGPT Agent is here!↳ What the heck is it? ↳ How does it work? ↳ What do you need to know? Glad you asked, shorties. Join us for the answers. Square keeps up so you don't have to slow down. Get everything you need to run and grow your business—without any long-term commitments. And why wait? Right now, you can get up to $200 off Square hardware at square.com/go/jordan. Run your business smarter with Square. Get started today.Newsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageJoin the discussion: Thoughts on this? Join the convo and connect with other AI leaders on LinkedIn.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:ChatGPT Agent Mode Overview & NamingLive ChatGPT Agent Demo WalkthroughChatGPT Agent Mode Availability & PricingOperator vs. Deep Research Capabilities ExplainedChatGPT Agent Virtual Computer FunctionsSpreadsheet and PowerPoint Generation in ChatGPTMini RAG-Ready Agents with Data ConnectorsChatGPT Agent Security and Biological Risk ClassificationTimestamps:00:00 "Introducing ChatGPT Agent"03:41 Potential Delay for Paid Plan Rollout09:24 "Chat GPT Agent: New Tools Overview"12:44 OpenAI-Microsoft Tensions Over Software Overlap16:42 "ChatGPT's New RAG Feature Unveiled"21:55 AI Agent with Weapon Risk23:31 Agent Models: Boon or Bane?29:05 "Agent Mode: Seamless Editing Integration"Keywords:ChatGPT Agent, Agent Mode, OpenAI, virtual computer, Agentic skills, Operator, Deep Research, browsing websites, web research, synthesizing information, Microsoft competitor, PowerPoint creation, Excel spreadsheet creation, terminal access, public API integration, connectors, data analysis, image generation, multi-agent environments, retrieval augmented generation, mini RAG, AI operating system, human-in-the-loop, security concerns, biology classifier, biological weapons classification, chemical weapons classification, O3 model, Google Gemini 2.5 Pro, agentic models, AI workflows, editable slide deck, Microsoft Office alternative, AI-powered presentations, spreadsheet automation, cloud-based agents, AI task automation, calendar integration, Gmail connector, Google Drive connector, Outlook connector, team collaboration, premium AI features, desktop to browser transition, file creation, terminal commands, workflow automationSend Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info) Ready for ROI on GenAI? Go to youreverydayai.com/partner

We're hours away from OpenAI's livestream announcement of what's reportedly called Agent Mode. There's been a few lines of reporting of what's coming!We tackle the rumors, what they mean, and how to be prepared for what this means for our day-to-day work lives. Square keeps up so you don't have to slow down. Get everything you need to run and grow your business—without any long-term commitments. And why wait? Right now, you can get up to $200 off Square hardware at square.com/go/jordan. Run your business smarter with Square. Get started today.Newsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageJoin the discussion:Thoughts on this? Join the convo and connect with other AI leaders on LinkedIn.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:ChatGPT Agent Mode Release RumorsChatGPT vs Microsoft Office CompetitionPotential Excel and PowerPoint IntegrationDeep Research and Agent Mode FeaturesOpenAI Operator and Browser UpdatesImpact on Microsoft Office Business ModelWorkflow Automation and App ConnectorsProductivity Tool Advancements for Knowledge WorkersTimestamps:00:00 "OpenAI's New Agent Announcement"04:56 OpenAI's New Features Reveal Tomorrow07:35 Microsoft-OpenAI Integration: Enhanced ChatGPT Features10:28 "ChatGPT-Powered Document Creation"13:42 "AI Tools for Visual Presentations"17:18 OpenAI's Enhanced Operator Unveiled19:55 "Anticipating Software Agent Reveal"25:28 AI Evolution: New Industry NormsKeywords:ChatGPT agent, OpenAI, agent mode, Microsoft Office competitor, Excel automation, PowerPoint automation, generative AI tools, spreadsheet AI, presentation AI, Operator, OpenAI browser, Canvas mode, Advanced Data Analysis, Microsoft Copilot, document management AI, workflow automation, browser automation, deep research, computer using agent, data analysis AI, GPT-4o image generation, Google Drive integration, report generation, database analysis, visual creation AI, productivity tool, chat-based document editing, slide generation, formula automation, business productivity AI, AI-powered presentations, AI-powered spreadsheets, AI advancements, IP sharing, OpenAI-Microsoft relationship, slide transitions AI, corporate data analysis, public data synthesis, Mac user productivity, PowerPoint, Excel, real-time updates AI, web sources integration.Send Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info) Ready for ROI on GenAI? Go to youreverydayai.com/partner

OpenAI is working on agent tools that build spreadsheets and presentations, and The Information's Stephanie Palazzolo and TITV Host Akash Pasricha break down her reporting. Plus, we talk with our IPO reporter Cory Weinberg about his exclusive story on blockchain lending company Figure's IPO and the IPO market broadly. And TITV sits down with 500 Global CEO and founding partner Christine Tsai to talk about her latest exit and which country outside the U.S. she is investing more in.

"Linux is getting boring" — or is it evolving into exactly what we wanted? In this episode, we chat retro consoles, 3D printing beasts, Titan phones, curriculum with Pybricks, and a Linux experience so stable it's suspicious. Plus: Wayland wins, Microsoft Office woes, and Wendy's robotics laptops ready for battle. Engage! Find the rest of the show notes at https://tuxdigital.com/podcasts/linux-out-loud/lol-113/ Connect with the Hosts:

Bu bölümde Masters of Doom ve Keyif Verici Maddelerin Tarihi kitapları, Apple'ın Liquid Glass değişikliklerine gelen eleştiriler ve abonelik sistemlerinin ne seviyeye gelebileceği üzerine konuştuk.Bizi dinlemekten keyif alıyorsanız, kahve ısmarlayarak bizi destekleyebilir ve Telegram grubumuza katılabilirsiniz. :)Yorumlarınızı, sorularınızı ya da sponsorluk tekliflerinizi info@farklidusun.net e-posta adresine iletebilirsiniz.Zaman damgaları:00:00 - Giriş03:30 - Liquid Glass29:20 - Abonelikler51:06 - Okuduklarımız, Masters of Doom, Keyif Verici Maddelerin Tarihi1:18:40 - Oynadıklarımız1:40:22 - Haftanın albümleriBölüm linkleri:MonoforRose-Gold-Tinted Liquid GlassesIn case of emergency, break glassMore assorted notes on Liquid GlassMore stray observations — on Liquid Glass, on Apple's lack of direction, then zooming out, on technological progressWhy I don't ride the AI Hype TrainThe Offline ClubFigma files for IPO on NYSE, plans to ‘take big swings' with acquisitionsDatadog's $65M/year customer mystery solvedWhy Denmark is dumping Microsoft Office and Windows for LibreOffice and LinuxCriminal Court: Microsoft's email block a wake-up call for digital sovereigntyNever Forget What They've DoneMasters of Doom: How Two Guys Created an Empire and Transformed Pop CultureThe World Atlas of CoffeeHow Not to InvestTastes of ParadiseBlack Mirror - Common PeopleHouseGoGo Penguin: Necessary FictionsGhost - SKELETAto a THollow KnightDOOM: The Dark AgesCabel Sasser, Panic - XOXO Festival (2024)

Wir leben längst in US-Software- und unter US-Überwachung: In jedem Rathaus, in jeder Kommune läuft Microsoft Office. Unsere E-Mails gehen über Outlook, unsere Akten entstehen in Word oder Excel und all das geschieht auf amerikanischer Software. Doch was viele übersehen: Jedes dieser Programme ist Teil eines weitverzweigten Überwachungsapparats. Daten, die in Europa entstehen, landen überWeiterlesen

Each year, we are so excited to recognize one of our customers as our CERTIFIED Educator of the Year during our annual CERTIFIED Educator Conference. We work with so many incredible educators, all of whom deserve recognition for their dedication and efforts. We're pleased to announce that Kim Kayser is our 2025 CERTIFIED Educator of the Year!  Kim has been teaching as well as learning technology with her students for fourteen years in Santa Rosa County, Florida. For the last ten of those years, she's been a career and technical educator, helping Woodlawn Beach Middle School students earn valuable, resume-building certifications in Microsoft Office, Entrepreneurship and Small Business, and Professional Communication. She loves being at the forefront of technology and always aims to keep classroom instruction engaging and relevant to prepare students for career and college readiness. In this episode, we talk with Kim about becoming the 2025 Educator of the Year, her pathway into teaching, and her approach to creating lasting relationships with her students. Inspiring and energizing, this is one episode you won't want to miss.  Learn more about Kim on our blog here.  You can also watch Kim in action (and hear from her students) in our CERTIFIED Educator of the Year video here.  Connect with educators like Kim in our CERTIFIED Educator Community here.  Don't miss your chance to register for our annual CERTIFIED Educator's Conference here.   

Henrico officials begin work on another stream restoration project; Weinstein JCC hires new CEO; a Henrico college student wins an award in a national Microsoft Office competition; Atlantic Union Bank expanding in Henrico.Support the show

Reed Albergotti is the technology editor at Semafor. He's back for our weekly discussion of the latest tech news. We cover 1) Cloudflare CEO Matthew Prince says AI is disappearing the web 2) Will there be new business models that replace the current web-based models? 3) Is the AI Agent thing really happening? 4) Vibecoding riches 5) Court rules Anthropic can train on books (but not steal them) 6) Anthropic will study AI's economic impact 7) Is chatbot companionship good for us? Anthropic says yes 8) OpenAI works on office productivity tools 9) Why OpenAi and Microsoft have tension 10) Will Stargate work? 11) Mira Murati's Think Machines plan 12) Tesla Robotaxi Rollout 13) Jeff Bezos gets married, who's coming?? --- Enjoying Big Technology Podcast? Please rate us five stars ⭐⭐⭐⭐⭐ in your podcast app of choice. Want a discount for Big Technology on Substack? Here's 25% off for the first year: https://www.bigtechnology.com/subscribe?coupon=0843016b Questions? Feedback? Write to: bigtechnologypodcast@gmail.com

OpenAI, Google & Anthropic are all eating different parts of the business & creative worlds but where does that leave us? For only 25 cents, you too can sponsor a human in a world of AGI. In the big news this week, OpenAI's takes on Microsoft Office, Google's cutting the cost of AI coding with their new Google CLI (Command Line Interface) and dropped an on-device robotics platform. Oh, and Anthropic just won a massive lawsuit around AI training and fair use. Plus, Tesla's rocky rollout of their Robotaxis, Eleven Labs' new MCP-centric 11ai voice agent, Runway's Game Worlds, the best hacker in the world in now an AI bot AND Gavin defends AI slop. US HUMANS AIN'T GOING AWAY. UNLESS THE AI GIVES US ENDLESS TREATS.  #ai #ainews #openai Join the discord: https://discord.gg/muD2TYgC8f Join our Patreon: https://www.patreon.com/AIForHumansShow AI For Humans Newsletter: https://aiforhumans.beehiiv.com/ Follow us for more on X @AIForHumansShow Join our TikTok @aiforhumansshow To book us for speaking, please visit our website: https://www.aiforhumans.show/ // Show Links //   OpenAI Developing Microsoft Office / Google Workplace Competitor https://www.theinformation.com/articles/openai-quietly-designed-rival-google-workspace-microsoft-office?rc=c3oojq OpenAI io / trademark drama:  https://www.theguardian.com/technology/2025/jun/23/openai-jony-ive-io-amid-trademark-iyo Sam's receipts from Jason Rugolo (founder of iYo the headphone company) https://x.com/sama/status/1937606794362388674 Google's OpenSource Comand Line Interface for Gemini is Free? https://blog.google/technology/developers/introducing-gemini-cli-open-source-ai-agent/ 1000 free Gemini Pro 2.5 requests per day https://x.com/OfficialLoganK/status/1937881962070364271 Anthropic's Big AI Legal Win  https://www.reuters.com/legal/litigation/anthropic-wins-key-ruling-ai-authors-copyright-lawsuit-2025-06-24/ More detail: https://x.com/AndrewCurran_/status/1937512454835306974 Gemini's On Device Robotics https://deepmind.google/discover/blog/gemini-robotics-on-device-brings-ai-to-local-robotic-devices/ AlphaGenome: an AI model to help scientists better understand our DNA https://x.com/GoogleDeepMind/status/1937873589170237738 Tesla Robotaxi Roll-out https://www.cnbc.com/2025/06/23/tesla-robotaxi-incidents-caught-on-camera-in-austin-get-nhtsa-concern.html Kinda Scary Looking: https://x.com/binarybits/status/1936951664721719383 Random slamming of brakes: https://x.com/JustonBrazda/status/1937518919062856107 Mira Murati's Thinking Machines Raises $2B Seed Round https://thinkingmachines.ai/ https://www.theinformation.com/articles/ex-openai-cto-muratis-startup-plans-compete-openai-others?rc=c3oojq&shared=2c64512f9a1ab832 Eleven Labs 11ai Voice Assistant https://x.com/elevenlabsio/status/1937200086515097939 Voice Design for V3 JUST RELEASED: https://x.com/elevenlabsio/status/1937912222128238967 Runway's Game Worlds  https://x.com/c_valenzuelab/status/1937665391855120525 Example: https://x.com/aDimensionDoor/status/1937651875408675060 AI Dungeon https://aidungeon.com/ The Best Hacker in the US in now an autonomous AI bot https://www.pcmag.com/news/this-ai-is-outranking-humans-as-a-top-software-bug-hunter https://x.com/Xbow/status/1937512662859981116 Simple & Good AI Work Flow From AI Warper https://x.com/AIWarper/status/1936899718678008211 RealTime Natural Language Photo Editing https://x.com/zeke/status/1937267796146290952 Bunker J Squirrel https://www.tiktok.com/t/ZTjc3hb38/ Bigfoot Sermons https://www.tiktok.com/t/ZTjcEq17Y/ John Oliver's Episode about AI Slop https://youtu.be/TWpg1RmzAbc?si=LAdktGWlIVVDqAjR Jabba Kisses Han https://www.reddit.com/r/CursedAI/comments/1ljjdw3/what_the_hell_am_i_looking_at/  

It makes for a great headline saying that 16 billion passwords were leaked. Was this some new massive data breach? What should you do about it? We take a look. We've got plenty of other tech news, tips, and picks to get you caught up on this week so you can get out there and tech better! Watch on YouTube! - Notnerd.com and Notpicks.com INTRO (00:00) It's not just Prime Video: Max shows 50% more ads now (06:45) MAIN TOPIC: 16 Billion with a B Passwords Leaked (09:20) 16 Billion Apple, Facebook, Google And Other Passwords Leaked No, the 16 billion credentials leak is not a new data breach haveibeenpwned.com Please use passkeys, a password manager, and 2FA! DAVE'S PRO-TIP OF THE WEEK:  Schedule Text Message, Send Later on iOS (18:55) JUST THE HEADLINES: (25:35) Applebee's and IHOP plan to introduce AI in restaurants Axolotl discovery brings us closer than ever to regrowing human limbs A mathematician calculated the size of a giant meatball made of every human Scientists once hoarded pre-nuclear steel; now we're hoarding pre-AI content Record DDoS pummels site with once-unimaginable 7.3Tbps of junk traffic Iran bans officials from using internet-connected devices Scientists create 'world's smallest violin' TAKES: Introducing Oakley Meta Glasses, a New Category of Performance AI Glasses (28:30) macOS Tahoe beta drops FireWire support (36:05) Project Indigo - a computational photography camera app from Adobe (38:55) Why Denmark is dumping Microsoft Office and Windows for LibreOffice and Linux (43:30) BONUS ODD TAKE: Catleidoscope and Catcordian! (46:50) PICKS OF THE WEEK: Dave: Lytro Camera (48:45) Nate: Ryan Trahan YouTube Channel (56:40) RAMAZON PURCHASE - Giveaway! (01:03:35)

video: https://youtu.be/txJomfjAUqI In this episode of Destination Linux, we unpack Denmark's push for digital sovereignty as it swaps Microsoft Office 365 for LibreOffice, question Google's commitment to openness after Pixel-specific code goes missing from the latest Android 16 AOSP drop, and celebrate KDE Plasma 6.4's slew of polish-packed upgrades. Tune in for the big picture on open-source wins, setbacks, and standout releases ... all in one quick-hitting show. Forum Discussion Thread (https://destinationlinux.net/forum) Download as MP3 (https://aphid.fireside.fm/d/1437767933/32f28071-0b08-4ea1-afcc-37af75bd83d6/37a9468e-5809-44e1-8510-e496533c93ce.mp3) Support the show by becoming a patron at tuxdigital.com/membership (https://tuxdigital.com/membership) or get some swag at tuxdigital.com/store (https://tuxdigital.com/store) Hosted by: Ryan (DasGeek) = dasgeek.net (https://dasgeek.net) Jill Bryant = jilllinuxgirl.com (https://jilllinuxgirl.com) Michael Tunnell = michaeltunnell.com (https://michaeltunnell.com) Chapters: 00:00:00 Intro 00:01:26 Community Feedback 00:04:37 Ryan Picks Arch (Again) 00:05:54 Ryan Is Okay, I Guess 00:06:25 Ricing Your System 00:10:00 Sandfly Security 00:13:57 Denmark Switches to LibreOffice 00:19:18 All Six Feet in the Water 00:20:19 Ryan Hates Centipedes 00:21:23 The DL Crew Loves Bees 00:22:41 Google Makes It's Android Open Source Less Accessible 00:32:28 Ryan Tries to Skip Michael's Topic 00:33:08 Ryan Makes Old Man References 00:34:14 KDE Plasma 6.4 Arrives 00:35:46 KDE Plasma 6.4: Flexible Tiling 00:38:34 KDE Fanboy Praises Plasma 00:39:05 KDE Plasma 6.4: HDR Calibration 00:40:30 Framwork has the crew excited 00:45:41 Drop the Extra 'S' 00:46:32 KDE Plasma 6.4: Spectacle Overhaul 00:47:49 KDE Plasma 6.4: System Monitoring 00:48:40 KDE Plasma 6.4: KRunner 00:50:29 KDE Plasma 6.4 Wrap Up 00:52:25 Tip of the Week: Viewing Logs in Linux 00:56:22 Support the Show 01:01:11 Outro 01:01:31 Post Show Links: Community Feedback https://destinationlinux.net/comments (https://destinationlinux.net/comments) https://destinationlinux.net/forum (https://destinationlinux.net/forum) Ryan Is Okay, I Guess https://store.tuxdigital.com/products/ryan-is-okay-i-guess-tee (https://store.tuxdigital.com/products/ryan-is-okay-i-guess-tee) Sandfly Security https://destinationlinux.net/sandfly (https://destinationlinux.net/sandfly) Denmark Switches to LibreOffice https://www.omgubuntu.co.uk/2025/06/denmark-government-replaces-microsoft-with-linux-libreoffice (https://www.omgubuntu.co.uk/2025/06/denmark-government-replaces-microsoft-with-linux-libreoffice) https://www.neowin.net/news/denmark-ditching-windows-and-office-for-linux-as-it-may-not-want-to-rely-on-microsoft-trump/ (https://www.neowin.net/news/denmark-ditching-windows-and-office-for-linux-as-it-may-not-want-to-rely-on-microsoft-trump/) Google Makes It's Android Open Source Less Accessible https://9to5google.com/2025/06/12/android-open-source-project-pixel-change/ (https://9to5google.com/2025/06/12/android-open-source-project-pixel-change/) KDE Plasma 6.4 https://kde.org/announcements/plasma/6/6.4.0/ (https://kde.org/announcements/plasma/6/6.4.0/) Tip of the Week: Viewing Logs in Linux https://destinationlinux.net/424 (https://destinationlinux.net/424) Support the Show https://tuxdigital.com/membership (https://tuxdigital.com/membership) https://store.tuxdigital.com/ (https://store.tuxdigital.com/)