Skip to content

Commit 6ce9320

Browse files
authored
2022 Wrapped (#115)
* Link to archive of page that no longer exists * Links to notes and exercises * Copy over some ad hoc revisions to assignment expectations that worked well this semester * Save more notebooks used this year * Upload some images used for branding
1 parent 67eb02c commit 6ce9320

16 files changed

Lines changed: 6950 additions & 2 deletions

admin/canvas_244.md

Lines changed: 103 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,103 @@
1+
2+
Here is some updated assignment language used in Fall 2022. We were able to acheive a better pace than previous offerings.
3+
4+
## Command Line Computing
5+
6+
Complete the Command Line Computing Exercises. Take some screenshots of your terminal output along the way, or just at the end. And upload the screenshots here.
7+
8+
Did you get to download any cool YouTube videos using the youtube-dl command-line tool?
9+
10+
## Run the App
11+
12+
Complete the Run the App Exercise, which asks you to run some existing code.
13+
14+
Do the Tic Tac Toe version. Take some screenshots of you playing the game via your terminal, and upload those screenshots here.
15+
16+
Feel free to explore the Daily Briefings version as well, if you'd like to fetch some weather forecast and send emails. Feel free to upload screenshots here if you do.
17+
18+
## Unemployment Report
19+
20+
Follow along with our in-class progress to re-create the Unemployment Report notebook, but using local development tools and a version controlled process. Complete all Challenges A, B, and C. Do at least the CSV or the JSON version, or both. If you do both, use separate files (see solution code).
21+
22+
For full points:
23+
24+
+ your repo's version history should reflect at least a handful of incremental commits (i.e. one commit for fetching the data, another for Challenge A, another for Challenge B, and another commit for Challenge C, etc.)
25+
+ your python script should demonstrate secure usage of environment variables, by reading them from the ".env" file
26+
+ your README file should contain comprehensive instructions (i.e. setup steps, usage commands, etc.) necessary to setup and run the file
27+
+ Make sure you've uploaded / pushed your most recent code to GitHub before submitting.
28+
29+
Submit the Repository URL via the Deliverable Submission Form.
30+
31+
## Unemployment Cleanup
32+
33+
Follow along with our in-class progress to simplify, refactor and test our Unemployment Report app, including branch operations and pull request workflow.
34+
35+
For full points, includes:
36+
37+
+ automated checks from GitHub Actions, with tests passing on CI
38+
+ evidence of branch operations and at least one merged Pull Request
39+
40+
Optionally:
41+
42+
+ include a PR review / comments from a classmate :-)
43+
44+
Make sure you've uploaded / pushed your most recent code to GitHub before submitting. Merge into the main branch any Pull Requests / branches that you want to be included for evaluation.
45+
46+
Submit the Repository URL via the Deliverable Submission Form, unless you're extending from a previously submitted repository, in which case there is no need to resubmit unless you'd like to.
47+
48+
## Unemployment Web
49+
50+
Follow along with our in-class progress to create a web application interface into the unemployment report, and deploy it to a server for hosting.
51+
52+
For full points, deploy the app to a server (you can use Heroku or any other platform). Note the hosted URL.
53+
54+
Submit the repository and hosted URLs via the Deliverable Submission Form.
55+
56+
<hr>
57+
58+
## Project Investigation and Proposal
59+
60+
### Subject Matter Selection
61+
62+
For your Freestyle Project, you are asked to make a user-facing software application, ideally for business purposes. Choose a subject matter that is interesting to you (from sports, to finance, music and movies, games, etc.). Or think of ways to improve some process you experience in your daily life. If you're stuck and looking for an idea, try searching the web for some data source (i.e. web page or API) of interest, and do something cool / interesting / useful / fun with the data. NOTE: your project doesn't need to focus on data - for example you could alternative make a RPG style game and that would be fine.
63+
64+
### Group Member Selection
65+
66+
For this project you can work by yourself, or in groups of two or three students total. Use the Group Formation Sheet to share project ideas and find group members. When you know who you will be working with, make sure to designate each group member's Net ID in the in the Group Formation Sheet, along with your subject matter of choice. It will be OK to revise your subject matter / pivot later, as necessary.
67+
68+
### Project Investigation / Prototyping
69+
70+
For this Investigation deliverable, explore your ability to make an app related to your proposed subject matter. You will most likely be doing this in notebook format. In a later deliverable we will likely translate your notebook prototype into a more fully-featured GitHub repository.
71+
72+
### Submission Instructions
73+
74+
When you're done with your prototype notebook, only one member of your group needs to submit the Project Proposal Form, listing the email addresses of all group members, answering the questions, and providing the link to your Colab notebook.
75+
76+
### Evaluation
77+
78+
On time submission of the proposal form is worth 5/15 points
79+
The content of your investigation / prototype notebook is worth 10/15 points
80+
81+
Example Prototype Notebook:
82+
+ Market Sentiments App Prototype
83+
84+
85+
## Project Implementation
86+
87+
See the Freestyle Project Implementation deliverable requirements for more details.
88+
89+
Implement a finished version of your project, ideally as a GitHub repository, however if you think a notebook is more desirable, discuss that with the professor.
90+
91+
When you're done, only one member of your group needs to submit the Deliverable Submission Form, selecting "Implementation" from the dropdown, listing the email addresses of all group members, and providing the link to your GitHub repo.
92+
93+
## Project Presentations
94+
95+
See the Freestyle Project Demonstration deliverable requirements for more details.
96+
97+
Prepare a slideshow in Google Slides. See deliverable requirements for details. Your presentation should be around 5-6 minutes in length total, so around 5-7 slides total. Upload your slides here in PDF format by the due date.
98+
99+
Our Demo Day is scheduled on ____ from ____ to ___. We will be Zoom-only during this time.
100+
101+
If you would like to prerecord your presentation (for example using Zoom recording), then you must upload your MP4 file here before the due date. Otherwise you will give your presentation live via Zoom on Demo Day.
102+
103+
The Demo Day Schedule is here. Please indicate if you will be presenting in person or prerecorded.
243 KB
Loading
78.4 KB
Loading

img/branding/python-banner.jpeg

27.1 KB
Loading

img/branding/startup.png

34.8 KB
Loading

img/slides/laptop-icon-10.png

28.9 KB
Loading

img/slides/mvp.jpg

30 KB
Loading

notes/info-systems/people.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ At the heart of any computer-based information system are the people within the
66

77
Because the system exists to help the user, the user's needs should be at the center of a system's design.
88

9-
> Start with people's needs. Begin projects by conducting research with real people to understand who they are, what they need, and how they behave. Design programs and services around those needs, continuously test with users, and refine policy and processes accordingly. - ["User Centered Design", from the Code for America Playbook](https://www.codeforamerica.org/practices/user-centered-design)
9+
> Start with people's needs. Begin projects by conducting research with real people to understand who they are, what they need, and how they behave. Design programs and services around those needs, continuously test with users, and refine policy and processes accordingly. - ["User Centered Design", from the Code for America Playbook, 2018](https://web.archive.org/web/20180720045811/https://www.codeforamerica.org/practices/user-centered-design)
1010
1111
## User Needs
1212

File renamed without changes.

0 commit comments

Comments
 (0)