As developers, we often focus on the task at hand, eager to roll out new features and fix bugs quickly to mark tickets as done. But then, inevitably, we must revisit an old codebase we’ve long forgotten.

When you’re the original author, you can usually grasp its architecture quickly. However, after weeks or months, the code may feel like it was written by a stranger. You recognize your work, but you still feel a bit lost. If the code isn’t yours, the investigation phase can be much longer, and you might even need to reach out to the original author—if they’re still with the company.

However, if you document your code while writing it and follow architecture guidelines with your colleagues, revisiting an old project shouldn’t be difficult. In the long run, the extra effort you put into writing clear, intelligible code pays off. Your future self will thank you, and your colleagues will appreciate the reduced frustration.