Today, I decided to revisit one of my biggest projects this year, PINUC, to see how I could improve it based on the knowledge I’ve gained since joining Zone01.
As soon as I opened the root project folder, it felt strangely unfamiliar. It looked like someone else’s code. I couldn’t easily remember where some of the configuration files were or why I had structured certain parts of the project the way I did.
It took me quite some time just to understand some of the code I had written and remember what certain lines were doing.
And that’s when I realised something I had previously overlooked: the importance of writing comments and documenting your code.
I used to ignore comments because I thought:
“I’m the one writing the code. How could I possibly forget it?”
Well… apparently, I could. 😂
Looking at PINUC months later made me realise that code isn’t only written for the developer you are today. It is also written for the developer you will become months or even years from now.
Comments and documentation are almost like leaving a note for your future self:
“Hey, this is what I was thinking when I built this.”
Now, as I continue my journey toward becoming a better developer, I’m going back through PINUC and working on improving its codebase, structure, configuration, and overall maintainability.
It’s interesting to revisit an old project with new knowledge. What once seemed perfectly structured now gives me plenty of things I would do differently.
And honestly, I think that’s a good sign.
Growth means being able to look at your old code and recognise how much you’ve learned since writing it.
For those who have not yet checked the webiste here is the link: https://pre-inspected-used-cars-git-master-collins-projects-3eca33c8.vercel.app/
Top comments (0)