Temporary Refactoring and Improving Your Code Reading Skills
Temporary Refactoring and Improving Your Code Reading Skills
A developer discusses technique he learned from a colleague in which he temporarily refactors code in order to better understand what another dev has done.
Join the DZone community and get the full member experience.
Join For FreeAdopting a DevOps practice starts with understanding where you are in the implementation journey. Download the DevOps Transformation Roadmap. Brought to you in partnership with Techtown.
I was talking to a friend of mine, Scott, over Slack about reading code! Specifically, how to improve your code reading skills.
I asked him what he usually does when he reads source code. What he said is interesting:
He does a temporary refactoring. That’s it.
He usually takes a long method that can be separated out and then he turns it into a separate method.
For example- readEmployeeDataFromDatabase()
This method can be broken into multiple methods and he does that. He keeps doing that until he gets a sense for what the intent of the larger method is about. Then he takes a few notes on what the method does and rolls back the changes.
He also mentioned that he does not do any unit testing because this refactoring is only temporary, and used just to understand the code!
I believe this could be a great way towards improving code reading skills. Although what he suggested isn’t really true refactoring, it can help you to understand the code you are reading.
Take Agile to the next level with DevOps. Learn practical tools and techniques in the three-day DevOps Implementation Boot Camp. Brought to you in partnership with Techtown.
Like This Article? Read More From DZone
Published at DZone with permission of A. N. M. Bazlur Rahman , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}