Web app back end development schedule

Between now and midterm break, we're going to introduce you to several techniques leading up to creating what's known as the back end or server side of your web application. By the Wednesday after midterm break (May 7), you will have designed and implemented a database-driven HTTP-based Application Programming Interface (more commonly known simply as an API) based on your chosen dataset.

Getting to an designed and implemented API by May 7 requires some step-by-step introduction to and practice with several new tools and techniques. To give you an idea of how this is going to go, here's the schedule we will follow to get there.

All of the ASSIGNMENT items will involve handing something in either individually or as a team on the specified date. The LAB items will be in-class activities, sometimes with a Google survey to fill out, sometimes not.

Reordered on April 22

W 04/16 - [LAB] Command-line interface (CLI) intro F 04/18 - [LAB] Flask intro - [ASSIGNMENT] individual CLI for one query M 04/21 - API design discussion - [ASSIGNMENT] individual Flask API endpoint based on CLI assignment W 04/23 - API design recap - [LAB] using flask on stearns.mathcs.carleton.edu F 04/25 - [LAB] Database (DB) and postgres intro - [ASSIGNMENT] team API design M 04/28 - API design feedback to each other - more database intro - [ASSIGNMENT] team DB design & population W 04/30 - DB design feedback F 04/25 - [ASSIGNMENT] team DB second draft and population M 05/05 - Midterm break W 05/07 - [ASSIGNMENT] team API second draft and implementation

There will be more information as we go, of course.