Build Boss Daily Development Cycle

Build Boss Daily Development Cycle(abovetheapi.com)

43 points by kenjinp 8 years ago | 6 comments

Deleting old branches is something that really helps with sanity but almost never gets done. It really should be a formalized process. But then the formalized process in many cases isn't done. I've lost count of the number of times we've come to the awareness, multiple times, that we need to do <thing-that-prevents-wasting-a-whole-day-to-dealing-with-git> and having it never get done again until it bites us again. Oh well. At least we're still getting paid.

delinka 8 years ago | |

Using on-prem bitbucket at work, and it's got an option to delete branches on merge: approve a PR, click merge, offered the option on the confirmation modal.

Is this not a common feature in other tools?

kenjinp 8 years ago | |

Yeah, that's exactly the lack of discipline I have.

I really think one of the keys is peer buy-in. One of the ways to increase buy-in from your peers is making it less a chore and more a 'thing you get to do'. That's kind of the main inspiration for this, hence the "Build Boss" title and special slack channel.

That, and making it simple as a post-it. I don't think it's quite there yet, though.

maephisto 8 years ago |

awesome read!

kenjinp 8 years ago | |

Thanks! I was trying to make something simple for my team that has no patience for discipline and protocol. I think it's simple enough that even the laziest of devs (often me) and dev teams can give it a try

sctb 8 years ago |

Since this is in fairly standard article format, we've removed “Show HN” so users aren't misled.