{"id":27150936,"url":"https://github.com/joshuamichaelhall-tech/6-7-coding-challenge","last_synced_at":"2025-07-25T20:35:43.142Z","repository":{"id":285408691,"uuid":"958040684","full_name":"JoshuaMichaelHall-Tech/6-7-coding-challenge","owner":"JoshuaMichaelHall-Tech","description":"A 500-day coding challenge (6 days/week) aligned with Launch School's mastery-based learning approach. Building mastery through consistent practice while honoring the Sabbath rest.","archived":false,"fork":false,"pushed_at":"2025-05-26T17:00:24.000Z","size":238,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2025-05-26T18:19:09.679Z","etag":null,"topics":["coding-challenge","discipline","full-stack","javascript","launch-school","machine-learning","mastery-based-learning","practice","programming-practice","python","ruby","software-engineering"],"latest_commit_sha":null,"homepage":"","language":"Ruby","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/JoshuaMichaelHall-Tech.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"docs/CONTRIBUTING.md","funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2025-03-31T14:46:03.000Z","updated_at":"2025-05-26T17:00:27.000Z","dependencies_parsed_at":"2025-04-07T18:32:42.841Z","dependency_job_id":null,"html_url":"https://github.com/JoshuaMichaelHall-Tech/6-7-coding-challenge","commit_stats":null,"previous_names":["joshuamichaelhall-tech/6-7-coding-challenge"],"tags_count":0,"template":true,"template_full_name":null,"purl":"pkg:github/JoshuaMichaelHall-Tech/6-7-coding-challenge","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JoshuaMichaelHall-Tech%2F6-7-coding-challenge","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JoshuaMichaelHall-Tech%2F6-7-coding-challenge/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JoshuaMichaelHall-Tech%2F6-7-coding-challenge/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JoshuaMichaelHall-Tech%2F6-7-coding-challenge/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/JoshuaMichaelHall-Tech","download_url":"https://codeload.github.com/JoshuaMichaelHall-Tech/6-7-coding-challenge/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JoshuaMichaelHall-Tech%2F6-7-coding-challenge/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":265016902,"owners_count":23698394,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["coding-challenge","discipline","full-stack","javascript","launch-school","machine-learning","mastery-based-learning","practice","programming-practice","python","ruby","software-engineering"],"created_at":"2025-04-08T14:22:36.415Z","updated_at":"2025-07-12T16:05:39.900Z","avatar_url":"https://github.com/JoshuaMichaelHall-Tech.png","language":"Ruby","funding_links":[],"categories":[],"sub_categories":[],"readme":"## This Ruby CLI tool was built during my software engineering studies.\nI now focus on DevOps/Infrastructure automation - see my AWS/Terraform projects.\n\n# 6/7 Coding Challenge\n\nA personal commitment to code for 500 days, six days a week (Monday through Saturday), while observing the Sabbath rest on Sundays.\n\n## What Is This?\n\nThe 6/7 Coding Challenge is a structured approach to mastering software engineering through consistent practice while respecting the importance of regular rest. The \"6/7\" represents coding for six days each week while resting on the seventh (Sabbath).\n\n## Current Phase\nYou're currently in: **Phase 1: Day 1**\n\n## 🚀 Quick Start\n\n```zsh\n# Clone the repository\ngit clone https://github.com/yourusername/6-7-coding-challenge.git\ncd 6-7-coding-challenge\n\n# Install the Ruby-based setup script\nmkdir -p ~/bin\ncp scripts/cc-installer.rb ~/bin/\nchmod +x ~/bin/cc-installer.rb\n\n# Run the installer\nruby ~/bin/cc-installer.rb\n\n# Source your .zshrc or restart your terminal\nsource ~/.zshrc\n\n# Start your first day\nccstart\n```\n\n## Core Commands\n\nAfter installation, these commands will be available:\n\n| Command    | Description                                           |\n|------------|-------------------------------------------------------|\n| `ccstart`  | Start the day's coding session in tmux                |\n| `cclog`    | Record your progress in the weekly log                |\n| `ccpush`   | Commit changes and increment the day counter          |\n| `ccstatus` | Show your overall challenge progress                  |\n| `ccconfig` | View or modify your configuration                     |\n| `ccupdate` | Update scripts to the latest version                  |\n| `ccbackup` | Backup logs and configuration                         |\n| `ccrestore`| Restore logs from a backup                           |\n| `ccuninstall` | Remove scripts and configuration                   |\n\n## Key Features\n\nThe 6/7 Coding Challenge includes several powerful features to enhance your learning journey:\n\n### Backup and Restore System\n\nMaintain your progress across different computers or through system changes:\n\n- **Local Backup**: Save logs to a timestamped directory in your home folder\n- **Git Repository**: Create special branches for logs in your repository\n- **Custom Location**: Specify any directory for your backup\n- **Simple Restore**: Easily restore from any backup source with `ccrestore`\n\n```zsh\n# Create a backup of your logs\nccbackup\n\n# Restore from a previous backup\nccrestore\n```\n\n### Flexible Phase Management\n\nAdapt your challenge structure without losing past progress:\n\n- **Interactive Configuration**: Update phases with guided prompts\n- **Customizable Structure**: Modify phase names, directories, and durations\n- **Safe Updates**: Change your challenge structure without losing logs\n\n```zsh\n# Update configuration interactively\nccconfig --interactive\n\n# Update specific phase information\nccconfig --set \"challenge.phases.1.name=New Phase Name\"\n```\n\n### Retroactive Logging\n\nNever lose track of your progress, even if you forget to log:\n\n- **Log Previous Days**: Add entries for days you've completed but forgotten to log\n- **Chronological Ordering**: Automatically places entries in the correct sequence\n- **Duplicate Handling**: Smart replacement of existing entries\n\n```zsh\n# Log the current day (standard usage)\ncclog\n\n# Log a specific previous day\ncclog 5  # Logs day 5 retroactively\n```\n\n### Project Templates\n\nStart each day with well-structured project templates:\n\n- **Phase-Specific Templates**: Tailored for different technologies\n- **Consistent Structure**: Maintain a uniform approach across your challenge\n- **Customizable**: Adapt templates to your specific needs\n\n## Daily Workflow\n\n1. **Start your day**: Run `ccstart` to set up your environment\n2. **Write code**: Work on your daily project\n3. **Document**: Fill in your README.md with goals and reflections\n4. **Log progress**: Run `cclog` to update your weekly log\n5. **Commit**: Run `ccpush` to commit changes and increment day counter\n\n## Challenge Structure Examples\n\nThe challenge is highly customizable. Here are some examples of how you might structure it:\n\n### Default Structure (Single Phase)\nA simple 500-day coding journey:\n- **Phase 1: Coding Challenge** - 500 days of consistent practice\n\n### Five-Phase Example (Technology Learning Path)\nA comprehensive programming language journey:\n\n1. **Phase 1: Backend Fundamentals** (100 days)\n   - Building server-side applications and mastering core language concepts\n   \n2. **Phase 2: Data Science \u0026 Analysis** (100 days)\n   - Working with data processing, visualization, and analysis tools\n   \n3. **Phase 3: Frontend Development** (100 days)\n   - Creating responsive user interfaces and interactive experiences\n   \n4. **Phase 4: Full-Stack Projects** (100 days)\n   - Integrating backend and frontend in complete applications\n   \n5. **Phase 5: Specialization** (100 days)\n   - Focusing on a specific area like ML, mobile development, or cloud\n\n### Three-Phase Example (Project-Based)\nA focused project creation journey:\n\n1. **Phase 1: Learning Fundamentals** (100 days)\n   - Mastering core technologies and concepts\n   \n2. **Phase 2: Building Projects** (200 days)\n   - Creating 10 complete projects of increasing complexity\n   \n3. **Phase 3: Advanced Specialization** (200 days)\n   - Focusing on large-scale applications in your desired specialty\n\n## Documentation\n\nFor more detailed information, check out these guides:\n\n- [Getting Started](docs/getting-started.md): Complete setup instructions\n- [About the Challenge](docs/ABOUT.md): Philosophy and motivation\n- [Customization Guide](docs/CUSTOMIZATION.md): How to tailor the challenge to your needs\n- [Project Templates](docs/project-templates.md): Templates for each phase\n- [Documentation Index](DOCUMENTATION.md): All available documentation\n\n## Project Philosophy\n\nThis challenge follows several key principles:\n\n1. **Mastery over Surface Knowledge**: Focus on deep understanding\n2. **Consistency over Intensity**: Regular, moderate practice\n3. **Application over Theory**: Hands-on projects\n4. **Documentation over Silent Progress**: Regular reflection\n5. **Structure over Randomness**: Organized approach\n6. **Rest as Essential**: Recognition that regular rest enhances productivity\n\n## Acknowledgements\n\nThis project was developed with assistance from Anthropic's Claude AI assistant, which helped with:\n- Documentation writing and organization\n- Code structure suggestions\n- Troubleshooting and debugging assistance\n\nClaude was used as a development aid while all final implementation decisions and code review were performed by the original creator.\n\n## License\n\nThis project is licensed under the MIT License - see the [LICENSE.txt](LICENSE.txt) file for details.\n\n## Disclaimer\n\nThis is a personal development and learning project. The code is provided as-is, with no guarantees or warranties. By using this codebase, you agree to use it at your own risk.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjoshuamichaelhall-tech%2F6-7-coding-challenge","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fjoshuamichaelhall-tech%2F6-7-coding-challenge","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjoshuamichaelhall-tech%2F6-7-coding-challenge/lists"}