The Spaghetti Code Chef

Hey chefs! 👋 Quick update from the kitchen.

Spaghetti Code Chef v0.1 is officially cooking! 🍳

I just finished the core backend logic. Now, when you paste a GitHub repo link, the Python backend dives deep (using the Recursive Tree API) to count indentations, nested loops, and complexity to judge if your code is “Al Dente” or just a total mess.

Updates: 🐛 Squashed a bug: The requests library was blocking the main thread and freezing the UI. Fixed the async logic, and now it runs smooth as butter. 🔐 Security: Moved API tokens to .env to keep things safe and bumped up the GitHub rate limits. 🍝 UI: Added a spinning pasta loading screen because… priorities.

Next up: Turning these text reports into cool charts! 📊

Thoughts?

👨‍🍳 KITCHEN IS OPEN! First Order: The Spaghetti Code Chef 🍝

I’ve officially tied my apron and stepped into the kitchen (VS Code). There is too much RAW, BLAND, and TANGLED code out there. It’s a disgrace! 😤 Someone has to step up and fix this mess.

What’s on the Menu? I’m building ‘The Spaghetti Code Chef’. It’s a Python-based backend tool that takes your messy, unreadable code and tells you exactly how much of a disaster it is. Is it Al Dente? Or is it just mush? We’re going to find out.

Today’s Special:

The Stove: FastAPI (Because it heats up fast 🚀).

The Sauce: A pinch of Jinja2 and some HTML.

Current Status: The water is boiling, and the first endpoints are served. I haven’t burned down the kitchen… yet.

Don’t bring me frozen code! Stay tuned, I’ll be here until this project is perfection. 🤌