Podcasts about Red Hat

Guest Dr. Bryan G. Behrenshausen Panelist Leslie Hawthorn | Abby Cabunoc Mayes Show Notes In this episode, hosts Leslie Hawthorn from Red Hat and Abby Cabunoc Mayes from GitHub, welcome Dr. Bryan G. Behrenshausen, a Senior Open Source Program Manager at GitLab. This episode delves deep into the world of open source, discussing its importance, challenges, and how companies like GitLab and GitHub are navigating and supporting the open source community. Bryan showcases GitLab's initiatives to support open source communities, touching on programs like the GitLab for Open Source, and the exclusive GitLab Open Source Partners program. Throughout the conversation topics like guidelines for diving into open source projects, the intrinsic link between open source and business strategy, and the role of effective social interaction in the open source realm are explored. The significance of maintaining transparent documentation, policies, and processes in an open source environment is also emphasized. Press download now to hear more! [00:01:29] Bryan tells us about his role at GitLab, where he operates at the interface between GitLab, the company, and the broader GitLab community, focusing on open source contributions. [00:03:23] Leslie inquires about specific support mechanisms GitLab offers to open source maintainers and Bryan mentions two significant programs at GitLab: The GitLab for Open Source program and The GitLab Open Source Partners program. He lists some major projects associated with the GitLab Open Source Partners program like Debian, Arch, Fedora, etc. [00:08:45] Bryan emphasizes the importance of sustainability and how being a part of a community can provide support, best practices, and even commiseration. [00:10:01] Abby points out the challenges of community interaction on platforms like GitHub and asks Bryan about the impact of his efforts on community building at GitLab. Bryan acknowledges the challenges and notes that while they're seeing progress in community building, it's an ongoing effort. [00:11:38] We hear how Bryan is handling open source projects that just need a private repository for security releases. [00:12:38] Leslie mentions the significance of sharing policies and processes publicly, particularly in Europe, given the legislative environment. Bryan explains how GitLab implements a management model called “team ops” for best practices in an all-remote environment. [00:13:33] Leslie stresses the importance of documentation, and Bryan shares that GitLab is active on Discord, and he tells the story of how the community started the server and later handed it to GitLab. [00:15:33] Abby praises both GitLab and Red Hat for running open source projects and documentation. Bryan highlights the challenges and decisions behind using Discord. [00:16:50] Bryan provides context for the open leadership assessment and talks about how open source principles impact organizational culture and design, he mentions he'll be speaking with Heidi Hess von Ludewig about one of his favorite projects at All Things Open-2023, and we hear about the “open source way,” which is another project he worked on. [00:20:58] Leslie raises the topic of interplay between work in communities and the responsibilities to employers, and Bryan explores the complexities of working in open source, the challenges, and frictions when balancing between community engagement and organizational objectives. [00:24:26] Abby asks if GitLab is offering guidelines for diving into open source projects. Bryan responds that GitLab's handbook provides some basic guides but lacks a full-fledged open source programs office. [00:25:42] Leslie discusses a trend in technology industry where companies scale back on their open source program office staff, especially during rough economic times, and Bryan talks about the intertwined nature of open source and business strategy in certain organizations, and how the open source strategy is essential from top to bottom. [00:28:27] Leslie suggests that achieving business outcomes can be smoother with the right tools, including the skills for effective social interactions in the open source realm. Quotes [00:03:45] “We owe it to the open source ecosystem of which we are a part to make sure that ecosystem is healthy and vibrant and has what it needs.” [00:19:45] “I just think that open source communities are really fascinating Petri dishes of self-organization and self-governance.” [00:24:02] “Participation in open source projects is all but unavoidable today as an organization.” Spotlight [00:29:32] Bryan's spotlight is his favorite open source project, WordGrinder. [00:31:02] Abby's spotlight is Random Name Picker for Lucky Draw. [00:31:44] Leslie's spotlight is reading a chapter on ‘Communication Channels' from the guidebook, The Turing Way. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) SustainOSS Mastodon (https://mastodon.social/tags/sustainoss) Open Collective-SustainOSS (Contribute) (https://opencollective.com/sustainoss) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Leslie Hawthorn Twitter (https://twitter.com/lhawthorn?lang=en) Abby Cabunoc Mayes Twitter (https://twitter.com/abbycabs?lang=en) Dr. Bryan Behrenshausen Website (https://semioticrobotic.net/) The Open Organization (https://theopenorganization.org/) GitLab (https://about.gitlab.com/) GitLab for Open Source (https://about.gitlab.com/solutions/open-source/join/) GitLab Open Source Partners (https://about.gitlab.com/solutions/open-source/partners/) All Things Open (ATO) 2023 (https://2023.allthingsopen.org/) WordGrinder (http://cowlark.com/wordgrinder/index.html) Random Name Picker for Lucky Draw (https://github.com/icelam/random-name-picker) The Turing Way-Communication Channels (https://the-turing-way.netlify.app/communication/os-comms/os-comms-channels) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Dr. Bryan Behrenshausen.

Willkommen zum FOCUS ON: Linux-Adventskalender! Die nächsten 24 Tage findet ihr jeden Tag eine kurze Folge zu einem Thema oder Menschen aus der Open Source-Szene in eurem Podcatcher. Den Anfang macht heute die Desktop-Distribution Fedora Silverblue, die von vielen als zukunftsweisend empfunden wird. Zusammen mit Robert Bohne (Solution Architect bei Red Hat) erarbeiten wir uns, was Silverblue von anderen Fedora-Varianten unterscheidet.

This week Steve goes through his data migration story at his house. What things should you consider before moving large datasets around, and what things need to be taken into account for a solid backup plan? -- During The Show -- 01:52 Home Automation Leak Detection - Jeremy You can't really Using cameras 08:06 mmWave sensor update/comparison Seedstudio mmWave Sensor (https://wiki.seeedstudio.com/mmwave_human_detection_kit/) Space for other sensors Way better than a PIR sensor Aqara Water Sensor (https://cloudfree.shop/product/aqara-water-sensor/) 11:19 Point of sale gear? - Charlie Odoo (https://github.com/odoo/odoo) Open Source POS (https://github.com/opensourcepos/opensourcepos) UniCenta (https://unicenta.com/) Squirrel Systems (https://www.squirrelsystems.com/squirrel-pos-for-hotels) 13:28 Succession Planning - David Password dump Bitwarden Network diagram with pictures Good documentation Techy friends Dave Ramsey - Legacy box Legacy Folder Data, external drives 23:23 Odoo for Accounting and Bookkeeping - Tiny Looks like a solid platform Expensive Self hosting not really an option Accounting solid but very basic no payroll Not fully open source 25:51 Backups? - Mike Copying the file MIGHT be ok if file system has bit rot protection works till it doesn't Better to use database tools External drives 3.5 StarTech Enclosure (https://www.amazon.com/StarTech-com-10Gbps-Enclosure-SATA-Drives/dp/B00XLAZEFC) Pelican 1120 Case 2.5 Cable Matters Enclosure (https://www.amazon.com/Cable-Matters-Aluminum-External-Enclosure/dp/B07CQD6M5B) Steve's M.2 Enclosure (https://www.amazon.com/gp/product/B09T97Z7DM) ASUS ROG M.2 Enclosure (https://www.amazon.com/ASUS-ROG-Arion-Aluminum-Enclosure/dp/B07ZKB4SLK) 37:57 News Wire OpenZFS 2.2.1 - Phoronix (https://www.phoronix.com/news/OpenZFS-2.2.1-Released) Weston 13.0 - Freedesktop.org (https://lists.freedesktop.org/archives/wayland-devel/2023-November/043326.html) OpenSSL 3.2 - GitHub (https://github.com/openssl/openssl/blob/openssl-3.2.0/NEWS.md) PipeWire 1.0 - Phoronix (https://www.phoronix.com/news/PipeWire-1.0-Released) LibreOffice 7.6.3 On Android - Document Foundation (https://blog.documentfoundation.org/blog/2023/11/23/libreoffice-763-and-android-viewer-app/) Wine 8.21 - Gaming On Linux (https://www.gamingonlinux.com/2023/11/wine-821-brings-high-dpi-scaling-and-initial-vulkan-support-for-wayland/) Studio One 6.5 - Presonus Software (https://www.presonussoftware.com/en_US/blog/studio-one-6-5-for-linux) PeerTube v6 - Frama Blog (https://framablog.org/2023/11/28/peertube-v6-is-out-and-powered-by-your-ideas/) Proxmox 8.1 - Proxmox (https://www.proxmox.com/en/about/press-releases/proxmox-virtual-environment-8-1) OpenMandriva - LX 5.0 - Beta News (https://betanews.com/2023/11/25/openmandriva-lx-50-linux-download/) Nitrix 3.2.0 - NXOS.org (https://nxos.org/changelog/release-announcement-nitrux-3-2-0/) Ultra Marine Linux 39 - Fyra Labs (https://blog.fyralabs.com/ultramarine-39-released/) Linux 6.6 tagged LTS - Security Boulevard (https://securityboulevard.com/2023/11/linux-6-6-is-now-officially-an-lts-release/) Linux Runs 20% Faster on Ryzen 7995WX - Toms Hardware (https://www.tomshardware.com/news/ubuntu-runs-20-faster-than-windows-11-on-amd-threadripper-pro-7995wx) MicroCloud - Infoq (https://www.infoq.com/news/2023/11/canonical-microcloud-open-source/) GIMP Team Targeting May 2024 - Librearts.org (https://librearts.org/2023/11/gimp-3-0-roadmap/) X11 Being Removed from RHEL 10 - Red Hat (https://www.redhat.com/en/blog/rhel-10-plans-wayland-and-xorg-server) Fuctional Source License - The Register (https://www.theregister.com/2023/11/24/opinion_column/) Kinsing Malware - Hack Read (https://www.hackread.com/kinsing-crypto-malware-linux-apache-activemq-flaw/) SysJoker Malware - Cyber Security News (https://cybersecuritynews.com/sysjoker-malware-attacking-windows-linux-and-mac-users-abusing-onedrive/) Looney Tunables - Security Affairs (https://securityaffairs.com/154573/security/cisa-known-exploited-vulnerabilities-catalog-looney-tunables.html) Open Source Tesla - The Verge (https://www.theverge.com/2023/11/23/23973701/tesla-roadster-is-now-fully-open-source) AMD GPU & RISC-V - Toms Hardware (https://www.tomshardware.com/pc-components/gpus/amds-fastest-gaming-gpu-now-works-with-risc-v-cpus-amd-radeon-rx-7900-xtx-open-source-linux-drivers-available) Real AI - Mark Tech Post (https://www.marktechpost.com/2023/11/23/real-ai-wins-project-to-build-europes-open-source-large-language-model/) Synthetic Machine Learning Data - SD Times (https://sdtimes.com/data/capital-one-open-sources-new-project-for-generating-synthetic-data/) Uploading Minds - Crypto Slate (https://cryptoslate.com/buterin-sees-benefit-of-uploading-minds-and-need-for-open-source-innovation-in-ai/) AI Linux Optimization - Toms Hardware (https://www.tomshardware.com/news/chinese-company-uses-ai-to-optimize-linux-kernel) 41:11 Nativefier Makes native Linux app out of web pages Saves credentials and session Mind Drip One (http://docs.minddripone.com/how-to/install-use-nativefier/) Nativefier GUI GitHub (https://github.com/mattruzzi/nativefier-gui) 45:44 Data Migration Good to rotate drives Disk burn in (bunch of rsync) Rsync 26 hours rsync will preserve hard links with the right flags software raid is more portable nuke & pave 2 vdevs, 3 drives per vdev can only loose one drive ZFS send/receive is much faster and better IDrive (https://www.idrive.com/) Kopia (https://kopia.io/) Spider Oak One Plan for your target rsync commands a: Archive mode, which preserves permissions, ownership, and timestamps. v: Verbose mode, which prints out detailed information about the transfer. H: Preserve hard links. P: Preserve permissions. Dumping a database is intensive Proxmox gets in the way doesn't gain Steve anything Special snowflake Custom UI Good for multi node No updates KVM works the same everywhere Cockpit GUI Will eventually replace virtmanager -- The Extra Credit Section -- For links to the articles and material referenced in this week's episode check out this week's page from our podcast dashboard! This Episode's Podcast Dashboard (http://podcast.asknoahshow.com/365) Phone Systems for Ask Noah provided by Voxtelesys (http://www.voxtelesys.com/asknoah) Join us in our dedicated chatroom #GeekLab:linuxdelta.com on Matrix (https://element.linuxdelta.com/#/room/#geeklab:linuxdelta.com) -- Stay In Touch -- Find all the resources for this show on the Ask Noah Dashboard Ask Noah Dashboard (http://www.asknoahshow.com) Need more help than a radio show can offer? Altispeed provides commercial IT services and they're excited to offer you a great deal for listening to the Ask Noah Show. Call today and ask about the discount for listeners of the Ask Noah Show! Altispeed Technologies (http://www.altispeed.com/) Contact Noah live [at] asknoahshow.com -- Twitter -- Noah - Kernellinux (https://twitter.com/kernellinux) Ask Noah Show (https://twitter.com/asknoahshow) Altispeed Technologies (https://twitter.com/altispeed)

In this episode, we dive into the exciting world of automation with the new Ansible collection for the Meraki dashboard API. Developed in collaboration with open source leader Red Hat, this automation platform opens up a world of possibilities for network admins and those interested in automation. We are joined by experts from Red Hat and Cisco Meraki to discuss the benefits of Ansible, the partnership between the two companies, and the use cases and future plans for this powerful tool. Tune in to learn more about this game-changing collaboration and the future of automation in the Meraki ecosystem.Host Tanner Yehlik—Technical Marketing Engineer, Cisco Meraki  GuestsDafné Mendoza—Principal Product Manager, Network Automation, Red HatOren Brigg—Product Manager, Developer Platform and Ecosystem, Cisco MerakiLearn moreDevNet Learning Lab - Using Ansible with Cisco MerakiMeraki Marketplace - Red Hat Ansible Automation Platform

Jeff Morris, VP of Product & Solutions Marketing at Couchbase, joins Corey on Screaming in the Cloud to discuss Couchbase's new columnar data store functionality, specific use cases for columnar data stores, and why AI gets better when it communicates with a cleaner pool of data. Jeff shares how more responsive databases could allow businesses like Dominos and United Airlines to create hyper-personalized experiences for their customers by utilizing more responsive databases. Jeff dives into the linked future of AI and data, and Corey learns about Couchbase's plans for the re:Invent conference. If you're attending re:Invent, you can visit Couchbase at booth 1095.About JeffJeff Morris is VP Product & Solutions Marketing at Couchbase (NASDAQ: BASE), a cloud database platform company that 30% of the Fortune 100 depend on.Links Referenced:Couchbase: https://www.couchbase.com/TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. This promoted guest episode of Screaming in the Cloud is brought to us by our friends at Couchbase. Also brought to us by Couchbase is today's victim, for lack of a better term. Jeff Morris is their VP of Product and Solutions Marketing. Jeff, thank you for joining me.Jeff: Thanks for having me, Corey, even though I guess I paid for it.Corey: Exactly. It's always great to say thank you when people give you things. I learned this from a very early age, and the only people who didn't were rude children and turned into worse adults.Jeff: Exactly.Corey: So, you are effectively announcing something new today, and I always get worried when a database company says that because sometimes it's a license that is going to upset people, sometimes it's dyed so deep in the wool of generative AI that, “Oh, we're now supporting vectors or whatnot.” Well, most of us don't know what that means.Jeff: Right.Corey: Fortunately, I don't believe that's what you're doing today. What have you got for us?Jeff: So, you're right. It's—well, what I'm doing is, we're announcing new stuff inside of Couchbase and helping Couchbase expand its market footprint, but we're not really moving away from our sweet spot, either, right? We like building—or being the database platform underneath applications. So, push us on the operational side of the operational versus analytic, kind of, database divide. But we are announcing a columnar data store inside of the Couchbase platform so that we can build bigger, better, stronger analytic functionality to feed the applications that we're supporting with our customers.Corey: Now, I feel like I should ask a question around what a columnar data store is because my first encounter with the term was when I had a very early client for AWS bill optimization when I was doing this independently, and I was asking them the… polite question of, “Why do you have 283 billion objects in a single S3 bucket? That is atypical and kind of terrifying.” And their answer was, “Oh, we built our own columnar data store on top of S3. This might not have been the best approach.” It's like, “I'm going to stop you there. With no further information, I can almost guarantee you that it was not.” But what is a columnar data store?Jeff: Well, let's start with the, everybody loves more data and everybody loves to count more things, right, but a columnar data store allows you to expedite the kind of question that you ask of the data itself by not having to look at every single row of the data while you go through it. You can say, if you know you're only looking for data that's inside of California, you just look at the column value of find me everything in California and then I'll pick all of those records to analyze. So, it gives you a faster way to go through the data while you're trying to gather it up and perform aggregations against it.Corey: It seems like it's one of those, “Well, that doesn't sound hard,” type of things, when you're thinking about it the way that I do, in terms of a database being more or less a medium to large size Excel spreadsheet. But I have it on good faith from all the customer environments. I've worked with that no, no, there are data stores that span even larger than that, which is, you know, one of those sad realities of the world. And everything at scale begins to be a heck of a lot harder. I've seen some of the value that this stuff offers and I can definitely understand a few different workloads in which case that's going to be super handy. What are you targeting specifically? Or is this one of those areas where you're going to learn from your customers?Jeff: Well, we've had analytic functionality inside the platform. It just, at the size and scale customers actually wanted to roam through the data, we weren't supporting that that much. So, we'll expand that particular footprint, it'll give us better integration capabilities with external systems, or better access to things in your bucket. But the use case problem is, I think, going to be driven by what new modern application requirements are going to be. You're going to need, we call it hyper-personalization because we tend to cater to B2C-style applications, things with a lot of account profiles built into them.So, you look at account profile, and you're like, “Oh, well Jeff likes blue, so sell him blue stuff.” And that's a great current level personalization, but with a new analytic engine against this, you can maybe start aggregating all the inventory information that you might have of all the blue stuff that you want to sell me and do that in real-time, so I'm getting better recommendations, better offers as I'm shopping on your site or looking at my phone and, you know, looking for the next thing I want to buy.Corey: I'm sure there's massive amounts of work that goes into these hyper-personalization stories. The problem is that the only time they really rise to our notice is when they fail hilariously. Like, you just bought a TV, would you like to buy another? Now statistically, you are likelier to buy a second TV right after you buy one, but for someone who just, “Well, I'm replacing my living room TV after ten years,” it feels ridiculous. Or when you buy a whole bunch of nails and they don't suggest, “Would you like to also perhaps buy a hammer?”It's one of those areas where it just seems like a human putting thought into this could make some sense. But I've seen some of the stuff that can come out of systems like this and it can be incredible. I also personally tend to bias towards use cases that are less, here's how to convince you to buy more things and start aiming in a bunch of other different directions where it starts meeting emerging use cases or changing situations rapidly, more rapidly than a human can in some cases. The world has, for better or worse, gotten an awful lot faster over the last few decades.Jeff: Yeah. And think of it in terms of how responsive can I be at any given moment. And so, let's pick on one of the more recent interesting failures that has popped up. I'm a Giants fan, San Francisco Giants fan, so I'll pick on the Dodgers. The Dodgers during the baseball playoffs, Clayton Kershaw—three-time MVP, Cy Young Award winner, great, great pitcher—had a first-inning meltdown of colossal magnitude: gave up 11 runs in the first inning to the Diamondbacks.Well, my customer Domino's Pizza could end up—well, let's shift the focus of our marketing. We—you know, the Dodgers are the best team in baseball this year in the National League—let's focus our attention there, but with that meltdown, let's pivot to Arizona and focus on our market in Phoenix. And they could do that within minutes or seconds, even, with the kinds of capabilities that we're coming up with here so that they can make better offers to that new environment and also do the decision intelligence behind it. Like, do I have enough dough to make a bigger offer in that big market? Do I have enough drivers or do I have to go and spin out and get one of the other food delivery folks—UberEats, or something like that—to jump on board with me and partner up on this kind of system?It's that responsiveness in real, real-time, right, that's always been kind of the conundrum between applications and analytics. You get an analytic insight, but it takes you an hour or a day to incorporate that into what the application is doing. This is intended to make all of that stuff go faster. And of course, when we start to talk about things in AI, right, AI is going to expect real-time responsiveness as best you can make it.Corey: I figure we have to talk about AI. That is a technology that has absolutely sprung to the absolute peak of the hype curve over the past year. OpenAI released Chat-Gippity, either late last year or early this year and suddenly every company seems to be falling all over itself to rebrand itself as an AI company, where, “We've been working on this for decades,” they say, right before they announce something that very clearly was crash-developed in six months. And every company is trying to drape themselves in the mantle of AI. And I don't want to sound like I'm a doubter here. I'm like most fans; I see an awful lot of value here. But I am curious to get your take on what do you think is real and what do you think is not in the current hype environment.Jeff: So yeah, I love that. I think there's a number of things that are, you know, are real is, it's not going away. It is going to continue to evolve and get better and better and better. One of my analyst friends came up with the notion that the exercise of generative AI, it's imprecise, so it gives you similarity things, and that's actually an improvement, in many cases, over the precision of a database. Databases, a transaction either works or it doesn't. It has failover or it doesn't, when—Corey: It's ideally deterministic when you ask it a question—Jeff: Yes.Corey: —the same question a second time, assuming it's not time-bound—Jeff: Gives you the right answer.Corey: Yeah, the sa—or at least the same answer.Jeff: The same answer. And your gen AI may not. So, that's a part of the oddity of the hype. But then it also helps me kind of feed our storyline of if you're going to try and make Gen AI closer and more accurate, you need a clean pool of data that you're dealing with, even though you've got probably—your previous design was such that you would use a relational database for transactions, a document database for your user profiles, you'd probably attach your website to a caching database because you needed speed and a lot of concurrency. Well, now you got three different databases there that you're operating.And if you're feeding data from each of those databases back to AI, one of them might be wrong or one of them might confuse the AI, yet how are you going to know? The complexity level is going to become, like, exponential. So, our premise is, because we're a multi-modal database that incorporates in-memory speed and documents and search and transactions and the like, if you start with a cleaner pool of data, you'll have less complexity that you're offering to your AI system and therefore you can steer it into becoming more accurate in its response. And then, of course, all the data that we're dealing with is on mobile, right? Data is created there for, let's say, your account profile, and then it's also consumed there because that's what people are using as their application interface of choice.So, you also want to have mobile interactivity and synchronization and local storage, kind of, capabilities built in there. So, those are kind of, you know, a couple of the principles that we're looking at of, you know, JSON is going to be a great format for it regardless of what happens; complexity is kind of the enemy of AI, so you don't want to go there; and mobility is going to be an absolute requirement. And then related to this particular announcement, large-scale aggregation is going to be a requirement to help feed the application. There's always going to be some other bigger calculation that you're going to want to do relatively in real time and feed it back to your users or the AI system that's helping them out.Corey: I think that that is a much more nuanced use case than a lot of the stuff that's grabbing customer attentions where you effectively have the Chat-Gippity story of it being an incredible parrot. Where I have run into trouble with the generative story has been people putting the thing that the robot that's magic and from the future has come up with off the cuff and just hurling that out into the universe under their own name without any human review, and that's fine sometimes sure, but it does get it hilariously wrong at some points. And the idea of sending something out under my name that has not been at least reviewed by me if not actually authored by me, is abhorrent. I mean, I review even the transactional, “Yes, you have successfully subscribed,” or, “Sorry to see you go,” email confirmations on stuff because there's an implicit, “Hugs and puppies, love Corey,” at the end of everything that goes out under my name.Jeff: Right.Corey: But I've gotten a barrage of terrible sales emails and companies that are trying to put the cart before the horse where either the, “Support rep,” quote-unquote, that I'm speaking to in the chat is an AI system or else needs immediate medical attention because there's something going on that needs assistance.Jeff: Yeah, they just don't understand.Corey: Right. And most big enterprise stories that I've heard so far that have come to light have been around the form of, “We get to fire most of our customer service staff,” an outcome that basically no one sensible wants. That is less compelling than a lot of the individualized consumer use cases. I love asking it, “Here's a blog post I wrote. Give me ten title options.” And I'll usually take one of them—one of them is usually not half bad and then I can modify it slightly.Jeff: And you'll change four words in it. Yeah.Corey: Yeah, exactly. That's a bit of a different use case.Jeff: It's been an interesting—even as we've all become familiar—or at least junior prompt engineers, right—is, your information is only going to be as good as you feed the AI system—the return is only going to be as good—so you're going to want to refine that kind of conversation. Now, we're not trying to end up replacing the content that gets produced or the writing of all kinds of pros, other than we do have a code generator that works inside of our environment called Capella iQ that talks to ChatGPT, but we try and put guardrails on that too, right, as always make sure that it's talking in terms of the context of Couchbase rather than, “Where's Taylor Swift this week,” which I don't want it to answer because I don't want to spend GPT money to answer that question for you.Corey: And it might not know the right answer, but it might very well spit out something that sounds plausible.Jeff: Exactly. But I think the kinds of applications that we're steering ourselves toward can be helped along by the Gen AI systems, but I don't expect all my customers are going to be writing automatic blog post generation kinds of applications. I think what we're ultimately trying to do is facilitate interactions in a way that we haven't dreamt of yet, right? One of them might be if I've opted into to loyalty programs, like my United account and my American Express account—Corey: That feels very targeted at my lifestyle as well, so please, continue.Jeff: Exactly, right? And so, what I really want the system to do is for Amex to reward me when I hit 1k status on United while I'm on the flight and you know, have the flight attendant come up and be like, “Hey, you did it. Either, here's a free upgrade from American Express”—that would be hyper-personalization because you booked your plane ticket with it, but they also happen to know or they cross-consumed information that I've opted into.Corey: I've seen them congratulate people for hitting a million miles flown mid-flight, but that's clearly something that they've been tracking and happens a heck of a lot less frequently. This is how you start scaling that experience.Jeff: Yes. But that happened because American Airlines was always watching because that was an American Airlines ad ages ago, right, but the same principle holds true. But I think there's going to be a lot more of these: how much information am I actually allowing to be shared amongst the, call it loyalty programs, but the data sources that I've opted into. And my God, there's hundreds of them that I've personally opted into, whether I like it or not because everybody needs my email address, kind of like what you were describing earlier.Corey: A point that I have that I think agrees largely with your point is that few things to me are more frustrating than what I'm signing up, for example, oh, I don't know, an AWS even—gee, I can't imagine there's anything like that going on this week—and I have to fill out an entire form that always asked me the same questions: how big my company is, whether we have multiple workloads on, what industry we're in. And no matter what I put into that, first, it never remembers me for the next time, which is frustrating in its own right, but two, no matter what I put in to fill that thing out, the email I get does not change as a result. At one point, I said, all right—I'm picking randomly—“I am a venture capitalist based in Sweden,” and I got nothing that is differentiated from the other normal stuff I get tied to my account because I use a special email address for those things, sometimes just to see what happens. And no, if you're going to make me jump through the hoops to give you the data, at least use it to make my experience better. It feels like I'm asking for the moon here, but I shouldn't be.Jeff: Yes. [we need 00:16:19] to make your experience better and say, you know, “Here's four companies in Malmo that you ought to be talking to. And they happen to be here at the AWS event and you can go find them because their booth is here, here, and here.” That kind of immediate responsiveness could be facilitated, and to our point, ought to be facilitated. It's exactly like that kind of thing is, use the data in real-time.I was talking to somebody else today that was discussing that most data, right, becomes stale and unvaluable, like, 50% of the data, its value goes to zero after about a day. And some of it is stale after about an hour. So, if you can end up closing that responsiveness gap that we were describing—and this is kind of what this columnar service inside of Capella is going to be like—is react in real-time with real-time calculation and real-time look-up and real-time—find out how you might apply that new piece of information right now and then give it back to the consumer or the user right now.Corey: So, Couchbase takes a few different forms. I should probably, at least for those who are not steeped in the world of exotic forms of database, I always like making these conversations more accessible to folks who are not necessarily up to speed. Personally, I tend to misuse anything as a database, if I can hold it just the wrong way.Jeff: The wrong way. I've caught that about you.Corey: Yeah, it's—everything is a database if you hold it wrong. But you folks have a few different options: you have a self-managed commercial offering; you're an open-source project, so I can go ahead and run it on my own infrastructure however I want; and you have Capella, which is Couchbase as a service. And all of those are useful and have their points, and I'm sure I'm missing at least one or two along the way. But do you find that the columnar use case is going to disproportionately benefit folks using Capella in ways that the self-hosted version would not be as useful for, or is this functionality already available in other expressions of Couchbase?Jeff: It's not already available in other expressions, although there is analytic functionality in the self-managed version of Couchbase. But it's, as I've mentioned I think earlier, it's just not as scalable or as really real-time as far as we're thinking. So, it's going to—yes, it's going to benefit the database as a service deployments of Couchbase available on your favorite three clouds, and still interoperable with environments that you might self-manage and self-host. So, there could be even use cases where our development team or your development team builds in AWS using the cloud-oriented features, but is still ultimately deploying and hosting and managing a self-managed environment. You could still do all of that. So, there's still a great interplay and interoperability amongst our different deployment options.But the fun part, I think, about this is not only is it going to help the Capella user, there's a lot of other things inside Couchbase that help address the developers' penchant for trading zero-cost for degrees of complexity that you're willing to accept because you want everything to be free and open-source. And Couchbase is my fifth open-source company in my background, so I'm well, well versed in the nuances of what open-source developers are seeking. But what makes Couchbase—you know, its origin story really cool too, though, is it's the peanut butter and chocolate marriage of memcached and the people behind that and membase and CouchDB from [Couch One 00:19:54]. So, I can't think of that many—maybe Red Hat—project and companies that formed up by merging two complementary open-source projects. So, we took the scale and—Corey: You have OpenTelemetry, I think, that did that once, but that—you see occasional mergers, but it's very far from common.Jeff: But it's very, very infrequent. But what that made the Couchbase people end up doing is make a platform that will scale, make a data design that you can auto partition anywhere, anytime, and then build independently scalable services on top of that, one for SQL++, the query language. Anyone who knows SQL will be able to write something in Couchbase immediately. And I've got this AI Automator, iQ, that makes it even easier; you just say, “Write me a SQL++ query that does this,” and it'll do that. But then we added full-text search, we added eventing so you can stream data, we added the analytics capability originally and now we're enhancing it, and use JSON as our kind of universal data format so that we can trade data with applications really easily.So, it's a cool design to start with, and then in the cloud, we're steering towards things like making your entry point and using our database as a service—Capella—really, really, really inexpensive so that you get that same robustness of functionality, as well as the easy cost of entry that today's developers want. And it's my analyst friends that keep telling me the cloud is where the markets going to go, so we're steering ourselves towards that hockey puck location.Corey: I frequently remark that the role of the DBA might not be vanishing, but it's definitely changing, especially since the last time I counted, if you hold them and use as directed, AWS has something on the order of 14 distinct managed database offerings. Some are general purpose, some are purpose-built, and if this trend keeps up, in a decade, the DBA role is going to be determining which of its 40 databases is going to be the right fit for a given workload. That seems to be the counter-approach to a general-purpose database that works across the board. Clearly you folks have opinions on this. Where do you land?Jeff: Oh, so absolutely. There's the product that is a suite of capabilities—or that are individual capabilities—and then there's ones that are, in my case, kind of multi-model and do lots of things at once. I think historically, you'll recognize—because this is—let's pick on your phone—the same holds true for, you know, your phone used to be a watch, used to be a Palm Pilot, used to be a StarTAC telephone, and your calendar application, your day planner all at the same time. Well, it's not anymore. Technology converges upon itself; it's kind of a historical truism.And the database technologies are going to end up doing that—or continue to do that, even right now. So, that notion that—it's a ten-year-old notion of use a purpose-built database for that particular workload. Maybe sometimes in extreme cases that is the appropriate thing, but in more cases than not right now, if you need transactions when you need them, that's fine, I can do that. You don't necessarily need Aurora or RDS or Postgres to do that. But when you need search and geolocation, I support that too, so you don't need Elastic. And then when you need caching and everything, you don't need ElastiCache; it's all built-in.So, that multi-model notion of operate on the same pool of data, it's a lot less complex for your developers, they can code faster and better and more cleanly, debugging is significantly easier. As I mentioned, SQL++ is our language. It's basically SQL syntax for JSON. We're a reference implementation of this language, along with—[AsteriskDB 00:23:42] is one of them, and actually, the original author of that language also wrote DynamoDB's PartiQL.So, it's a common language that you wouldn't necessarily imagine, but the ease of entry in all of this, I think, is still going to be a driving goal for people. The old people like me and you are running around worrying about, am I going to get a particular, really specific feature out of the full-text search environment, or the other one that I pick on now is, “Am I going to need a vector database, too?” And the answer to me is no, right? There's going—you know, the database vendors like ourselves—and like Mongo has announced and a whole bunch of other NoSQL vendors—we're going to support that. It's going to be just another mode, and you get better bang for your buck when you've got more modes than a single one at a time.Corey: The consensus opinion that's emerging is very much across the board that vector is a feature, not a database type.Jeff: Not a category, yeah. Me too. And yeah, we're well on board with that notion, as well. And then like I said earlier, the JSON as a vehicle to give you all of that versatility is great, right? You can have vector information inside a JSON document, you can have time series information in the document, you could have graph node locations and ID numbers in a JSON array, so you don't need index-free adjacency or some of the other cleverness that some of my former employers have done. It really is all converging upon itself and hopefully everybody starts to realize that you can clean up and simplify your architectures as you look ahead, so that you do—if you're going to build AI-powered applications—feed it clean data, right? You're going to be better off.Corey: So, this episode is being recorded in advance, thankfully, but it's going to release the first day of re:Invent. What are you folks doing at the show, for those who are either there and for some reason, listening to a podcast rather than going to getting marketed to by a variety of different pitches that all mention AI or might even be watching from home and trying to figure out what to make of it?Jeff: Right. So, of course we have a booth, and my notes don't have in front of me what our booth number is, but you'll see it on the signs in the airport. So, we'll have a presence there, we'll have an executive briefing room available, so we can schedule time with anyone who wants to come talk to us. We'll be showing not only the capabilities that we're offering here, we'll show off Capella iQ, our coding assistant, okay—so yeah, we're on the AI hype band—but we'll also be showing things like our mobile sync capability where my phone and your phone can synchronize data amongst themselves without having to actually have a live connection to the internet. So, long as we're on the same network locally within the Venetian's network, we have an app that we have people download from the Apple Store and then it's a color synchronization app or picture synchronization app.So, you tap it, and it changes on my screen and I tap it and it changes on your screen, and we'll have, I don't know, as many people who are around standing there, synchronizing, what, maybe 50 phones at a time. It's actually a pretty slick demonstration of why you might want a database that's not only in the cloud but operates around the cloud, operates mobile-ly, operates—you know, can connect and disconnect to your networks. It's a pretty neat scenario. So, we'll be showing a bunch of cool technical stuff as well as talking about the things that we're discussing right now.Corey: I will say you're putting an awful lot of faith in conductivity working at re:Invent, be it WiFi or the cellular network. I know that both of those have bitten me in various ways over the years. But I wish you the best on it. I think it's going to be an interesting show based upon everything I've heard in the run-up to it. I'm just glad it's here.Jeff: Now, this is the cool part about what I'm talking about, though. The cool part about what I'm talking about is we can set up our own wireless network in our booth, and we still—you'd have to go to the app store to get this application, but once there, I can have you switch over to my local network and play around on it and I can sync the stuff right there and have confidence that in my local network that's in my booth, the system's working. I think that's going to be ultimately our design there because oh my gosh, yes, I have a hundred stories about connectivity and someone blowing a demo because they're yanking on a cable behind the pulpit, right?Corey: I always build in a—and assuming there's no connectivity, how can I fake my demos, just because it's—I've only had to do it once, but you wind up planning in advance when you start doing a talk to a large enough or influential enough audience where you want things to go right.Jeff: There's a delightful acceptance right now of recorded videos and demonstrations that people sort of accept that way because of exactly all this. And I'm sure we'll be showing that in our booth there too.Corey: Given the non-deterministic nature of generative AI, I'm sort of surprised whenever someone hasn't mocked the demo in advance, just because yeah, gives the right answer in the rehearsal, but every once in a while, it gets completely unglued.Jeff: Yes, and we see it pretty regularly. So, the emergence of clever and good prompt engineering is going to be a big skill for people. And hopefully, you know, everybody's going to figure out how to pass it along to their peers.Corey: Excellent. We'll put links to all this in the show notes, and I look forward to seeing how well this works out for you. Best of luck at the show and thanks for speaking with me. I appreciate it.Jeff: Yeah, Corey. We appreciate the support, and I think the show is going to be very strong for us as well. And thanks for having me here.Corey: Always a pleasure. Jeff Morris, VP of Product and Solutions Marketing at Couchbase. This episode has been brought to us by our friends at Couchbase. And I'm Cloud Economist Corey Quinn. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry comment, but if you want to remain happy, I wouldn't ask that podcast platform what database they're using. No one likes the answer to those things.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

An airhacks.fm conversation with Martin Stefanko (@xstefank) about: starting with 4th generation i7 in 2013, the kernel hacker look, starting with Java 6, starting at RedHat, joining the JBoss EAP team, starting to maintain MicroProfile.io Health specification, Quarkus in Action book, smallrye.io vs. MicroProfile.io, Glassfish to Quarkus migrations, using Quarkus internal APIs, MicroProfile API compatibility, a composite quarkus-microprofile extension, Quarkus deploys at build time, saving money in the cloud, MicroProfile Metrics vs. micrometer, the burning icon and xstefank, SpringBoot vs. Quarkus startup time Martin Stefanko on twitter: @xstefank

In this episode of Infrastructure Matters, recorded at KubeCon 2023 in Chicago, hosts Steven Dickens and Camberely Bates discuss the latest trends and announcements in the world of Kubernetes and cloud-native technologies. They delve into the growth in KubeCon attendance, the increasing adoption of Kubernetes in enterprise environments, and the focus on platform engineering. Their conversation includes insights into various vendor announcements, including NetApp's Astra Control and Red Hat's new features, as well as a broader discussion on the maturation of the Kubernetes ecosystem, emphasizing the importance of security, resilience, and complexity in modern IT infrastructure. Key points from their discussion: KubeCon showcases significant growth and increasing enterprise adoption of Kubernetes. Vendors like NetApp and Red Hat announce new features and capabilities. Observability and security emerge as key themes in Kubernetes ecosystem development. The shift towards curated and opinionated Kubernetes stacks for easier management and better security.  

CHAOSScast – Episode 74 On this episode, our host Georg Link kicks off the discussion, introducing a stellar lineup of panelists including Sean Goggins, Yehui Wang, Mike Nolan, and Cali Dolfi. The topics discussed today are the CHAOSS software, Augur, and GrimoireLab, and the different applications built on top of this software. The panel members discuss the projects they are involved in, such as the Augur project, OSS Compass, and Project Aspen's 8Knot. Then, we'll delve into Mystic's prototype software, aiming to transform how academic contributions are recognized and valued. The discussion dives deep into the role of CHAOSS software in open source and community health, talks about Augur and GrimoireLab projects, ecosystem-level analysis, and data visualization. Press download now to hear more! [00:00:58] The panelists each introduce themselves. [00:03:03] Georg explains the origins of CHAOSS software, particularly Augur and Grimoire Lab, and their development. He dives into Grimoire Lab's focus on data quality, flexibility, and its identity management tool, Sorting Hat. [00:05:55] Sean details Augur's inception, its focus on a relational database, and its capabilities in data collection and validation. Georg and Sean recall Augur's early days, focusing on GitHub archive data, and its evolution into a comprehensive system. [00:09:28] Yehui discusses OSS Compass, its goals, the integration of metrics models, and the choice of using Grimoire Lab as a backend. He elaborates on OSS Compass's ease of use and the adoption of new data sources like Gitee. [00:14:16] Mike inquires about the handling of the vast number of repositories on Gitee, and Yehui explains using a message bus and RabbitMQ for both data handling and parallel processing. Sean clarifies that Gitee is a Git platform similar to GitHub and GitLab, and OSS Compass is the metrics and modeling tool. [00:15:29] Cali asks about the visualization tool used, and Yehui mentions moving away from Kibana to front-end technologies and libraries like ECharts for creating visualizations, which is an Apache open source project. [00:16:29] Cali describes 8Knot under Project Aspen built in Plotly Dash and Repel, focusing on mapping open source ecosystems using Augur data. She emphasizes the data science approach to analyzing open source communities and the templated nature of 8Knot for easy visualization creation by data scientists. [00:20:19] Sean comments on the ease of adding new visualizations with Dash Plotly technology in 8Knot. Cali adds that new visualizations can be easily made an that 8Knot is connected to a maintained Augur database but can also be forked for specific community and company needs. [00:2342] Georg underlines the importance of ecosystem-level analysis, especially for software supply chain security. Cali shares the goals of analyzing ecosystems to understand relationships between projects, influenced by Red Hat's interests in investing in interconnected communities. [00:26:30] The conversation shifts to Mystic, and Mike describes it as a prototype software integrating both GrimoireLab and Augur, with the goal of better integrating these projects through development. [00:27:30] Mike outlines Mystic's goal to serve as a front-end to date collection systems, with a specific focus on the academic community's contributions to technology research. He envisions Mystic as a tool for academics to measure community health and impact of their projects, aiding in tenure and promotion cases. [00:30:52] Yehui asks about integration of Grimoire Lab and Augur within Mystic and the selection of components for the solution. Mike explains the early stages of integration and the plan to combine data collection services from GrimoireLab into Augur to support undergraduate student development. [00:32:30] Mike details research on Mystic, including interviews with faculty from various departments to understand their digital collaboration and artifact creation. He aims to develop generalized models of collaboration applicable to multiple data sources, allowing systems like Mystic to support diverse academic disciplines. Value Adds (Picks) of the week: [00:36:26] Georg's pick is focusing on the slogan, “One day at a time.” [00:37:12] Cali's pick is doing a Friendsgiving this week. [00:38:08] Sean's pick is the launch of the tv show ‘Moonlighting' from the 80's. [00:38:49] Yehui's pick is riding his bike to work which is peaceful for him. [00:39:52] Mike's pick is attending The Turing Way Book Dash. Panelists: Georg Link Sean Goggins Michael Nolan Cali Dolfi Yehui Wang Links: CHAOSS (https://chaoss.community/) CHAOSS Project X/Twitter (https://twitter.com/chaossproj?lang=en) CHAOSScast Podcast (https://podcast.chaoss.community/) podcast@chaoss.community (mailto:podcast@chaoss.community) Ford Foundation (https://www.fordfoundation.org/) Georg Link Website (https://georg.link/) Sean Goggins Website (https://www.seangoggins.net/) Mike Nolan LinkedIn (https://www.linkedin.com/in/mikenolansoftware/?originalSubdomain=uk) Cali Dolfi LinkedIn (https://www.linkedin.com/in/calidolfi/) Yehui Wang GitHub (https://github.com/eyehwan) Augur (https://github.com/chaoss/augur) GrimoireLab (https://chaoss.github.io/grimoirelab/) Perceval-GitHub (https://github.com/chaoss/grimoirelab-perceval) Gitee (https://gitee.com/) RabbitMQ (https://www.rabbitmq.com/) OSS Compass-GitHub (https://github.com/oss-compass) Kibana (https://www.elastic.co/kibana) Apache ECharts (https://echarts.apache.org/en/index.html) 8Knot (https://eightknot.osci.io/) Building an open source community health analytics platform (Mystic) (https://opensource.com/article/21/9/openrit-mystic) The Turing Way Book Dashes (https://the-turing-way.netlify.app/community-handbook/bookdash.html) Special Guests: Cali Dolfi, Mike Nolan, and Yehui Wang.

Red Hat/Blue Hat Talk - Two Friends Who Disagree about Trump. Today Doug Pagitt and Casey Franklin are together in the studio  for the first time. They also talk about their shared experience at the Eagles concert.  Doug Pagitt and Casey Franklin are decades-long friends, they are both faith leaders, and, they seriously disagree about Donald Trump. Over the last year, they have texted regularly about those disagreements.  They are now bringing that conversation to this livestream/podcast. Their love for each other will be on display and so will their perspectives. And, there might even be a song or two.  Welcome to the first edition of “Red Hat - Blue Hat Talk” www.VoteCommonGood.com

Colin Fisher, Global Senior Director, Cloud Partner Ecosystem at Red Hat, is a panellist at CIONEXT | Mastering the Cloud on the 29th of November! Register now

On this episode of TWIL (242), we'll find out if it will blend with Blender 4.0. OBS project has released OBS Studio 30. AlmaLinux has a new release with 9.3. GNOME is getting funding of 1 Million euros. The Linux Foundation is creating a new foundation for High Performance Software. All of this and more […]

Summary: FOSS4G NA 2023 speaker, Michael Terner, addresses the question of making money with FOSS4G (Free and Open Source Software for Geospatial) technology. He outlines three viable business models: the Red Hat model (service and support fees), integration of FOSS4G into larger solutions, and open-sourcing technology with a premium model. Terner emphasizes the evolving hybrid landscape where open source and proprietary technologies coexist, highlighting the importance of supporting and giving back to the FOSS4G community. Highlights:

Alan Clark of SUSE talks with IEEE Spectrum editor Stephen Cass about the disruption in the enterprise Linux community caused by recent announcements by Red Hat over open source access to its codebase, and the formation of the Open Enterprise Linux Alliance (Open ELA) by SUSE, Oracle and CIQ in response.

A few months ago, Red Hat made the decision to restrict it's source code. As much as it pains Tom to say, he thinks Red Hat was smart to do it, even though its a move thats been fairly unpopular with its own community and users. It proves that Red Hat understands something Tom calls the "Trinity of Open Source". Chunga is curious about the impact these decisions will have over other open source projects and companies. Additionally, he wonders how much influence Red Hat actually has in the open source space in todays world. Tom has many opinions and thoughts to answer Chunga's curiosity about this area. For years, Red Hat has been the example and model of how open source companies choose to operate. However, as companies have evolved over the years, that may no longer be the case according to Tom.  Why?  Listen now to find out!  Get started with Salt in just a few minutes!

Julien Danjou is the founder of Mergify - a tool that helps merge code safer and faster. Summary (auto-generated): How do you split your time between work and marketing? 0:00 Julian splits 50% of his time between building the product and the other 50% doing marketing and bringing people to the product. Julian talks about mergerfi. Where do you start with product development? 1:23 The goal is to solve a problem for an engineer. They co-founded Mirchi Fi with Mary and wrote their own tool. The role of time is a lot of time. The importance of doing demos and showing the product around to the team, and how that has changed over time. How the product is simple and there are a lot of viable options around it, but it's hard to think about all the tiny details. How did they get started? 5:08 They both started with a full-time job and moved from a platform to get up. They felt naked without any of their tools. They wanted to build their own tools. They found a first rate customer, pitch.com, and then found more startups willing to use a merge request tool. One of the challenges of being a bootstrapped company is that they only have two hours per week to work on the tool. It is easy to not get good at making decisions when you can do everything, but in air quotes, do everything. How long did it take to write the first dashboard? 10:07 Before people started using it internally, they did most of the grunt work of writing the first version. The first version was a mvp. The first dashboard they wrote was like HTML and the bootstrap framework, which was pretty bad, but it was good enough. The first version of the product is the only thing that is going to be out in front of users or customers. The importance of being an entrepreneur-minded person. When they found the first customers, they decided not to build a company right away, but to focus on building a few hours a week into bots. The real trap. Marketing and getting the word out. 16:00 The root problem is that nobody knows about you because you are not doing marketing. You have to go with the event if you have a competitor or inspire something. It is easy to build the things for a year or so, especially when you are a developer. Not everything works, but what works well is open source projects. For example, amazon is using lodgify on their open source project. One of their biggest customers was using one of the engineer's projects on github.com, and they talk to their manager about it. Marketing and marketing budget. 20:30 Marketing is a lot of different channels that they can use, and they have tried almost everything to see if it works, and if it doesn't work, they try to future-harm. They try to provide value for free to open source users and projects and are happy to do that. Adding value in open source is about saving time and giving time to most open source projects using a merge tool. If a company is new to open source, they need a tool to help them with a workflow tool, marketing, etc. How did you find out about rescue? 25:36 The number of people using rescue is small. There are very small projects with just one or two people mentioning it to project being run by 50 or 100 person behind. The main goal is to actually work on the open source projects, not start a new one. Redhat was working on an open source project with Eddie when they started. Redhat is a great leverage for building a company. One takeaway for a dev tool founder, be strict about splitting 50% of your time between building the product and doing the fun stuff.

With Watson 1.0, IBM deviated from the silicon valley mantra, fail fast, as it took nearly a decade for the company to pivot off of its original vision. In our view, a different dynamic is in play today with Watson 2.0 – i.e. watsonx. IBM's deep research in AI and learnings from its previous mistakes, have positioned the company to be a major player in the Generative AI era. Specifically, in our opinion, IBM has a leading technological foundation, a robust and rapidly advancing AI stack, a strong hybrid cloud position (thanks to Red Hat), an expanding ecosystem and a consulting organization with deep domain expertise to apply AI in industry-specific use cases.  In this Breaking Analysis we share our takeaways and perspectives from a recent trip to IBM's research headquarters. To do so we collaborate with analyst friends in theCUBE Collective, Sanjeev Mohan, Tony Baer and Merv Adrian. We'll also share some relevant ETR spending data to frame the conversation. 

Maddie Franklin joins Doug Pagitt and Casey Franklin who are decades-long friends, they are both faith leaders and, they seriously disagree about Donald Trump. Over the last two years, they have texted regularly about those disagreements.  They are now bringing that conversation to this livestream/podcast. Their love for each other will be on display and so will their perspectives. Welcome to episode 4 of “Red Hat/Blue Hat Talk

Get 50 Free Lessons From 50 Top Entrepreneurs From Season 1: https://www.ehandbook.com/subscribeEach week, we interview real experts about topics you need to know about.Today we have Wei Lien Dang, who is a General Partner at Unusual Ventures and before that was an exited cofounder at StackRox which got acquired by RedHat.We're covering How To Scale An Open Source Startup - And Should You?Our Website: https://www.ehandbook.comUnusual Ventures: https://www.unusual.vc/Wei Lien Dang: https://www.linkedin.com/in/weiliendang/

Guillermo Rauch is the CEO of Vercel, a frontend-as-a-service product that was valued at $2.5b in 2021. Vercel serves customers like Uber, Notion and Zapier, and their React framework - Next.js - is used by over 500,000 developers and designers worldwide. Guillermo started his first company at age 11 in Buenos Aires and moved to San Francisco at age 18. In 2013, he sold his company Cloudup to Automattic (the company behind WordPress), and in 2015 he founded Vercel. — In today's episode we discuss: Guillermo's fascinating path into tech Learnings from building Cloudup and selling the company to Automattic (the company behind WordPress) Vercel's origin story and path to product market fit How to make an open source business successful Vercel's unique philosophy on developer experience Insights and predictions on the future of AI — Referenced: Algolia: https://www.algolia.com/ Apache Zookeeper: https://zookeeper.apache.org/ Apache Kafka: https://kafka.apache.org/ AWS: https://www.aws.training/ C++: https://www.techtarget.com/searchdatamanagement/definition/C Clerk: https://clerk-tech.com/ Cloudup: https://cloudup.com/ Commerce Cloud: https://www.salesforce.com/products/commerce/ Contentful: https://www.contentful.com/ Debian: https://www.debian.org/ Fintool: https://www.fintool.com/ Figma: https://www.figma.com/ GitLab: https://about.gitlab.com/ IRC: https://en.wikipedia.org/wiki/Internet_Relay_Chat KDE: https://kde.org/ Linux: https://en.wikipedia.org/wiki/Linux Mozilla: https://www.mozilla.org MooTools (UI library): https://mootools.net/ Next.js: https://nextjs.org/ React Native: https://reactnative.dev/ Red Hat: https://www.redhat.com/ Redpanda: https://redpanda.com/ Resend: https://resend.com/ Rust: https://www.rust-lang.org/ Salesforce: https://www.salesforce.com Servo: https://servo.org/ Shopify: https://www.shopify.com/ Socket.io: https://socket.io/ Symphony: https://symphony.com/ Trilio: https://trilio.io/ Twilio: https://www.twilio.com Vercel: https://vercel.com/ V0.dev: https://v0.dev/ — Where to find Guillermo: Twitter/x: https://twitter.com/rauchg LinkedIn: https://www.linkedin.com/in/rauchg/ Personal website: https://rauchg.com/ — Where to find Todd Jackson: Twitter: https://twitter.com/tjack LinkedIn: https://www.linkedin.com/in/toddj0 — Where to find First Round Capital: Website: https://firstround.com/ First Round Review: https://review.firstround.com/ Twitter: https://twitter.com/firstround Youtube: https://www.youtube.com/@FirstRoundCapital This podcast on all platforms: https://review.firstround.com/podcast — Timestamps: (02:35) Becoming an “internet celebrity” at age 11 (08:30) Guillermo's first company: Cloudup (11:09) Biggest learnings from Cloudup and WordPress (15:06) The insights behind starting Vercel (17:11) Sources of validation for Vercel (20:29) How Vercel formed its V1 product (23:25) Navigating the early reactions from competitors and users (25:58) The paradox of developers and how it impacted Next.js (31:20) Advice on finding product market fit (34:48) The forces behind a trend towards "Front-end Cloud” (38:35) Why people now pay so much attention to the front-end (40:06) How to make an open source business successful (44:54) Insights on product positioning and category creation (48:52) Vercel's journey through becoming multi-product (51:44) Guillermo's take on the future of AI (53:43) Heuristics for building better product experiences (55:49) AI insights from Vercel's customers (57:37) How AI might change engineering in the next 10-20 years (62:43) Guillermo's favorite advice (65:45) Guillermo's advice to himself of 10 years ago

Matthew has loved technology since his first Commodore 64, and that passion remains to this day. His days have me integrating enterprise platforms with Octopus, writing guides and books for platforms like Kubernetes, blogging, and training my colleagues, testing bleeding edge open source projects, and contributing to various blogs.   Matthew is a 5-star published author and has created solutions that Red Hat felt were worthy of being submitted for a patent. CEOs endorse his development skills.   Although he calls himself a developer, Matthew is quite comfortable administering a Linux server, managing a MySQL database, deploying infrastructure with Ansible, reconfiguring a firewall, or just doing what needs to be done to get the job finished.   To ensure that he is learning the industry's best practices, Matthew pushes himself to gain certification in technologies that he relies on, with Oracle proudly telling him “You are among the elite 1% of certified Java professionals who have gone on to achieve the Java Enterprise Architect certification.”   Topics of Discussion: [3:36] Mike talks about some high points in his varied career. [6:33] What is platform engineering? [8:22] Most jobs fall into the category of DevOps. [10:58] The platform team is looking inward and trying to scale up the team members as opposed to scaling up the technology. [13:08] Has Matt seen any of the job boards coming out with how we need to hire a platform engineering director or platform engineering analyst? [15:08] What does Matt's typical work day and work week look like? [17:02] Guiding customers into creating useful solutions in their own teams. [18:17] Have we figured out the difference between platform engineering and DevOps? [20:05] “Needless creativity.” [23:56] The importance of consistent feedback and improvement. [25:58] Developers have a $0 budget, but an unlimited time budget. [30:55] DevOps teams need to take dependencies seriously. [31:44] How we can standardize and automate some of those internal processes through platform engineering. [35:06] Dependabot.   Mentioned in this Episode: Clear Measure Way Architect Forum Software Engineer Forum Programming with Palermo — New Video Podcast! Email us at programming@palermo.net. Clear Measure, Inc. (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! Jeffrey Palermo's Twitter — Follow to stay informed about future events! Matt Casperson LinkedIn Octopus Enterprise Deployment Patterns Github.com/OctopusSolutionsEngineering/EnterprisePatternsReferenceImplementation/tree/main   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Curious about edge computing? Want to understand why it's the next big thing in the world of IT? My conversation with Mark Swinson, an enterprise IT Automation Sales Specialist at Red Hat, might just be the discussion you're looking for.Mark takes us on a deep dive into the world of edge computing, discussing its benefits, applications, and the crucial role of open-source projects. We navigate the diverse applications of edge computing, exploring its transformative impact in sectors like retail, autonomous driving, and more. Mark also enlightens us on the significant role of AI and Kubernetes in shaping the edge computing landscape. Our conversation also touches upon the unique challenges in edge computing and why data security is paramount in this field. More on MarkMark on LinkedInResources MentionedRed Hat Connect London  7 November 2023The Age of AI - Henry Kissinger, Eric Schmidt, Daniel HuttenlocherYour Host: Actionable Futurist® & Chief Futurist Andrew GrillFor more on Andrew - what he speaks about and recent talks, please visit ActionableFuturist.com Andrew's Social ChannelsAndrew on LinkedIn@AndrewGrill on Twitter @Andrew.Grill on InstagramKeynote speeches hereAndrew's upcoming book

Today on Christopher Lochhead: Follow Your Different, we have a special episode featuring a good friend of mine, Dr. Giora Yaron. We talk about what's happening in Israel now, the realities of the situation Israel faces and what's likely to happen next. Dr. Giora Yaron is considered a legend in the startup tech world. He's known as one of the key players in creating the tech startup VC ecosystem. He started his career as a Senior Executive in National Semiconductor in the United States. And subsequent to that he's founded, co-founded, and/or been the chairman of more than 25 Deep-tech startups. He's also the former chairman of Tel Aviv University. Dr. Yaron is also a decorated Israeli Defense Forces Combat officer. And today, he serves as a strategic adviser to the Israeli Ministry of Defense. No matter what you think about this war, no matter how much you think you might know, there's a lot to learn in this riveting captivating, in depth, no BS conversation with a living Israeli legend. Also, it's important to note this episode was recorded on October 26 2023. You're listening to Christopher Lochhead: Follow Your Different. We are the real dialogue podcast for people with a different mind. So get your mind in a different place, and hey ho, let's go. Dr. Giora Yaron on the current situation in Israel Christopher Lochhead and Dr. Giora Yaron discuss the situation in Israel. Dr. Yaron shares how his family was safe living far from conflict zones, although they hosted affected families initially. He mentioned the challenges faced by IDF with a significant number drafted and the delicate balance in completing the mission while saving hostages. Dr. Yaron also highlighted past incidents, comparing the current situation to previous attacks in 1973 and 2002. He expressed concerns about dealing with barbarian savages and the challenge of maintaining Israeli values while addressing the crisis. Dr. Giora Yaron on the conflict's impact on civilians The conversation then shifts to the topic of the recent conflict in Israel and its impact on civilians. Dr. Yaron discusses the strategic and moral dilemmas faced by Israel in dealing with groups like Hamas and the challenges in differentiating between combatants and civilians. He emphasizes the need to combat extremist groups aiming to establish an Islamic state and the importance of military action to achieve this. Christopher notes that many veterans, like Colin Powell, become peacemakers later in life and discussed the heroic efforts of civilians in the conflict. But Dr. Yaron responds that the situation isn't about pursuing peace but dealing with an ongoing conflict. Dr. Giora Yaron on Cultural Differences and how it affects perception in the West Dr. Yaron shares his concerns about the disconnect between Western sympathies for Palestinians and the harsh realities faced by Israelis due to terrorist attacks. He emphasizes the need for a practical approach and shared personal experiences, such as Mellanox's tragic incident, to illustrate the challenges faced in pursuing peace in the region. He further underscores the complexities of the situation and the clash between idealistic hopes for peace and the harsh realities on the ground. To hear more from Dr. Giora Yaron and the clash of ideals in Israel, download and listen to this episode. Bio Dr. Giora Yaron is the former Chairman of Tel Aviv University (Executive Council), and on the board of Amdocs (DOX). Dr. Yaron serves on the advisory board of the Israeli Ministry of Defense. He is also an active Founding Investor and Founder of a group of high-tech and med-tech companies; P-cube, (acquired by Cisco), PentaCom (acquired by Cisco), Qumranet (acquired by Redhat), Comsys (acquired by Conexant, Texas Instruments), Exanet (acquired by Dell) Hyperwise Security (acquired by Checkpoint) Qwilt, Itamar Medical, Excelero, Equalum and, Aqua Security. Dr. Yaron has been serving as board member and/or Chairman of the Boards of these com...

Red Hat/Blue Hat Talk - Two Friends Who Disagree about Trump. Episode 7   Doug Pagitt and Casey Franklin are decades-long friends, they are both faith leaders, and, they seriously disagree about Donald Trump.   Over the last year they have texted regularly about those disagreements.  They are now bringing that conversation to this livestream/podcast.   Their love for each other will be on display and so will their perspectives.   Welcome to episode 7 of “Red Hat/Blue Hat Talk

Rob Wilmoth from Red Hat joined me in the mobile studio at the 2023 SCTE Cable-Tech Expo, where we delved into numerous discussions on enterprise technology, software customization, open-source security, and innovation. Red Hat, known for its 30-year history, has been instrumental in the enterprise technology landscape. The company's ability to harden, secure, and provide […]

Welcome back to another exciting episode of Data Driven! In today's episode, we're diving into the world of artificial intelligence, as our very own Frank La Vigne takes us on a journey through his experiences at the OpenShift Commons gathering in Raleigh.From delivering a captivating demo to moderating a thought-provoking panel, Frank's agenda is packed with fascinating insights and surprises. Join us as we explore the power of open source AI, the importance of community-driven innovation, and why transparency is key in today's evolving landscape. So sit back, relax, and get ready to delve into the world of AI at OpenShift Commons Gathering. Let's get started!Show Notes[00:01:31] Newcomer excited for first OpenShift gathering to give demo, moderate panel, and interview attendees. Registration booth opening soon, located near Raleigh's main park and an IMAX.[00:04:34] Transparency, innovation, trust in OpenAI, Elon Musk's comments on openness and Red Hat's departure.[00:07:53] Excitement about hall track conversations, public vs private cloud, and upcoming discussions.

ACP was joined by The Red Hat team for an inside look at how to become a competitive candidate. Red Hat is the world's leading provider of enterprise open-source solutions, using a community-powered approach to deliver high-performing Linux, hybrid cloud, edge, and Kubernetes technologies. Red Hat continues to be a catalyst in open-source communities, helping build flexible and powerful IT infrastructure solutions. Their culture is built on the open-source principles of transparency, collaboration, and inclusion. Red Hat's Military Veterans community empowers the voices of Veterans and their allies to amplify their contributions and opportunities by harnessing their leadership and experience.Tune in to learn even more!  ACP Website: https://www.acp-usa.org/Mentor Application Link: https://www.acp-usa.org/mentorVeteran Link:  https://www.acp-usa.org/mentoring-program/veteran-applicationMilitary Spouse Application Link: https://www.acp-usa.org/spousesACP LinkedIn Account: https://www.linkedin.com/company/american-corporate-partners/mycompany/ACP Connects, LinkedIn Group: https://www.linkedin.com/groups/12259026/  Support the showSupport the show

Steam Next Fest picks! Unity gets a Red Hat, Nvidia 4080 Ti targets AI gamers, Diablo IV is Steam Deck certified, and Counter-Strike drops support for macOS.

This week, we discuss measuring developer productivity, Unity licensing backlash, and some follow-up on Wireless Emergency Alerts. Plus, thoughts on coconuts. Watch the YouTube Live Recording of Episode (https://www.youtube.com/watch?v=bQtDvRPqXFs) 436 (https://www.youtube.com/watch?v=bQtDvRPqXFs) Runner-up Titles One day an ice machine will run on RISC-V Mo Developers Mo Problems W3C my ass. That's almost an aggressive blue. Wait. Do I live in an office complex? You pay the same Quarantine Quarters Maybe I have too much mindlessness Out of my way Costco, I'm going direct. Candy Corn Have you tried a bubble-sort? Omerta for developers Understand what you're measuring, or you'll just get measurements. KCNA23VMWEO20 Just make the bed Rundown Developer Productivity McKinsey Developer Productivity Review (https://dannorth.net/mckinsey-review/) Even longer rebuttal (https://newsletter.pragmaticengineer.com/p/measuring-developer-productivity). The only people who don't like metrics are the people being measured, or, developer productivity metrics quicksand (https://newsletter.cote.io/p/the-only-people-who-dont-like-metrics) Reports Kubernetes at Scale: Challenges, Priorities, Adoption Patterns, and Solutions (https://tanzu.vmware.com/content/analyst-reports/kubernetes-at-scale) Announcing the 2023 State of DevOps Report (https://cloud.google.com/blog/products/devops-sre/announcing-the-2023-state-of-devops-report) John Riccitiello is out at Unity, effective immediately (https://www.theverge.com/2023/10/9/23910441/unity-ceo-president-john-riccitiello-out-retire) Wireless Emergency Alerts (WEA) (https://www.fcc.gov/consumers/guides/wireless-emergency-alerts-wea) Relevant to your Interests Why companies still want in-house data centres (https://www.economist.com/business/2023/10/05/why-companies-still-want-in-house-data-centres) Understanding the Cyber Resilience Act: What Everyone involved in Open Source Development Should Know (https://www.linuxfoundation.org/blog/understanding-the-cyber-resilience-act) PayPal faces new antitrust lawsuit claiming it unfairly stifles competition with Stripe, Shopify and more (https://techcrunch.com/2023/10/05/paypal-faces-new-antitrust-lawsuit-claiming-it-unfairly-stifles-competition-with-stripe-shopify-and-more/) DuckDB Labs puts limit on free support, rules out VC funding (https://www.theregister.com/2023/10/05/duckdb_labs_puts_limit_on_vc_funds/) Genetics firm 23andMe says user data stolen in credential stuffing attack (https://www.bleepingcomputer.com/news/security/genetics-firm-23andme-says-user-data-stolen-in-credential-stuffing-attack/) Hackers are selling the data of millions lifted from 23andMe's genetic database (https://www.theverge.com/2023/10/7/23907330/23andme-leak-hackers-selling-user-dna-data) Datadog stumbles as Bank of America downgrades, citing recent checks (https://seekingalpha.com/news/4019064-datadog-stumbles-bank-of-america-downgrades-recent-checks) IBM CEO in damage control mode after AI job loss comments (https://www.itpro.com/technology/artificial-intelligence/ibm-ceo-in-damage-control-mode-after-ai-job-loss-comments) Google announces new generative AI search capabilities for doctors (https://www.cnbc.com/2023/10/09/google-announces-new-generative-ai-search-capabilities-for-doctors-.html) Be an Open Source Absolutist! (https://twitter.com/ID_AA_Carmack/status/1711737838889242880) Google Cloud mitigated largest DDoS attack, peaking above 398 million rps (https://cloud.google.com/blog/products/identity-security/google-cloud-mitigated-largest-ddos-attack-peaking-above-398-million-rps/) Nonsense Ice Is Not Necessary. So Why Do Hotels Provide It for Free? (https://slate.com/human-interest/2015/08/why-are-there-ice-machines-in-so-many-hotels.html) Listener Feedback Biogen hiring Senior Manager, Solution Architecture, Global Commercial and Medical IT (hybrid work) (https://jobs.smartrecruiters.com/Biogen/743999935046183-senior-manager-solution-architecture-global-commercial-and-medical-it-hybrid-work-) RedHat hiring Principal Product Marketing Manager, OpenShift in Remote (https://us-redhat.icims.com/jobs/100399/principal-product-marketing-manager%2c-openshift/job?mode=view&mobile=true&width=428&height=739&bga=true&needsRedirect=false&jan1offset=-300&jun1offset=-240) Conferences Oct 17th SpringOne Tour Online (free!) (https://springonetour.io/?utm_source=cote&utm_campaign=devrel&utm_medium=newsletter&utm_content=newsletterUpcoming) - Coté talking about platform engineering. Oct 17th and 24th **talk series (yes, a “webinar”): Building a Path to Production: A Guide for Managers and Leaders in Platform Engineering (https://series.brighttalk.com/series/6011/?utm_source=cote&utm_campaign=devrel&utm_medium=newsletter&utm_content=newsletterUpcoming). Coté's doing this. Nov 6-9, 2023, KubeCon NA (https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/), SDT's a sponsor, Matt's there. Use this VMware discount code for 20% off: KCNA23VMWEO20. Nov 6-9, 2023 VMware Explore Barcelona (https://www.vmware.com/explore/eu.html), Coté's attending Nov 7–8, 2023 RISC-V Summit | Linux Foundation Events (https://events.linuxfoundation.org/riscv-summit/) Jan 29, 2024 to Feb 1, 2024 That Conference Texas (https://that.us/events/tx/2024/schedule/) If you want your conference mentioned, let's talk media sponsorships. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us: Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk), Threads (https://www.threads.net/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: macOS Sonoma (https://www.apple.com/macos/sonoma/) Matt: HomeSeek (https://www.homeseekgame.com/) - post apocalyptic SimCity Coté: Menewood (https://www.goodreads.com/en/book/show/60784675), finally out! Over 700 subscribers for my newsletter - are you subscribed (https://newsletter.cote.io)?! Photo Credits Header (https://unsplash.com/photos/dFoOWRT97_0) Artwork (https://unsplash.com/photos/umixjcVd0Ws)

Frank Calderoni, CEO of Velocity Global Frank has been an executive at some of the most high-profile tech companies in the world, including IBM, SanDisk, QLogic, Cisco, Red Hat, Anaplan and Velocity Global. We get the inside track into his career progression, starting from IBM and its legendary internship and leadership development programs. He shares why he decided to go into tech instead of working at one of the Big Four accounting firms and what it was like working all around the world. Frank then gives us a good look into what it's like being a c-suite executive, CEO and board member of some public companies. We explore whether the adage "it's lonely at the top" rings true, which promotions were most challenging to earn in his career, and the most valuable skills he credits to his success today. You don't want to miss Frank's master class on c-suite roles, people management and leadership development. http://blindap.onelink.me/ttCg/9emoyqui

Brian Proffitt is the Senior Manager of Community Outreach at Red Hat's OSPO. In this episode, we connect at the Open Source Summit EU to discuss how Brian uses events to drive both lead generation and community-building efforts. Throughout our conversation, Brian describes how measuring the ROI of an event can be tricky and why it's important to look at events as a long game strategy. We also discuss why events provide some of the most valuable feedback when testing your positioning and messaging, and what can be done to increase the odds that your events are successful and produce good outcomes.Highlights: I introduce Brian, who is the Senior Manager of Community Outreach at Red Hat's OSPO as he joins me at the Open Source Summit EU (00:28) How Brian categorizes the different types of events he attends and hosts (01:55) The primary metric and objective for lead gen events, and what can be done to increase the odds that your lead gen events bear fruit (05:18) Why events are such a valuable part of testing your positioning and messaging (09:14) Brian delves into the value of community events and what the ROI for those looks like (12:50) The strategy Brian employs for getting the most out of community events when ROI can be difficult to measure (15:40) Brian shares why he feels that events are more of a long game strategy (23:24) The advice that Brian would give to an open-source founder or start-up that is looking to get the most out of their events strategy (25:28) The best ways to learn more and connect with Brian (31:34) Links:Brian LinkedIn: https://www.linkedin.com/in/brianproffitt/ Twitter: https://twitter.com/TheTechScribe Company: https://www.redhat.com/en/blog/channel/red-hat-open-source-program-office

Day 11 of 31 Days of Halloween//Have you been tempted to answer the call of the void?//I bet you have...//This episode was brought to you by our newest Patreon Members and their generosity. Today we'd like to thank: Kiki Weed, Sheri Mos, AlicenWrites, Cat Holtz, and Margaret Terrill.//If you'd like to join them visit patreon.com/pulpaudioEdited By: Cole WeaversDirected by Cole WeaversWritten By: Ester Ellis//This episode featured:Ester Ellis as MyselfFor more work by Ester Ellis, check out The Goblet Wire Podcast wherever you listen to podcasts, or visit:https://thegobletwire.carrd.co///You can subscribe to this podcast using your podcast software of choice, or by visiting our Patreon for additional episodes and content//Marketed and Distributed By Rusty Quill Network Hosted on Acast. See acast.com/privacy for more information.

This episode is sponsored by Netsuite by Oracle, the number one cloud financial system, streamlining accounting, financial management, inventory, HR, and more. Download NetSuite's popular KPI Checklist, designed to give you consistently excellent performance - absolutely free at NetSuite.com/EYEONAI   On episode #144 of Eye on AI, Craig Smith sits down with Matt Hicks, President and CEO of Red Hat, a leading provider of enterprise open source software solutions. In this episode, Matt takes us through the evolution of Linux and the rise of the open source models. We explore how Red Hat's long-term support and predictable life cycles have empowered companies to embrace Linux. Additionally, we delve into the transformative potential of deploying open source software alongside proprietary solutions and examine the challenges and opportunities that lie ahead for open source in the realm of generative AI. To wrap things up,as we discuss the importance of efficiency, cost constraints, and specialized models for businesses, all while navigating the ongoing debate on general-purpose AI and the risks and rewards it brings.    Craig Smith Twitter: https://twitter.com/craigss Eye on A.I. Twitter: https://twitter.com/EyeOn_AI   (00:00) Preview,Introduction & Netsuite (03:11) The Role of OS in Tech (08:06) Red Hat, Open Source, and Generative AI (16:12) Large Language Models and Building Foundations (24:18) AI: Commoditization, Frontier, & Hardware Predictions (32:24) Open Source AI a Dual-Edged Sword? (40:30) Regulatory Aspects & Red Hat's Future Directions (48:36) IBM's Acquisition of Red Hat (55:21) Outro & Netsuite by Oracle

Jeff Geerling, Owner of Midwestern Mac, joins Corey on Screaming in the Cloud to discuss the importance of storytelling, problem-solving, and community in the world of cloud. Jeff shares how and why he creates content that can appeal to anybody, rather than focusing solely on the technical qualifications of his audience, and how that strategy has paid off for him. Corey and Jeff also discuss the impact of leading with storytelling as opposed to features in product launches, and what's been going on in the Raspberry Pi space recently. Jeff also expresses the impact that community has on open-source companies, and reveals his take on the latest moves from Red Hat and Hashicorp. About JeffJeff is a father, author, developer, and maker. He is sometimes called "an inflammatory enigma".Links Referenced:Personal webpage: https://jeffgeerling.com/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. A bit off the beaten path of the usual cloud-focused content on this show, today I'm speaking with Jeff Geerling, YouTuber, author, content creator, enigma, and oh, so much more. Jeff, thanks for joining me.Jeff: Thanks for having me, Corey.Corey: So, it's hard to figure out where you start versus where you stop, but I do know that as I've been exploring a lot of building up my own home lab stuff, suddenly you are right at the top of every Google search that I wind up conducting. I was building my own Kubernete on top of a Turing Pi 2, and sure enough, your teardown was the first thing that I found that, to be direct, was well-documented, and made it understandable. And that's not the first time this year that that's happened to me. What do you do exactly?Jeff: I mean, I do everything. And I started off doing web design and then I figured that design is very, I don't know, once it started transitioning to everything being JavaScript, that was not my cup of tea. So, I got into back-end work, databases, and then I realized to make that stuff work well, you got to know the infrastructure. So, I got into that stuff. And then I realized, like, my home lab is a great place to experiment on this, so I got into Raspberry Pis, low-power computing efficiency, building your own home lab, all that kind of stuff.So, all along the way, with everything I do, I always, like, document everything like crazy. That's something my dad taught me. He's an engineer in radio. And he actually hired me for my first job, he had me write an IT operations manual for the Radio Group in St. Louis. And from that point forward, that's—I always start with documentation. So, I think that was probably what really triggered that whole series. It happens to me too; I search for something, I find my old articles or my own old projects on GitHub or blog posts because I just put everything out there.Corey: I was about to ask, years ago, I was advised by Scott Hanselman to—the third time I find myself explaining something, write a blog post about it because it's easier to refer people back to that thing than it is for me to try and reconstruct it on the fly, and I'll drop things here and there. And the trick is, of course, making sure it doesn't sound dismissive and like, “Oh, I wrote a thing. Go read.” Instead of having a conversation with people. But as a result, I'll be Googling how to do things from time to time and come up with my own content as a result.It's at least a half-step up from looking at forums and the rest, where I realized halfway through that I was the one asking the question. Like, “Oh, well, at least this is useful for someone.” And I, for better or worse, at least have a pattern of going back and answering how I solved a thing after I get there, just because otherwise, it's someone asked the question ten years ago and never returns, like, how did you solve it? What did you do? It's good to close that loop.Jeff: Yeah, and I think over 50% of what I do, I've done before. When you're setting up a Kubernetes cluster, there's certain parts of it that you're going to do every time. So, whatever's not automated or the tricky bits, I always document those things. Anything that is not in the readme, is not in the first few steps, because that will help me and will help others. I think that sometimes that's the best success I've found on YouTube is also just sharing an experience.And I think that's what separates some of the content that really drives growth on a YouTube channel or whatever, or for an organization doing it because you bring the experience, like, I'm a new person to this Home Assistant, for instance, which I use to automate things at my house. I had problems with it and I just shared those problems in my video, and that video has, you know, hundreds of thousands of views. Whereas these other people who know way more than I could ever know about Home Assistant, they're pulling in fewer views because they just get into a tutorial and don't have that perspective of a beginner or somebody that runs into an issue and how do you solve that issue.So, like I said, I mean, I just always share that stuff. Every time that I have an issue with anything technological, I put it on GitHub somewhere. And then eventually, if it's something that I can really formulate into an outline of what I did, I put a blog post up on my blog. I still, even though I write I don't know how many words per week that goes into my YouTube videos or into my books or anything, I still write two or three blog posts a week that are often pretty heavy into technical detail.Corey: One of the challenges I've always had is figuring out who exactly I'm storytelling for when I'm putting something out there. Because there's a plethora, at least in cloud, of beginner content of, here's how to think about cloud, here's what the service does, here's why you should use it et cetera, et cetera. And that's all well and good, but often the things that I'm focusing on presuppose a certain baseline level of knowledge that you should have going into this. If you're trying to figure out the best way to get some service configured, I probably shouldn't have to spend the first half of the article talking about what AWS is, as a for instance. And I think that inherently limits the size of the potential audience that would be interested in the content, but it's also the kind of stuff that I wish was out there.Jeff: Yeah. There's two sides to that, too. One is, you can make content that appeals to anybody, even if they have no clue what you're talking about, or you can make content that appeals to the narrow audience that knows the base level of understanding you need. So, a lot of times with—especially on my YouTube channel, I'll put things in that is just irrelevant to 99% of the population, but I get so many comments, like, “I have no clue what you said or what you're doing, but this looks really cool.” Like, “This is fun or interesting.” Just because, again, it's bringing that story into it.Because really, I think on a base level, a lot of programmers especially don't understand—and infrastructure engineers are off the deep end on this—they don't understand the interpersonal nature of what makes something good or not, what makes something relatable. And trying to bring that into technical documentation a lot of times is what differentiates a project. So, one of the products I love and use and recommend everywhere and have a book on—a best-selling book—is Ansible. And one of the things that brought me into it and has brought so many people is the documentation started—it's gotten a little bit more complex over the years—but it started out as, “Here's some problems. Here's how you solve them.”Here's, you know, things that we all run into, like how do you connect to 12 servers at the same time? How do you have groups of servers? Like, it showed you all these little examples. And then if you wanted to go deeper, there was more documentation linked out of that. But it was giving you real-world scenarios and doing it in a simple way. And it used some little easter eggs and fun things that made it more interesting, but I think that that's missing from a lot of technical discussion and a lot of technical documentation out there is that playfulness, that human side, the get from Point A to Point B and here's why and here's how, but here's a little interesting way to do it instead of just here's how it's done.Corey: In that same era, I was one of the very early developers behind SaltStack, and I think one of the reasons that Ansible won in the market was that when you started looking into SaltStack, it got wrapped around its own axle talking about how it uses ZeroMQ for a full mesh between all of the systems there, as long—sorry [unintelligible 00:07:39] mesh network that all routes—not really a mesh network at all—it talks through a single controller that then talks to all of its subordinate nodes. Great. That's awesome. How do I use this to install a web server, is the question that people had. And it was so in love with its own cleverness in some ways. Ansible was always much more approachable in that respect and I can't understate just how valuable that was for someone who just wants to get the problem solved.Jeff: Yeah. I also looked at something like NixOS. It's kind of like the arch of distributions of—Corey: You must be at least this smart to use it in some respects—Jeff: Yeah, it's—Corey: —has been the every documentation I've had with that.Jeff: [laugh]. There's, like, this level of pride in what it does, that doesn't get to ‘and it solves this problem.' You can get there, but you have to work through the barrier of, like, we're so much better, or—I don't know what—it's not that. Like, it's just it doesn't feel like, “You're new to this and here's how you can solve a problem today, right now.” It's more like, “We have this golden architecture and we want you to come up to it.” And it's like, well, but I'm not ready for that. I'm just this random developer trying to solve the problem.Corey: Right. Like, they should have someone hanging out in their IRC channel and just watch for a week of who comes in and what questions do they have when they're just getting started and address those. Oh, you want to wind up just building a Nix box EC2 for development? Great, here's how you do that, and here's how to think about your workflow as you go. Instead, I found that I had to piece it together from a bunch of different blog posts and the rest and each one supposed that I had different knowledge coming into it than the others. And I felt like I was getting tangled up very easily.Jeff: Yeah, and I think it's telling that a lot of people pick up new technology through blog posts and Substack and Medium and whatever [Tedium 00:09:19], all these different platforms because it's somebody that's solving a problem and relating that problem, and then you have the same problem. A lot of times in the documentation, they don't take that approach. They're more like, here's all our features and here's how to use each feature, but they don't take a problem-based approach. And again, I'm harping on Ansible here with how good the documentation was, but it took that approach is you have a bunch of servers, you want to manage them, you want to install stuff on them, and all the examples flowed from that. And then you could get deeper into the direct documentation of how things worked.As a polar opposite of that, in a community that I'm very much involved in still—well, not as much as I used to be—is Drupal. Their documentation was great for developers but not so great for beginners and that was always—it still is a difficulty in that community. And I think it's a difficulty in many, especially open-source communities where you're trying to build the community, get more people interested because that's where the great stuff comes from. It doesn't come from one corporation that controls it, it comes from the community of users who are passionate about it. And it's also tough because for something like Drupal, it gets more complex over time and the complexity kind of kills off the initial ability to think, like, wow, this is a great little thing and I can get into it and start using it.And a similar thing is happening with Ansible, I think. We were at when I got started, there were a couple hundred modules. Now there's, like, 4000 modules, or I don't know how many modules, and there's all these collections, and there's namespaces now, all these things that feel like Java overhead type things leaking into it. And that diminishes that ability for me to see, like, oh, this is my simple tool that solving these problems.Corey: I think that that is a lost art in the storytelling side of even cloud marketing, where they're so wrapped around how they do what they do that they forget, customers don't care. Customers care very much about their problem that they're trying to solve. If you have an answer for solving that problem, they're very interested. Otherwise, they do not care. That seems to be a missing gap.Jeff: I think, like, especially for AWS, Google, Azure cloud platforms, when they build their new services, sometimes you're, like, “And that's for who?” For some things, it's so specialized, like, Snowmobile from Amazon, like, there's only a couple customers on the planet in a given year that needs something like that. But it's a cool story, so it's great to put that into your presentation. But some other things, like, especially nowadays with AI, seems like everybody's throwing tons of AI stuff—spaghetti—at the wall, seeing what will stick and then that's how they're doing it. But that really muddies up everything.If you have a clear vision, like with Apple, they just had their presentation on the new iPhone and the new neural engine and stuff, they talk about, “We see your heart patterns and we tell you when your heart is having problems.” They don't talk about their AI features or anything. I think that leading with that story and saying, like, here's how we use this, here's how customers can build off of it, those stories are the ones that are impactful and make people remember, like, oh Apple is the company that saves people's lives by making watches that track their heart. People don't think that about Google, even though they might have the same feature. Google says we have all these 75 sensors in our thing and we have this great platform and Android and all that. But they don't lead with the story.And that's something where I think corporate Apple is better than some of the other organizations, no matter what the technology is. But I get that feeling a lot when I'm watching launches from Amazon and Google and all their big presentations. It seems like they're tech-heavy and they're driven by, like, “What could we do with this? What could you do with this new platform that we're building,” but not, “And this is what we did with this other platform,” kind of building up through that route.Corey: Something I've been meaning to ask someone who knows for a while, and you are very clearly one of those people, I spend a lot of time focusing on controlling cloud costs and I used to think that Managed NAT Gateways were very expensive. And then I saw the current going rates for Raspberries Pi. And that has been a whole new level of wild. I mean, you mentioned a few minutes ago that you use Home Assistant. I do too.But I was contrasting the price between a late model, Raspberry Pi 4—late model; it's three years old if this point of memory serves, maybe four—versus a used small form factor PC from HP, and the second was less expensive and far more capable. Yeah it drags a bit more power and it's a little bit larger on the shelf, but it was basically no contest. What has been going on in that space?Jeff: I think one of the big things is we're at a generational improvement with those small form-factor little, like, tiny-size almost [nook-sized 00:13:59] PCs that were used all over the place in corporate environments. I still—like every doctor's office you go to, every hospital, they have, like, a thousand of these things. So, every two or three or four years, however long it is on their contract, they just pop all those out the door and then you get an E-waste company that picks up a thousand of these boxes and they got to offload them. So, the nice thing is that it seems like a year or two ago, that really started accelerating to the point where the price was driven down below 100 bucks for a fully built-out little x86 Mini PC. Sure, it's, you know, like you said, a few generations old and it pulls a little bit more power, usually six to eight watts at least, versus a Raspberry Pi at two to three watts, but especially for those of us in the US, electricity is not that expensive so adding two or three watts to your budget for a home lab computer is not that bad.The other part of that is, for the past two-and-a-half years because of the global chip shortages and because of the decisions that Raspberry Pi made, there were so few Raspberry Pis available that their prices shot up through the roof if you wanted to get one in any timely fashion. So, that finally is clearing up, although I went to the Micro Center near me yesterday, and they said that they have not had stock of Raspberry Pi 4s for, like, two months now. So, they're coming, but they're not distributed evenly everywhere. And still, the best answer, especially if you're going to run a lot of things on it, is probably to buy one of those little mini PCs if you're starting out a home lab.Or there's some other content creators who build little Kubernetes clusters with multiple mini PCs. Three of those stack up pretty nicely and they're still super quiet. I think they're great for home labs. I have two of them over on my shelf that I'm using for testing and one of them is actually in my rack. And I have another one on my desk here that I'm trying to set up for a five gigabit home router since I finally got fiber internet after years with cable and I'm still stuck on my old gigabit router.Corey: Yeah, I wound up switching to a Protectli, I think is what it's called for—it's one of those things I've installed pfSense on. Which, I'm an old FreeBSD hand and I haven't kept up with it, but that's okay. It feels like going back in time ten years, in some respects—Jeff: [laugh].Corey: —so all right. And I have a few others here and there for various things that I want locally. But invariably, I've had the WiFi controller; I've migrated that off. That lives on an EC2 box in Ohio now. And I do wind up embracing cloud services when I don't want it to go down and be consistently available, but for small stuff locally, I mean, I have an antenna on the roof doing an ADS-B receiver dance that's plugged into a Pi Zero.I have some backlogged stuff on this, but they've gotten expensive as alternatives have dropped in price significantly. But what I'm finding as I'm getting more into 3D printing and a lot of hobbyist maker tools out there, everything is built with the Raspberry Pi in mind; it has the mindshare. And yeah, I can get something with similar specs that are equivalent, but then I've got to do a whole bunch of other stuff as soon as it gets into controlling hardware via GPIO pins or whatnot. And I have to think about it very differently.Jeff: Yeah, and that's the tough thing. And that's the reason why Raspberry Pis, even though they're three years old, even though they're hard to get, they still are fetching—on the used market—way more than the original MSRP. It's just crazy. But the reason for that is the Raspberry Pi organization. And there's two: there's the Raspberry Pi Foundation that's goals are to increase educational computing and accessibility for computers for kids and learning and all that, then there's the Raspberry Pi trading company that makes the Raspberry Pis.The Trading Company has engineers who sit there 24/7 working on the software, working on the kernel drivers, working on hardware bugs, listening to people on the forums and in GitHub and everywhere, and they're all English-speaking people there—they're over in the UK—and they manufacture their own boards. So, there's a lot of things on top of that, even though they're using some silicons of Broadcom chips that are a little bit locked down and not completely open-source like some other chips might be, they're a phone number you could call if you need the support or there's a forum that has activity that you can get help in and their software that's supported. And there's a newer Linux kernel and the kernel is updated all the time. So, all those advantages mean you get a little package that will work, it'll sip two watts of power, sitting 24/7. It's reliable hardware.There's so many people that use it that it's so well tested that almost any problem you could ever run into, someone else has and there's a blog post or a forum post talking about it. And even though the hardware is not super powerful—it's three years old—you can add on a Coral TPU and do face recognition and object recognition. And throw in Frigate for Home Assistant to get notifications on your phone when your mom walks up to the door. There's so many things you can do with them and they're so flexible that they're still so valuable. I think that they really knocked it out of the park with that model, the Raspberry Pi 4, and the compute module 4, which is still impossible to get. I have not been able to buy one for two years now. Luckily, I bought 12 two-and-a-half years ago [laugh] otherwise I would be running out for all my projects that I do.Corey: Yeah. I got two at the moment and two empty slots in the Turing Pi 2, which I'll care more about if I can actually get the thing up and booted. But it presupposes you have a Windows computer or otherwise, ehh, watch this space; more coming. Great. Like, do I build a virtual machine on top of something else? It leads down the path super quickly of places I thought I'd escaped from.Jeff: Yeah, you know, outside of the Pi realm, that's the state of the communities. It's a lot of, like, figuring out your own things. I did a project—I don't know if you've heard of Mr. Beast—but we did a project for him that involves a hundred single-board computers. We couldn't find Raspberry Pi's so we had to use a different single-board computer that was available.And so, I bought an older one thinking, oh, this is, like, three or four years old—it's older than the Pi 4—and there must be enough support now. But still, there's, like, little rough edges everywhere I went and we ended up making them work, but it took us probably an extra 30 to 40 hours of development work to get those things running the same way as a Raspberry Pi. And that's just the way of things. There's so much opportunity.If one of these Chinese manufacturers that makes most of these things, if one of them decided, you know what? We're going to throw tons of money into building support for these things, get some English-speaking members of these forums to build up the community, all that stuff, I think that they could have a shot at Raspberry Pi's giant portion of the market. But so far, I haven't really seen that happen. So far, they're spamming hardware. And it's like, the hardware is awesome. These chips are great if you know how to deal with them and how to get the software running and how to deal with Linux issues, but if you don't, then they're not great because you might not even get the thing to boot.Corey: I want to harken back to something you said a minute ago, where there's value in having a community around something, where you can see everyone else has already encountered a problem like this. I think that folks who weren't around for the rise of cloud have no real insight into how difficult it used to be just getting servers into racks and everything up, and okay, they're identical, and seven of them are working, but that eighth one isn't for some strange reason. And you spend four hours troubleshooting what turns out to be a bad cable or something not seated properly and it's awful. Cloud got away from a lot of that nonsense. But it's important—at least to me—to not be Captain Edgecase, where if you pick some new cloud provider and Google for how to set up a load balancer and no one's done it before you, that's not great. Whereas if I'm googling now in the AWS realm and no one has done, the thing I'm trying to do, that should be something of a cautionary flag of maybe this isn't how most people go about approaching production. Really think twice about this.Jeff: Yep. Yeah, we ran into that on a project I was working on was using Magento—which I don't know if anybody listening uses Magento, but it's not fun—and we ran into some things where it's like, “We're doing this, and it says that they do this on their official supported platform, but I don't know how they are because the code just doesn't exist here.” So, we ran into some weird edge cases on AWS with some massive infrastructure for the databases, and I ran into scaling issues. But even there, there were forum posts in AWS here and there that had little nuggets that helped us to figure out a way to get around it. And like you say, that is a massive advantage for AWS.And we ran into an issue with, we were one of the first customers trying out the new Lambda functions for RDS—or I don't remember exactly what it was called initially—but we ended up not using that. But we ran into some of these issues and figured out we were the first customer running into this weird scaling thing when we had a certain size of database trying to use it with these Lambda calls. And eventually, they got those things solved, but with AWS, they've seen so many things and some other cloud providers haven't seen these things. So, when you have certain types of applications that need to scale in certain ways, that is so valuable and the community of users, the ability to pull from that community when you need to hire somebody in an emergency, like, we need somebody to help us get this project done and we're having this issue, you can find somebody that is, like, okay, I know how to get you from Point A to Point B and get this project out the door. You can't do that on certain platforms.And open-source projects, too. We've always had that problem in Drupal. The amount of developers who are deep into Drupal to help with the hard problems is not vast, so the ones who can do that stuff, they're all hired off and paid a handsome sum. And if you have those kinds of problems you realize, I either going to need to pay a ton of money or we're just going to have to not do that thing that we wanted to do. And that's tough.Corey: What I've found, sort of across the board, has been that there's a lot of, I guess, open-source community ethos that has bled into a lot of this space and I wanted to make sure that we have time to talk about this because I was incensed a while back when Red Hat decided, “Oh, you know that whole ten-year commitment on CentOS? That project that we acquired and are now basically stabbing in the face?”—disclosure. I used to be part of the CentOS project years ago when I was on network staff for the Freenode IRC network—then it was, “Oh yeah, we're just going to basically undermine our commitments to you and now you can pay us if you want to get that support there.” And that really set me off. Was nice to see you were right there as well in almost lockstep with me, pointing out that this is terrible, just as far as breaking promises you've made to customers. Has your anger cooled any? Because mine hasn't.Jeff: It has not. My temper has cooled. My anger has not. I don't think that they get it. After all the backlash that they got after that, I don't think that the VP-level folks at Red Hat understand that this is already impacting them and will impact them much more in the future because people like me and you, people who help other people build infrastructure and people who recommend operating systems and people who recommend patterns and things, we're just going to drop off using CentOS because it doesn't exist. It does exist and some other people are saying, “Oh, it's actually better to use this new CentOS, you know, Stream. Stream is amazing.” It's not. It's not the same thing. It's different. And—Corey: I used to work at a bank. That was not an option. I mean, granted at the bank for the production systems it was always [REL 00:25:18], but being able to spin up a pre-production environment without having to pay license fees on every VM. Yeah.Jeff: Yeah. And not only that, they did this announcement and framed it a certain way, and the community immediately saw. You know, I think that they're just angry about something, and whether it was a NASA contract with Rocky Linux, or whether it was something Oracle did, who knows, but it seems petty in retrospect, especially in comparison to the amount of backlash that came out of it. And I really don't think that they understand the thing that they had with that Red Hat Enterprise Linux is not a massive growth opportunity for Red Hat. It's, in some ways, a dying product in terms of compared to using cloud stuff, it doesn't matter.You could use CoreOS, you could use NixOS, and you could use anything, it doesn't really matter. For people like you and me, we just want to deploy our software. And if it's containers, it really doesn't matter. It's just the people in government or in certain organizations that have these roles that you have to use whatever FIPS and all that kind of stuff. So, it's not like it's a hyper-growth opportunity for them.CentOS was, like, the only reason why all the software, especially on the open-source side, was compatible with Red Hat because we could use CentOS and it was easy and simple. They took that—well, they tried to take that away and everybody's like, “That's—what are you doing?” Like, I posted my blog post and I think that sparked off quite a bit of consternation, to the point where there was a lot of personal stuff going on. I basically said, “I'm not supporting Red Hat Enterprise Linux for any of my work anymore.” Like, “From this point forward, it's not supported.”I'll support OpenELA, I'll support Rocky Linux or Oracle Linux or whatever because I can get free versions that I don't have to sign into a portal and get a license and download the license and integrate it with my CI work. I'm an open-source developer. I'm not going to pay for stuff or use 16 free licenses. Or I was reached out to and they said, “We'll give you more licenses. We'll give you extra.” And it's like, that's not how this works. Like, I don't have to call Debian and Ubuntu and [laugh] I don't even have to call Oracle to get licenses. I can just download their software and run it.So, you know, I don't think they understood the fact that they had that. And the bigger problem for me was the two-layer approach to destroying all the trust that the community had. First was in, I think it was 2019 when they said—we're in the middle of CentOS 8's release cycle—they said, “We're dropping CentOS 8. It's going to be Stream now.” And everybody was up in arms.And then Rocky Linux and [unintelligible 00:27:52] climbed in and gave us what we wanted: basically, CentOS. So, we're all happy and we had a status quo, and Rocky Linux 9 and [unintelligible 00:28:00] Linux nine came out after Red Hat 9, and the world was a happy place. And then they just dumped this thing on us and it's like, two major release cycles in a row, they did it again. Like, I don't know what this guy's thinking, but in one of the interviews, one of the Red Hat representatives said, “Well, we wanted to do this early in Red Hat 9's release cycle because people haven't started migrating.” It's like, well, I already did all my automation upgrades for CI to get all my stuff working in Rocky Linux 9 which was compatible with Red Hat Enterprise Linux 9. Am I not one of the people that's important to you?Like, who's important to you? Is it only the people who pay you money or is it also the people that empower your operating system to be a premier Enterprise Linux operating system? So, I don't know. You can tell. My anger has not died down. The amount of temper that I have about it has definitely diminished because I realize I'm talking at a wall a lot of times, when I'm having conversations on Twitter, private conversations and email, things like that.Corey: People come to argue; they don't come to actually have a discussion.Jeff: Yeah. I think that they just, they don't see the community aspect of it. They just see the business aspect. And the business aspect, if they want to figure out ways that they can get more people to pay them for their software, then maybe they should provide more value and not just cut off value streams. It doesn't make sense to me from a long-term business perspective.From a short term, maybe there were some clients who said, “Oh, shoot. We need this thing stable. We're going to pay for some more licenses.” But the engineers that those places are going to start making plans of, like, how do we make this not happen again. And the way to not make that happen, again is to use, maybe Ubuntu or maybe [unintelligible 00:29:38] or something. Who knows? But it's not going to be increasing our spend with Red Hat.Corey: That's what I think a lot of companies are missing when it comes to community as well, where it's not just a place to go to get support for whatever it is you're doing and it's not a place [where 00:29:57] these companies view prospective customers. There's more to it than that. There has to be a social undercurrent on this. I look at the communities I spend time in and in some of them dating back long enough, I've made lifelong significant friendships out of those places, just through talking about our lives, in addition to whatever the community is built around. You have to make space for that, and companies don't seem to fully understand that.Jeff: Yeah, I think that there's this thing that a community has to provide value and monetizable value, but I don't think that you get open-source if you think that that's what it is. I think some people in corporate open-source think that corporate open-source is a value stream opportunity. It's a funnel, it's something that is going to bring you more customers—like you say—but they don't realize that it's a community. It's like a group of people. It's friends, it's people who want to make the world a better place, it's people who want to support your company by wearing your t-shirt to conferences, people want to put on your red fedora because it's cool. Like, it's all of that. And when you lose some of that, you lose what makes your product differentiated from all the other ones on the market.Corey: That's what gets missed. I think that there's a goodwill aspect of it. People who have used the technology and understand its pitfalls are likelier to adopt it. I mean, if you tell me to get a website up and running, I am going to build an architecture that resembles what I've run before on providers that I've run on before because I know what the failure modes look like; I know how to get things up and running. If I'm in a hurry, trying to get something out the door, I'm going to choose the devil that I know, on some level.Don't piss me off as a community member and incentivize me to change that estimation the next time I've got something to build. Well, that doesn't show up on this quarter's numbers. Well, we have so little visibility into how decisions get made many companies that you'll never know that you have a detractor who's still salty about something you did five years ago and that's the reason the bank decided not to because that person called in their political favors to torpedo that deal and have a sweetheart offer from your competitor, et cetera and so on and so forth. It's hard to calculate the actual cost of alienating goodwill. But—Jeff: Yeah.Corey: I wish companies had a longer memory for these things.Jeff: Yeah. I mean, and thinking about that, like, there was also the HashiCorp incident where they kind of torpedoed all developer goodwill with their Terraform and other—Terraform especially, but also other products. Like, I probably, through my book and through my blog posts and my GitHub examples have brought in a lot of people into the HashiCorp ecosystem through Vagrant use, and through Packer and things like that. At this point, because of the way that they treated the open-source community with the license change, a guy like me is not going to be enthusiastic about it anymore and I'm going to—I already had started looking at alternatives for Vagrant because it doesn't mesh with modern infrastructure practices for local development as much, but now it's like that enthusiasm is completely gone. Like I had that goodwill, like you said earlier, and now I don't have that goodwill and I'm not going to spread that, I'm not going to advocate for them, I'm not going to wear their t-shirt [laugh], you know when I go out and about because it just doesn't feel as clean and cool and awesome to me as it did a month ago.And I don't know what the deal is. It's partly the economy, money's drying up, things like that, but I don't understand how the people at the top can't see these things. Maybe it's just their organization isn't set up to show the benefits from the engineers underneath, who I know some of these engineers are, like, “Yeah, I'm sorry. This was dumb. I still work here because I get a paycheck, but you know, I can't say anything on social media, but thank you for saying what you did on Twitter.” Or X.Corey: Yeah. It's nice being independent where you don't really have to fear the, well if I say this thing online, people might get mad at me and stop doing business with me or fire me. It's well, yeah, I mean, I would have to say something pretty controversial to drive away every client and every sponsor I've got at this point. And I don't generally have that type of failure mode when I get it wrong. I really want to thank you for taking the time to talk with me. If people want to learn more, where's the best place for them to find you?Jeff: Old school, my personal website, jeffgeerling.com. I link to everything from there, I have an About page with a link to every profile I've ever had, so check that out. It links to my books, my YouTube, all that kind of stuff.Corey: There's something to be said for picking a place to contact you that will last the rest of your career as opposed to, back in the olden days, my first email address was the one that my ISP gave me 25 years ago. I don't use that one anymore.Jeff: Yep.Corey: And having to tell everyone I corresponded with that it was changing was a pain in the butt. We'll definitely put a link to that one in the [show notes 00:34:44]. Thank you so much for taking the time to speak with me. I appreciate it.Jeff: Yeah, thanks. Thanks so much for having me.Corey: Jeff Geerling, YouTuber, author, content creator, and oh so very much more. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry comment that we will, of course, read [in action 00:35:13], just as soon as your payment of compute modules for Raspberries Pi show up in a small unmarked bag.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Here's what to expect on the podcast:Curiosity is essential in your journey to being INVINCIBLE!What is SEO? What does it stand for? What's it for?What about keywords? How do you use them?A “genuine” way to do SEO.Have you considered what you'll do if you become viral?Breaking free from everyone else's perceptions of reality.And much more! About Michelle Bassett:Michelle A. Bassett's journey is a testament to resilience and the power of self-learning. Born into poverty and spending her early years in the projects of Queens, NY, she grappled with a subpar education system, a less-than-ideal family dynamic, and, to top it all off, dyslexia. Despite her challenges, she was not only the first in her family to graduate college but also went on to earn a master's degree and postgraduate certificates.Her professional journey began with a bachelor's degree in behavior analysis in 2011, leading to a master's in internet marketing in 2013. Michelle quickly discovered that her unique blend of statistical behavioral understanding and digital marketing expertise set her apart in her field. She helped many brands thrive, even before terms like “conversion rate optimization” became mainstream. As her career evolved, she expanded her skills by earning a data science certificate from Emory University in 2017.She has worked with globally recognized companies such as Coca-Cola, IBM, RedHat, NextDoor, Snap (formerly Snapchat), Mailchimp, Best Buy, and the parent company of Burger King and Popeyes, RBI.Website: https://kitcaster.com/michelle-bassett/ Connect with Kamie Lehmann!Website: https://www.kamielehmann.com/Facebook: https://www.facebook.com/kamie.lehmann.1Instagram: https://www.instagram.com/shesinvinciblepodcast/LinkedIn: https://www.linkedin.com/in/kamie-lehmann-04683473National Domestic Violence Hotline: https://www.thehotline.org/Get your Podcast on IMDB: https://imdb.failureguy.com/submitpodcastkamieLearn more about how to minimize the emotional side effects of cancer: https://adventurefound.org/

Welcome episode 228 of the Cloud Pod podcast - where the forecast is always cloudy! This week your hosts Justin, Jonathan, Matthew and Ryan are taking a look at Magic Quadrant, Gemini AI, and GraalOS - along with all the latest news from OCI, Google, AWS, and Azure.  Titles we almost went with this week: The CloudPod wonders if Anthropic's Santa Clause will bring us everything we want in an AI Bot. The Cloud Pod recommends protection to achieve Safer Google rides the gemini rocket to AI JPB The only Copilot I need Azure, is Booze GraalOS, or what we now call ‘the noise our CFO makes when he receives the Oracle audit bills' The hosts of the Cloud pod would like to understand how to properly pronounce GraalOS Is Oracle even on the magic quadrant for cloud? RedHat Puts lipstick on the pig and calls it OpenStack A big thanks to this week's sponsor: Foghorn Consulting provides top-notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you have trouble hiring?  Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week.

I have seen Larry Roberts from Red Hat Media do presentations on Chat GPT multiple times, and when Jim let me know he was out this week, I saw it as an opportunity to bring Larry in have Larry Co-Host. He is also the co-host of the show Branded. The "Cherry on top" was School of Podcasting member Craig Vanslyke from the Live Well and Flourish show (who teaches Information Systems at Louisiana Tech University) Check out Larry's slides. JOIN THE SCHOOL OF PODCASTING Join the School of Podcasting worry-free using the coupon code " coach " and save 20%. Your podcast will have you sounding confident, sound great (buying the best equipment for your budget), and have you syndicated all over the globe. There is a 30-day worry-free money-back guarantee Go to https://www.schoolofpodcasting.com/coach Sponsor: PodcastBranding.co If you need podcast artwork, lead agents or a full website, podcastbranding.co has you covered. Mark is a podcaster in addition to being an award-winning artist. He designed the cover art for the School of Podcasting, Podcast Rodeo Show, and Ask the Podcast Coach. Find Mark at  podcastbranding.co Mugshot: Based on a True Story Podcast Ever wonder how much of those "Based on a true story" movies are real? Find out at www.basedonatruestorypodcast.com  Timeline and Topics: 00:03:25 Enter Lary Roberts  00:04:46 Prompt Engineer 00:05:00 Before Your Prompt 00:06:46 Opting Out For Security 00:08:52 Are Robots Taking Over? 00:11:15 Chat GPT Templates? 00:12:22 Does GPT Replace Other Tools? 00:14:34 Dr. Craig VanSlyke Joins 00:15:51 Larry's Podcast 00:16:03 Chat GPT As a Ranker 00:17:44 Bard Likes Craig's Show 00:18:22 Chat GPT Teaches You Chat GPT 00:20:18 What Does an error Look Like on Chat GPT 00:21:31 AI As a Consultant 00:22:20 Chat GPT and Show Notes 00:23:44 Larry's Squirrel Book 00:25:31 Is GPT Limit to 2021? 00:28:33 Thoughtspace.ai 00:31:07 MIdjourney vs Dolle 00:35:42 Can It Pull Out Websites? 00:36:53 I Craig Teaching this in College? 00:37:48 Should I Know Them All? 00:39:32 Bing and Bard 00:39:44 Favorite Plugins 00:42:36 Thanks For Your Support 00:44:43 Links to Prompts 00:45:18 The Coolest GPT Output You've Seen 00:47:39 The Story of the Red Hat 00:50:36 Where Do You Start? 00:51:24 AI Is Not New 00:53:20 An AI Musician 00:54:09 The Writer's Strike 00:56:11 Ecam Live Thoughts? 00:59:40 Podmic vs SM7B Vs SM7DB 01:01:56 RE320 - Do You Like the Way You Sound 01:03:04 Bes Travel Micorphone 01:04:16 MMMmm Barrrr.. 01:04:39 ATR2100X USBC Mentioned In This Episode Check out Larry's slides. Red Hat Media www.redhatmedia.io  Live Well and Flourish www.livewellandflourish.com  Podpage www.trypodpage.com Home Gadget Geeks www.homegadgetgeelks.com  The School of Podcasting www.schoolofpodcasting.com/coach  Become an Awesome Supporter www.askthepodcastcoach.com/awesome  Chat GPT https://chat.openai.com/  Bard https://bard.google.com/ Claud https://claude.ai/login Otter https://supportthisshow.com/otter Castmagic https://supportthisshow.com/castmagic  Capsho https://supportthisshow.com/capsho  Podmatch https://supportthisshow.com/podmatch  Rode Podmic https://supportthisshow.com/podmicusb SM7B https://supportthisshow.com/sm7b RE320 Microphone  https://supportthisshow.com/re320 Thoughtspace www.Thoughtspace.ai Shure SM7DB https://supportthisshow.com/sm7db  Shure SM58 https://amzn.to/3LQEkEr (aff) Every week Dave Jackson from the School of Podcasting and Jim Collison from the Average Guy Network answer your podcast questions. This episode 455 is part of the Power of Podcasting Network. As an Amazon Associate, I earn from qualifying purchases

Hablamos con la gente de de Red Hat sobre 'Red Hat Academy', una iniciativa que se asocia con instituciones educativas de todo el mundo, para ofrecer a la última generación de especialistas en IT, en especial a las mujeres.Hablamos del nuevo dispositivo de la marca Xiaomi, el Xiaomi 13T que llega al mercado colombiano.La subida de precios que se asoma en las suscripciones de Netflix. Noticia sobre la aventura sobre ruedas eléctricas de 6,500 kilómetros que lideró un equipo suizo/alemánThis show is part of the Spreaker Prime Network, if you are interested in advertising on this podcast, contact us at https://www.spreaker.com/show/4129325/advertisement

This week, we discuss paying ransom to cyberattackers, an overview of the "Infrastructure as Code" market, and remote worker productivity. Plus, Matt provides a review of the Raspberry 5 and shares his reasons for refusing to install the Global Entry Mobile App. Watch the YouTube Live Recording of Episode (https://www.youtube.com/live/6vmdE20_Eak?si=qcONahAxeLtl2Fc5) 435 (https://www.youtube.com/live/6vmdE20_Eak?si=qcONahAxeLtl2Fc5) Runner-up Titles All my takes are spicy, once I get enough caffeine We're doing this for science No, just no, Dad No exceeding expectations in that role I will do horrible things with YAML My business is my business They don't have room for purity Rundown Emergency broadcast (https://apnews.com/article/ee3a3039a5cf452a8f307c8f6f8dcbf3) not (https://apnews.com/article/ee3a3039a5cf452a8f307c8f6f8dcbf3) used by Trump (https://apnews.com/article/ee3a3039a5cf452a8f307c8f6f8dcbf3) CBP announces new (https://www.cbp.gov/newsroom/national-media-release/cbp-announces-new-global-entry-mobile-app) MGM, Caesars Cyberattack Responses Required Brutal Choices (https://www.darkreading.com/application-security/mgm-caesars-incident-responses-required-brutal-choices) Creator of Ansible ships "Jetporch" (https://github.com/jetporch/jetporch) Cloud startup Pulumi raises $41M from Madrona, NEA to grow ‘infrastructure as code' platform (https://www.geekwire.com/2023/cloud-startup-pulumi-raises-41m-from-madrona-nea-to-grow-infrastructure-as-code-platform/) Red Hat bins Bugzilla for RHEL issue tracking, jumps on Jira (https://www.theregister.com/2023/09/29/red_hat_bugzilla_jira_migration/) Work From Home Works - Marginal REVOLUTION (https://marginalrevolution.com/marginalrevolution/2023/10/work-from-home-works.html?utm_source=rss&utm_medium=rss&utm_campaign=work-from-home-works) The Raspberry Pi 5 is finally here (https://www.theverge.com/2023/9/28/23889238/raspberry-pi-5-specs-availability-pricing) Relevant to your Interests OpenAI Seeks New Valuation of Up to $90 Billion in Sale of Existing Shares (https://www.wsj.com/tech/ai/openai-seeks-new-valuation-of-up-to-90-billion-in-sale-of-existing-shares-ed6229e0) Epic Games Asks Supreme Court to Hear Apple Case (https://www.macrumors.com/2023/09/27/epic-games-supreme-court/) FCC announces plans to reinstate net neutrality (https://techcrunch.com/2023/09/26/fcc-announces-plans-to-reinstate-net-neutrality/) Mark Zuckerberg reveals Meta AI chatbot, his answer to ChatGPT (https://cointelegraph.com/news/meta-ai-ceo-mark-zuckerberg-unveil-chatbot-rayban-metaverse) Epic Games cuts around 830 jobs (https://www.theverge.com/2023/9/28/23894266/epic-games-layoffs-fortnite-unreal-engine) How Swiggy migrated its k8s workload to Graviton (https://bytes.swiggy.com/how-swiggy-migrated-its-k8s-workload-to-graviton-d2643bbc7871) Passkeys: all the news and updates around passwordless sign-on (https://www.theverge.com/2023/9/29/23895518/passkey-passwordless-login-announcements-news-updates) The potential gap (https://open.substack.com/pub/benn/p/the-potential-gap?r=2d4o&utm_medium=ios&utm_campaign=post) Apple acknowledges hot iPhone 15 Pros, says software fixes are coming (https://www.yahoo.com/news/apple-acknowledges-hot-iphone-15-215031767.html) What's next for VMware? Long-term Virtzilla-watchers opine (https://www.theregister.com/2023/10/02/vmware_broadcom_pundit_predictions/) Bill Ackman reportedly said he would 'absolutely' do a deal with X with his new SPARC funding vehicle (https://www.cnbc.com/2023/10/01/bill-ackman-would-absolutely-do-a-deal-with-x-with-his-new-sparc.html) Open source Datadog rival SigNoz lands on the cloud with $6.5M investment (https://techcrunch.com/2023/09/28/open-source-datadog-rival-signoz-lands-on-the-cloud-with-6-5m-investment/) Okta acquires a16z-backed password manager Uno to develop a personal tier (https://techcrunch.com/2023/10/04/okta-acquires-a16z-backed-password-manager-uno-to-develop-a-personal-tier/) Amazon Used Secret ‘Project Nessie' Algorithm to Raise Prices (https://www.wsj.com/business/retail/amazon-used-secret-project-nessie-algorithm-to-raise-prices-6c593706?st=9ubhqeyjqgu0b2x&reflink=mobilewebshare_permalink) Look what ChatGPT vision can do. (https://twitter.com/_borriss_/status/1707412406048063788) Voice and Video Demos with ChatGPT, How AI Could Redeem Meta's Mixed Reality Bets, OpenAI Explores Hardware (https://overcast.fm/+8XV3Zc4Pg) AI, Hardware, and Virtual Reality (https://stratechery.com/2023/ai-hardware-and-virtual-reality/) The Senate's email system melted down in the face of security test and reply-all chaos. (https://www.politico.com/minutes/congress/09-8-2023/senate-reply-all-mess/) Nonsense Costco is selling gold bars and they are selling out within a few hours (https://www.cnbc.com/2023/09/27/costco-is-selling-gold-bars-and-they-are-selling-out-within-a-few-hours.html) Costco Offers Members $29 Online Health Care Visits (https://www.bloomberg.com/news/articles/2023-09-25/costco-offers-health-care-to-members-in-deal-with-sesame-cost?cmpid=socialflow-twitter-business&utm_source=twitter&utm_content=business&utm_medium=social&utm_campaign=socialflow-organic) Conferences Oct 9th Spring Tour Amsterdam (https://connect.tanzu.vmware.com/EMEA_P7_DG_FE_Q324_Event_S1TourAmsterdam_TanzuLP-AltS1TBanner.html?utm_source=cote&utm_campaign=devrel&utm_medium=newsletter&utm_content=newsletterUpcoming) Oct 10th, 17th, 24th talk series: Building a Path to Production: A Guide for Managers and Leaders in Platform Engineering (https://series.brighttalk.com/series/6011/?utm_source=cote&utm_campaign=devrel&utm_medium=newsletter&utm_content=newsletterUpcoming) November 6-9, 2023, KubeCon NA (https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/), SDT's a sponsor, Matt's there November 6-9, 2023 VMware Explore Barcelona (https://www.vmware.com/explore/eu.html), Coté's attending Jan 29, 2024 to Feb 1, 2024 That Conference Texas (https://that.us/events/tx/2024/schedule/) If you want your conference mentioned, let's talk media sponsorships. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us: Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk), Threads (https://www.threads.net/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: Dental Monitoring (https://dentalmonitoring.com) and Anker Magsafe Battery (https://www.amazon.com/Anker-PowerCore-Magnetic-Slim-B2C/dp/B099284SRR/ref=sr_1_2_sspa?crid=3JIBPD0L930O5&keywords=anker+magsafe+charger&qid=1696440885&sprefix=anker+mag%2Caps%2C170&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&psc=1) Matt: Search Engine podcast: Wait, should I not be drinking airplane coffee? (https://podcasts.apple.com/au/podcast/wait-should-i-not-be-drinking-airplane-coffee/id1614253637?i=1000619792437) Photo Credits Header (https://unsplash.com/photos/GGewLGcQD-I)

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