Artwork

Konten disediakan oleh Joshua Kerievsky. Semua konten podcast termasuk episode, grafik, dan deskripsi podcast diunggah dan disediakan langsung oleh Joshua Kerievsky atau mitra platform podcast mereka. Jika Anda yakin seseorang menggunakan karya berhak cipta Anda tanpa izin, Anda dapat mengikuti proses yang diuraikan di sini https://id.player.fm/legal.
Player FM - Aplikasi Podcast
Offline dengan aplikasi Player FM !

Interview with Arlo Belshee

19:08
 
Bagikan
 

Manage episode 205663268 series 1377427
Konten disediakan oleh Joshua Kerievsky. Semua konten podcast termasuk episode, grafik, dan deskripsi podcast diunggah dan disediakan langsung oleh Joshua Kerievsky atau mitra platform podcast mereka. Jika Anda yakin seseorang menggunakan karya berhak cipta Anda tanpa izin, Anda dapat mengikuti proses yang diuraikan di sini https://id.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 episode

Artwork

Interview with Arlo Belshee

The Modern Agile Show

58 subscribers

published

iconBagikan
 
Manage episode 205663268 series 1377427
Konten disediakan oleh Joshua Kerievsky. Semua konten podcast termasuk episode, grafik, dan deskripsi podcast diunggah dan disediakan langsung oleh Joshua Kerievsky atau mitra platform podcast mereka. Jika Anda yakin seseorang menggunakan karya berhak cipta Anda tanpa izin, Anda dapat mengikuti proses yang diuraikan di sini https://id.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 episode

Semua episode

×
 
Loading …

Selamat datang di Player FM!

Player FM memindai web untuk mencari podcast berkualitas tinggi untuk Anda nikmati saat ini. Ini adalah aplikasi podcast terbaik dan bekerja untuk Android, iPhone, dan web. Daftar untuk menyinkronkan langganan di seluruh perangkat.

 

Panduan Referensi Cepat