How phillipai/100-days-of-code-python works
Overall Project Type and Purpose
• This repository is not a single unified application—it is a curated collection of individual projects/exercises developed over 100 days. Each “dayXX” directory contains its own mini-project that covers different technical topics ranging from basic Python scripting to full-stack web development and data science.
• The README categorizes projects into Beginner, Intermediate, Intermediate+, Advanced, and Professional Portfolio Projects. This categorization along with the diversity of technologies (from simple scripts to Flask applications, data science notebooks, and web scraping tools) should be clearly conveyed.
Analyzing the File Structure
• The top-level file tree is organized by “dayXX” directories, each representing a separate coding challenge with its own README and main script (and sometimes extra modules, assets, or data files).
• Some directories (e.g., day56, day57, day61, day62, etc.) have subdirectories like “static”, “templates”, or even additional documentation/PDFs. This indicates that some exercises employ web frameworks (mostly Flask) and even design patterns for organizing client-side and server-side concerns.
• Other days include Jupyter notebooks (notebooks, CSV, or data files) and even a few projects with external CSVs and configuration files.
Using Insights from the README
• It also outlines the evergreen themes: core Python concepts, object-oriented programming, GUI development (using Tkinter), web development (HTML, CSS, Flask), and data science techniques (using Pandas, NumPy, Matplotlib, etc.).
a. Main Components:
• The Repository Backbone: A high-level component that represents the organization of projects by day.
• Categories of Projects: Separate nodes for Beginner, Intermediate, Intermediate+, Advanced, and Portfolio Projects.
• Individual Project Modules: Within each category, each “dayXX” can be represented as a subcomponent. For example:
• “Day 07 – Hangman” (console game)
• “Day 15/16 – Coffee Machine and OOP practice”
• “Day 56/57 – Flask applications with static files and templates”
• “Day 71, 72, etc. – Data Science notebooks”
• Technology/Framework Specific Components: In projects where the structure is more layered, mark out:
• Frontend elements (HTML, CSS, JavaScript in Flask projects),
• Backend logic (main.py, server.py, etc.),
• Static assets (assets, static, templates directories),
• Data sources (CSV files, SQLite databases, etc.).
b. Relationships and Interactions:
• For data science projects, highlight the interaction between raw data (CSV files, databases) and analytical notebooks where processing and visualization occur.
c. Architectural Patterns and Design Principles:
• For Flask-based projects, explain that they generally adhere to a Model-View-Controller (MVC) or similar templating pattern.
• In gaming or GUI projects (Tkinter or Turtle), note that the design is event-driven.
• Importance of modularity as each “day” works as an independent, self-contained module that reinforces a particular programming concept.
d. Mention Key Technologies:
• Python 3 as the core language.
• For web development: Flask, Jinja templating, HTML5, CSS3, and Bootstrap (for styling).
• For data science: Jupyter Notebooks, Pandas, NumPy, Matplotlib, Plotly, Seaborn.
• Additional tools: Selenium, Beautiful Soup, Tkinter, and SQL (with SQLite/PostgreSQL in applicable days).
Elements
• Clear labels for each main component (e.g., “Day 07: Hangman Game”, “Day 61: Advanced Forms with Flask”, “Day 100: Multivariable Regression”).
• The overall structure of the repository as a compilation of multiple, independent projects.
• Grouping projects based on difficulty/technology (as per the README’s categories).
• For each project, show its component layers (code logic, UI, data source) as applicable.