SousChef
FastAPI + Streamlit recipe system with AI extraction from text/images/URLs, JWT auth, Redis-backed background work, Docker Compose and Playwright E2E.
Engineering of Advanced Software Solutions is a two-part HIT course about ownership. Part A: one student builds one complete system. Part B: a team turns technology into an operating company.
Each student takes an idea to a running, testable product and practices architecture, interfaces, reliability, deployment, and end-to-end ownership.
Core: Python & uv · Git/Linux · HTTP/APIs · FastAPI · persistence/migrations · frontend · Docker/Compose · testing/CI · auth/security · async work · caching/queues · cloud/AI · observability.
Teams choose a real problem, find users, ship, operate the product, measure what happens, and change direction from evidence. Product, engineering, ML and GTM become one loop.
Core: problem selection · customer discovery · product scope · team ownership · production operations · analytics/experiments · AI/ML where useful · reliability/security · pricing/positioning · distribution/GTM · weekly shipping · metrics · demo day.
A verified sample across cohorts showing progression from full-stack foundations to AI-native systems.
FastAPI + Streamlit recipe system with AI extraction from text/images/URLs, JWT auth, Redis-backed background work, Docker Compose and Playwright E2E.
FastAPI prompt library with SQLModel/Alembic, Redis, a separate analyzer service, Claude via Pydantic AI, Docker Compose and async refresh.
Scheduled flight-data ingestion with FastAPI, Streamlit, PostgreSQL, analytics endpoints and Docker Compose.
React frontend, FastAPI backend, MongoDB and Docker Compose—the early-course end-to-end pattern in a compact system.
Teams own users, operations, measurement, iteration, distribution, and the code that supports them.
AI home-food management for inventory, recipe suggestions and shopping. The team also did customer segmentation, market research, revenue modeling, lead generation and outreach.
System → users → market → leads.
A live publishing product with content, readers, distribution, and an operating public surface.
Build → publish → operate → learn.
An earlier cohort applied computer vision to contamination in waste streams and connected model output to an operational decision.
455 questions across 34 modules covering durable systems mental models and practical engineering.
Reproducible project evaluation with setup, lint/test workflows, parallel execution and structured comparison.
Engineering checklist spanning Bash, Git, Docker, FastAPI, Pytest, React, HTTP, AWS, security and data.
Part A: one person owns a system end-to-end. Part B: a team builds a company that ships, learns and grows.