Okay, let me start with the most embarrassing thing that happened today. I spent a solid hour trying to figure out why my project folder structure looked completely wrong in my IDE. Turns out, I was creating folders using BOTH my IDE terminal AND my computer's regular terminal at the same time.
Picture this: I'm typing mkdir components in IDE terminal, then switching to my system terminal and typing mkdir src, then back to IDE terminal for mkdir utils... No wonder my folder tree looked like it was designed by a caffeinated squirrel!
Pro tip for fellow beginners: Pick ONE terminal and stick with it. Your future self will thank you.
The Project That's Teaching Me Everything
So here's what I'm actually building - an infographics generator that's going to enhance Weam AI's capabilities:
📊 Infographics Generator Project Report
What it does:
- Takes a topic or data as input
- Uses Claude API to generate structured content results
- Converts results into styled HTML that looks like an actual infographic
- Exports the final infographic into a downloadable PDF format
I'm building this inside Trae IDE (might switch to Cursor later) using Weam AI's source code as my foundation. The idea is to add this as a new "Brain" feature that teams can use to quickly create visual content.
Code Indexing: The Thing I Didn't Know I Needed
Here's the funny thing about code indexing - I kept hearing about it but had no idea what it actually meant. Today I finally figured it out, and it's actually pretty cool.
What is Code Indexing?
Code indexing is basically creating a smart, searchable database of your entire codebase. Think of it like Google, but for your code. It analyzes:
- Every function and what it does
- How different files connect to each other
- Import/export relationships
- Variable definitions and where they're used
- Class structures and inheritance chains
It's like having a super-organized librarian who knows exactly where every piece of information lives in your massive code library.
The Benefits (Why This Actually Matters)
For You:
- Jump to any function definition instantly
- Find where variables are used across the entire project
- Understand code relationships without reading everything
- Refactor safely knowing what will break
For AI Assistants:
- They can understand your project context instead of just seeing individual files
- Better suggestions because they know how your code connects
- More accurate auto-completions
- Can help with complex refactoring across multiple files
Code Indexing in Different IDEs
Cursor IDE:
- Built-in AI that uses indexing to understand your entire codebase
- Can answer questions like "how does authentication work in this project?"
- Suggestions are context-aware based on your project patterns
- Works especially well with TypeScript/JavaScript projects
Trae IDE:
- Similar AI-powered indexing capabilities
- Focuses on collaborative coding with AI
- Real-time code analysis and suggestions
- Good for rapid prototyping and experimentation
VS Code + GitHub Copilot:
- Copilot uses a form of indexing but more limited to immediate context
- Extensions like "Code Tour" help with manual code indexing
- IntelliSense provides basic indexing for autocomplete
- Not as comprehensive as dedicated AI IDEs but still helpful
The Real Game Changer:
Once your code is properly indexed, asking an AI "add a search feature similar to the user search" actually works because the AI knows exactly what "user search" refers to and how it's implemented.
Next Steps: Getting My Act Together
So for the next stage, I need to:
- Prepare a proper folder structure (using ONE terminal this time!)
- Work towards dependencies - figure out what packages I actually need
- Proper documentation is important - document my approach before diving into code
The 2% progress might seem small, but I'm learning that preparation is everything. Better to spend time understanding the foundation than building on quicksand.
Wait for My Update
As I work towards these goals, I'll keep documenting the messy, confusing, but hopefully educational journey of building something real in open source.
Anyone else been through the "I understand the concepts but have no idea how to start" phase? What got you unstuck?
Day 3 coming soon - where I'll either have a beautiful folder structure or completely break something. Place your bets! 😄
Thank you for following along on this chaotic learning adventure!
Top comments (0)