{"push_id":1419913367,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b92b7d088362bf587194a2538fac50fdf8435aa3","before":"b2dc481160ad95e8e10ee3ce64b2ec160e2b5f85","commits":[{"sha":"b92b7d088362bf587194a2538fac50fdf8435aa3","author":{"name":"Gustavo Martin Morcuende","email":"53788e389a25003da8b9a29d26fe3eaacc1c8b3a@scmspain.com"},"message":"Thoughts about Feature Envy and path to follow when refactoring legacy code\n\n1. When writing tests for legacy code we go from shortest to deepest branches.\n2. When refactoring legacy code (handmade modifications) we go from deepest to shortest branches (just the opposite)\n\nFeauture envy: some class (TripService) wants to do some action that should be implemented by another class which we\nare using to extract the data and perform some action. Data and action should be done by the same class (User)","distinct":true,"url":"https://api.github.com/repos/gumartinm/JavaForFun/commits/b92b7d088362bf587194a2538fac50fdf8435aa3"}]}
{"actor":{"display_login":"gumartinm"}}