Rewriting History - Cleaning Up Commits for Others to Review
When tackling large merges in code, having your changes organized and allotted into sequential commits makes it easy for your teammates to review and understand your code. So we should all intentionally think out our plan of attack before we start coding and only commit as we complete each specific step, right? No! Not at all, code the chaotic mess first, commit as you please with messages like "everything is broken" or "I have no idea why this is working but it does" and then come back and use interactive rebasing to remove all evidence of anything other than clean, clear code. Your co-worker who twitches every time someone commits a nonsense message will love you. There will be no evidence of the endless adding and removing of your console logs. And maybe, just maybe, you'll get your code reviewed faster and with less begging.Speakers
Get your ticket to attend REFACTR.TECH in Atlanta, September 14 - 16 for 3 days packed full of workshops, keynotes, tech sessions and demos, and of course, parties! With tracks from software engineering to leadership to data and community, there’s something for everybody!