Old GitHub Projects
Recently, I took a peek at some of my older GitHub projects.
That account is nearly 10 years old, and I’ve been uploading semi-consistently the whole time — so it’s basically a time capsule of how I’ve grown as a developer. The further back you go, the more chaotic everything gets. But moving forward through the timeline, patterns start to emerge: consistent calling conventions, cleaner decomposition, a style that slowly becomes mine.
And in the newest projects, it finally clicks: the code is clean, self-documenting, and genuinely production-ready.
Then I opened my current “learning project” for the React Native + Expo stack…
…and it hit me: code clarity isn’t something you achieve once. It’s a process. A discipline. You have to keep yourself in check — know when you’re getting carried away, and refactor before messy becomes normal. Even in strongly-typed, object-oriented languages, avoiding spaghetti takes effort.
Because the real problem isn’t one badly named variable or one hacky fix.
The problem is that these things compound.
Like the “Broken Windows Theory,” messy code sends a message to the whole team: quality doesn’t matter here.
So get it right. Build habits that scale: clean code, clear intent, and documentation that respects the next person — even if that next person is you.