Skip to content
Maintainable cover art

All Episodes

Maintainable — 234 episodes · page 2 of 3

#
Title
101

Courtney Wilburn - Maintainable Software Has Good Community Around It

102

Nelida Velazquez - We Have to Express Our Opinions

103

Casey Watts! - Culturesmithing

104

Marc Cornellà - Maintaining Open Source Projects

105

Shanea Leven - How To Bring Visibility To Your Codebase

106

Greg Foster - A Pattern for Smaller, Faster, and Frequent Code Reviews

E
107

Urban Hafner - Management Isn't For Everyone

E
108

Amy Isikoff Newell - Code Shouldn't Drive Us To Drink

109

Podcast Panel at RailsConf 2022

E
110

Chelsea Troy - All Code Has Maintenance Load

111

Paula Paul - Getting People To Understand Is a Challenge

E
112

Ben Halpern - Adventures In Open Sourcing Your Existing Application

113

Avdi Grimm - Don't Be Too Clingy To Your Tests

114

Aran Khanna - De-risk Your Cloud Resources

115

Jerod Santo - Having to Maintain Your Own Cleverness

116

Idit Levine - Production is the Real Test

117

Emily Giurleo - Maintaining Open Source vs Proprietary Software

E
118

Jean Yang - Not All Software is Meant to be Maintained

E
119

Shaundai Person: Work on Having a Short-term Memory

E
120

Chris Birchall: Re-Engineering Legacy Software

E
121

Swizec Teller: What is a Senior (Engineer) Mindset?

E
122

Heidi Waterhouse: Documentation: The Best Diff is a Red Diff

E
123

DHH: Celebrating Legacy Software as a Victory and the Story of How Humans Can't Estimate

E
124

Matt Wynne: Cucumber and Why Is TDD Such a Challenge?

E
125

Tom Granot: Finding Your Style When Explaining Things to Technical Audiences

E
126

Andrew Watkins: How To Test What You're Trying to Build

E
127

Rodney Cobb: Repeatable. Testable. Scalable.

E
128

Dr. Michaela Greiler: Getting Awesome at Code Reviews

129

Mark Kilby: Overcoming Challenges that Remote Technical Teams Experience

130

Kevin Stewart: Short-term Decisions That Need To Be Revisited

131

Ken Fogel: What Are You Leaving Behind?

132

Murray Steele: Maintainable Code Is Easy to Turn Off and Delete

133

Dr. Felienne Hermans: Looking Inside The Programmer's Brain

134

Bertold Kolics: Are You Carrying the Weight of Dead Code?

135

Kent C. Dodds: AHA Programming and Testing JavaScript

136

Mark Adams: HOWTO Prepare (Your Nails) for Burning Man

E
137

Amy Sorensen: Nail Baths vs Nail Soaks

E
138

Logan Luke Tyler Tanner: Overcoming Nail Biting During a Pandemic

E
139

Erica Tafavoti: Adding Density to Extend Their Life

E
140

Duncan Thorpe: Disrupting the Mammalian Industrial Nail Complex

E
141

Shannon Jackson: Oh, Wait, Nope...Those Aren't My Gutter Nails

142

Brian Scanlan: Improving Oncall Support with Meaningful Alarms

143

Alexandre Omeyer: Removing the Barriers to Track Technical Debt

144

Roopak Venkatakrishnan: The Importance of Optimizing For Local Development and Build Systems

145

Benjamin Wood: Rescuing Ruby on Rails Projects

146

Johanna Rothman: No, Great Developers Aren't Destined to Be Great Managers

147

Helen Scott: Strategies For Measuring Developer Experience (DX)

148

Robert Kaufman: Running a Consultancy and a Coding School

149

Heidi Helfand: The Art and Wisdom of Changing Teams

150

Jutta Eckstein: How Software Impacts Our Planet

151

John Cech: How To Mentor Interns On Software Projects

152

Theresa Neate: Testing != Quality

E
153

Michael Springer: Vetting External Dependencies

154

Jason Swett: Refactoring Is Necessary to Keep Your Blade Sharp

155

Sudhir Reddy: Don't Be Afraid to Slash and Burn

156

Monica Lent: Progress Is More Important Than Perfection

157

Trae Robrock: Understanding Your Risk Tolerance As An Engineer

158

Mark Erikson: Accidentally Becoming an Open Source Maintainer

159

Bonnie Brennan: Building Community

160

Khaled Souf: Track Down Dead Code and Delete it

161

Adrianna Chang: Using the Strangler Fig Pattern at Shopify

162

Mark Downie: Balancing The Promises That Open Source Projects Make

163

Glenn Vanderburg: Don't Ask For Small Things

164

Suzan Bond: Embracing Discomfort and Navigating Transitions

165

Nicolas Carlo: Changing Messy Software Without Breaking It

166

Brittany Martin: How to Quit Your Job and Leave Your Code in Good Hands

167

Luke Redpath: User Stories Should Prompt Conversations

168

Hampton Lintorn Catlin: Only Add Complexity When Necessary

169

Pat Kua: The Challenges that Come with Becoming a Tech Lead

170

Aaron Blohowiak: The Myth of the Sufficiently Smart Engineer

171

Magda Miu: Building a Technical Leadership Career Around Teaching

172

Gant Laborde: Technical Debt — Trading Risk for an Advantage

173

Karen Lee Rigg: Where Are the Bad Habits Coming From?

E
174

Gianluca Arbezzano: Technical Debt Beyond Code & Your First Contributions to Open Source

E
175

Ali Spittel: Junior Developers and Helping Unlock Their Potential

E
176

Robby Russell: Turning the Mic Around with Kayla Reopelle

E
177

Ryan Cromwell: Is the Juice Worth the Squeeze?

E
178

Camille Fournier: How Does a Developer Become a Manager?

E
179

Gonçalo Silva: How A Fully-Remote Team Builds and Maintains Software

180

Tudor Girba: Moldable Development and Software Environmentalism

E
181

Jeff Haynie: How Can We Make Software Development Better for Dev Teams?

E
182

Vladimir Khorikov: 100% Test Coverage is an Artificial Metric

E
183

Bryan Helmkamp: Don't Let Perfect Be The Enemy of Good

E
184

Dr. Aino Vonge Corry: Why Do We Have Retrospectives, Again?

185

Trisha Gee: Developers Should Invest More Time Into Learning Their Tools

E
186

Sandi Metz: Making is Easy, Mending is a Challenge

187

Clare Sudbery: Refactoring Should Be Part of Your Daily Work

E
188

Kelly Sutton: Custodians of the Monolith

E
189

Jonathan Abourbih: Creating a Culture Where It's Okay To Take Risks

E
190

Jessica Kerr: Software Is Not A Craft (or an Art)

E
191

Jon Thornton: Technical Debt is a Good Thing (Sometimes)

E
192

Ben Orenstein: "Someday We'll Go Clean That Up" Doesn't Work

193

Ernesto Tagwerker: Tracking Technical Debt With Metrics (aka Stink Score)

194

Marit van Dijk: How Are We Going to Test This?

E
195

Mike Perham: How Developers Underestimate Long-Term Costs of External Dependencies

E
196

Ev Haus: Good Code Can Be Easily Deleted

E
197

Adam Tornhill: Prioritizing Technical Debt With Behavioral Code Analysis

E
198

M. Scott Ford: Menders In Hiding and the Joy of Legacy Code

E
199

Gitte Klitgaard: Making Space For Psychological Safety in Software Teams

E
200

Nathaniel Bibler: Communication Strategies Between Developers and Clients

E