How jasonthename/tech-boot-camp works
Project type and purpose
• This is a “Tech-Boot-Camp” monorepo containing learning materials (PDF guides, Jupyter notebooks), standalone Python scripts, and a collection of small Flask-based demo applications. Its goal is to provide tutorials, exercises, and sample apps for boot-camp students.
File structure
• Top-level folders:
• Guides and Help – PDF teaching materials
• Notebooks – Jupyter notebooks for hands-on data exploration and API exercises
• Projects – individual demo web apps (each in its own subfolder)
• Root-level Python scripts (adventure_game.py, etc.) are standalone command-line activities.
• Within Projects, each subfolder is a self-contained microservice:
• click_counter (Flask + Jinja2)
• social_feed (Flask + Jinja2)
• sentiment-messages-analysis (Flask, JSON data, text analysis core)
• whatsapp-chatbot (Flask webhook)
• faiss-search (local Python script using FAISS)
• whisper-transcribe (backend + a “site/frontend” static HTML + Flask wrapper)
README
• Very minimal (“# Tech-Boot-Camp”), so rely primarily on folder names and file conventions to infer tech stack: Python 3, Flask, Jinja2, Jupyter, FAISS, local JSON, static assets.
Main components
a. Repository root – container for all artifacts
b. Documentation cluster – “Guides and Help” PDFs
c. Notebook cluster – Jupyter server instance with multiple notebooks
d. Demo apps – six independent Python/Flask microservices:
• Click Counter
• Social Feed
• Sentiment Analyzer (with core text_analysis)
• WhatsApp Chatbot
• FAISS-based Search
• Whisper Transcription (backend + frontend)
e. Standalone CLI scripts (adventure_game.py, etc.)
Relationships and interactions
• All components share the same Python runtime environment (node indicating “Python 3.x interpreter + pip”).
• Flask apps serve HTTP requests, render Jinja2 templates, and optionally read local JSON or audio files.
• Jupyter notebooks connect to the same Python kernel.
• No direct inter-service calls; they are decoupled demos.
Architectural patterns and design principles
• Modular monorepo: each project in its own folder with its own requirements.txt.
• Microservice-style demos (small, single responsibility).
• Separation of concerns: documentation vs. interactive notebooks vs. web apps vs. CLI scripts.
Relevant technologies/frameworks
• Python 3, Flask, Jinja2, Jupyter Notebook, FAISS, local JSON files, static HTML.
Detail
• Project folder as its own node
• With its primary framework/library (e.g., “Flask + Jinja2,” “FAISS”)
• That each demo has its own requirements.txt—imply isolated environments