search

AnneTheAgile / bc-ruby

Try little programs, tests, algorithms with Ruby.
MIT License
0 stars 0 forks source link

Doc: Refactor/Git: Use Rebase tools to Clean the Commit Log. #12

Open AnneTheAgile opened 10 years ago

AnneTheAgile commented 10 years ago

Confusing, difficult to read commit logs are considered to be possibly the number one worst Technical Debt offender.

AnneTheAgile commented 10 years ago

The talk that crystallized my understanding on this issue was the March 2014 NYC HTML5 Meetup.

http://www.meetup.com/nychtml5/events/167187142/ March 12 · 6:30 PM Taming the Technical Debt, HTML5 and the Magical Mobile App, and Isomorphic JS Taming the Technical Debt by Brittany Storoz Committing hacky code is unavoidable at times, but when it becomes a habit rather than an exception, it breeds quickly. How can we better handle the technical debt that creeps into our codebase before it gets out of control, and how can we heal a codebase that's already in the red? We'll talk about some strategies for keeping up with the clean up, without having to dedicate your day to maintenance.

Anne Moroney This was a great meetup! One question I had for Brittany Storoz was did you create the branch for the Superbowl ahead of running into the hectic commits? Or did you move the hectic commits from the master then to a branch, worked there, then later cherrypicked to post back to master? March 15 ·

Brittany Storoz We make a separate branch prior to the chaos. The good commits will be cherry-picked in after the fact. 1 · Unlike · March 17