Class 5: September 1, 2026 · ENTR 5000
Notes from September 1, 2026. These notes record the discussion and instructions given that day. For current requirements and due dates, use the assignment guidelines and semester schedule.
From project ideas to learning goals
Students introduced a problem they wanted to investigate and technical skills needed to make progress. The exercise separated the customer problem from the proposed technology: before committing to features, articulate who needs help and what improvement would matter. Peer working groups can form around a shared problem or a similar technical learning level; they are flexible, not permanent project teams.
The discussion also stressed scope. When two different business ideas both look promising, choosing one can produce more useful progress within a short sprint. A personally successful workflow must become understandable and repeatable for someone without its creator’s background knowledge before it can serve other users.
Technical concepts introduced
- API: a defined way for software systems to request data or actions from another system. Spotify’s Web API was the example used to discuss data access and permissions.
- MCP (Model Context Protocol): a standard for exposing tools and context to AI applications. An MCP server can connect an AI application to underlying APIs and other resources. See the official introduction.
- Back-end responsibilities: security, authentication, privacy, database administration and scaling. A convincing front end does not establish that these responsibilities are handled.
- Continuous integration/deployment: a workflow for repeatedly integrating changes and delivering tested updates, rather than treating each release as a wholly separate project.
- Durable project context: move important decisions and explanations into documentation so they do not depend on a single chat history.
The name-practice tool was briefly revisited; the AI class’s optional extra-credit challenge remains Thursday, September 3.
Before Thursday, September 3
- Share your sprint-preparation responses in the designated Slack thread—paste text or link to your Google Doc.
- Complete any two adventures at AI Adventure. The Excursion or Expedition levels were recommended; choose activities that develop something useful for you. Be ready to share what you tried or built.
- Note classmates you might want to work alongside, based on problem interests or technical goals. We will use small groups to define success criteria for the next part of the sprint.
Optional additional practice: Create Club RSVP, also linked in the announcements deck.