Artwork

محتوای ارائه شده توسط Joshua Kerievsky. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Joshua Kerievsky یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
Player FM - برنامه پادکست
با برنامه Player FM !

Interview with Arlo Belshee

19:08
 
اشتراک گذاری
 

Manage episode 205663268 series 1377427
محتوای ارائه شده توسط Joshua Kerievsky. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Joshua Kerievsky یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
Episode 28 of the Modern Agile Show features an interview with Arlo Belshee, a pioneering agilest who is constantly pushing the boundaries of agility, from planning to programming. Arlo was at the deliver:Agile conference in Austin, Texas to talk about mastering legacy code via ultra-safe refactorings. Arlo describes “recipes” that people can execute manually on languages that have lacked automated refactoring tools (like C++). Together with his colleagues at Tableaux software, Arlo has helped to find a way to solve the classic chicken-and-egg problem of not being able to refactor because you lack tests and not being able to test code without first refactoring. The safe recipes use the type system and rely on the compiler to ensure that you can indeed refactor without automated tests and that the design transformations you make are perfectly safe. Each recipe involves micro-changes that together help you safely make important design changes. Arlo explains how his approach to ultra safe refactoring helped him and his colleagues make design changes in legacy Microsoft products, like Foxpro. This is the essence of the Modern Agile principle, Make Safety A Prerequisite. Also also mentions a practice called “safeguarding”, a practice of analyzing a defect stream after an incident occurs. His teams performs RCA (root cause analysis) to identify the hazards that were present when an incident occurred, followed by “remediation”, which is a small, time-boxed fix to make the code less hazardous.
  continue reading

46 قسمت

Artwork

Interview with Arlo Belshee

The Modern Agile Show

58 subscribers

published

iconاشتراک گذاری
 
Manage episode 205663268 series 1377427
محتوای ارائه شده توسط Joshua Kerievsky. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Joshua Kerievsky یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
Episode 28 of the Modern Agile Show features an interview with Arlo Belshee, a pioneering agilest who is constantly pushing the boundaries of agility, from planning to programming. Arlo was at the deliver:Agile conference in Austin, Texas to talk about mastering legacy code via ultra-safe refactorings. Arlo describes “recipes” that people can execute manually on languages that have lacked automated refactoring tools (like C++). Together with his colleagues at Tableaux software, Arlo has helped to find a way to solve the classic chicken-and-egg problem of not being able to refactor because you lack tests and not being able to test code without first refactoring. The safe recipes use the type system and rely on the compiler to ensure that you can indeed refactor without automated tests and that the design transformations you make are perfectly safe. Each recipe involves micro-changes that together help you safely make important design changes. Arlo explains how his approach to ultra safe refactoring helped him and his colleagues make design changes in legacy Microsoft products, like Foxpro. This is the essence of the Modern Agile principle, Make Safety A Prerequisite. Also also mentions a practice called “safeguarding”, a practice of analyzing a defect stream after an incident occurs. His teams performs RCA (root cause analysis) to identify the hazards that were present when an incident occurred, followed by “remediation”, which is a small, time-boxed fix to make the code less hazardous.
  continue reading

46 قسمت

همه قسمت ها

×
 
Loading …

به Player FM خوش آمدید!

Player FM در سراسر وب را برای یافتن پادکست های با کیفیت اسکن می کند تا همین الان لذت ببرید. این بهترین برنامه ی پادکست است که در اندروید، آیفون و وب کار می کند. ثبت نام کنید تا اشتراک های شما در بین دستگاه های مختلف همگام سازی شود.

 

راهنمای مرجع سریع