DEV Community

Cover image for From Hackathon Chaos to Clean CLI: Reviving My Daily Routine Analyser with GitHub Copilot
Tanush
Tanush

Posted on

From Hackathon Chaos to Clean CLI: Reviving My Daily Routine Analyser with GitHub Copilot

GitHub “Finish-Up-A-Thon” Challenge Submission

🧠 What I Built

I revived a C-based CLI project called Daily Routine Analyser, originally built during a hackathon under extreme time pressure.

At its core, the tool helps users break down their 24-hour day into:

  • Study 📚
  • Sleep 😴
  • Exercise 🏃
  • Leisure 🎮

It then calculates a simple productivity score out of 10 and provides insights about daily balance.

What started as a rushed prototype has now been transformed into a clean, modular, and readable CLI application with improved structure and logic.

👉 GitHub Repo: https://github.com/tanush326k/daily-routine-analyser


🎬 Demo

🔗 GitHub Repository:

https://github.com/tanush326k/daily-routine-analyser

💻 How it works:

  • User enters daily activity hours
  • Program validates total ≤ 24
  • System evaluates habit balance
  • Outputs:
    • Time breakdown
    • Habit insights

    - Final productivity score (/10)

🔁 The Comeback Story

The original version of this project was written during a hackathon in a highly rushed environment.

🔴 Before (Hackathon Version)

  • Everything inside a single main() function
  • No modular structure
  • Hardcoded logic and repetitive flow
  • Built just to “make it work”

It functioned — but it wasn’t maintainable or scalable.


🟢 After (Revived Version)

When I revisited it, I focused on turning it into something cleaner and more structured:

  • Refactored code into modular functions
  • Improved scoring logic clarity
  • Added structured thinking using struct
  • Enhanced readability and maintainability
  • Cleaned up nested loops and logic flow

The goal wasn’t just to fix it — it was to make it feel like a real project, not a hackathon leftover.


🤖 My Experience with GitHub Copilot

GitHub Copilot played a key role in this revival process.

It helped me:

  • Break down a large main() function into smaller reusable functions
  • Suggest cleaner implementations for scoring logic
  • Improve structure using struct for better data organization
  • Reduce unnecessary nesting and improve readability
  • Speed up refactoring decisions

Instead of writing everything from scratch again, Copilot acted like a pair programmer helping restructure legacy code into something clean and modern.


💡 Key Takeaway

This project taught me that:

“A hackathon project is not the end — it’s the starting point.”

Even simple ideas can become meaningful software when revisited with better structure and tools.


🚀 Future Improvements

  • Save daily logs to CSV
  • Weekly progress tracking system
  • Graph-based visualization
  • Habit streak tracking system
  • Possible GUI/web version

👨‍💻 Closing Note

This project represents my journey from:
“just getting it working” → “making it well-designed and maintainable.”

And GitHub Copilot helped accelerate that transformation significantly.

Top comments (0)