Grading

See also: SyllabusSyllabus
See also: Lectures · Class Schedule · Grading · AI Policy

Course Title: Tech 1 — Web & Mobile Ecosystem Fundamentals

Course Objective: Gain a foundational understanding of the...
· LecturesLectures
See also: Syllabus · Class Schedule · Grading

One 2-hour session per week, Tuesdays 2:15–4:15pm. No class on 8 and 15 September.


{%- for l in site.data.lectures -%}
{%- assign targ...

Tech 1 Grading Plan

Assessment and Grading Breakdown

# Component Weightage (%)
1 Attendance and Class Participation 10%
2 Class Exercises 50%
3 Final Project 40%

(If the university requires written midterm/endterm exams, weightages will be adjusted and announced in class.)

1. Attendance and Class Participation (10%)

Attendance is recorded each session. I have an open door policy — if you need to take a break or leave, feel free to do so. The penalty is that you don't get the attendance credit and don't learn from the material. No distinction is made between excused and unexcused absences.

2. Class Exercises (50%)

Weekly build exercises, done mostly in class and finished as homework:

  1. Exercise - Ship a Page with GitHub PagesExercise - Ship a Page with GitHub Pages
    Put your website on the real internet — free, today

    You already have a repo made from web-starter. Now we tell GitHub to serve it as a live website. This is called GitHub Pages — free hosting for ...
  2. Exercise - Redesign your Home Page in FigmaExercise - Redesign your Home Page in Figma
    Make your home page your own

    You have a live website, but it looks like the template. Before we learn CSS next week, decide what you actually want your own home page to look like — in the tool you...
  3. Exercise - Figma to CodeExercise - Figma to Code
    Make the real page match your Figma

    Last week you designed your home page in Figma. This week you build it. The design already exists, so the exercise is to translate your designs into implementat...
  4. Exercise - Unusual InteractionsExercise - Unusual Interactions
    The web is standardised

    Most blogs look like blogs. Most news sites look like news sites. Most Ecommerce websites look like ecommerce websites.

    What if we kept the standard interactions aside and...
  5. Exercise - Trace a RequestExercise - Trace a Request
    Watch your website load, piece by piece

    Use the browser's Network tab to observe everything that happens between typing your URL and seeing your page.

    Steps


    Open your own site (from Exercis...
  6. Exercise - Add a DatabaseExercise - Add a Database
    Make something two people can use at once

    Everything you built before this week forgets on refresh, and none of it knows anyone else exists. Fix both. Build a small thing backed by Firebase Realti...
  7. Exercise - API Mashup Note does not exist
    This note is has not been published (yet).
    or Exercise - Add an AI FeatureExercise - Add an AI Feature
    Put a model inside your product

    Add one genuinely useful AI feature to something you've already built this semester. The bar: it must be better because it's AI, not AI for its own sake.

    Ideas


    ...
  8. Exercise - Mobile Ecosystem ComparisonExercise - Mobile Ecosystem Comparison
    iOS vs Android, from a product team's chair

    Compare and contrast the iOS and Android ecosystems for app development and distribution, highlighting the differences that would actually change a prod...
  9. Exercise - SDLC Stage Mapping Note does not exist
    This note is has not been published (yet).

Each is graded out of 8 on outcome quality, understanding demonstrated, and process documentation (including prompt logs). I will consider your best 6 scores.

3. Final Project (40%)

Group project (up to 3 people), built over the last third of the course and presented at Demo Day. See Project - Final Project Note does not exist
This note is has not been published (yet).
for the brief and rubric.

A note on AI and academic integrity

See the full AI PolicyAI Policy
See also: Grading · Syllabus

In many courses, an AI policy is a list of things you can't do. This course is different: using AI to generate code is the expected way of working here. The sk...
. In this course, using AI to generate code is not just allowed — it's the expected way of working. What is dishonest:

  • Presenting work you can't explain. If you shipped it, you should be able to answer "how does this part work?" at the level this course teaches.
  • Hiding your process. Prompt logs and iteration history are part of every submission.
  • Copying another student's project or prompts wholesale.

Cite third-party assets, datasets, templates, and any substantial code you didn't generate yourself. For group projects, each member's contributions must be documented.