Podcasts about refactoring

Nach einer kurzen Frühlingspause melden sich Alois und Oliver mit einer Jam-Session zurück und widmen sich der Frage, wie Unternehmen – vom Start-up bis zum Weltkonzern – sowie Staaten eine praxisnahe KI-Strategie entwickeln und umsetzen können.Vom Buzzword zur WertschöpfungKI wird inflationär benutzt; echte Orientierung fehlt.Erster Schritt: konkrete Use-Cases in den eigenen Kernprozessen identifizieren, statt PowerPoint-Strategien zu schreiben oder externe Schablonen blind zu kopieren.Schnell ins Tun kommenArbeitskreise bremsen – lieber Sandbox-Ansätze nutzen und mit fertigen Toolchains experimentieren.Erfolg wird an harten Metriken gemessen: Durchlaufzeiten, Qualität, Kosten.Datenkompetenz & Compliance als FundamentAufbau von Data-Literacy und Klarheit über IP-relevante Daten.Recht, Datenschutz und Betriebsrat müssen mitgenommen werden, aber erst nach dem Use-Case-Proof, um Hürden nicht künstlich aufzublähen.Legacy als Chance statt LastAlte Systemlandschaften gleichen Jenga-Türmen – riskant, aber ersetzbar.KI ermöglicht Refactoring in Wochen statt Jahren und bietet Hidden Champions ein „Leapfrog“-Potenzial, Märkte zu disruptieren.Ressourcen & KulturwandelRiesige IT-Abteilungen müssen neu gedacht werden: Produktivität steigt x-fach durch KI-gestützte Entwicklung.Organisationen – bis hin zu Staaten – brauchen Tempo, Agilität und eine klare Haltung zu Responsible AI.IP neu definierenIn einer Welt generativer Modelle verlieren Source-Code-Monopole an Gewicht; Patente und Marktdurchdringung gewinnen relativ an Bedeutung.Globale Standardisierungsgremien suchen nach neuen Regeln für Urheberrecht und Patentschutz.FazitZaudern ist keine Option: Wer die Lernkurve verpasst, wird für Talente unattraktiv und verliert Wettbewerbsvorteile.Zugleich braucht es bewusste Grenzen („Wo setzen wir KI nicht ein?“), um Werte, Ethik und Unabhängigkeit zu sichern.

Kristen Shaker joins Timur and Phil. Kristen talks to us about her C++ on Sea keynote about the C++ interview process, her previous work at Google, and why she has made a slightly unusual career change. Show Notes News libc++ removed the base template for std::char_traits "how to break or continue from a lambda loop?" - Vittoria Romeo Results from the 2025 Annual C++ Developer Survey "Lite" (pdf) Links C++ on Sea schedule (with Kristen and Timur's keynotes) BrontoSource "What Can We Learn From the Results of C++ Community Surveys?" - Anastasia Kazakova "Sorting Resumes" - Joel Spolsky (introducing the idea of filtering) "How to Build Your First C++ Automated Refactoring Tool" - Kristen's CppCon 2023 talk

In this episode, Amir sits down with Brent Keator, an expert advisor at Primary Venture Partners, to unpack one of the most debated engineering challenges: tech debt versus reengineering. They explore how to define tech debt, when to refactor versus rebuild, the ROI of revisiting old code, and how AI is (and isn't) changing the equation. This is a must-listen for engineering leaders navigating complex technical decisions in fast-moving environments.

Parliamo di refactoring. Cosa vuol dire fare refactoring di un software, perché farlo, quando farlo ma soprattutto come spiegare in azienda e al tuo cliente l'importanza di questo passaggio, che sarà fondamentale per colmare eventuale debito tecnico e assicurare lunga vita al tuo applicativo.Ascoltaci!

Ponad 2000 osób w 500 zespołach, 3000 różnych mikroserwisów i kilkaset tysięcy eventów na sekundę - skala Allegro zawsze robi wrażenie. Jak w tym wszystkim wdrożono architekturę mikrofrontendów, która pozwala sprawnie łączyć różne mikroserwisy i tworzyć podstrony największego w Polsce e-commerce'u prosto z panelu?W drugiej części rozmowy o mikrforontendach, Bartosz Gałek, Principal Engineer w Allegro, uchyli rąbka tajemnicy i przedstawi trochę technikaliów. W tym odcinku usłyszysz między innymi o:skali systemu, z jaką mierzą się zespoły developerskie Allegrowybranych metrykach zapewniających observability systemu od strony frontendowejprojektowaniu optymalizacji i zapewnianiu dużej wydajności systemuprojektowaniu stron portalu z użyciem komponentów i wprowadzaniu nowych funkcjonalności na produkcjęstreamingu HTML-astopniowej migracji monolitu do architektury mikroserwisowejDzięki Bartkowi mamy możliwość zajrzeć za kulisy i zobaczyć co się dzieje "pod maską" Allegro, gdy odwiedzasz przykładowo podstronę interesującego Cię produktu. I dlaczego, dzięki stosowanym rozwiązaniom i optymalizacjom, jest to tak wydajne...Materiały dodatkowe do tego odcinka znajdują się na stronie tego odcinka na bettersoftwaredesign.pl.YouTube Alert! Odcinki podcastu są także dostępne na moim kanale na YouTube. Warto zasubskrybować, aby być na bieżąco z kolejnymi odcinkami.

Produktqualität ist ein Thema, das Product Owner immer wieder vor Herausforderungen stellt. In der neuesten Episode der Produktwerker sprechen Oliver und Dominique darüber, wie Product Owner das Bewusstsein für Qualität im gesamten Team stärken können. Denn schlechte Produktqualität kann nicht nur die Nutzererfahrung negativ beeinflussen, sondern auch den Arbeitsfluss des Teams stören und langfristig viele negative Folgen verursachen. Die Verantwortung für die Produktqualität wird in vielen agilen Produktteams unterschiedlich wahrgenommen. Während Entwickler häufig die technische Qualität in den Fokus stellen, müssen Product Owner sicherstellen, dass das Produkt nicht nur funktional, sondern auch nutzerzentriert und nachhaltig entwickelt wird. Hier entsteht schnell ein Spannungsfeld zwischen Geschwindigkeit und Sorgfalt. Oliver und Dominique sind sich einig: Qualität, egal über welche Perspektive man spricht, ist nicht verhandelbar. In einem iterativen Entwicklungsprozess muss Qualität von Anfang an mitgedacht und konsequent umgesetzt werden, damit ein stabiles, erweiterbares und zukunftsfähiges Produkt entsteht. Auf der einen Seite ist die äußere Produktqualität wichtig, also wie Nutzer das Produkt erleben. Um sicherzustellen, dass ein Produkt einen Beitrag zur Problemlösung leisten kann, ist es wichtig, die Erwartungshaltung von Nutzern genau zu kennen und Metriken zur Messung der Nutzererfahrung zu etablieren. Product Owner können Qualität in den Fokus rücken, indem sie diese Metriken nicht nur bei der Entwicklung neuer Features berücksichtigen, sondern auch in Reviews und strategische Entscheidungen mit einfließen lassen. Ebenso bedeutend ist die innere Qualität, also die technische Exzellenz des Produkts. Ein schlecht strukturierter Code kann langfristig zu Problemen führen, die die Entwicklung verlangsamen und Innovationen erschweren. Daher ist es wichtig, dass Product Owner Raum für technische Verbesserungen und nachhaltige Entwicklungspraktiken wie automatisierte Tests oder Refactoring schaffen. Hier sollten sie mit Entwicklern und dem Scrum Master offen diskutieren, wie viel Zeit für technische Qualität eingeplant wird, um langfristig effizient zu bleiben. Ein weiterer Faktor ist die Zusammenarbeit im Team. Qualität entsteht nicht nur durch technisches Können, sondern auch durch gute Kommunikation, klare Verantwortlichkeiten und Vertrauen. Product Owner sollten in Retrospektiven gezielt das Thema Produktqualität ansprechen und gemeinsam mit dem Team reflektieren, welche Maßnahmen Qualität langfristig sichern können. Auch psychologische Sicherheit spielt eine Rolle: Teammitglieder müssen sich trauen, Probleme offen anzusprechen, um Verbesserungen anzustoßen. Ein starkes Qualitätsbewusstsein entsteht nicht von heute auf morgen. Es erfordert kontinuierliche Aufmerksamkeit, einen gemeinsamen Anspruch an Exzellenz und eine Kultur der Zusammenarbeit. Product Owner haben dabei die Aufgabe, das Thema Qualität immer wieder ins Bewusstsein zu rufen und durch ihr eigenes Verhalten vorzuleben. Denn nur so kann langfristig ein Produkt entstehen, das sowohl technisch robust als auch für Nutzer wertvoll ist.

Today's guest is Joel Chippindale!Joel is a full-time CTO Coach and one of the coaches-in-residence in the Refactoring community, where he runs monthly mastermind sessions and other community events.So with Joel, we dived into what coaching is, the difference with mentoring, one-on-one versus group coaching, and what are the top challenges that CTO faces today, based on the work that Joel does with his coaches.02:34 Introduction03:40 Joel's journey in tech05:21 Finding a definition of coaching07:25 Mentoring and coaching roles10:22 One-to-on and group coaching12:53 The "hows" of coaching15:12 Is coaching a widespread practice?18:35 Top CTOs challenges21:43 Right support for right challenges26:08 Advocating for technical work31:53 Commonalities and uniquenesses in CTOs challenges34:20 The platonic ideal of CTO36:49 Choosing what to focus on39:48 How to delegate properly—This episode is brought to you by https://workos.com—You can also find this at:-

Stewart Alsop sat down with Nick Ludwig, the creator of Kibitz and lead developer at Hyperware, to talk about the evolution of AI-powered coding, the rise of agentic software development, and the security challenges that come with giving AI more autonomy. They explored the power of Claude MCP servers, the potential for AI to manage entire development workflows, and what it means to have swarms of digital agents handling tasks across business and personal life. If you're curious to dive deeper, check out Nick's work on Kibitz and Hyperware, and follow him on Twitter at @Nick1udwig (with a ‘1' instead of an ‘L').Check out this GPT we trained on the conversation!Timestamps00:00 Introduction to the Crazy Wisdom Podcast00:52 Nick Ludwig's Journey with Cloud MCP Servers04:17 The Evolution of Coding with AI07:23 Challenges and Solutions in AI-Assisted Coding17:53 Security Implications of AI Agents27:34 Containerization for Safe Agent Operations29:07 Cold Wallets and Agent Security29:55 Agents and Financial Transactions33:29 Integrating APIs with Agents36:43 Discovering and Using Libraries43:19 Understanding MCP Servers47:41 Future of Agents in Business and Personal Life54:29 Educational and Medical Revolutions with AI56:36 Conclusion and Contact InformationKey InsightsAI is shifting software development from writing code to managing intelligent agents. Nick Ludwig emphasized how modern AI tools, particularly MCP servers, are enabling developers to transition from manually coding to overseeing AI-driven development. The ultimate goal is for AI to handle the bulk of programming while developers focus on high-level problem-solving and system design.Agentic software is the next frontier of automation. The discussion highlighted how AI agents, especially those using MCP servers, are moving beyond simple chatbots to autonomous digital workers capable of executing complex, multi-step tasks. These agents will soon be able to operate independently for extended periods, executing high-level commands rather than requiring constant human oversight.Security remains a major challenge with AI-driven tools. One of the biggest risks with AI-powered automation is security, particularly regarding prompt injection attacks and unintended system modifications. Ludwig pointed out that giving AI access to command-line functions, file systems, and financial accounts requires careful sandboxing and permissions to prevent catastrophic errors or exploitation.Containerization will be critical for safe AI execution. Ludwig proposed that solutions like Docker and other containerization technologies can provide a secure environment where AI agents can operate freely without endangering core systems. By restricting AI's ability to modify critical files and limiting its spending permissions, businesses can safely integrate autonomous agents into their workflows.The future of AI is deeply tied to education. AI has the potential to revolutionize learning by providing real-time, personalized tutoring. Ludwig noted that LLMs have already changed how people learn to code, making complex programming more accessible to beginners. This concept can be extended to broader education, where AI-powered tutors could replace traditional classroom models with highly adaptive learning experiences.AI-driven businesses will operate at unprecedented efficiency. The conversation explored how companies will soon leverage AI agents to handle research, automate customer service, generate content, and even manage finances. Businesses that successfully integrate AI-powered workflows will have a significant competitive edge in speed, cost reduction, and adaptability.We are on the verge of an "intelligence explosion" in both AI and human capabilities. While some fear AI advancements will outpace human control, Ludwig argued that AI will also dramatically enhance human intelligence. By offloading cognitive burdens, AI will allow people to focus on creativity, strategy, and high-level decision-making, potentially leading to an era of rapid innovation and problem-solving across all industries.

Artificial intelligence is radically transforming software development. AI-assisted coding tools are generating billions in investment, promising faster development cycles, and shifting engineering roles from code authors to code editors. But how does this impact software quality, security, and team dynamics? How can product teams embrace AI without falling into the hype? In this episode, AI assisted Agile expert Mike Gehard shares his hands-on experiments with AI in software development. From his deep background at Pivotal Labs to his current work pushing the boundaries of AI-assisted coding, Mike reveals how AI tools can amplify quality practices, speed up prototyping, and even challenge the way we think about source code. He discusses the future of pair programming, the evolving role of test-driven development, and how engineers can better focus on delivering user value. Unlock the full potential of your product team with Integral's player coaches, experts in lean, human-centered design. Visit integral.io/convergence for a free Product Success Lab workshop to gain clarity and confidence in tackling any product design or engineering challenge. Inside the episode... Mike's background at Pivotal Labs and why he kept returning How AI is changing the way we think about source code as a liability Why test-driven development still matters in an AI-assisted world The future of pair programming with AI copilots The importance of designing better software in an AI-driven development process Using AI to prototype faster and build user-facing value sooner Lessons learned from real-world experiments with AI-driven development The risks of AI-assisted software, from hallucinations to security Mentioned in this episode Mike's Substack: https://aiassistedagiledevelopment.substack.com/ Mike's Github repo: https://github.com/mikegehard/ai-assisted-agile-development Pivotal Labs: https://en.wikipedia.org/wiki/Pivotal_Labs 12-Factor Apps: https://12factor.net/  GitHub Copilot: https://github.com/features/copilot Cloud Foundry: https://en.wikipedia.org/wiki/Cloud_Foundry Lean Startup by Eric Ries: https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898 Refactoring by Martin Fowler and Kent Beck https://www.amazon.com/Refactoring-Improving-Existing-Addison-Wesley-Signature/dp/0134757599 Dependabot: https://github.com/dependabot Tessl CEO Guy Podjarny's talk: https://youtu.be/e1a3WuxTY-k  Aider AI Pair programming terminal: https://aider.chat/ Gemini LLM: https://gemini.google.com/app Perplexity AI: https://www.perplexity.ai/ DeepSeek: https://www.deepseek.com/ Ian Cooper's talk on TDD: https://www.youtube.com/watch?v=IN9lftH0cJc Mike's newest Mountain Bike IBIS Ripmo V2S: https://www.ibiscycles.com/bikes/past-models/ripmo-v2s Mike's recommended house slippers: https://us.giesswein.com/collections/mens-wool-slippers/products/wool-slippers-dannheim Sorba Chattanooga Mountain Biking Trails: https://www.sorbachattanooga.org/localtrails Subscribe to the Convergence podcast wherever you get podcasts, including video episodes on YouTube at youtube.com/@convergencefmpodcast Learn something? Give us a 5-star review and like the podcast on YouTube. It's how we grow.

Ivett Ördög speaks with host Sam Taggart about rewrite versus refactor -- a choice that many projects face as they grow. It's a topic that inspires a lot of dogmatic feelings. They discuss how companies and projects end up at this crossroads and consider some strategies to try to avoid it. Ivett challenges the myth that you should never rewrite but points to two key factors that need to be present for a successful large-scale rewrite or refactor. They end by talking about how to get management on board for such large-scale rewrite or refactor projects. Brought to you by IEEE Computer Society and IEEE Software magazine.

To open the show, Ben and Andrew dive into the latest headlines about DeepSeek from last week. We answer questions like “why did everyone search ‘Jevons paradox'?” and discuss strategic AI investments from financial giants like Goldman Sachs. These moves underscore the growing importance of strong engineering leadership in the age of AI.Then, Luca Rossi of Refactoring joins us to discuss his latest research. Drawing from a comprehensive survey of engineering professionals (thanks to you!), Luca breaks down the key traits and practices of successful engineering teams, revealing surprising correlations between team happiness, shipping frequency, and recognition by non-technical leadership.Be sure to grab your copy of the report to follow along with today's insights.Show Notes:Dev Interrupted SurveyBeyond the DORA FrameworksIntroducing AI-Powered Code Review with gitStreamBook a demoFollow the hosts:Follow BenFollow AndrewFollow today's guest:Follow LucaReferenced in today's show:IBM cashing in on AIAI Stocks: How DeepSeek Changed Views On U.S.-China Artificial Intelligence Competition | Investor's Business DailyWilliam Stanley JevonsGoldman Sachs hires Amazon exec in senior AI engineering role | ReutersSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

Scott and Wes explore the world of coding agents, diving into tools like Cursor and Windsurf that promise to change how we write and manage code. They discuss modes, workflows, and practical tips for experimenting with these AI-powered tools in your next project. Show Notes 00:00 Welcome to Syntax! 04:12 What are AI Agents? Cursor Features, Windsurf Features. 07:25 Brought to you by Sentry.io. 07:50 Chat Mode. 08:11 Composer Mode. 08:55 Agent Mode. 10:03 Inline Chat Mode. 11:02 JavaScript Set Methods Demo. Wes' Example on X. 16:10 Fire Dispatch Data. 20:01 Rules Files. Cursor Directory. 22:37 Use screenshots. 23:36 Refactoring to separate files. 23:53 Use it to experiment. Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

In this episode of The BlueHat Podcast, hosts Nic Fillingham and Wendy Zenone are joined by BlueHat 2024 presenter Joe Bialek, a security engineer at Microsoft with over 13 years of experience. Joe shares his fascinating journey from intern to red team pioneer, recounting how he helped establish the Office 365 Red Team and pushed the boundaries of ethical hacking within Microsoft. He discusses his formative years building sneaky hacking tools, navigating the controversial beginnings of red teaming, and transitioning to the Windows Security Team to focus on low-level security and mitigations. Joe reflects on the challenges of internal hacking, the human reactions to being "hacked," and the value of strengthening defenses before external threats arise.    In This Episode You Will Learn:     How Microsoft is developing tooling to identify and address bad programming patterns  Why kernel-related discussions are primarily focused on Windows and driver developers  The challenges developers face when reading and writing through pointers in C or C++    Some Questions We Ask:    How does working with the Windows kernel impact system security and performance?  What sets Windows kernel and driver development apart from other types of development?  Why should internal teams test systems for vulnerabilities before external hackers?      Resources:       View Joe Bialek on LinkedIn   View Wendy Zenone on LinkedIn    View Nic Fillingham on LinkedIn     BlueHat 2024 Session: Pointer Problems – Why We're Refactoring the Windows Kernel    Related Microsoft Podcasts:     Microsoft Threat Intelligence Podcast    Afternoon Cyber Tea with Ann Johnson    Uncovering Hidden Risks        Discover and follow other Microsoft podcasts at microsoft.com/podcasts    The BlueHat Podcast is produced by Microsoft and distributed as part of N2K media network. 

In this episode of Tech Talks Daily, I explore the cutting-edge intersection of AI and software development with Justine Gehring, an AI researcher at Moderne and the author of AI for Mass-Scale Code Refactoring and Analysis. Justine shares her insights into how AI is addressing one of the most complex challenges in the industry: large-scale code migrations and updates across enterprise environments. While AI tools like GitHub Copilot and ChatGPT have excelled at assisting individual developers with writing and optimizing code, Justine explains how large-scale code refactoring requires an entirely different approach. At this level, AI must account for enterprise-wide complexity, maintain reliability, and ensure security across thousands of repositories. She also dives into Moderne's use of open-source frameworks like OpenRewrite, which enable deterministic, verifiable code changes and combine machine learning for targeted tasks. We also discuss how this transformative use of AI is reshaping collaboration between human developers and machines. From accelerating the onboarding process for developers to simplifying migrations for legacy systems, AI is offering groundbreaking opportunities to enhance productivity, maintainability, and innovation. How are industries like banking, insurance, and others with vast, complex codebases benefiting from these advancements? And what does the future hold for AI-human collaboration in software development? Tune in to find out.

"il faut que tu kiffes ce que tu es en train de faire. Et coder fait partie des choses que je kiffe" Le DEV de la semaine est Alex Delivet, Fondateur @ Collect. Alex partage son retour au développement après dix ans d'absence, tout en dirigeant Collect, une plateforme SaaS spécialisée dans la collecte de documents. Il met en lumière les défis des développeurs modernes, entre choix technologiques, gestion de startup, et compétences variées comme le marketing. Alex insiste sur l'importance de l'apprentissage constant, valorisant une approche collaborative et ouverte au recrutement. Il conclut que le développement est un domaine accessible à tous, demandant une diversité de compétences et un engagement dans l'évolution continue des technologies.Chapitrages00:00:59 : Introduction à l'apprentissage du code00:01:08 : Le besoin de coder par nécessité00:04:41 : Lancer un projet sans savoir coder00:13:13 : Stratégies d'apprentissage et de planification00:15:08 : Méthodes et réflexions sur le développement00:18:15 : Choix de la technologie et de la stack00:20:44 : Ressources et défis techniques en entreprise00:24:52 : Approche pragmatique et feedback en production00:34:11 : Accueillir un développeur dans l'équipe00:37:30 : Réécritures et évolutions de code00:38:00 : Refactoring et optimisation avec l'IA00:42:28 : Évolution de la perception du métier de dev00:50:23 : Réflexions sur l'entrepreneuriat et le développement00:54:28 : Limites rencontrées en tant que développeur Liens évoqués pendant l'émission How Canva Saved $22 Million Annually by Optimizing AWS S3 Storage 🎙️ Soutenez le podcast If This Then Dev ! 🎙️ Chaque contribution aide à maintenir et améliorer nos épisodes. Cliquez ici pour nous soutenir sur Tipeee 🙏Archives | Site | Boutique | TikTok | Discord | Twitter | LinkedIn | Instagram | Youtube | Twitch | Job Board |

פרק מספר 487 של רברס עם פלטפורמה - באמפרס מספר 85: רן, דותן ואלון באולפן הוירטואלי עם סדרה של קצרצרים שתפסו את תשומת הלב בתקופה האחרונה - בלוגים מעניינים, דברים מ- GitHub, וכל מיני פרויקטים מעניינים או דברים יפים שראינו באינטרנט וחשבנו לאסוף ולהביא אליכם.וכמיטב המסורת לאחרונה - גם לא מעט AI, כי על זה הצעירים מדברים בזמן האחרון.

Cits and Civs, Captains and Commanders, you’re tuned to episode 508 of Guard Frequency — the best damn space game podcast ever! This episode was recorded on Friday, December 20 and released for streaming and download on Tuesday, December 24, 2024 at GuardFrequency.com [Download this episode](Right click, Save As…) This Week’s Schedule Links & The […]

What does it take to shift from fear to flow when reading and refactoring code? In this episode of the Mob Mentality Show, we dive deep into **"Paradigms of Code Reading"**, exploring the mindsets and techniques that shape how developers approach software understanding. Whether you're navigating legacy code or striving for clean, maintainable designs, this discussion offers actionable insights for individuals, pairs, and mobs alike.   ### What You'll Learn in This Episode:   - **Code Reading Paradigms**: Discover the two ends of the spectrum:     - **Understand Every Line**: Keeping every detail in your head.     - **Extreme Abstraction Zen**: Focusing only on the current module or method.   - **AB Testing in Code Reading**: Insights from live experiments on how pairs and mobs read and understand code.   - **The Role of Trust**: How levels of trust in variable names, methods, and classes influence reading strategies.   - **Overcoming Fear and Skepticism**: What causes developers to ignore method names or distrust the knowledge baked into the code?   - **Cognitive Load and Flow Efficiency**: Learn how reducing cognitive load through small, fast tests can lead to more effective coding sessions.   - **Code Reading Clubs**   - **Coaching Toward Abstraction Zen**: Practical strategies to influence and support others in adopting better reading and refactoring paradigms.   - **Embracing Skeptics**: The value of radical candor, genuine curiosity, and visual aids like diagrams in addressing fear and building trust.   ### Key Takeaways:   - Refactoring starts with trust - Genuine curiosity can replace complaints, transforming how teams collaborate and learn.   - Drawing pictures and visualizing code can unlock new perspectives and improve comprehension.   - Skeptics are not obstacles—they're opportunities for deeper conversations and better design.   Whether you're a seasoned software engineer, a pair programming enthusiast, or new to mob programming, this episode will provide you with practical tools and thought-provoking questions to enhance your coding practice.  

In this episode of the Mob Mentality Show, we dive into our Software Professional Resources Board, a dynamic Trello-based hub designed for software professionals looking to enhance their learning and collaboration in the industry. Join us as we share the board's origin story and our journey in creating a comprehensive resource for everything from Extreme Programming (XP), mobbing, and leadership to cloud infrastructure, agile retrospectives, lean principles, and much more. ### What Makes Our Board Unique? We start by exploring why we chose **Trello** for our resource board and how it has become a cornerstone for organizing, sharing, and discovering knowledge. With its flexibility, Trello enables us to create an easily navigable environment, where resources are not only organized but can also be searched, linked, and explored across various software domains. Our conversation touches on other similar boards we've seen, like our popular "Retrospective Techniques for Coaches, Scrum Masters, and Facilitators" board, as well as spin-offs we've created for specific topics. ### A Variety of Topics Our board covers a broad spectrum of topics that are essential for modern software professionals, including **mobbing**, **refactoring**, **leadership**, **Infrastructure as Code (IaC)**, **agile** practices, and more. With resources curated for both technical and strategic learning, the board has become a go-to reference for articles, blog posts, videos, academic papers, book links, and quotes on various disciplines within software development. ### How We Use the Board for Continuous Learning Discover how we leverage the board not only to organize information but to foster continuous learning. We discuss Chris' “community-supported learning binges” and our process for capturing insightful book quotes and key takeaways, turning the board into a knowledge-sharing powerhouse for software teams and individual contributors alike. ### Refactoring the Mind: Evolving the Board to Stay Relevant Our discussion also delves into the concept of "refactoring my mind by refactoring the board"—an idea about how reorganizing knowledge can improve our mental clarity and adaptability in complex projects. This involves regularly revisiting, reshaping, and expanding board content to reflect the latest insights and trends in software development, keeping it a living, breathing resource for our community. ### The Impact of Public Knowledge Sharing One of the most inspiring aspects of this board is its role in **public knowledge sharing**. We highlight feedback from the community, stories of how others have used the board in their professional journeys, and our own experiences with learning in public. By sharing this resource openly, we invite others to benefit from it, create connections, and add to the body of knowledge that supports software development excellence. Whether you're a developer, coach, Scrum Master, or technical leader, this episode offers valuable insights into how to create and use a resources board to drive personal and team growth. Listen in for tips on organizing knowledge, capturing valuable insights, and using community feedback to make a resource board that truly enhances your software development journey. ### Topics Discussed: - The board's origin story and why we chose Trello - Organizing, searching, and sharing resources in Trello - Similar boards, including "Retrospective Techniques for Coaches, Scrum Masters, and Facilitators" - Variety of topics: mobbing, XP, leadership, IaC, agile, cloud, business, tech, retrospectives, and more - Types of media: articles, blogs, videos, book quotes, academic papers, and beyond - Spin-off boards and community learning sessions - Feedback from the community and lessons for public knowledge sharing **Subscribe on YouTube or your favorite podcast platform to catch this episode and more!** Video and Show Notes: https://youtu.be/GmfWWiIeaVY 

Robby sits down with Justine Gehring, an AI Research Engineer at Moderne, to explore how AI tools are transforming code maintenance and scalability. They dive into the unique ways AI can support refactoring for massive and legacy codebases, from retrieval-augmented generation (RAG) to lossless semantic trees, and discuss how developers can benefit from AI-assisted planning and refactoring.Justine shares her background transitioning from academia to industry and reflects on the essential role of reproducibility in AI, why maintainable code is often overlooked in research, and the challenges of balancing innovation with real-world reliability in software projects.Topics DiscussedWhat Makes Software Maintainable: Justine's take on good documentation, reusable code, and ensuring new team members can quickly navigate a codebase. [00:00:42]Academia vs. Industry in Code Maintainability: Why reproducibility and code maintenance often diverge in research settings, and how industry standards address this gap. [00:01:14]From Academia to AI Engineering: Justine shares her journey and how her background in machine learning led to a career in AI-focused software maintenance. [00:04:48]Scaling Refactoring with OpenRewrite: An introduction to OpenRewrite, the open-source tool that facilitates large-scale code transformations, developed by Moderne. [00:12:15]Lossless Semantic Trees: The benefits of LSTs for detailed code analysis, retaining essential syntax and type information critical for reliable AI refactoring. [00:20:24]Retrieval-Augmented Generation (RAG): Justine explains RAG's significance in allowing AI models to provide context-specific responses without heavy re-training. [00:26:00]Trust and Validation in AI-Generated Code: The importance of robust test cases and human oversight when leveraging AI-generated code to avoid cascading errors. [00:31:36]AI as a Planning Tool for Refactoring Projects: Justine's insights on using AI as a collaborative coding assistant, offering developers suggestions for planning refactoring and maintenance tasks. [00:35:24]Real-World Example of Scaling Refactoring: Justine recounts a case study where Moderne used OpenRewrite to facilitate large-scale code migration involving multiple frameworks. [00:42:00]Advocating for AI Tools in Code Maintenance: Tips for developers interested in introducing AI tools and approaches within their teams or organizations. [00:42:31]Key TakeawaysAI Supports Reproducibility and Reliability: Ensuring reproducibility in AI-driven tools can enhance both credibility and usability for complex codebases.Prioritize Planning Before Refactoring: Understanding code dependencies and structure is key to successful refactoring; AI tools like OpenRewrite can automate targeted changes.Human Expertise Remains Essential: AI can be an effective coding assistant, but human oversight is necessary to ensure accuracy and quality.Experiment and Scale: Start with small, impactful AI-assisted refactoring recipes and scale up once the process is reliable, saving significant development hours over time.ResourcesModerneJustine Gehring's LinkedInOpenRewrite DocumentationGetting to Yes by Roger Fisher and William UryThanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

AI is being integrated and adopted across much of the IT world, but can it work magic in transforming old legacy code into shiny modern code? When it comes to this magic trick, it’s important to look behind the curtain. On today’s Day Two DevOps podcast we discuss the reality of AI in refactoring code... Read more »

AI is being integrated and adopted across much of the IT world, but can it work magic in transforming old legacy code into shiny modern code? When it comes to this magic trick, it’s important to look behind the curtain. On today’s Day Two DevOps podcast we discuss the reality of AI in refactoring code... Read more »

AI is being integrated and adopted across much of the IT world, but can it work magic in transforming old legacy code into shiny modern code? When it comes to this magic trick, it’s important to look behind the curtain. On today’s Day Two DevOps podcast we discuss the reality of AI in refactoring code... Read more »

Exploring Rust for Embedded Systems with Philip MarkgrafIn this episode of the Agile Embedded Podcast, hosts Jeff Gable and Luca Ingianni are joined by Philip Markgraf, an experienced software developer and technical leader, to discuss the use of Rust in embedded systems. Philip shares his background in C/C++ development, his journey with Rust, and the advantages he discovered while using it in a large development project. The conversation touches on memory safety, efficient resource management, the benefits of Rust's type system, and the supportive Rust community. They also explore the practical considerations for adopting Rust, including its tooling, ecosystem, and applicability to Agile development. The episode concludes with Philip offering resources for learning Rust and connecting with its community.00:00 Introduction and Guest Welcome00:26 Philip's Journey with Rust01:01 The Evolution of Programming Languages02:27 Evaluating Programming Languages for Embedded Systems06:13 Adopting Rust for a Green Energy Project08:57 Benefits of Using Rust11:24 Rust's Memory Management and Borrow Checker15:50 Comparing Rust and C/C++19:32 Industry Trends and Future of Rust22:30 Rust in Cloud Computing and Embedded Systems23:11 Vendor-Supplied Driver Support and ARM Processors24:09 Open Source Hardware Abstraction Libraries25:52 Advantages of Rust's Memory Model29:32 Test-Driven Development in Rust30:35 Refactoring and Tooling in Rust31:14 Simplicity and Coding Standards in Rust32:14 Error Messages and Linting Tools33:32 Sustainable Pace and Developer Satisfaction36:15 Adoption and Transition to Rust39:37 Hiring Rust Developers42:23 Conclusion and ResourcesResourcesPhil's LinkedinThe Rust LanguageRust chat rooms (at the Awesome Embedded Rust Resources List)The Ferrocene functional-safety qualified Rust compiler  You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.Want to join the agile Embedded Slack? Click here

In this episode, Dominik Dorfmeister, TanStack maintainer, joins us to discuss component composition in React. He discusses breaking components apart, managing conditional rendering, and the benefits of early returns in improving code readability and maintainability. Links https://tkdodo.eu/blog/component-composition-is-great-btw https://tkdodo.eu/blog https://github.com/TkDodo https://www.dorfmeister.cc https://x.com/TkDodo https://www.linkedin.com/in/dominik-dorfmeister-8a71051b9 We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Dominik Dorfmeister.

Connect to John Gilroy on LinkedIn   https://www.linkedin.com/in/john-gilroy/ Want to listen to other episodes? www.Federaltechpodcast.com Joel Krooswik from Gitlab has seen more code reviews than he can count. He has seen duplicate code, insufficient data, and insecure code. "Work harder" may be the maxim in the NFL, but this is a fool's errand regarding software development. Traditionally, a code review would yield remediation that would take hours and detailed work. During the interview today, Joel looks at how Artificial Intelligence can be applied to four areas: Clean code. A system may work now despite problems. However, it can fail once it is stress-assessed with mountains of data. Clean code means it is easier to scale. Speed. Humans may not be able to see system inadequacies that slow it down. AI can see log jams that a human cannot. Duplicate code. Various individuals have maintained older systems so that code may have been duplicated. Duplicate code is complex for humans to find but easy for AI. New features. Application "A" may run on a system with no problems; when updated, it may highlight issues you do not know exist. AI can look at code and allow for more accessible features. During the interview, Joel focuses on how these abilities can be applied to the federal environment.  

Safely inside Station 151, Richard and Astrid confront Wayne about a mysterious, painful mass on his neck. Richard leaves the station to hunt down Spegg, but returns with an unexpected and disturbing find. Content warning: profanity, loud noises, violence, bodily sounds Can't wait for more? Patreon members get all episodes early and ad-free. Headphones highly recommended Support the show If you're enjoying the Station 151 science-fiction podcast series, we invite you to connect with us on Facebook, Twitter, and Instagram, or come and hang out with us and other fans on Discord! If you really like what you hear, you can support us over at Patreon—every dollar helps fund our monthly costs. Please follow the series on your favorite podcast platform, and let us know how you're liking it by leaving us a rating or review. Your support goes a long way toward helping us grow our listener base. Learn more about your ad choices. Visit megaphone.fm/adchoices

What's the difference between solving problems and recognizing patterns, and why does it matter for developers? In this episode, Stephanie and Joël discuss transitioning from collecting solutions to identifying patterns applicable to broader contexts in software development. They explore the role of heuristics, common misconceptions among junior and intermediate developers, and strategies for leveling up from a solution-focused mindset to thinking in patterns. They also discuss their experiences of moving through this transition during their careers and share advice for upcoming software developers to navigate it successfully. They explore how learning abstraction, engaging in code reviews, and developing a strong intuition for code quality help developers grow. Uncover the issue of over-applying patterns and gain insights into the benefits of broader, reusable approaches in code development. Join us to discover how to build your own set of coding heuristics, the pitfalls of pattern misuse, and how to become a more thoughtful developer. Tune in now! Key Points From This Episode: Stephanie unpacks the differences between patterns and solutions. The role of software development experience in recognizing patterns. Why transitioning from solving problems to recognizing patterns is crucial. Joël and Stephanie talk about the challenges of learning abstraction. Hear pragmatic strategies for implementing patterns effectively. How junior developers can build their own set of heuristics for code quality. Discover valuable tools and techniques to identify patterns in your work. Find out about approaches to documenting, learning, and sharing patterns. Gain insights into the process of refactoring a solution into a pattern. Outlining the common mistakes developers make and the pitfalls to avoid. Steps for navigating disagreements and feedback in a team environment. Links Mentioned in Today's Episode: RubyConf 2021 - The Intro to Abstraction I Wish I'd Received (https://www.youtube.com/watch?v=m0dC5RmxcFk) 'Ruby Science' (https://thoughtbot.com/ruby-science/introduction.html) Refactoring.Guru (https://refactoring.guru/) Thoughtbot code review guide (https://github.com/thoughtbot/guides/blob/main/code-review/README.md) The Bike Shed (https://bikeshed.thoughtbot.com/) Joël Quenneville on LinkedIn (https://www.linkedin.com/in/joel-quenneville-96b18b58/) Joël Quenneville on X (https://x.com/joelquen) Support The Bike Shed (https://github.com/sponsors/thoughtbot)

Scott and Wes serve up ways developers can use AI tools like Claude, GitHub Copilot, and more to boost productivity. From error tracing to refactoring code and automating mundane tasks, they break down how AI can handle the heavy lifting so you can focus on the fun stuff! Show Notes 00:00 Welcome to Syntax! 01:23 Brought to you by Sentry.io. 01:43 Using AI tools effectively. 05:29 Stack trace reading and error finding. 08:37 San Francisco Syntax Meetup! 09:19 Research and validation. 12:19 Completing mundane tasks. 14:10 Refactoring. 18:56 Simple typescript. 20:29 Summarizing docs and source code. 23:56 Quick hits. Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Steve Smith, founder and principal architect at Nimble Pros, joins host Jeff Doolittle for a conversation about software quality. The episode begins with a discussion of why software quality matters for businesses, customers, and developers. Steve explains some patterns and practices that help teams design for quality. They discuss in detail the practices of testing and quality assurance, and the conversation wraps up with suggestions for fostering a culture of quality in teams and organizations. Brought to you by IEEE Computer Society and IEEE Software magazine.

In this special episode of Book Overflow, Martin Fowler joins Carter and Nathan to discuss his book Refactoring: Improving the Design of Existing Code. Join them as Martin shares why he wrote Refactoring, how the art of refactoring has changed, and how he views the book's legacy!https://martinfowler.com/-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------Refactoring: Improving the Design of Existing Code by Martin Fowler and Kent Beckhttps://amzn.to/4enmuox (paid link)The Art of Agile Development, 2nd Edition by James Shore and Shane Wardenhttps://amzn.to/47TiM3D (paid link)Make No Law: The Sullivan Case and the First Amendment by Anthony Lewishttps://amzn.to/3zJ3K3O (paid link)----------------00:00 Intro01:58 Motivation for writing the book09:45 Refactoring, Extreme Programming, and testing19:17 Estimating, Unknowns, and Complexity23:40 Trust and High Performing Teams30:32 refactoring in the wild: imitate, assimilate, innovate, best practices and sensible defaults43:39 Legacy of the book and rational for second edition47:35 What are the role of books now? Evergreen content, Long-form content in a world of short-form content.01:03:21 Book Recommendations01:09:12 Closing Thoughts----------------Spotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5LApple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325X: https://x.com/bookoverflowpodCarter on X: https://x.com/cartermorganNathan's Functionally Imperative: www.functionallyimperative.com----------------Book Overflow is a podcast for software engineers, by software engineers dedicated to improving our craft by reading the best technical books in the world. Join Carter Morgan and Nathan Toups as they read and discuss a new technical book each week!The full book schedule and links to every major podcast player can be found at https://www.bookoverflow.io

In this podcast episode, Walter Sweat hosts Chad Jones and Paul Holland from Astadia to discuss the evolving landscape of mainframe modernization and cloud migration. They explore the historical context of mainframe migration, the shift in customer needs towards agility and cloud solutions, and the current trends in refactoring versus replatforming. The conversation also touches on the importance of planning, automation, and the role of Gen AI in modernizing legacy systems. The experts share insights on how organizations can successfully navigate their mainframe to cloud journeys and the future potential of Gen AI in this space.

“The four common obstacles that are stopping engineers in progressing in their journey are the imposter syndrome, burnout, trouble dealing with other people, and self marketing struggles." Dagna Bieda is an engineer turned coach and the author of “Brain Refactor”. In this episode, Dagna discusses the common obstacles that prevent engineers from progressing in their careers. She also introduces her latest book, “Brain Refactor,” which offers strategies for overcoming these obstacles and achieving success in tech. Dagna emphasizes the importance of understanding our “legacy mental code” and how it can impact our career growth. She outlines an algorithm for reprogramming our legacy mental code, discussing practical steps for identifying the root causes, planning the refactors, scripting new responses, and continuously executing improvements. Towards the end, Dagda dives deeper into handling burnout and dealing with other people and provides practical tips to resolve those common bugs.   Listen out for: Career Journey - [00:02:03] Dagna's Career Transition - [00:04:27] Our Legacy Codebase - [00:10:08] Feedbacks as Debugging Point - [00:13:04] Psychological Safety in Receiving Feedback - [00:17:52] 3 Common Mental Code Refactoring - [00:20:49] The Brain Refactor Algorithm - [00:25:23] Script New Responses - [00:33:45] Merge Conflicts & Cognitive Dissonance - [00:37:33] Common Bug #1: Burnout - [00:42:07] Common Bug #2: Dealing with Other People - [00:51:21] 3 Tech Lead Wisdom - [00:57:02] _____ Dagna Bieda's BioDagna Bieda is an Engineer turned Coach for Engineers and ambitious professionals in tech. With 10+ years of coding experience and coaching since 2019, she's the tough love, “been in your shoes” kinda Coach. Her clients' backgrounds include a spectrum ranging from ICs to CTOs, from small startups to FAANG+ companies, from 2 to 20+ years of experience, and from self-taught devs through career-changing Bootcamp grads to college grads and PhDs. She helps her clients reach their potential and exciting career opportunities by refactoring their brains. Follow Dagna: LinkedIn – https://www.linkedin.com/in/dagnabieda Website – themindfuldev.com

Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: Refactoring cryonics as structural brain preservation, published by Andy McKenzie on September 11, 2024 on LessWrong. I first learned about cryonics when I read Eliezer and Robin's posts about it on Overcoming Bias years ago. I got cryopilled. Somewhat amazingly to me, I'm now a researcher in this field. So I thought this community might be interested to know that I was one of several co-authors on a paper just published in Frontiers in Medical Technology, titled "Structural brain preservation: a potential bridge to future medical technologies". In this paper, we propose reframing cryonics as a type of structural brain preservation, focusing on maintaining the brain's physical structure that encodes memories and personality, rather than making the focus about low-temperature storage per se. We explore what brain structures likely need to be preserved to retain long-term memories and other valued aspects of personal identity. We then review different methods of brain preservation, including cryopreservation, aldehyde-stabilized cryopreservation, fluid preservation, and fixation followed by polymer embedding. The paper also discusses the two most commonly discussed potential future revival technologies, i.e. molecular nanotechnology and whole brain emulation. We argue that this structural preservation framing may be more technically grounded and agreeable to mainstream researchers than some of the traditional ways that cryonics has been discussed. As a personal reflection here, I want to briefly discuss the idea of fluid preservation, which is one topic discussed in our review paper. I remember first reading about this idea in approximately 2017 on a cryonics mailing list. Even though I was already sold on the idea of aldehyde-stabilized cryopreservation -- using fixation as a short-term bridge to cryoprotection and cryopreservation, I remember thinking that the idea of simply leaving the brain in fixative solution for the long-term was bizarre and outlandish. Around 2020-2022, I spent a good amount of time researching different options for higher temperature (and thus lower cost) brain preservation. Mostly I was looking into different methods for embedding fixed brain tissue in polymers, such as paraffin, epoxy, acrylates, or silicon. I also studied the options of dehydrated preservation and preserving the fixed brain in the fluid state, which I was mostly doing for the sake of completeness. To be clear, I certainly don't want to make it seem like this was a lone wolf effort or anything. I was talking about the ideas with friends and it was also in the zeitgeist. For example, John Smart wrote a blog post in 2020 about this, titled "Do we need a noncryogenic brain preservation prize?" (There still is no such prize.) In 2022, I was reading various papers on brain preservation (as one does), when I came across Rosoklija 2013. If I recall correctly, I had already seen this paper but was re-reading it with a different eye. They studied human and monkey brain tissue that had been preserved in formalin for periods ranging from 15 months to 55 years, using the Golgi-Kopsch silver staining method to visualize neuronal structures. They reported that even after 50 years of formalin fixation at room temperature, the method yielded excellent results. In particular, they had this figure: That's a picture showing well-impregnated neurons with preserved dendritic spines. Looking at this picture was a viewquake for me. I thought, if fluid preservation can preserve the structure of the 1-5% of cells that are stained by the Golgi-Kopsch method, why not other cells? And if it can work in this one part of the brain, why not the whole brain? And if it can do it for 50 years, why not 100 or 150? Chemically, it is not clear why there would be differences across the tissue. Aldehydes crosslin...

Code quality matters! When developers write better, cleaner, and safer code - their deliverables improve significantly. When code is safer, there are less problems with crashes and unintended errors. When code is cleaner, team members find it easier to read, peer review, and add on to down the line. Improving the quality of your code is easier said than done, however, as it takes more than just "getting good" at coding. In this episode, Matt and Mike discussed the importance of and how to improve your code quality by keeping coding styles consistent with your team, refactoring, writing good tests, using prettier formatting, and linting. Show Notes: https://www.htmlallthethings.com/podcasts/why-code-quality-matters-testing-linting-refactoring Thanks to Wix Studio for sponsoring this episode! Check out Wix Studio, the web platform tailored to designers, developers, and marketers via this link: https://www.wix.com/studio

Terri Morgan, Co-Founder and Principle Designer and Chris Demiris, Co-Founder and Principal Engineer of Luma Touch are back to discuss two new features to LumaFusion: Speed Ramping and Enhance Keyframing. They explain why speed ramping was their most requested feature, and how they have improved the process of keyframing. The discussion also touches on grids, an adjustable user interface, integrated access to training, and their pricing model.  This edition of MacVoices is supported by MacVoices After Dark. What happens before and after the shows is uncensored, on-topic, off-topic, and always off the wall. Sign up as a MacVoices Patron and get access! http://patreon.com/macvoices Show Notes: Chapters: 00:00 Introduction to LumaFusion 01:34 New Features Overview 04:56 Speed Ramping and Keyframing 07:41 Refactoring for Future-Proofing 17:12 Hardware Compatibility and Requirements 19:07 Editing on iPhone 24:40 LumaFusion in Education 27:38 Android and Chromebook Experience 34:32 Pricing Model and Features 40:50 Customer Support and Resources Links: Luma Touch - Speed Ramping & Enhanced Keyframing Guests: Terri Morgan is Co-Founder and Principle Designer at LumaTouch. She brings over 30 years of experience from the video industry to her passion for user experience and design. In 1988 Terri helped usher in the era of non-linear editing as a video editor at Alpha Cine Labs in Seattle. In 1995 she joined Lightworks in London, and became a Product Specialist, creating a powerful, multi-track editing system. In 2000, she founded a video editing and consulting business providing design and testing for Fast Multimedia and Pinnacle Systems. In 2007, Terri joined Avid as a Principal Product Designer where she led the product management and design of Pinnacle Studio for iPad and was honored with the Avid Achievement Award. Terri has received multiple awards for her editing work, including 3 Telly awards. She earned her BA in Visual Communications at The Evergreen State College, and her Professional Certificate in Human Centered Design and Engineering at the University of Washington. Chris Demiris is Co-Founder and Principal Engineer at Luma Touch. He is an expert at building new technologies into complete products, leading engineering teams to create quality results and integrating technologies to create complete, award-winning apps. Focused on video editing and video effects apps for iOS. Chris' specialties include iOS native media and UI development, OpenGL, DirectX, 3D graphics for video processing, video effects, digital rights management, and  3D editing tool creation. Support: Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect: Web:      http://macvoices.com Twitter: http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices Mastodon:      https://mastodon.cloud/@chuckjoiner Facebook:      http://www.facebook.com/chuck.joiner MacVoices Page on Facebook:      http://www.facebook.com/macvoices/ MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice LinkedIn:      https://www.linkedin.com/in/chuckjoiner/ Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher: Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Terri Morgan, Co-Founder and Principle Designer and Chris Demiris, Co-Founder and Principal Engineer of Luma Touch are back to discuss two new features to LumaFusion: Speed Ramping and Enhance Keyframing. They explain why speed ramping was their most requested feature, and how they have improved the process of keyframing. The discussion also touches on grids, an adjustable user interface, integrated access to training, and their pricing model.    This edition of MacVoices is supported by MacVoices After Dark. What happens before and after the shows is uncensored, on-topic, off-topic, and always off the wall. Sign up as a MacVoices Patron and get access! http://patreon.com/macvoices Show Notes: Chapters: 00:00 Introduction to LumaFusion 01:34 New Features Overview 04:56 Speed Ramping and Keyframing 07:41 Refactoring for Future-Proofing 17:12 Hardware Compatibility and Requirements 19:07 Editing on iPhone 24:40 LumaFusion in Education 27:38 Android and Chromebook Experience 34:32 Pricing Model and Features 40:50 Customer Support and Resources Links: Luma Touch - Speed Ramping & Enhanced Keyframing Guests: Terri Morgan is Co-Founder and Principle Designer at LumaTouch. She brings over 30 years of experience from the video industry to her passion for user experience and design. In 1988 Terri helped usher in the era of non-linear editing as a video editor at Alpha Cine Labs in Seattle. In 1995 she joined Lightworks in London, and became a Product Specialist, creating a powerful, multi-track editing system. In 2000, she founded a video editing and consulting business providing design and testing for Fast Multimedia and Pinnacle Systems. In 2007, Terri joined Avid as a Principal Product Designer where she led the product management and design of Pinnacle Studio for iPad and was honored with the Avid Achievement Award. Terri has received multiple awards for her editing work, including 3 Telly awards. She earned her BA in Visual Communications at The Evergreen State College, and her Professional Certificate in Human Centered Design and Engineering at the University of Washington. Chris Demiris is Co-Founder and Principal Engineer at Luma Touch. He is an expert at building new technologies into complete products, leading engineering teams to create quality results and integrating technologies to create complete, award-winning apps. Focused on video editing and video effects apps for iOS. Chris' specialties include iOS native media and UI development, OpenGL, DirectX, 3D graphics for video processing, video effects, digital rights management, and  3D editing tool creation. Support:      Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:      http://macvoices.com      Twitter:      http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices      Mastodon:      https://mastodon.cloud/@chuckjoiner      Facebook:      http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:      http://www.facebook.com/macvoices/      MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice      LinkedIn:      https://www.linkedin.com/in/chuckjoiner/      Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Jonathan Schneider is Co-Founder & CEO of Moderne, the platform for code migrations. Moderne has raised up to a Series A from investors including Intel Capital and True Ventures. In this episode, we dig into the importance of software refactoring and the security and engineering challenges that come up when code isn't maintained, why they started with Java refactoring, their rewrite open source project, how the amount of code created with GenAI has made refactoring an even bigger challenge & more!

In this episode of the Arguing Agile podcast, Enterprise Agility Coach Om Patel and Product Manager Brian Orlando are joined by Alex Polyakov, CEO of Project Simple (https://projectsimple.ai) for an immersive discussion of the complex topic of technical debt. They discuss what technical debt really means, when it can be beneficial vs harmful, and strategies for prioritizing and paying down tech debt while still delivering value to users. Learn how to have productive conversations about technical debt with your development teams and stakeholders.technical debt, agile development, product management, refactoring, software architecture, prioritization, user needs, agile transformation, arguing agile podcast= = = = = = = = = = = =Watch it on YouTube= = = = = = = = = = = =Subscribe to our YouTube Channel:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1Apple Podcasts:https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotify:https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Amazon Music:https://music.amazon.com/podcasts/ee3506fc-38f2-46d1-a301-79681c55ed82/Agile-Podcast= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Emily Bache, founder of the Samman Technical Coaching Society and author of several books about technical agile coaching, talks with SE Radio host Sam Taggart about katas and the importance of practice. They discuss how practicing in a safe environment helps developers to learn new skills and build new habits. They also talk about how Samman coaching combines this sort of deliberate practice with applying the lessons learned in practice to the production code base. They also touch briefly on the advantages of working in an ensemble fashion. Brought to you by IEEE Computer Society and IEEE Software magazine.

Jonathan Schneider, the cofounder of Moderne and the creator of OpenRewrite, talks with SE Radio's Gregory Kapfhammer about automated software maintenance. In addition to exploring the design and implementation of OpenRewrite, Schneider explains how the tool can automatically support software maintenance tasks such as framework migration and security fixes for programs implemented in languages like Java. The episode also explores how OpenRewrite uses the lossless semantic tree to support automated refactoring though the use of recipes. Brought to you by IEEE Computer Society and IEEE Software magazine.