Stop Being Scared of Deleting Code
Read full transcript 1 segments
-
Who here has guilt merged a PR before? Who here has guilt merged a PR before? Where you just felt bad because somebody Where you just felt bad because somebody Where you just felt bad because somebody put a lot of work in, it's not quite the put a lot of work in, it's not quite the put a lot of work in, it's not quite the right thing, but you merge it anyways right thing, but you merge it anyways right thing, but you merge it anyways cuz the alternative was a conversation cuz the alternative was a conversation cuz the alternative was a conversation you didn't want to have. you didn't want to have. you didn't want to have. Why do we do this to ourselves? We just Why do we do this to ourselves? We just Why do we do this to ourselves? We just care too much, is the point I'm trying care too much, is the point I'm trying care too much, is the point I'm trying to make. And the things we care about to make. And the things we care about to make. And the things we care about are not necessarily the things that are not necessarily the things that are not necessarily the things that matter anymore. And I hope we can matter anymore. And I hope we can matter anymore. And I hope we can finally start to challenge some of finally start to challenge some of finally start to challenge some of these.
Summary
This transcript discusses the common developer practice of "guilt merging" pull requests, where code is merged despite not being ideal to avoid difficult conversations. The core theme is that we often care too much about superficial aspects, leading to actions that don't align with what truly matters. The takeaway is to challenge these ingrained behaviors and re-evaluate what we prioritize.