Podcasts about LVM

Die Themen im heutigen Versicherungsfunk Update sind: Vergleichsportale legen deutlich zu – Maklervertrieb bleibt stabil Laut dem „Kundenmonitor e-Assekuranz 2024“ von Sirius Campus stieg die Akzeptanz von Vergleichsportalen als Abschlussweg für Versicherungen deutlich an – auf nun 39 %. Auch die Nutzung zur Information legte spürbar zu. Klassische Vertriebswege wie Banken und Vertreter verlieren hingegen weiter an Zustimmung. Der Maklervertrieb hält sich stabil bei 51 % Akzeptanz. Finanz Informatik und IBM verlängern Partnerschaft Die Finanz Informatik (FI), IT-Dienstleister der Sparkassen-Finanzgruppe, setzt ihre langjährige Zusammenarbeit mit IBM fort. Ein neuer Vertrag sichert den Einsatz modernster IBM-Technologien – darunter KI, Automatisierung und Hybrid-Cloud – für die weitere Digitalisierung und Resilienz der Sparkassen. Ziel ist eine effizientere Servicebereitstellung, mehr Cyber-Sicherheit und zukunftsfähige IT-Infrastruktur. Die Kooperation soll zudem die Umsetzung der Digital Operational Resilience Act (DORA) stärken. HDI Deutschland: Führungswechsel bei Finanzvertrieben/Pools Oliver-Alexander Elter übernimmt zum 1. Juli die Leitung des Bereichs Finanzvertriebe/Pools bei HDI Deutschland. Er folgt auf Tom Rohrbach, der das Unternehmen nach neun Jahren verlässt. Elter bringt umfangreiche Erfahrung aus dem Makler- und Kooperationsvertrieb mit und war zuletzt für den Angebotsservice Firmen Freie Berufe und die Direktbetreuung Makler verantwortlich. Plansecur überschreitet 150-Mio.-EUR-Marke in der Fonds-Vermögensverwaltung Die Finanzberatungsgruppe Plansecur hat in der Fonds-Vermögensverwaltung einen neuen Meilenstein erreicht: Der Bestand überschritt erstmals 150 Mio. EUR. Die Vermögensverwaltung erfolgt in Kooperation mit der FIL Fondsbank und der Reuss Private Bank. Auch die Depotbetreuung wächst – im Herbst 2024 lag das betreute Volumen erstmals bei über 1,5 Mrd. EUR. Der Ausbau des Segments soll weiter vorangetrieben werden. LVM lädt zum „Tag der Ausbildung“ nach Münster Am 24. Mai veranstaltet die LVM Versicherung erneut ihren „Tag der Ausbildung“ am LVM-Campus in Münster. Jugendliche und Eltern erhalten Einblicke in Ausbildungsberufe, duale Studiengänge und die Arbeitswelt in der LVM-Zentrale. Neben Führungen, Bewerbungstipps und einem Escape Game rund um Versicherungsfälle stehen aktuelle Azubis und Ausbilder Rede und Antwort. Eine Anmeldung ist erforderlich: lvm.de/tag-der-ausbildung BdV warnt: Kaskoschutz bei E-Autos oft lückenhaft Wer ein E-Auto fährt, sollte die Kaskoversicherung sorgfältig auswählen – darauf weist der Bund der Versicherten (BdV) hin. Besonders der Akku kann im Schadenfall hohe Kosten verursachen. Laut BdV-Expertin Bianka Bobell ist eine All-Risk-Deckung ratsam, die auch Tierbiss- und Kurzschlussfolgeschäden bis mindestens 20.000 EUR abdeckt. Ebenso wichtig: Neuwertentschädigung, Entsorgungskosten bei Totalschaden und Pannenhilfe bei leerem Akku. Auch Wallboxen sollten gegen Schäden und Diebstahl mitversichert sein. Die Leistungen variieren stark – ein Blick ins Kleingedruckte lohnt sich. Ein kostenloses Infoblatt hilft beim Tarifvergleich.

Die Themen im heutigen Versicherungsfunk Update sind: Check24: EuGH weist Klage der Huk-Coburg zurück Der Versicherer Huk-Coburg ist mit einer Klage gegen Check24 vor dem Europäischen Gerichtshof vorerst gescheitert. Die Bewertungsnoten auf dem Vergleichsportal seien keine unzulässige Werbung, so das Urteil. Das gilt zumindest, solange das Vergleichsportal nicht als direkter Wettbewerber der Versicherungsunternehmen auftritt. Mehr dazu hier >>> Talanx erhöht Dividende Die virtuelle Hauptversammlung der Talanx AG hat einer deutlichen Dividendenerhöhung zugestimmt: Aktionäre erhalten künftig zwei Euro siebzig je Aktie – ein Plus von fünfunddreißig Cent. Für das Jahr zwanzig vierundzwanzig verzeichnete der Konzern ein Ergebnisplus von fünfundzwanzig Prozent auf knapp zwei Milliarden Euro. Mit sechshundertvier Millionen Euro startet Talanx auch im ersten Quartal robust ins neue Geschäftsjahr. Bis zum Jahr zwanzig siebenundzwanzig soll die Dividende weiter auf vier Euro steigen. Solvenzquoten nach Neuberechnung rückläufig – Basiswerte bleiben stabil Die Bundesanstalt für Finanzdienstleistungsaufsicht veranlasste im Jahr zwanzig vierundzwanzig eine Neuberechnung der Übergangsmaßnahmen nach Solvency II. Das führte bei vielen Lebensversicherern zu teils drastisch gesunkenen SCR-Bedeckungsquoten – im Branchenschnitt von sechshundertdreiundsechzig auf rund dreihundertvierzig Prozent. Ohne Übergangshilfen blieben die Solvenzquoten mit dreihundertneun Prozent dagegen weitgehend stabil. Besonders stark aufgestellt: LV 1871, WGV und LVM. Drei Lebensversicherer verfehlten die Einhundert-Prozent-Marke ohne Hilfsmaßnahmen. MRH Trowe beteiligt sich an Debt Advisory Partners MRH Trowe erweitert mit der Beteiligung an der Debt Advisory Partners GmbH sein Geschäftsfeld Finance. Die strategische Partnerschaft bringt mittelständischen Unternehmen und Private-Equity-Investoren Zugang zu maßgeschneiderten Finanzierungslösungen – von Kapitalbeschaffung über Unternehmensübernahmen bis Restrukturierung. Kunden profitieren von einem integrierten Beratungsansatz für Finanzierung und Risikomanagement. DEVK-Umfrage: Mehrheit für beitragsabhängige Hundetarife nach Rasse Laut einer aktuellen Civey-Umfrage im Auftrag der DEVK sprechen sich zweiundfünfzig Prozent der Hundehalter für eine risikobasierte Beitragsgestaltung nach Hunderasse aus. Die DEVK führt dafür vier Risikoklassen ein – mit Schutz auch für schwer versicherbare Tiere. Ergänzt wird das Angebot um Auslandsschutz, Leistungen bei Entlaufen und psychologische Hilfe im Trauerfall. Wechsel in der Geschäftsführung bei Doktor Ihlas GmbH: Thomas Lindner rückt auf Die Doktor Ihlas GmbH hat mit Thomas Lindner einen erfahrenen Experten aus der Industrieversicherung in die Geschäftsleitung berufen. Der Rechtsanwalt und Spezialist für Financial Lines wird künftig als Co-Geschäftsführer neben Gründer Doktor Horst Ihlas agieren. Das Unternehmen gehört zur Summitas Gruppe.

Die Themen im heutigen Versicherungsfunk Update sind: WIFO veröffentlicht Übersicht zu Pauschalgrenzen in der DU-Versicherung Wie hoch dürfen Beamte ihre Dienstunfähigkeitsrente absichern? Die Antwort hängt von Status, Besoldungsgruppe und Versicherer ab. WIFO hat nun eine aktuelle Übersicht zu den Pauschalgrenzen veröffentlicht – inklusive Sonderregelungen und Anforderungen bei Überschreitung. Zur Übersicht Susanna Adelhardt neue Vorsitzende der DAV Wechsel an der Spitze der Deutschen Aktuarvereinigung (DAV): Susanna Adelhardt wurde im Rahmen der Jahrestagung in Bonn zur neuen Vorsitzenden gewählt. Die Statistikerin folgt auf Dr. Maximilian Happacher, der dem engeren Vorstand erhalten bleibt. Adelhardt will die Nachwuchsarbeit, internationale Vernetzung und das Ehrenamt stärken. Mit ihr steht erstmals eine Frau an der Spitze der DAV. P&R-Insolvenz: 122 Mio EUR an Gläubiger ausgezahlt Die Insolvenzverwalter der vier deutschen P&R-Containergesellschaften haben rund 122 Mio EUR an über 54.000 Gläubiger ausgezahlt. Damit erhöht sich die Gesamtsumme der bisherigen Abschlagsverteilungen auf über 666 Mio EUR. Die Verwertung der Containerflotte verläuft weiter planmäßig – Quoten bis zu 21,5 % wurden bereits erreicht, teilten die Insolvenzverwalter Dr. Michael Jaffé und Dr. Philip Heinke mit. Helvetia bleibt hochsolvent – SST-Quote stabil bei 288 % Die Helvetia-Gruppe weist für das Geschäftsjahr 2024 erneut eine starke SST-Quote von 288 % aus – ein Wert, der deutlich über den regulatorischen Anforderungen liegt. Die Kapitalstärke und ausgewogene Risikoposition unterstreichen die Widerstandsfähigkeit des Geschäftsmodells. Trotz Dividendenausschüttung und Hybridanleihe-Rückzahlung bleibt die Solvenz auf Vorjahresniveau. Für 2025–2027 plant Helvetia Dividenden in Höhe von über 1,2 Mrd CHF. LVM wächst deutlich stärker als der Markt Die LVM Versicherung hat 2024 rund 1,3 Mio Neuverträge abgeschlossen und die Beitragseinnahmen im Konzern auf knapp 4,9 Mrd EUR gesteigert – ein Plus von 9,1 % gegenüber dem Vorjahr. Der Jahresüberschuss lag bei 241,2 Mio EUR. Besonders stark entwickelten sich Kfz- und Sachversicherungen. Für 2025 plant die LVM über 500 Neueinstellungen am Standort Münster. BarmeniaGothaer startet erste Markenkampagne Knapp sieben Monate nach dem Zusammenschluss von Barmenia und Gothaer zur BarmeniaGothaer startet der Versicherer heute seine erste Markenkampagne. Ziel ist es, Sichtbarkeit und Bewusstsein für die noch junge Marke zu schaffen. Wie man das erreichen will, erklärt Stephanie Nippgen, Abteilungsleiterin Strategie und Kundenmarketing, im Podcast mit ihren eigenen Worten.

In dieser besonderen Folge von „Safe!“ begrüßt Moderatorin Josephine Kahnt ein echtes LVM-Urgestein: Peter Bochnia, Vorstandsmitglied und seit über 37 Jahren Teil des Unternehmens. Gemeinsam werfen die beiden einen Blick zurück auf seine Anfänge mit Dreitagebart und Vokuhila-Frisur, sprechen über Stationen seiner beeindruckenden Karriere und die Entwicklung der LVM vom familiären Versicherer zur modernen Vertriebsorganisation mit Herz. Josi und wir erfahren dabei: Authentizität, gute Stimmung und starke Partnerschaften sind für Peter Bochnia nicht nur Buzzwords, sondern gelebte Werte. Ob Ausschließlichkeitsprinzip, seinen Auftritt bei LinkedIn oder die neue Hauptpartnerschaft mit Fußball-Zweitligist Preußen Münster – der LVM-Vorstand gibt vielfältige Einblicke in seinen Alltag als Vertriebsvorstand und zeigt, wie wichtig Nähe, Vertrauen und Begeisterung für den Job sind.

Matt Crumpton is the host of the podcast Solving JFK.Low Value Mail is a live call-in show with some of the most interesting guests the internet has to offer.Every Monday night at 9pm ETSupport The Show:

In dieser Folge von „Safe!“ nimmt uns Markus Becker, Teamleiter „Meine LVM & IT-Kundensupport“, mit hinter die Kulissen eines digitalen Erfolgsmodells der LVM-Versicherung. Gemeinsam mit Host Josephine Kahnt spricht er über die Erfolgsgeschichte des Kundenportals „Meine LVM“ – von den ersten Anfängen im Jahr 2010 bis zur Millionengrenze an Nutzerinnen und Nutzern. Markus erzählt, wie sein junges Werkstudierendenteam den digitalen Service-Alltag meistert, was einen typischen Arbeitstag ausmacht – und warum ein starker Kaffee oder ein kurzer Plausch an der LVM-Kaffeebar manchmal genauso wichtig ist wie eine schnelle Problemlösung. Außerdem in dieser Folge: Welche Anfragen kommen eigentlich täglich rein? Was macht „Meine LVM“ so nutzerfreundlich? Und warum ist der Teamspirit bei Markus einfach unschlagbar? Josi und ihr könnt erfahren, wie Digitalisierung bei der LVM gelebt wird – mit Herz, Verstand und Teamwork.

In dieser Episode von „Safe!“ wird es sachlich – aber keineswegs trocken! Denn zu Gast bei Moderatorin Josi ist Ina Graap, Spezialistin im Schadenmanagement der LVM. Sie erzählt von ihrem spannenden Karriereweg, wie sie sich von der Position der Sachbearbeiterin zur Spezialistin im Schadenmanagement weiterentwickelt hat und welche Herausforderungen und Chancen ihr neuer Job mit sich bringt. Josi und Ina sprechen über typische Sach-Schadenfälle, wie etwa Leitungswasserschäden oder solche an Wohngebäuden und Hausrat, warum eine gesunde Fehlerkultur so wichtig ist und wie Schulungen für den Außendienst in Zukunft noch interaktiver werden. Außerdem gibt Ina Einblicke in die Unternehmenskultur und warum man sich bei der LVM vom ersten Tag an nie fremd fühlt.

Tiekamies ar Zemkopības ministru Armandu Krauzi. Jautājumi, par ko runājam - saltbriežu skaits un postījumi, LVM līgumi - kāpēc 57 mednieku klubi kļuvuši par ķīlniekiem, vai staltbriežus medīsim bez limita, vilki un lāči - ko ar tiem darīt, kāda situācija. Abonē un lasi žurnālu Medības: https://lasi.lv/abonesana/izdevumi/medibas-ar-pielikumiem.33Pievienojieties šim kanālam, lai iegūtu piekļuvi privilēģijām.https://www.youtube.com/channel/UCqB3nyhYHXKobopia9d7xgA/join

Saruna par lūšiem un to, kur pazūd stirnas, par to, kā sačakarēt labi strādājošu sistēmu. Artūra Surmoviča īsais rezumē par LVM klātienes diskusiju - vai ir kāda labā ziņa. Tad runājam mazliet arī par ragotājiem un cieņu pret cita īpašumu un to, vai ragotāji būtu jāsāk regulēt. Esam ciemos SIA "Ieroči" veikalā Rīgā, un Arvids Baumanis stāsta par veikala jaunumiem! Sia "Ieroči", 9 veikali visā Latvijā: https://siaieroci.lv/Konkursam arī balviņa no SIA Ieroči! Pievienojieties šim kanālam, lai iegūtu piekļuvi privilēģijām.https://www.youtube.com/channel/UCqB3nyhYHXKobopia9d7xgA/join

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

Join Lois Houston and Nikita Abraham as they kick off a two-part episode on MySQL backups with MySQL expert Perside Foster. In this conversation, they explore the critical role of backups in data recovery, error correction, data migration, and more.   Perside breaks down the differences between logical and physical backups, discussing their pros and cons, and shares valuable insights on how to create a reliable backup strategy to safeguard your data.   MySQL 8.4 Essentials: https://mylearn.oracle.com/ou/course/mysql-84-essentials/141332/226362 Oracle University Learning Community: https://education.oracle.com/ou-community LinkedIn: https://www.linkedin.com/showcase/oracle-university/ X: https://x.com/Oracle_Edu   Special thanks to Arijit Ghosh, David Wright, Kris-Ann Nansen, Radhika Banka, and the OU Studio Team for helping us create this episode.   --------------------------------------------------------   Episode Transcript:   00:00 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started! 00:25 Lois: Welcome to the Oracle University Podcast! I'm Lois Houston, Director of Innovation Programs with Oracle University, and with me is Nikita Abraham, Team Lead of Editorial Services.  Nikita: Hi everyone! This is Episode 6 in our series on MySQL, and today we're focusing on how to back up our MySQL instances. This is another two-parter and we've got Perside Foster back with us.    00:49 Lois: Perside is a MySQL Principal Solution Engineer at Oracle and she's here to share her insights on backup strategies and tools. In this episode, we'll be unpacking the types of backups available and discussing their pros and cons. Nikita: But first let's start right at the beginning. Perside, why is it essential for us to back up our databases? 01:10 Perside: The whole point of a database is to store and retrieve your business data, your intellectual property. When you back up your data, you are able to do disaster recovery so that your business can continue after some catastrophic event. You can recover from error and revert to a previous known good version of the data. You can migrate effectively from one system to another, or you can create replicas for load balancing or parallel system. You can retain data for archival purposes. Also, you can move large chunks of data to other systems, for example, to create a historical reporting application. And then you can create test environments for applications that are in development and that need real world test data. 02:10 Lois: Yes, and creating a robust backup strategy takes planning, doesn't it? Perside: As with any complex business critical process, there are challenges with coming up with a backup strategy that you can trust. This requires some careful planning. Any backup process needs to read the data. And in a production system, this will involve adding input/output operations to what might be an already busy system. The resources required might include memory or disk I/O operation and of course, you'll want to avoid downtime, so you might need to schedule the backup for a time when the system is not at peak usage. You'll also need to consider whether the backup is on network storage or some local storage so that you don't exceed limitations for those resources. It isn't enough just to schedule the backup. You'll also need to ensure that they succeed, which you can do with monitoring and consistency check. No backup is effective unless you can use it to restore your data, so you should also test your restore process regularly. If you have business requirements or regulatory commitments that control your data storage policies, you need to ensure your backup also align with those policies. Remember, every backup is a copy of your data at that moment in time. So it is subject to all of your data retention policies, just like your active data. 04:02 Nikita: Let's talk backup types. Perside, can you break them down for us? Perside: The first category is logical backup. A logical backup creates a script of SQL statements that will re-create the data structure and roles of the live database. Descript can be moved to another server as required. And because it's a script, it needs to be created by and executed on a running server. Because of this, the backup process takes up resources from the source server and is usually slower than a physical media backup.  04:45 Nikita: Ok… what's the next type? Perside: The next category is physical backup. This is a backup of the actual data file in the server. Bear in mind that the file copy process takes time, and if the database server is active during that time, then the later parts of the copy data will be inconsistent with those parts copied earlier. Ideally, the file must be stable during the backup so that the database state at the start of the copy process is consistent with the state at the end. If there is inconsistency in the data file, then MySQL detects that when the server starts up and it performs a crash recovery. From MySQL's perspective, there is no difference between a database backup copied from a running server and restarting a server after a crash. In each case, the data files were not saved in a consistent state and crash recovery can take a lot of time on large databases. 06:02 Lois: I see… how can MySQL Enterprise Backup help with this? Perside: MySQL Enterprise Backup has features that enable a consistent backup from a running server. If you create file system copies, either by copying the data files or by performing a file system snapshot, then you must either shut the server down before the copy and undergo crash recovery on the server that starts with those copied files. 06:35 Lois: And aside from logical and physical backups, are there other techniques to back up data? Perside: The binary log enables point-in-time recovery. You can enable replication in a couple of ways. If you start replication and then stop it at a particular time, the replica effectively contains a live backup of the data at the time that you stopped replication. You can also enable a defined replication lag so that the replica is always a known period of time behind the production database. You can also use transportable tablespaces, which are tables or sets of tables in a specific file that you can copy to another server. 07:34 AI is being used in nearly every industry…healthcare, manufacturing, retail, customer service, transportation, agriculture, you name it! And it's only going to get more prevalent and transformational in the future. It's no wonder that AI skills are the most sought-after by employers. If you're ready to dive in to AI, check out the OCI AI Foundations training and certification e that's available for free! It's the perfect starting point to build your AI knowledge. So, get going! Head over to mylearn.oracle.com to find out more. 08:14 Nikita: Welcome back! I want to return to the topic of crafting an effective backup strategy. Perside, any advice here? Perside: We can use the different backup types to come up with an effective backup strategy based on how we intend to restore the data. A full backup is a complete copy of the database at some point in time. This can take a lot of time to complete and to restore. An incremental backup contains only the changes since the last backup, as recorded in the binary log files. To restore an incremental backup, you must have restored the previous full backup and any incremental backups taken since then. For example, you might have four incremental backups taken after the last full backup. Each incremental backup contains only the changes since the previous backup. If you want to restore to the point at which you took the fourth incremental backup, then you must restore the full backup and each incremental backup in turn. A differential backup contains all changes since the last full backup. It contains only those portions of the database that are different from the full backup. Over time, the differential backup takes longer because it contains more changes. However, it is easier to restore because if you want to restore to the point at which you took a particular differential backup, you must restore the last full backup and only the differential backup that you require. You can ignore the intermediate differential backups. 10:13 Lois: Can you drill into the different types of backups and explain how each technique is used in various situations? Perside: One of the physical backup techniques is taking a snapshot of the storage medium. The advantages of a snapshot include its quickness. A snapshot is quick to create and restore. It is well-suited to situations where you need to quickly revert to a previous version of the database. For example, in a development environment. A storage snapshot is often a feature of the underlying file system. Linux supports logical volume management or LVM, and many storage area networks or network-attached storage platforms have native snapshot features. You can also use a storage snapshot to supplement a more scheduled logical backup structure. This way, the snapshot enables quick reversion to a previous type, and the logical backup can be used for other purposes, such as archiving or disaster recovery. 11:28 Nikita: Are there any downsides to using snapshots? Perside: First one includes issues with consistency. Because taking a snapshot is quick and does not cause a database performance hit, you might take the snapshot while the system is running. When you restore such a snapshot, MySQL must perform a crash recovery. If you want a consistent snapshot, you must shut down MySQL in advance. Another problem is that the snapshot is a copy of the file system and not of the database. So if you want to transfer it to another system, you must create a database backup from the storage. This adds step in time. A snapshot records the state of the disk at a specific point in time. Initially, the snapshot is practically empty. When a data page changes, the original version of that page is written to the snapshot. Over time, the snapshot storage grows as more data pages are modified. So multiple snapshots result in multiple writes whenever a snapshot data page is changed. To avoid performance deterioration, you should remove or release snapshots when they are no longer in use. Also, because snapshots are tied to the storage medium, they're not suited to moving backups between systems. 13:03 Lois: How about logical backups? How do we create those? Perside: The mysqldump utility has long been a standard way to create logical backups. It creates a script made up of the SQL statement that creates the data and structure in a database or server.  13:21 Nikita: Perside, what are the advantages and disadvantages of mysql dump? Perside: It is an excellent solution for preserving the database structure or for backing up small databases. Logical backups naturally require that the server is running. And they use system resources to produce the SQL statements, so they are less likely for very large databases. The output is a human-readable text file with SQL statements that you can edit as a text file. It can be managed by a source code management system. This allows you to maintain a known good version of the database structure, one that matches your application source code version, which can also include sample data. The mysqldump disadvantages are it needs to run against an active server. So if your production server is busy, you must take action to ensure a consistent backup. This requires locking tables or using the single transaction option, which can result in application delays as the backup completes in a consistent way. Mysqldump does not track changes since the last backup, so it has no way of recording only those rows that have changed. This means it's not suited to perform differential or incremental backups. The scripts must be executed against a running server, so it is slower to restore than using a data dump or physical backup. Additionally, if the database structure has indexes of foreign keys, these conditions must be checked and updated as the data is imported. You can disable these checks during the import but must handle any risks that come from doing so. Because the backup is nothing more than an SQL script, it is easy to restore. You can simply use the MySQL client or any other client tool that can process scripts.  15:46 Nikita: Is there an alternative tool for logical backups? Perside: MySQL Shell is another utility that supports logical backup and restore. Unlike mysqldump, it dumps data in a form that can be processed in parallel, which makes it much faster to use for larger data sets. This enables it to export to or import from remote storage where it can stream data without requiring the whole file before starting the input. It can process multiple chunks of imported data in parallel, and you can monitor progress as it completes. You can also pause import and resume later. For example, in the event of network outage. You can dump and restart table structure, including indexes and primary keys. The utilities in MySQL Shell are exposed through functions. The dumpInstance and dumpSchema utilities back up the whole server or specified schemas respectively. And loadDump is how you restore from such a dump. 17:07 Lois: Thanks for that rundown, Perside! This concludes our first part on MySQL backups. Next week, we'll take a look at advanced backup methods and the unique features of MySQL Enterprise Backup. Nikita: And if you want to learn more about everything we discussed today, head over to mylearn.oracle.com and explore the MySQL 8.4 Essentials course. Until then, this is Nikita Abraham… Lois: And Lois Houston signing off! 17:37 That's all for this episode of the Oracle University Podcast. If you enjoyed listening, please click Subscribe to get all the latest episodes. We'd also love it if you would take a moment to rate and review us on your podcast app. See you again on the next episode of the Oracle University Podcast.

Die Themen im heutigen Versicherungsfunk Update sind: Wie sich der digitale Makler heute Versicherer aussucht: Zwischen Daten und Bauchgefühl Bei der Auswahl eines passenden Produktes zählen nicht nur Preis und Leistung. Für Versicherungsmakler ist die Suche nach dem optimalen Versicherungsschutz für den Kunden deutlich umfangreicher. So zählen beispielsweise die Stabilität des Versicherers oder die schnelle Bearbeitung von Schäden zu den wichtigsten Punkten, weiß Versicherungsmakler und Bestseller-Autor Bastian Kunkel. Auf was es bei der Versicherer-Suche für digitale Makler ankommt, erklärt uns der Gründer der Social-Media-Marke „Versicherungen mit Kopf“ in seiner jüngsten Kolumne für Versicherungsbote. Jan Roß steigt bei Pfefferminzia ein Die Firma von Jan Roß, die 'Roß Perspektiven Management GmbH' beteiligt sich an der Pfefferminzia Medien GmbH. Das teilte der frühere Bereichsvorstand Maklermarkt der Zurich, Jan Roß, auf seinem LinkedIn-Profil mit. "Die Kombination aus tiefer Marktkenntnis, strategischer Beratung, hervorragender Medienarbeit und erstklassiger redaktioneller Expertise bietet einzigartige Synergien", hieß es zur Begründung. Münchener Verein legt Deutsche Handwerker BU neu auf Der Münchener Verein hat seine Deutsche Handwerker Berufsunfähigkeitsversicherung (BU) Aktiv neu aufgelegt. Der Tarif bietet unter anderem eine schnellere Leistungserbringung durch eine AU-Option, Soforthilfe bei schweren Krankheiten, eine Umorganisationshilfe für Selbstständige von bis zu 10.000 Euro und einen Heldenbonus für ehrenamtlich Tätige. Neu ist die Verfügbarkeit der BU für Schüler ab dem 10. Lebensjahr. -Talanx steigert Konzernergebnis 2024 um 25 % Die Talanx Gruppe hat im Geschäftsjahr 2024 ein Konzernergebnis von 1,977 Mrd. Euro erzielt, was einem Anstieg um 25 % im Vergleich zum Vorjahr entspricht. Der Versicherungsumsatz wuchs um 11 % auf 48,1 Mrd. Euro, und die Eigenkapitalrendite liegt voraussichtlich bei 17,8 %. Der Vorstand schlägt eine Dividende von 2,70 Euro je Aktie vor, die das ursprüngliche Ziel frühzeitig übertrifft. Für 2025 bestätigt die Gruppe ihr Gewinnziel von mehr als 2,1 Mrd. Euro und strebt bis 2027 ein Konzernergebnis von über 2,5 Mrd. Euro an. Die finalen Zahlen werden am 19. März 2025 veröffentlicht. LVM Versicherung verlängert Hauptsponsoring beim USC Münster Die LVM Versicherung bleibt weitere drei Jahre Hauptsponsor des Volleyball-Bundesligisten USC Münster. Am 7. Februar 2025 unterzeichneten LVM-Vorstandsmitglied Peter Bochnia und USC-Präsident Jürgen Aigner die Vertragsverlängerung bis 2028. Die Partnerschaft zwischen der LVM und dem USC Münster besteht bereits seit 35 Jahren. Immer mehr Frauen beziehen Grundsicherung im Alter Immer mehr Frauen sind im Rentenalter auf Grundsicherung im Alter angewiesen. Wie aus einer Antwort der Bundesregierung auf eine Kleine Anfrage der Gruppe Die Linke hervorgeht, ist die Zahl von 312.388 im Jahr 2014 auf 413.955 im vergangenen Jahr gestiegen.

Großstadt oder Kleinstadt – macht das eigentlich einen Unterschied für eine Versicherungsagentur? Und was ist das Besondere daran, eine LVM-Agentur zu leiten? In dieser Folge spricht Moderatorin Josi mit Thomas Kräusel, Agenturleiter in Bielefeld, und Christian Bolte, Agenturleiter in Mastholte, über ihren beruflichen Alltag, die Herausforderungen im Kundenkontakt und die spannenden Facetten ihres Jobs. Wie gewinnt man neue Kundinnen und Kunden? Gibt es auf dem Land wirklich mehr persönliche Beratung als in der Stadt? Und wie sieht die Arbeit hinter den Kulissen aus – von Personalmanagement bis Digitalisierung? Unsere beiden Gäste geben ehrliche Einblicke und verraten, warum sie sich auch nach 20 Jahren keinen besseren Job vorstellen können als eine LVM Agentur zu leiten.

Tiekamies ar LMS jauno vadītāju Juri Buškevicu, lai pārrunātu aktualitātes, nākotnes perspektīvas, medību saimniecības problēmas un prioritātes. Liela daļa sarunas par LVM rīkoto klātienes diskuciju par staltbriežu populācijas apsaimniekošanu. Juris atzīst, ka ar rezultātiem nav apmierināts. Ir pozitīvas tendences, bet tomēr viennozīmīga risinājuma nav. Konkursā balva no OUTDOOREXPERTS.LV - kāds no Recoil ieroču košanas līdzekļu flakoniņiem: https://outdoorexperts.lv/lv/mekl%C4%93t?controller=search&s=recoil Facebook grupa, kur meklēt un piedāvāt medību iespējas: Gribu medīt! https://www.facebook.com/groups/739968340083804 Pievienojieties šim kanālam, lai iegūtu piekļuvi privilēģijām. https://www.youtube.com/channel/UCqB3nyhYHXKobopia9d7xgA/join

In this episode, I discuss the problem of unclear economic thinking in Biblical scholarship. Terms like ‘capitalism' and ‘socialism' are often left undefined by the scholars who employ them, and the vague cultural notion that ‘capitalism' is about evil and greed while ‘socialism' is about virtue and charity characterizes the use of economic language in scholarship on the Bible. I discuss how many excellent scholars nevertheless make Jesus out to be a modern socialist despite doing excellent historical work on ancient economic systems. I define capitalism as it is understood by the Austrian school as a theory of private capital accumulation based on absolute respect for property rights. I then explain how modern economic concepts are foreign to ancient thinkers. I read through Luke 12:13-34 and explain the historical questions which need to be asked to accurately interpret this passage and explain how modern interpreters gloss over Jesus's statements on wealth and charity with an uncritical appeal to socialism. I then explore this dynamic by reviewing the work of two New Testament scholars, Richard Horsley and Douglas Oakman, who do excellent historical analysis on ancient economic and political systems but impose modern socialist ideas onto the texts while coming to the incorrect political conclusions that all our modern problems are a result of capitalism on ‘capitalism', when the real problem are socialist policies that they support. They allow their biases to determine interpretive outcomes. I also reveal that I am writing a book about all of this which I hope will be published in 2026.   Media Referenced:LVM vs. N.T. Wright: https://libertarianchristians.com/episode/ep-178-ludwig-von-mises-vs-a-christian-scholar-round-3-n-t-wright/LVM vs. James K.A. Smith: https://libertarianchristians.com/episode/ludwig-von-mises-vs-christian-scholar-round-2-james-k-a-smith/LVM vs. Michael Gorman: https://libertarianchristians.com/episode/ludwig-von-mises-vs-christian-scholar-round-1-michael-gorman/James Crossley: https://libertarianchristians.com/episode/ep-169-the-next-quest-for-the-historical-jesus-with-james-crossley/The Political Aims of Jesus, Oakman: https://www.amazon.com/dp/0800638476?ref_=cm_sw_r_ffobk_cp_ud_dp_R1NS418YPJNNEY9DRTDS_2&skipTwisterOG=1&bestFormat=true&newOGT=1Jesus and Empire, Horsley: https://www.amazon.com/dp/080063490X?ref_=cm_sw_r_ffobk_cp_ud_dp_NBCAC8JTEJVMTVEC3M94&skipTwisterOG=1&bestFormat=true&newOGT=1 The Protestant Libertarian Podcast is a project of the Libertarian Christian Institute and a part of the Christians For Liberty Network. The Libertarian Christian Institute can be found at www.libertarianchristians.com.Questions, comments, suggestions? Please reach out to me at theprotestantlibertarian@gmail.com.  You can also follow the podcast on Twitter: @prolibertypod, and YouTube, @ProLibertyPod, where you will get shorts and other exclusive video content. 

Šoreiz aktīvi diskutējam par staltbriežu izšaušanu un selektīvo medību beigām. Jaunajam gadam sākoties, medniecības dzīvē ir sācies jauns posms, kas ienes arī jaunu atmosfēru Latvijas Mednieku savienībā. Tāpat atskatāmies uz piedzīvoto fazānu medībās Polijā un apspriežam daudzas citas, aktuālas un interesantas tēmas - drāmu ar LVM un stalrbriežu skaita samazinājumu - kopā ar mednieku Artūru Surmoviču.

Hur man stöttar en person som inte mår bra och samtidigt tar hand om sig självMånga av oss befinner oss någon gång i livet i en situation där vi har en anhörig, en vän eller en nära kollega som inte mår bra. I det här avsnittet har jag med mig Pernilla Aspe, terapeut och ledarskapskonsult, delar i detta poddavsnitt med sig av sina erfarenheter och verktyg för hur man kan navigera i denna ibland svåra roll.De vanligaste utmaningarna för anhörigaEnligt Pernilla är skuld en av de mest frekventa känslorna som drabbar personer som är anhöriga till någon som mår dåligt. Skulden kan vara dubbel:Skuld gentemot personen som mår dåligt, eftersom man kanske inte känner att man räcker till eller gör tillräckligt.Skuld gentemot andra delar av sitt liv, som jobb, andra relationer och barn som kanske inte får lika mycket uppmärksamhet.Denna skuld skapar en “klämsits” som gör att många känner sig otillräckliga på flera fronter samtidigt. Samtidigt kan det finnas en känsla av skam för att erkänna att man inte klarar av situationen.Hur man navigerar känslan av att inte räcka tillPernilla poängterar att det är avgörande att kartlägga sina resurser och energinivåer. Hon föreslår en proaktiv strategi för att identifiera:Vad tar energi?Vad ger energi?Vad är nödvändigt att prioritera?Tillåt dig att säga: ”Jag är trött”Ett av de viktigaste stegen för att hantera situationen är att kunna erkänna sina egna begränsningar och behov. Pernilla beskriver hur svårt det kan vara för många att tillåta sig själva att uttrycka saker som:”Det här är jobbigt.””Jag är trött och orkar inte mer.”Att erkänna detta innebär inte att man är en dålig förälder, partner eller kollega – det är snarare ett sätt att möta verkligheten och börja skapa lösningar. Pernilla menar att det är avgörande att söka trygga rum där man kan ventilera dessa känslor utan att bli dömd.Återhämtning och glädje – vad längtar du efter?För att orka stötta någon annan måste man själv fylla på energi. Men vad är återhämtning? Pernilla poängterar att det ser olika ut för olika individer och att det inte alltid är enkelt att veta vad man behöver. Hon föreslår frågor som:Vad längtar du efter?Hur kan du skapa utrymme för återhämtning?Att fånga det positiva – utan att ignorera det jobbigaPernilla betonar vikten av att kunna hitta de små positiva stunderna i en annars tuff vardag. Detta handlar inte om ”toxic positivity” eller att förneka svårigheter, utan om att låta både det jobbiga och det positiva existera sida vid sida.Reflektera över vad som gick bra idagTillåt dig att känna glädjeSätt gränser och våga be om hjälpSäg nej utan skuldBe om hjälpStötta på arbetsplatsen – rollen som chef och kollegaChefers rollSkapa en tillåtande kulturHjälp till med prioriteringarHa täta avstämningarKollegors rollLyssna utan att dömaFråga hur du kan stöttaDela glädje med fingertoppskänslaPernillas råd är en påminnelse om att vi alla är människor med begränsade resurser. Att ta hand om sig själv är inte egoistiskt – det är nödvändigt. Sköt om dig! Hosted on Acast. See acast.com/privacy for more information.

Willkommen im Podcast-Jahr 2025! Auch in diesem Jahr stellen wir euch in „Safe!“ Kolleginnen und Kollegen aus unterschiedlichsten Bereichen der LVM vor und reden mit ihnen über ihren ganz persönlichen Arbeitsalltag. Den Anfang macht Franziska de Waal, die gemeinsam mit unserer Moderatorin Josi einen Blick wirft hinter die Kulissen eines komplexen und wichtigen Themengebiets: Compliance. Franziska erzählt von ihrem bisherigen Karriereweg, der Bedeutung von Compliance für das Unternehmen und wie es gelingt, trockene Gesetzestexte in greifbare Orientierungshilfen für den Arbeitsalltag zu übersetzen. Wir lernen, was hinter sperrigen Begriffen wie Verhaltenskodex oder Hinweisgebersystem steckt, warum Vertrauen der Schlüssel zu erfolgreicher Compliance ist und wie Franziska es schafft, zwischen Paragraphen und Teamwork ihren vielseitigen Arbeitsalltag zu meistern.

Diskusija šoreiz par to, ka AS Latvijas valsts meži paredzējuši medību tiesību nomas līgumus pārslēgt uz pieciem gadiem, kas ir laika posms, kura ietvaros nav iespējams veidot veidot medību saimniecību, ieguldot tajā laiku, resursus un finanses. Viedoklis ir no LATMA vadītāja Haralda Barvika un no LMS vadītāja - Jāņa Baumaņa. LVM bija pārāk aizņemti, lai sniegtu savu viedokli. Tad nu diskusija par riskiem un iespējamām problēmām. Abonē 2025. gadam, saņem dāvanā “Medību” kalendāru un vari laimēt karabīni no SIA “IEROČI” 1369,00 EUR vērtībā. https://lasi.lv/abonesana/izdevumi/medibas.28 Pievienojieties šim kanālam, lai iegūtu piekļuvi privilēģijām. https://www.youtube.com/channel/UCqB3nyhYHXKobopia9d7xgA/join

40 Jahre LVM – eine Karriere voller Entwicklung, Abwechslung und spannender Projekte. Darüber spricht Monika Homann mit unserer Moderatorin Josi in der letzten Episode von „Safe!“ für dieses Jahr. Monika erzählt uns von ihrem Weg von der Unfallabteilung bis zur Spezialistin in der Personal- und Organisationsentwicklung und verrät uns dabei ihr eigenes „Entwicklungsgeheimnis“: Immer neugierig bleiben und die Chancen nutzen, die ein Unternehmen wie die LVM bietet.Außerdem sprechen Josi und Monika in dieser Episode über ein echtes Herzensprojekt der LVM: „Wir für Demokratie“. Monika erzählt, wie aus der Idee einer Kollegin ein unternehmensweites Programm wurde, das den Wert demokratischer Strukturen wieder ins Bewusstsein rückt. Mit Formaten wie Diskussionen, Workshops und Aktionen setzt die LVM mit ihrem Demokratieprojekt ein Zeichen für Offenheit, Vielfalt und Teilhabe. Das Projekt zeigt, wie viel Wirkung Unternehmen für die Gesellschaft entfalten können – von virtuellen Führungen durchs Europaparlament bis hin zu besonderen Freistellungen für Wahlhelfer.Übrigens, die Playlist, über die Monika in der Episode spricht, findet ihr hier bei Spotify.

Vorstandsmitglied Marcus Loskant erzählt uns, wie sich die LVM bezüglich GenAI positioniert!

Jack Kelley is the creator of the documentary the Atlantis Puzzle available to buy or rent on Youtube. Low Value Mail is a live call-in show with some of the most interesting guests the internet has to offer. Every Monday night at 9pm ET Support The Show:

Das komplexe, aber für Unternehmen wie die LVM sowohl nach Außen in Richtung Kundinnen und Kunden als auch nach Innen in Richtung der Mitarbeitenden extrem wichtige Thema UX-Design steht im Mittelpunkt dieser Episode von „Safe!“. Moderatorin Josephine Kahnt hat die UX-Designerin Ricarda Jankord und den UX-Designer Rosen Lütke zu Gast. Die beiden sprechen mit Josi über die Grundlagen und den Mehrwert von User Experience Design, kurz „UX-Design“. Wir lernen dabei, dass UX-Design weit über die reine Gestaltung hinausgeht und darauf abzielt, Produkte und Dienstleistungen zu kreieren – vor allem auch im digitalen Bereich wie etwa Websites oder Apps –, die intuitiv und zufriedenstellend nutzbar sind. So kann etwa die schnelle Auffindbarkeit eines bestimmten Formulars auf der Website mit ausschlaggebend dafür sein, ob eine Kundin oder ein Kunde zufrieden mit der Versicherung ist oder nicht. Dahinter steht die Erkenntnis, das vermitteln Ricarda und Rosen sehr anschaulich in dieser Episode, dass es oft wichtiger ist, ein Problem gründlich zu verstehen, bevor man zur Lösung übergeht – und wie gutes Design für echte Zufriedenheit sorgt.

Diese Episode von „Safe!“ ist im wahrsten Sinne „historisch“. Dafür sorgt Silke Thommessen, die Moderatorin Josephine Kahnt dieses Mal zu Gast hat. Silke ist bereits seit 26 Jahren bei der LVM tätig, begann ihre Laufbahn zunächst in der Unternehmenskommunikation und ist gemeinsam mit ihrem Team heute verantwortlich für den Aufbau und die Pflege des historischen Unternehmensarchivs der Versicherung. Wir erfahren in dieser Episode, was ein Unternehmensarchiv genau ist, warum es für die LVM so wichtig ist und wie historische Dokumente nicht nur die Vergangenheit, sondern auch die Zukunft des Unternehmens prägen. Dazu verrät Silke, welche bedeutsamen oder auch skurrilen Funde es bereits gegeben hat, warum auch das Foto einer Weihnachtsfeier von vor Jahrzehnten nicht uninteressant ist und wie die LVM gemeinsam mit Wissenschaftlerinnen und Wissenschaftlern die Rolle der LVM in der NS-Zeit erforscht hat.

In dieser Episode von „Safe!“ steht das wichtige Thema Inklusion im Fokus. Moderatorin Josephine Kahnt hat dazu Nicole Wethkamp zu Gast. Nicole ist im „Hauptberuf“ Personalreferentin bei der LVM und begleitet in dieser Rolle Mitarbeiterinnen und Mitarbeiter in allen Phasen des Arbeitslebens – von der Einstellung bis hin zur Personalplanung. Darüber hinaus hat die erfahrene LVM-Kollegin auch noch die wichtige und verantwortungsvolle Aufgabe der Inklusionsbeauftragten bei der LVM übernommen. Nicole erklärt, was Inklusion für sie persönlich und für die LVM bedeutet und wie das Unternehmen Barrieren abbaut, um ein inklusives Arbeitsumfeld zu schaffen. Sie spricht über ihre Rolle als Inklusionsbeauftragte und die Herausforderungen, denen Menschen mit Behinderung in der Arbeitswelt begegnen. Nicole teilt ihre Erfahrungen aus dem betrieblichen Eingliederungsmanagement und gibt zudem wertvolle Tipps für Menschen mit Behinderung, die sich bei der LVM bewerben möchten. Die Episode zeigt, wie die LVM sich aktiv für eine vielfältige und unterstützende Unternehmenskultur einsetzt und welche Schritte noch unternommen werden können, um Inklusion weiter zu fördern.

Die Themen im heutigen Versicherungsfunk Update sind: Generali verliert beim Konzernergebnis Die Generali hat gebuchten Bruttobeiträge im ersten Halbjahr 2024 im Vergleich zum Vorjahreszeitraum um 20,4 Prozent auf 50,1 Milliarden Euro steigern können. Das operative Ergebnis verbesserte sich leicht um 1,6 Prozent auf 3,7 Milliarden Euro. Das bereinigte Konzernergebnis belief sich auf 2,0 Milliarden Euro und sackte damit um 13,1 Prozent ab. Dies habe hauptsächlich an Kapitalgewinnen und anderen Einmaleffekten im ersten Halbjahr 2023 gelegen. Ohne diese Effekte wäre das bereinigte Konzernergebnis stabil geblieben, erklärte der Versicherer. Ammerländer bekommt neuen Vertriebsleiter Reiner Ihnken ist seit dem 1. August 2024 der neue Leiter Vertrieb bei der Ammerländer Versicherung. Der gelernte Versicherungskaufmann verantwortet in dieser Position unter anderem die Weiterentwicklung und Umsetzung der Vertriebsstrategie sowie die Optimierung der Vertriebsprozesse. Seine Vorgängerin, Kerstin Duda, übernimmt auf eigenen Wunsch neue Aufgaben und wird unter anderem das unternehmensweite Prozessmanagement aufbauen. Adam Riese erweitert Unfallversicherung Adam Riese baut mit weiteren Leistungen den eigenen Unfalltarif aus. Neuerungen der Police sind der Wegfall von Gesundheitsfragen in der umfangreichsten Tariflinie sowie die Einführung neuer Altersstufen. Den bedeutendsten Pluspunkt bietet die Tariflinie Riesig: Diese kann ab sofort ohne die Beantwortung von Gesundheitsfragen abgeschlossen werden. LVM erstattet PKV-Beiträge zurück Krankenversicherte der LVM erhalten einen Teil ihrer 2023 gezahlten Beiträge zurück. Durchschnittlich beläuft sich diese Beitragsrückerstattung auf etwa 650 Euro pro Vertrag. Insgesamt schüttet der Versicherer den fast 40.000 privat Krankenversicherten rund 18 Millionen Euro aus. Beiträge zurückerstattet erhalten diejenigen Privatversicherten, die im vergangenen Jahr entweder keinen Arzt besucht oder aber geringe ambulante Behandlungskosten selbst übernommen haben. 60 % der 15- bis 24-Jährigen verfügen über keine eigenen Einnahmen Gut 60 % der jungen Menschen im Alter von 15 bis 24 Jahren standen im vergangenen Jahr finanziell noch nicht auf eigenen Beinen, sondern waren für ihren Lebensunterhalt hauptsächlich auf familiäre Unterstützung oder staatliche Leistungen angewiesen. Knapp 39 % verdienten ihr Geld dagegen überwiegend selbst, bezogen ihren Lebensunterhalt also überwiegend aus eigener Erwerbstätigkeit. Für knapp 1 % war bereits in jungem Alter ein eigenes Vermögen die Quelle des Lebensunterhalts. Das teilt das Statistische Bundesamt (Destatis) auf Basis von Ergebnissen des Mikrozensus mit. Die Hälfte der 15- bis 24-Jährigen (49 %) lebte hauptsächlich vom Einkommen der Eltern oder anderer Angehöriger. Jeder neunte junge Mensch (11 %) bezog seinen Lebensunterhalt 2023 überwiegend aus öffentlichen Leistungen, wie etwa BAföG, Stipendien oder Bürgergeld. Die Bafin besiegelt das Ende der Condor Allgemeinen Versicherung Mit der Verschmelzung auf die R+V Allgemeine nimmt der Konzern seine 2008 erworbene Tochter vom Markt. Für Kunden und Vermittler solle sich nichts ändern. Die Condor Leben bleibt davon unberührt, berichtet das VersicherungsJournal.

Shownotes: Episode 00094 ist da! Die üblichen News versorgen euch mit allem rund um E-Mobilität, KI, Hardware und Gaming, usw.! Mit uns seid ihr immer versorgt und auf dem neuesten Stand! ;) Danach haben wir diese Woche in den Themen: Erst von Chris einen Überblick darüber, welche Container-Systeme man auf Servern einsetzt und wo die Vor- und Nachteile liegen. Wann nutzt man VMs? Wann Docker? Und was ist LVM? Hört rein! :) Dann kommt von Pati ein Bericht zum Stand der Batteriezellenproduktion in Deutschland. Haben wir sowas? Wer produziert hier? Lohnt sich das? Und können wir China damit paroli bieten? Im Dummschnack geht es dann wie so oft noch etwas ums Gaming! :) Ansonsten wie immer: Sharen, Kommentieren, Mailen, Messagen… alles sehr nice! :) Schreibt uns einfach auf Insta oder ne Mail unter jasiapodcast@gmail.com oder kommentiert bei Spotify direkt unter der Folge! :) Ihr könnt uns auch gerne Audiokommentare mit dem Hinweis, ob wir das in einer der nächsten Folgen einspielen dürfen, schicken. Bis zur nächsten Folge! :) Unsere Links: Unser Discord-Server: http://discord.ja-sia.de Instagram: https://www.instagram.com/jasiapodcast/ Facebook: https://www.facebook.com/jasiapodcast/ Mail: jasiapodcast@gmail.com Kapitel: 00:00:00 Intro 00:02:21 Begrüßung und Aufwärmschnack 00:07:06 Themenvorstellung 00:10:09 News 00:59:50 Thema 1: Server, Container, VM oder wie oder was? 01:58:01 Thema 2: Batteriezellen Made in Germany? 02:21:01 Dummschnack 02:40:45 Zusammenfassung Links zur Sendung: Intels AI Playground: https://game.intel.com/us/stories/introducing-ai-playground/ Viewfinder Game Trailer: https://www.youtube.com/watch?v=uk8_FUIJh7Q Folge direkt herunterladen

In dieser Episode von Safe!, dem Karrierepodcast der LVM Versicherung, hat Josephine Kahnt wieder einmal eine Kollegin und einen Kollegen aus der Münsteraner Zentrale zu Gast: Jacqueline Scheifel und Henrik Plath arbeiten dort als Business Analysten in der IT-Koordination. Jacqueline berichtet zunächst von ihrem Studium, das sie auch nach Moskau und Taiwan geführt hat, und wie sie schließlich „fachfremd“ zur LVM kam. Henrik erzählt von seiner Zeit im Projektmanagement bei TV-Produktionsfirmen und wie er dann doch wieder in seine ursprüngliche gelernte Branche Versicherungen zurückkam. Im Gespräch mit Josi erklären sie, was eigentlich ein Business Analyst oder eine Business Analystin ist und erläutern ihre Aufgaben in der IT-Koordination, wo sie als Schnittstelle zwischen der Fachabteilung und der IT fungieren. Zum Abschluss verraten Jacqueline und Henrik noch wertvolle Tipps für diejenigen, die sich beruflich verändern möchten und ermutigen dazu, mutig zu sein und sich auch auf Stellen zu bewerben, bei denen man nicht alle Anforderungen erfüllt, da viele Fähigkeiten im Job erlernt werden können.

Die Themen im heutigen Versicherungsfunk Update sind: Allianz angelt sich französischen SachbestandIm Januar 2024 kündigte der Online-Versicherer Allianz Direct die Übernahme des französischen Hausratversicherungsgeschäfts von Luko an. Dieser Schritt wurde am 1. Februar 2024 vollzogen. Nach Genehmigung durch die deutschen und französischen Aufsichtsbehörden wurden am 29. Juli 2024 auch alle bestehenden Verträge der Luko Insurance AG auf die französische Niederlassung der Allianz Direct Versicherungs-AG übertragen. Ex-BaFin-Aufseher wechselt zur GeneraliDer ehemalige BaFin-Exekutivdirektor Frank Grund wechselt in die Aufsichtsgremien der Generali. Beim italienischen Versicherer soll Grund die Aufsichtsräte der Holding, des Lebens- sowie des Sachversicherers einziehen. Darüber berichtet das Fachportal "Versicherungsmonitor". Continentale bekommt neuen VorstandsvorsitzendenDr. Gerhard Schmitz wird zum 1. August 2024 neuer Vorstandsvorsitzender im Continentale Versicherungsverbund. Die Aufsichtsräte haben den Diplom-Ökonomen zum Nachfolger von Dr. Christoph Helmich ernannt, der nach neun Jahren als Vorstandsvorsitzender am 31. Juli 2024 in den Ruhestand geht. Neu ins Vorstandsteam rückt der bisherige Leiter des Rechnungswesens, Marcus Lauer. Nürnberger streicht GewinnprognoseDie Nürnberger Beteiligungs-AG passt die Prognose für das Konzernergebnis 2024 an. Ursprünglich war der Versicherer von einem Gewinn in der Bandbreite von 40 bis 50 Millionen Euro ausgegangen. Aufgrund der höheren Aufwendungen in der Schadenversicherung, die insbesondere durch Elementar- und Großschäden sowie die anhaltende Inflation vor allem in der Kfz-Versicherung bedingt werden, rechnet die Nürnberger Beteiligungs-AG nunmehr mit einem ausgeglichenen Konzernergebnis im Jahr 2024. Für das erste Halbjahr zeichnet sich ein klar negatives Ergebnis ab. MLP steigert Zahlen deutlichAuf Basis vorläufiger Geschäftszahlen für das zweite Quartal 2024 erzielte der MLP Konzern ein vorläufiges Ergebnis vor Zinsen und Steuern (EBIT) von rund 12 Millionen Euro. Dieser Wert liegt deutlich über dem Vergleichswert des Vorjahres von 5,0 Millionen Euro. Das vorläufige EBIT für das erste Halbjahr 2024 beläuft sich damit auf rund 49 Millionen Euro. Im Vergleichszeitraum des Vorjahres waren es: 37,4 Millionen Euro. Nach der erfolgreichen Entwicklung im ersten Halbjahr 2024 geht MLP nun davon aus, die obere Hälfte der für das Gesamtjahr prognostizierten EBIT-Spanne von 75 bis 85 Millionen Euro zu erreichen. LVM steigt beim VfL Bochum aufDie LVM Versicherung wird ein neuer Premium Partner beim VfL Bochum 1848. Der Kontrakt gelt bis 2027 und sei ligaunabhängig. Bereits seit einigen Jahren ist eine Werbegemeinschaft von acht LVM-Versicherungsagenturen aus dem Einzugsbereich des Revierklubs beim Verein aktiv. Durch die erweiterte Partnerschaft solle die Zusammenarbeit im Bereich der Sachversicherung verstärkt werden.

Ashley Nemeth is a returning guest and communications professional who agrees self-advocacy without snark can be a challenge! In this episode, Jennie and Ashley uncover how they wade through awkward moments in the workplace and beyond. They rise above low expectations and non-compliments, discover a hidden moustache, and ask themselves when is “just sit on it”the most appropriate response? Highlights:Just Sit On It (00:00)Introducing Ashley Nemeth (00:20)Plus ça Change, Plus C'est la Même Chose (02:17)Keeping it Professional (03:00)Lowered Expectations (05:56)Awareness & Accommodations (10:21)Filling in the Gaps (17:20)What Were They Thinking? (22:20)The “Don't Talk to Me” Vibe (26:00)Meek & Mild (28:59)Find Ashley Nemeth Online (31:56)Show Close (32:31)Guest Bio:Ashley Nemeth is a badass mom of three hailing from Saskatchewan. A communications professional, and stealth self-advocate, she takes her coffee with a good book.Guest Description:Ashley has short strawberry blonde hair and wears a green-grey sweatshirt. Her face is expressive and she sits in a room with light grey walls. Links:Ashley's prior LVM episode “What Did You Just Say to Me?” (Audio Only)Instagram @AshleyNemethOfficial Host description: Jennie is a woman with shoulder-length white-blonde hair, strong glasses with purple rims. She has very pale skin and wears light makeup. Her facial expressions are animated and she often speaks with her hands. She wears a small pink stud nose jewellery. The background includes two large bookcases, full of a variety of books, DVDs, toys, and nicknacks. About Low Vision Moments:Part story time, part comedy, part awareness driven, Jennie Bovard presents funny experiences that happen when you are blind or partially sighted. Jennie Bovard is a running, beer-drinking, thirtysomething with albinism. She loves trying all the things, making people laugh, and volunteering to create accessible sport and recreation opportunities in her community. Jennie, who has lived with partial sight all her life, has a diploma in film and TV production. Jennie lives in Halifax. About AMIAMI is a not-for-profit media company that entertains, informs and empowers Canadians who are blind or partially sighted. Operating three broadcast services, AMI-tv and AMI-audio in English and AMI-télé in French, AMI's vision is to establish and support a voice for Canadians with disabilities, representing their interests, concerns and values through inclusion, representation, accessible media, reflection, representation and portrayal. Learn more at AMI.caConnect on Twitter @AccessibleMediaOn Instagram @accessiblemediaincOn Facebook at @AccessibleMediaIncEmail feedback@ami.ca

We daily drive Asahi Linux on a MacBook, chat about how the team beat Apple to a major GPU milestone, and an easy way to self-host open-source ChatGPT alternatives. Special Guest: Neal Gompa.

Can we build an indestructible server that stands up to the test of giving out root login to the Internet?

Tyler and Jordan review the “Momentum Factor” in our fourth and final installment of the fundamental factors of investing. Momentum investing is a strategy that seeks to profit from the continuance of an existing market trend. This trading strategy centers around investors buying stocks that are already going up and selling stocks that are falling. The largest ETF by assets under management (AUM) for momentum investing is the iShares Momentum factor ETF which analyzes stock prices, adjusted for volatility, over the past 6 and 12 months. Momentum is about price and price can tell a story about how investors sentiment stands for a certain security or the market. One potential issue with using price as your only guide is that momentum can change very quickly, and investors need to have a set of rules in place to follow including rebalancing rules to account for frequent changes in momentum trends. It is best to use these strategies that have frequent rebalancing and turnover in the correct type of accounts as turnover and realized sell activity can cause tax consequences in taxable accounts.   Tyler and Jordan conclude with how LVM uses the momentum factor, which focuses on momentum in analysts' earnings and revenue estimate trends. 

SIM EU LEMBREI DOS LINKS CAIU O ESTADO Chopp sem imposto: https://sites.google.com/studentsforliberty.org/chopp-sem-imposto-sudeste/chopp-sem-imposto-sfl?authuser=0 Fórum da Liberdade: https://www.forumdaliberdade.com.br/ Código RaphaVIP pro desconto da galera LibertyCon Europa: https://libertycon.net/ Código LIMA pra 50% de desconto São Carlos: https://www.sympla.com.br/evento/2-summer-school-semente-da-liberdade/1897373 Livros https://www.amazon.com.br/Indiv%C3%ADduo-Economia-Estado-Murray-Rothbard/dp/6550520681/ref=mp_s_a_1_1?crid=3J3XLWWCMXN25&keywords=lvm+individuo+economia+e+estado&qid=1677975763&sprefix=lvm+individuo+economia+e+estado%2Caps%2C154&sr=8-1 https://www.amazon.com.br/Legal-Systems-Very-Different-Ours/dp/1793386722 Quer fugir do Brasil? Nos contate: https://www.settee.io/ https://youtube.com/c/Setteeio Nos acompanhe no Telegram: https://t.me/ideiasradicais Quer comprar Bitcoin no melhor preço do mercado? Bitpreço! http://bit.ly/BitprecoRadical Apoie o Ideias Radicais: https://www.catarse.me/projects/152640/ 0:00 Introdução 2:53 Esquerdistas, miséria e problemas 7:58 Carta pela democracia funciona? 11:35 Lapada no preço da gasolina 14:06 Em que o partido Novo pretende focar para 2024: Prefeitos ou vereadores? 15:39 Grupo de estudos pró-liberdade na universidade é válido ou é pouco? 16:58 Por que você escolheu um partido político ao invés de um movimento? 19:00 Já pensou em trazer o assunto de finanças pro canal? 20:00 Man, Economy and State pela LVM? 20:28 O que você pensa sobre Konkin e agorismo? 22:32 Islândia medieval 24:28 O Milei tem reais chances de levar a presidência da Argentina? 30:08 Haiti Ancap 35:00 Qual é a crítica mais válida sobre o Bitcoin? 35:25 Como fazer o Novo chegar nas massas

Jimmy har varit kriminell hela sitt liv. Men hösten 2019 förändras allt. Han träffar Mikaela och bestämmer sig för att lämna kriminaliteten. Jimmy och Mikaela lever ett till synes vanligt liv med småbarn och villa. Men för bara några år sedan såg allt annorlunda ut.2019 skriver Jimmy in sig på ett LVM-hem för att bli nykter. Där jobbar Mikaela och de får snabbt känslor för varandra. Men de är varandras motsatser.Kärleken får Jimmy att lämna kriminella livsstilenHan har varit kriminell hela sitt liv. Uppväxten kantas av småstölder och snatterier och allt eftersom blir brotten tyngre. Han gör sig ett namn i kriminella kretsar. Driver in skulder, är med i mc-klubbar och skadar människor.Hon är dotter till en militär och uppväxt med vad som är rätt och riktigt.När de träffas bestämmer Jimmy sig för att lämna den kriminella livsstilen men vägen till ett vanligt Svenssonliv visar sig innehålla både utmaningar och krockar för dem båda.Jimmy och Mikaela heter egentligen något annat.Av: Alexandra Sannemalm Producent: Håkan Engström Slutmix: Fredrik Nilsson

Tyler and Jordan review the growth factor for our third installment of the fundamental factors of investing. The growth factor or style of investing focuses on companies that have an above average rate of revenue or earnings growth. Growth investing typically favors younger companies with shorter track records but potentially a new or untapped economic market. They also include investments or companies in new technologies or services. Some companies classified as growth will pay a dividend but, historically, growth companies prioritize reinvesting earnings internally versus paying shareholders in the form of a dividend as they try to grow with their expending economic market. Typically, companies classified as value will return a larger percentage of their earnings to shareholders via dividends. We review two of the largest ETF provider classifications for growth and the factors LVM uses for scoring companies based on growth including, five-year sales growth, five-year earnings per share growth, five-year dividend growth, and projected revenue growth for each of the next two-years. Tyler and Jordan end with reviewing how to combine the value and growth factors for analysis including Craig's quote during our value factor podcast “Value and growth are two sides of the same coin.  A stock is not a good value if there is not some underlying growth, and a growth stock is not a good investment if you pay too high a price.”

table td.shrink { white-space:nowrap } New hosts Welcome to our new host: Kinghezy. Last Month's Shows Id Day Date Title Host 3717 Tue 2022-11-01 Video editing with Shotcut on a low end PC MrX 3718 Wed 2022-11-02 Making Ansible playbooks to configure Single Sign On for popular open source applications Jeroen Baten 3719 Thu 2022-11-03 HPR News Some Guy On The Internet 3720 Fri 2022-11-04 Practicing Batch Files With ECHO Ahuka 3721 Mon 2022-11-07 HPR Community News for October 2022 HPR Volunteers 3722 Tue 2022-11-08 Bash snippet - plurals in messages Dave Morriss 3723 Wed 2022-11-09 HPR News Some Guy On The Internet 3724 Thu 2022-11-10 My top Android apps Archer72 3725 Fri 2022-11-11 How to use OSMAnd with Public Transport Ken Fallon 3726 Mon 2022-11-14 Breaches ever reaching Lurking Prion 3727 Tue 2022-11-15 Expanding your filesystem with LVM Rho`n 3728 Wed 2022-11-16 Pinebook Pro review binrc 3729 Thu 2022-11-17 Contributing to SuperTuxKart Celeste 3730 Fri 2022-11-18 Into Arizona Ahuka 3731 Mon 2022-11-21 Speech recognition in Kdenlive dnt 3732 Tue 2022-11-22 My experience owning an Atari Jaguar m0dese7en 3733 Wed 2022-11-23 Smite Some Guy On The Internet 3734 Thu 2022-11-24 Inetd: the internet super-server binrc 3735 Fri 2022-11-25 i3 Tiling Window Manager Archer72 3736 Mon 2022-11-28 Metasyntactic words Klaatu 3737 Tue 2022-11-29 Review of KOBO Libra H20 e-reader Rho`n 3738 Wed 2022-11-30 Intro to KMyMoney Kinghezy Comments this month These are comments which have been made during the past month, either to shows released during the month or to past shows. There are 25 comments in total. Past shows There are 6 comments on 5 previous shows: hpr3698 (2022-10-05) "Spectrogram" by Klaatu. Comment 2: MrX on 2022-11-04: "What a great tip" hpr3705 (2022-10-14) "The Year of the FreeBSD Desktop" by binrc. Comment 3: binrc on 2022-11-03: "additional links" hpr3711 (2022-10-24) "Cars" by Zen_Floater2. Comment 2: dnt on 2022-11-09: "pedestrians and cyclists" hpr3714 (2022-10-27) "The News with Some Guy On the Internet" by Some Guy On The Internet. Comment 5: Dave Morriss on 2022-11-02: "Beautifully done!" hpr3715 (2022-10-28) "Secret hat conversations, Part 2." by Some Guy On The Internet. Comment 3: Dave Morriss on 2022-11-02: "A very interesting discussion" Comment 4: DeepGeek on 2022-11-03: "Phone, Tiling wm," This month's shows There are 19 comments on 12 of this month's shows: hpr3719 (2022-11-03) "HPR News" by Some Guy On The Internet. Comment 1: mike M. on 2022-11-04: "Another form of typosquatting" hpr3721 (2022-11-07) "HPR Community News for October 2022" by HPR Volunteers. Comment 1: Archer72 on 2022-11-07: "Weirdos" hpr3722 (2022-11-08) "Bash snippet - plurals in messages" by Dave Morriss. Comment 1: rho`n on 2022-11-11: "Great tip!"Comment 2: Dave Morriss on 2022-11-16: "Thanks rho`n" hpr3725 (2022-11-11) "How to use OSMAnd with Public Transport " by Ken Fallon. Comment 1: Kevin O'Brien on 2022-11-14: "Useful and timely" hpr3726 (2022-11-14) "Breaches ever reaching" by Lurking Prion. Comment 1: hammerron on 2022-11-15: "Old LiveJournal" hpr3727 (2022-11-15) "Expanding your filesystem with LVM" by Rho`n. Comment 1: Zen_floater2 on 2022-11-18: "Love server problems" hpr3728 (2022-11-16) "Pinebook Pro review" by binrc. Comment 1: Zen_floater2 on 2022-11-18: "I liked this show."Comment 2: one_of_spoons on 2022-11-21: "Programmable ROM."Comment 3: b on 2022-11-24: "rockchip"Comment 4: sunzu on 2022-11-26: "available distros" hpr3729 (2022-11-17) "Contributing to SuperTuxKart" by Celeste. Comment 1: dnt on 2022-11-17: "Car rambling" hpr3730 (2022-11-18) "Into Arizona" by Ahuka. Comment 1: Clinton Roy on 2022-11-19: "Dam?" hpr3731 (2022-11-21) "Speech recognition in Kdenlive" by dnt. Comment 1: Celeste on 2022-11-21: "didn't know the feature"Comment 2: dnt on 2022-11-22: "re: both libre/opensource" hpr3733 (2022-11-23) "Smite" by Some Guy On The Internet. Comment 1: Lurking Prion on 2022-11-23: "Let's do a show"Comment 2: Some Guy On The Internet on 2022-11-24: "Sure" hpr3734 (2022-11-24) "Inetd: the internet super-server" by binrc. Comment 1: sinza on 2022-11-24: "Great show!"Comment 2: Zen_floater2 on 2022-11-27: "loved this" Mailing List discussions Policy decisions surrounding HPR are taken by the community as a whole. This discussion takes place on the Mail List which is open to all HPR listeners and contributors. The discussions are open and available on the HPR server under Mailman. The threaded discussions this month can be found here: https://hackerpublicradio.org/pipermail/hpr_hackerpublicradio.org/2022-November/thread.html Events Calendar With the kind permission of LWN.net we are linking to The LWN.net Community Calendar. Quoting the site: This is the LWN.net community event calendar, where we track events of interest to people using and developing Linux and free software. Clicking on individual events will take you to the appropriate web page. Any other business HPR RSS feeds and https links A question came up in November regarding the HPR RSS feeds. All of the URLs in these feeds use 'http' as opposed to 'https'. Although this may seem odd, this is a fairly common thing to do, because the RSS standard (such as it is) does not cater for 'https' links. There is a concern that passing an RSS feed with such links to a validator (such as the W3C Feed Validation Service) will result in it being marked as invalid. Older HPR shows on archive.org, phase 2 Now that all shows from number 1 to the latest have been uploaded to the Internet Archive there are other tasks to perform. We are reprocessing and re-uploading shows in the range 871 to 2429 as explained in the Community News show notes released in May 2022. We are keeping a running total here to show progress: Month Month count Running total Remainder 2022-04 130 130 1428 2022-05 140 270 1288 2022-06 150 420 1138 2022-07 155 575 983 2022-08 155 730 828 2022-09 150 880 678 2022-10 155 1035 523 2022-11 230 1265 293 Updated: 2022-12-03 16:10:11

Tyler and Craig review the “Value Factor” for our second installment of the fundamental factors of investing. In the investment industry there are various definitions of the value factor, but one description refers to the value factor as the factor that aims to capture excess returns from stocks that have low prices relative to their fundamental value. This is commonly tracked by price to book, price to earnings, dividends, and free cash flow. Historically it is the price to book valuation method that is most often cited for value investing. With low price to book being classified as a value stock. Price to book simply compares the company's accounting book value or net assets relative to the market capitalization. We review how LVM uses the value factor in finding attractive investments including relative valuation methods such as price to earnings and absolute valuations such as the discounted cash flow method.  Craig reviews some common pitfalls investors come across when analyzing the value factor and discusses some of the historical return studies on value versus growth. Tyler reviews current market valuations and compares them to recent historical averages. 

Synopis I installed a new 1TB Crucial MX500 SSD into my work computer. While we are mostly a Windows based business, as the IT guy I do get a bit of discretion when updating my own machine (i.e. I get to solve all the problems I create). Last year, I decided to run the Pop!_OS distribution of Linux on my work computer and run Windows in a VM on it. Recently the Windows image had grown and was causing disk space notifications. This prompted the additional hard drive. During the initial installation of Pop!_OS, I remember deciding not to bother with installing Linux Volume Management (LVM). I have used it in the past, but I am still much more comfortable with the old style device mapping and mounting disk partitions to directories. I even rationalized that if I needed to add more space, I will just add a new disk with one big partition and map it to the home directory. Now a year later I am adding a new HD and thinking, I really hate all the space that is most likely going to be wasted once I move the Windows image to the new drive. Ok, I guess I should figure out how to install LVM, and use it to manage the space on both drives. Luckily there a number of good blogs to be found on adding LVM to an existing system. The following are the steps and commands I used to accomplish my goal. Commands Most of the following commands need to be run as root. I decided to change to root user instead of typing sudo before every command. The basic steps to creating a single filesystem sharing the storage space between two physical disk partitions are: Let LVM know about the new disk. In my case, create a volume group and add the new disk and its full storage space to it. Copy the disk partition with the root filesystem from the origin disk to the new volume group Expand the root filesystem on the volume group to the full size of the volume group. Update system configuration to boot with the root filesystem on the new volume group. Let LVM know about the old root disk partition. Add the old root partition to the volume group. Expand the root filesystem on the volume group to include the new space in the volume group. root@work# pvcreate /dev/sdb root@work# pvdisplay "/dev/sdb" is a new physical volume of "931.51 GiB" --- NEW Physical volume --- PV Name /dev/sdb VG Name PV Size 931.51 GiB Allocatable NO PE Size 0 Total PE 0 Free PE 0 Allocated PE 0 PV UUID wRBz38-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx root@work# vgcreate workvg /dev/dsb No device found for /dev/dsb. root@work# vgcreate workvg /dev/sdb Volume group "workvg" successfully created root@work# vgdisplay --- Volume group --- VG Name workvg System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 1 VG Access read/write VG Status resizable MAX LV 0 Cur LV 0 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 931.51 GiB PE Size 4.00 MiB Total PE 238467 Alloc PE / Size 0 / 0 Free PE / Size 238467 / 931.51 GiB VG UUID 67DSwP-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx root@work# pvdisplay --- Physical volume --- PV Name /dev/sdb VG Name workvg PV Size 931.51 GiB / not usable 1.71 MiB Allocatable yes PE Size 4.00 MiB Total PE 238467 Free PE 238467 Allocated PE 0 PV UUID wRBz38-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx root@work# lvcreate -n root -L 931.51 workvg Rounding up size to full physical extent 932.00 MiB Logical volume "root" created. root@work# cat /dev/sda3 >/dev/mapper/workvg-root cat: write error: No space left on device Hmmm why can't it copy the smaller disk onto a larger one? root@work# pvdisplay --- Physical volume --- PV Name /dev/sdb VG Name workvg PV Size 931.51 GiB / not usable 1.71 MiB Allocatable yes PE Size 4.00 MiB Total PE 238467 Free PE 238234 Allocated PE 233 PV UUID wRBz38-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx root@work# lvdisplay --- Logical volume --- LV Path /dev/workvg/root LV Name root VG Name workvg LV UUID srXpUd-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx LV Write Access read/write LV Creation host, time work.example.com, 2022-10-18 08:46:34 -0400 LV Status available # open 0 LV Size 932.00 MiB Current LE 233 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 Whoops, the default unit for the lvcreate is MB, and I forgot to add G to my size. A good reason to always include units in whatever you do :) Also, pay attention to any reports printed at the end of a successful command. When I scrolled back I realized it told me the size it created. root@work# lvextend -l +100%FREE /dev/workvg/root Size of logical volume workvg/root changed from 932.00 MiB (233 extents) to 931.51 GiB (238467 extents). Logical volume workvg/root successfully resized. root@work# lvdisplay --- Logical volume --- LV Path /dev/workvg/root LV Name root VG Name workvg LV UUID srXpUd-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx LV Write Access read/write LV Creation host, time work.example.com, 2022-10-18 08:46:34 -0400 LV Status available # open 0 LV Size 931.51 GiB Current LE 238467 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 root@work# cat /dev/sda3 >/dev/mapper/workvg-root root@work# mkdir /media/new-root root@work# mount /dev/mapper/workvg-root /media/new-root root@work# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 450G 421G 5.6G 99% / /dev/sda1 497M 373M 125M 76% /boot/efi /dev/sda2 4.0G 3.4G 692M 84% /recovery /dev/mapper/workvg-root 450G 421G 5.7G 99% /media/new-root Ok, the LV volume is resized but the filesystem now needs to expanded to use the new disk space root@work# umount /media/new-root/ root@work# resize2fs /dev/mapper/workvg-root resize2fs 1.46.5 (30-Dec-2021) Please run 'e2fsck -f /dev/mapper/workvg-root' first. root@work# e2fsck -f /dev/mapper/workvg-root e2fsck 1.46.5 (30-Dec-2021) Pass 1: Checking inodes, blocks, and sizes Inode 7210086 extent tree (at level 2) could be narrower. Optimize? yes Pass 1E: Optimizing extent trees Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/mapper/workvg-root: ***** FILE SYSTEM WAS MODIFIED ***** /dev/mapper/workvg-root: 827287/29974528 files (1.2% non-contiguous), 112395524/119870981 blocks root@work# resize2fs /dev/mapper/workvg-root resize2fs 1.46.5 (30-Dec-2021) Resizing the filesystem on /dev/mapper/workvg-root to 244190208 (4k) blocks. The filesystem on /dev/mapper/workvg-root is now 244190208 (4k) blocks long. root@work# mount /dev/mapper/workvg-root /media/new-root root@work# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 450G 421G 5.5G 99% / /dev/mapper/workvg-root 916G 421G 449G 49% /media/new-root Much better. Now we need to get the computer to boot using LVM and the new drive. Need to make sure /etc/fstab is updated to point to the new root filesystem. Make some in-memory filesystems available under the new root: root@work# mount --rbind /dev /media/new-root/dev root@work# mount --bind /proc /media/new-root/proc root@work# mount --bind /sys /media/new-root/sys root@work# mount --bind /run /media/new-root/run root@work# chroot /media/new-root root@work# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # PARTUUID=949a09f0-xxxx-xxxx-xxxx-xxxxxxxxxxxx /boot/efi vfat umask=0077 0 0 PARTUUID=bbcc2068-xxxx-xxxx-xxxx-xxxxxxxxxxxx /recovery vfat umask=0077 0 0 UUID=9f1f68bb-xxxx-xxxx-xxxx-xxxxxxxxxxxx / ext4 noatime,errors=remount-ro 0 0 /dev/mapper/cryptswap none swap defaults 0 0 root@work# vi /etc/fstab root@work# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # PARTUUID=949a09f0-xxxx-xxxx-xxxx-xxxxxxxxxxxx /boot/efi vfat umask=0077 0 0 PARTUUID=bbcc2068-xxxx-xxxx-xxxx-xxxxxxxxxxxx /recovery vfat umask=0077 0 0 /dev/mapper/workvg-root / ext4 noatime,errors=remount-ro 0 0 /dev/mapper/cryptswap none swap defaults 0 0 root@it05:/media/new-root/etc/initramfs-tools# lsinitramfs /boot/initrd.img-$(uname -r) | grep lvm etc/lvm etc/lvm/lvm.conf etc/lvm/lvmlocal.conf etc/lvm/profile etc/lvm/profile/cache-mq.profile etc/lvm/profile/cache-smq.profile etc/lvm/profile/command_profile_template.profile etc/lvm/profile/lvmdbusd.profile etc/lvm/profile/metadata_profile_template.profile etc/lvm/profile/thin-generic.profile etc/lvm/profile/thin-performance.profile etc/lvm/profile/vdo-small.profile scripts/init-bottom/lvm2 scripts/local-block/lvm2 scripts/local-top/lvm-workaround scripts/local-top/lvm2 usr/lib/udev/rules.d/56-lvm.rules usr/lib/udev/rules.d/69-lvm-metad.rules usr/sbin/lvm root@it05:/# update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.19.0-76051900-generic cryptsetup: WARNING: Resume target cryptswap uses a key file kernelstub.Config : INFO Looking for configuration... kernelstub.Drive : ERROR Could not find a block device for the a partition. This is a critical error and we cannot continue. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 56, in __init__ self.esp_fs = self.get_part_dev(self.esp_path) File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 94, in get_part_dev raise NoBlockDevError('Couldn't find the block device for %s' % path) kernelstub.drive.NoBlockDevError: Couldn't find the block device for /boot/efi run-parts: /etc/initramfs/post-update.d//zz-kernelstub exited with return code 174 root@it05:/# lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sda ├─sda1 │ vfat FAT32 D499-28CF ├─sda2 │ vfat FAT32 D499-2B97 ├─sda3 │ ext4 1.0 9f1f68bb-xxxx-xxxx-xxxx-xxxxxxxxxxxx └─sda4 swap 1 1758e7a0-xxxx-xxxx-xxxx-xxxxxxxxxxxx └─cryptswap swap 1 cryptswap e874c9cc-xxxx-xxxx-xxxx-xxxxxxxxxxxx [SWAP] sdb LVM2_m LVM2 wRBz38-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx └─workvg-root ext4 1.0 9f1f68bb-xxxx-xxxx-xxxx-xxxxxxxxxxxx 448.6G 46% / root@it05:/# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/workvg-root 916G 421G 449G 49% / tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs 1.6G 2.4M 1.6G 1% /run root@it05:/# mount /dev/sda1 /boot/efi root@it05:/# update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.19.0-76051900-generic cryptsetup: WARNING: Resume target cryptswap uses a key file kernelstub.Config : INFO Looking for configuration... kernelstub : INFO System information: OS:..................Pop!_OS 22.04 Root partition:....../dev/dm-1 Root FS UUID:........9f1f68bb-xxxx-xxxx-xxxx-xxxxxxxxxxxx ESP Path:............/boot/efi ESP Partition:......./dev/sda1 ESP Partition #:.....1 NVRAM entry #:.......-1 Boot Variable #:.....0000 Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash Kernel Image Path:.../boot/vmlinuz-5.19.0-76051900-generic Initrd Image Path:.../boot/initrd.img-5.19.0-76051900-generic Force-overwrite:.....False kernelstub.Installer : INFO Copying Kernel into ESP kernelstub.Installer : INFO Copying initrd.img into ESP kernelstub.Installer : INFO Setting up loader.conf configuration kernelstub.Installer : INFO Making entry file for Pop!_OS kernelstub.Installer : INFO Backing up old kernel kernelstub.Installer : INFO Making entry file for Pop!_OS ok, moment of truth, can i reboot into the new root filesystem root@it05:/# shutdown -r now Running in chroot, ignoring request. root@it05:/# exit root@work# shutdown -r now Whoot! Success. Booted right back up, and can verify running from new LV rhorning@icon-n.com@it05:~$ df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/workvg-root 916G 421G 449G 49% / /dev/sda1 497M 373M 125M 76% /boot/efi Next step, add the original root partition (/dev/sda3) to the volume group so there is 1.5Gb available to the filesystem root@work# pvcreate /dev/sda3 WARNING: ext4 signature detected on /dev/sda3 at offset 1080. Wipe it? [y/n]: y Wiping ext4 signature on /dev/sda3. Physical volume "/dev/sda3" successfully created. root@work# vgextend workvg /dev/sda3 Volume group "workvg" successfully extended root@work# vgdisplay --- Volume group --- VG Name workvg System ID Format lvm2 Metadata Areas 2 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 1 Max PV 0 Cur PV 2 Act PV 2 VG Size

The focus of the new Ubuntu release, Gitea's surprising announcement, and Linux prepares to drop another architecture.

The Internet is going crazy with AI-generated media. What's the open-source story, and is Linux being left out? Plus, we try out the new Ubuntu release on the ODROID H3+.

Linus Tech Tips blows it again, and we clean up. Plus, we push System76's updated Thelio Workstation to the breaking point.

A História do Brasil Império é recheada de fatos curiosos e desconhecidos. Diferentes personagens dessa época foram responsáveis pela formação de um novo país, agora independente de Portugal. Neste contexto, surge nossa primeira Constituição, um exemplo de descentralização de poder em todo o mundo, em contraste ao absolutismo tão caro a outras monarquias da época. Inclusive, Dom Pedro I, autor da Constituição de 1824, foi também responsável pela Constituição portuguesa de 1826. Nesta semana, damos continuidade ao papo entre Rodrigo Marinho e os editores da LVM, Chiara Ciadarot e Pedro Henrique Alves.

Lotta Lubkoll hat einen Kindheitstraum: einmal mit einem Esel auf Wanderschaft gehen. Doch erst als ihr Vater plötzlich erkrankt und kurz darauf stirbt, wird ihr klar, dass man solche Träume nicht auf die lange Bank schieben sollte. Sie macht sich also auf die Suche – und findet Jonny, einen grau-weißen Esel wie aus dem Bilderbuch. Gemeinsam ziehen die beiden los, zu Fuß von München immer Richtung Süden. Was Lotta auf der dreimonatigen Tour mit ihrem eseligen Begleiter erlebte, erfahrt ihr in dieser Episode des Weltwach Podcast. Mit im Gespräch dabei: Tropenökologin und Ameisenbärenforscherin Lydia Möcklinghoff!WERBUNGIhr plant gerade eure nächste Reise? Ein gutes Gefühl gibt euch dabei die Reiserücktrittsversicherung der LVM - mit marktüberdurchschnittlichen Leistungen und günstigen Preisen seid ihr bei Reiserücktritt – oder -abbruch bestens abgesichert. Weitere Infos und den Online-Abschluss findet ihr unter: www.lvm.de/reiseversicherungen See acast.com/privacy for privacy and opt-out information.

Atemberaubende Aufnahmen von fernen und nahen Orten, von Grizzlybären über Bullenhaie bis hin zum Feldhamster und wilden Honigbienen – dafür steht Deutschlands wohl renommiertestem Natur- und Tierfilmer, Andreas Kieling.In dieser Episode von Weltwach erzählt er von seinem Leben, von Dreharbeiten in aller Welt, von gefährlichen Situationen und magischen Momenten, und davon, was ihn heute bei seiner Arbeit antreibt.Andreas Kieling veröffentlichte Reportagen und Aufnahmen in zahlreichen Tageszeitungen sowie großen Magazinen wie „Geo" und „Stern". Zu seinen Büchern gehören „Im Bann der Bären“, „Meine Expeditionen zu den Letzten ihrer Art“, „Yukon-River-Saga“, „Bären, Lachse, wilde Wasser“, „Durchs wilde Deutschland“ und – aktuell – „Kielings Kleine Waldschule“, jeweils erschienen bei Piper Malik. Seine Filme werden weltweit über National Geographic Channel ausgestrahlt. Dem deutschen Publikum ist er u. a. durch die ZDF-Serie „Terra X: Kieling – Expeditionen zu den Letzten ihrer Art“ bekannt. Für den ARD-Dreiteiler „Abenteuer Erde – Yukon River" wurde er mit dem Panda Award ausgezeichnet, dem Oscar des Tierfilms.Homepage von Andreas Kieling: https://www.andreas-kieling.de/Andreas Kielings Kleine Waldschule auf Facebook: https://www.facebook.com/Andreas.KielingWERBUNGLVM VersicherungIhr plant gerade eure nächste Reise? Ein gutes Gefühl gibt euch dabei die Reiserücktrittsversicherung der LVM - mit marktüberdurchschnittlichen Leistungen und günstigen Preisen seid ihr bei Reiserücktritt – oder -abbruch bestens abgesichert. Weitere Infos und den Online-Abschluss findet ihr unter: www.lvm.de/reiseversicherungenTOURLANETOURLANE ist eine Online-Reisebuchungsplattform der besonderen Art. Hier stellen Reiseexperten für dich individuelle und unvergessliche Trips zusammen. Sie machen die komplette Reiseplanung, angefangen von den Unterkünften über die Flüge bis hin zu den Routen und Aktivitäten. Lass dir unverbindlich und kostenfrei eine Traumreise nach deinen Wünschen zusammenstellen. Probiere es jetzt aus und gehe auf www.tourlane.de/weltwach.Wichtig: Mit dem Rabattcode „Weltwach200“ bekommst du 200 Euro Rabatt auf deine erste Reise. See acast.com/privacy for privacy and opt-out information.

Ein Mensch, der das scheinbar Unmögliche möglich macht. So würden wir Tom Belz beschreiben, der sich, nachdem er mit acht Jahren infolge einer Knochenkrebsdiagnose ein Bein verlor, nicht von diesem Umstand aufhalten ließ. In diese Episode erzählt Tom von emotionalen Berg- und Talfahrten und dem Neuerlernen von vermeintlich alltäglichen Aktivitäten. Und er erzählt von seinem wohl bisher größten Abenteuer: Mit einem Bein (und handelsüblichen Krücken!) den Kilimandscharo zu besteigen! Tom berichtet, wie er den Aufstieg des höchsten Bergs Afrikas erlebte, welche Herausforderungen ihm begegneten und wie er den Moment empfand, als er schließlich am Gipfel ankam. Neben einem Film (“Mbuzi Dume - Strong Goat” – entstanden im Rahmen der European Outdoor Film Tour 2018/19) erschienen außerdem zwei Bücher: “Do what you can't” (Fischer Verlag) und das Kinderbuch “Kleiner Löwe großer Mut – Eine Mutmachgeschichte inspiriert von Tom Belz” (arsedition). Wir wünschen: Viel Spaß mit dieser mutmachenden Episode!Tom Belz auf Instagram: https://www.instagram.com/tomnative/WERBUNGIhr wollt den Klimandscharo besteigen oder habt andere spannende Reiseziele? Die Auslandskrankenversicherung der LVM schützt euch vor hohen Kosten bei Krankheiten oder Unfällen im Ausland – für bis zu acht Wochen mit marktüberdurchschnittlichen Leistungen. Weitere Infos und den Online-Abschluss findet ihr unter: www.lvm.de/reiseversicherungenWillkommen im Paradies: Wo die Sonne vom Himmel lacht und der Mond eine Treppe zur Erde schickt, wo Kängurus am Strand liegen und Delfine zum Frühstück vorbeischauen, wo man in Felsenpools baden und unter Wasserfällen duschen kann, wo das Didgeridoo erklingt, und die Regenbogenschlange wohnt, dort liegt Westaustralien. Inspirationen für dein ganz persönliches Westaustralien-Abenteuer findest du unter: www.westernaustralia.com/de See acast.com/privacy for privacy and opt-out information.

LVM 8x103 | Curb your enthusiasm

LVM 8x102 | La última oportunidad.

LVM 8x100 | Programa cien.

LVM 8x96 | Se vienen boicots.