- **Epistemic status:** #seedlings Refactoring code is necessary when the code needs to be clear, when it doesn't follow the [[Don't repeat yourself (DRY) principle]], or when the team finds the code in question a pain point. Refactoring can often be a time drain when chosen in incorrect situations, keeping you away from working with other people on your team. A good rule of thumb is to not refactor a colleague code because yours is “cleaner”. They might not agree with your code, and you stepped on their beauty. It will damage your rapport on the team. Arguing or worrying about code styles is typically a waste of time. The focus should be on how the component interacts. --- ## References - “Tips for Ramping Up as a Senior Engineer : ExperiencedDevs.” Accessed June 30, 2022. <https://www.reddit.com/r/ExperiencedDevs/comments/iu4g74/tips_for_ramping_up_as_a_senior_engineer/?utm_source=share&utm_medium=web2x&context=3>.