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)