🗺️ CodeAtlas — 14 Days Later
😭🗿🥳 After 10.5 hours of grind… CodeAtlas is gonna be SHIPPED!!
For the last 14 days, I’ve been building CodeAtlas — a tool that helps developers understand unfamiliar GitHub repositories without having to manually dig through hundreds of files.
The idea is simple: give developers a map before they explore the territory.
🔥 What did I build?
CodeAtlas takes a GitHub repository and turns it into an interactive view of the codebase.
📂 1. Better Codebase Explorer
I started with a basic file tree and turned it into something much more useful liikee…..

*Expandable folders

*File-type indicators

*File selection

*Dependency counts

*Codebase search

*Entry-point detection

🕸️ 2. Dependency Graph
CodeAtlas analyzes imports between source files and turns them into an interactive graph.
Instead of opening files one-by-one to figure out what depends on what, you can actually see the relationships.
I also connected the Explorer and Graph, so selecting a file highlights its relevant connections.
🧭 3. Architecture Insights
CodeAtlas can identify things like:

🚪 Entry point

🔗 Most connected file
📁 File/folder counts

🕸️ Dependency count

Nothing overly complicated — just useful information to help you figure out where to start.
🧩 The QoL improvements
A lot of the work wasn’t flashy new features. It was making the experience actually feel usable.
Search → select a file → see its connections.
Select something in the Explorer → understand where it sits in the architecture.
File types → easier scanning.
Dependency numbers → quickly spot highly connected files.
Those small things made a surprisingly big difference.
😭 The 14-day journey
This definitely wasn’t:
code → works → ship
It was more like:
code → break → stare at error for 12 mins → debug → fix → break something else → repeat.
I ran into TypeScript errors, React issues, Git problems, dependency-resolution bugs, UI problems and plenty of things that made absollllutely no sense at first!! 💀
And honestly, I solved a lot of those problems myself.
That’s probably what I’m happiest about.
I didn’t just learn how to write code.
I learned how to debug, rethink, and keep going when the code doesn’t cooperate.
Okayy..🤔 Is the idea completely new?
Nope.
There are already tools and projects exploring codebase visualization and dependency analysis.
And that’s okay.
For me, the goal wasn’t to invent an entirely new category.
It was to take an idea I found interesting, build my own version from scratch, understand the underlying concepts, and actually ship it.
And I am GOing to!!
🚀 What’s next?
There’s still a lot I’d love to explore like :-
Better dependency analysis
Circular dependency detection
More languages
Git history visualization
Smarter architecture analysis
AI-assisted codebase explanations

But for now…
14 days. 10.5 hours of grind. Countless bugs. A ridiculous amount of debugging. And one shipped project.
😭🗿🥳 CodeAtlas — Gonna get SHIPPED. 🚀 (P.s It was a pain to find and put all these emojis, especially those arrows!)