INF2144H Coded Cultures: The Rise of Digital Media Platforms

How INF2144H is assessed

The Fall 2026 syllabus publishes five coursework components totaling 100%. Use Quercus for current group allocations, submission instructions and operational updates.

What INF2144H covers

Twelve chapters follow the published class sequence from computing histories to critical code, with methods for research reviews and platform design.

It then follows those practices into platform infrastructures, algorithms, creator economies and critical code. The central habit is to reject inevitability.

Present systems are outcomes of design choices, standards, business arrangements, institutions and user adaptations, and earlier alternatives reveal that the current configuration was not the only imaginable path.

From code to platform culture

Code appears in several forms: programming languages, markup, character systems and encoding formats. Each form makes a different operation possible.

Software combines operations into usable workflows, interfaces make some actions visible and convenient, and platforms coordinate participants through rules, data and discovery. Infrastructure extends beneath the visible service through networks, identity, payments, hosting, standards and maintenance.

A careful analysis keeps these layers distinct long enough to identify the mechanism joining them.

Technical history as a method

The early chapters examine software industries, time-sharing, information networks and desktop publishing. These histories are not a parade of inventions.

They ask how technical functions became sustainable products and practices through distribution, support, complementary tools, standards and organizational work.

A successful case study follows an artifact or workflow, identifies the actors and choices that shaped it, and compares an alternative without treating market survival as proof of superior design.

Media forms and interfaces

Digital images, audio and games show why technical affordance is only one part of cultural form.

A file format can enable animation or compression, but software operations, platform circulation and community conventions determine how an artifact is used and understood. Games similarly join executable rules, fictional framing and situated play; streaming adds performance, audience and platform relations.

The guide uses controlled comparisons so that claims remain attached to the layer that performs the action.

Algorithms, visibility and research limits

Algorithmic visibility must be studied through bounded evidence.

Platform statements establish declared objectives, interfaces show visible options, creator accounts reveal perceived incentives, output samples show patterns and audits test responses under controlled conditions. None of these surfaces alone reveals an entire ranking system.

The useful result is a qualified inference about a specific platform surface, metric, audience and period, together with an account of how creators adapt under uncertainty.

Place, economy and intermediation

Urban platforms coordinate activities that remain grounded in streets, housing, workplaces and public institutions.

Creator and gig-economy platforms also reorganize money, data, visibility and risk across participant positions. The analytical task is to trace each flow separately, identify the rule-maker and test dependence through alternatives, portability and exit cost.

Broad judgments become stronger when they name the rule or information advantage producing the observed distribution.

Critical code

The final topic connects executable operations to representations and institutional consequences. A critical code argument begins with a tractable object such as a validation rule, data field, permission or API change.

It describes what the operation does, which categories it relies on, who may act through it and which organization gives the result force. This layered route avoids leaping from a line of code to society while refusing to treat technical detail as neutral.

How assessment shapes preparation

The course uses five coursework components.

The group presentation and summary document emphasize accurate reading summaries, relevant further readings and discussion questions. The Platform Review and Code Review are connected research papers that require varied sources, flexible but coherent structure and neutral language. The Design a Platform Project asks for a creative proposal responding to an unmet need.

Strong preparation therefore combines retrieval of course concepts with source evaluation, controlled comparison and explicit governance design.

How to work with this guide

For each chapter, reconstruct the concept map, then complete the worked case without looking. Change one condition and identify the first inference that fails. For an assignment, select the chapter whose analytical move matches your question.

Use the source grid to assign a distinct evidential job to each reference, and finish with a boundary that states what could revise the claim. Check current operational details on Quercus while preserving the published assessment labels and weights.

Worked example · free

Turn a platform feature into a research claim

Key terms

Metamedium

A metamedium is a programmable medium capable of representing or simulating many other media forms.

Platform

A platform coordinates participants and complementary activities through technical resources, interfaces and governance rules.

Infrastructure

Infrastructure is a shared, embedded system whose services support activity across multiple applications or institutions.

Intermediation

Intermediation is the organization of exchange between participants through categories, rules, information and transaction systems.

Affordance

An affordance is an action possibility that emerges from the relation between a designed object and a situated user.

Datafication

Datafication is the representation of activities or qualities as data that can be stored, compared and acted upon.

Algorithmic Visibility

Algorithmic Visibility is exposure shaped by computational selection, interface placement and participant adaptation.

Third Place

A Third Place is a recurring social setting outside home and work characterized by informal interaction and shared norms.

Relational Labour

Relational Labour is ongoing work used to create and maintain social connection with audiences, clients or supporters.

Platform Urbanism

Platform Urbanism studies how digital coordination systems interact with urban space, infrastructure and governance.

Code Space

Code Space is a setting whose ordinary functioning depends on software operations and classifications.

Critical Code

Critical Code analysis connects executable operations and data structures to cultural interpretation and institutional consequence.

INF2144H FAQ

Questions students ask in each INF2144H chapter

Why is a platform history more than a timeline?

A useful platform history explains how technical possibilities, standards, firms, institutions and user practices combined to normalize one arrangement. Chronology orders events, while analysis identifies the decisions and dependencies that made those events consequential. Compare a discarded or competing configuration, identify what it required, and explain why the focal arrangement gathered stronger technical, commercial or institutional support. Keep the chosen period and participant group explicit so later practices are not projected backward. Chapter 01 · Metamedia and Coded Cultures

When can the same system be both platform and infrastructure?

It can coordinate an ecosystem for complementors while operating as an embedded dependency for another organization. State the actor, scale and function for each reading instead of searching for one permanent label. Add evidence about rule-setting, maintenance and switching cost so the labels explain a relation rather than merely redescribe the architecture. Test the classification again after a failure or provider change. Chapter 02 · Platform Studies and Infrastructure

How can a software history avoid a progress narrative?

Compare technical functions, distribution, support, organizational work and alternatives in their own period. Explain why a configuration became durable without assuming that survival demonstrates the best possible design. Separate technical novelty, commercial reach and workflow change, because a source proving one outcome cannot automatically establish the others. Name the vendor, organization and user consequence at the close. Chapter 03 · Software Histories and Industry

Why does network connection not prove collaboration?

Collaboration also needs shared objects, conventions, permissions, communication and coordinated practice. A technical link creates a condition for interaction, while institutions and participants determine what that interaction becomes. Trace a persistent record and the next participant action to show whether information is merely transmitted or incorporated into joint work. Qualify the claim with the actual access conditions. Chapter 04 · Time-Sharing and Information Networks

How should a breakthrough technology be evaluated?

Separate its technical function, coordinating role, distribution, compatibility and commercial context. Then compare earlier or rival configurations so the case does not collapse ecosystem adoption into heroic invention. Follow one document through the complement system and identify the exact connection that becomes reliable for users. State which dependency arrives with that reliability. Chapter 05 · Desktop Publishing Ecosystems

Why can a file format not explain a media genre alone?

The format provides technical possibilities, while software operations, platform display and circulation, creator choices and community recognition turn those possibilities into a recurring expressive convention. Hold the artifact steady across settings to identify whether encoding, interface, policy or situated interpretation accounts for the difference. Record the property that remains unchanged across the comparison. Chapter 06 · Digital Images, Interfaces and Formats

What can creator accounts reveal about an algorithm?

They reveal perceived incentives, practical adaptation and shared theories about visibility. They do not establish the proprietary ranking mechanism by themselves, so combine them with platform documents and bounded output evidence. Record the interface, metric and period, then list alternative explanations before attributing a change to ranking. Preserve the next observation that would revise the inference. Chapter 07 · Algorithms and Visibility

What makes an audio platform an alternative?

Specify the dimension of difference, such as governance, revenue, creator data, catalogue, portability or audience relation. A service may differ meaningfully while still depending on shared payment or hosting infrastructures. Compare the same creator objective across routes and include the work and switching cost required by each arrangement. Name the audience relation produced by the route. Chapter 08 · Digital Audio Platforms

Why is a map display not direct evidence of urban activity?

The display reflects the platform's collection, categories, coverage and ranking. Activity may occur outside those representations, so compare platform data with situated observation and institutional context. Identify the urban resource, participation threshold and off-platform practice that could reveal what the representation omits. State who can contest the displayed classification. Chapter 09 · Platform Urbanism and Third Places

How does streaming change play without changing game rules?

It adds audience feedback, performance incentives, discovery, recording and monetization around the underlying game. Those relations can reshape player decisions while the executable constraint remains the same. Compare a traced play sequence with and without the audience condition to locate the change at the correct layer. Preserve the game version and performance setting. Chapter 10 · Games, Rules and Streaming

How can platform growth coexist with participant insecurity?

More transactions or users can accompany volatile income, unpaid administrative work, limited data access or unilateral rule changes. Measure the outcome for each participant position instead of using aggregate growth as distributional evidence. Trace money, data, visibility and risk separately, then test which resources survive a realistic platform exit. Keep the comparison period and rule change explicit. Chapter 11 · Platform Economies and Intermediation

What makes code analysis critical rather than merely technical?

It describes executable behaviour and then traces how representations, permissions, interfaces and institutional rules give that behaviour cultural or organizational consequence. Interpretation remains accountable to operation and evidence. Test a changed input or permission and follow the result through the same institutional workflow to locate an intervention point. Record the execution environment, version and data condition so the operation can be checked. Use policy and workflow evidence to establish who acts on the output, and participant evidence to establish the experienced consequence. Keep stated rationale separate from observed effect. A technically accurate description becomes critical when it shows how a category, default or permission distributes practical capacity and when it identifies a change capable of revising that distribution. Name the smallest change that would alter the outcome. A complete analysis also distinguishes a representation from the people or places represented by it. Fields and defaults prepare information for computation, but they omit qualities that may matter to the affected participant. Compare the accepted input, rejected case and error or appeal path. Then ask which organizational actor can override the result and what record remains. This makes contestability part of the software analysis and prevents a narrow operation from being treated as the entire institution. Preserve one counterexample that the current data model handles poorly, because it keeps the category boundary visible and gives a future design revision a concrete test case. Chapter 12 · Critical Code and Software Power

How to prepare for the assessments

Retrieve the layer distinctions, trace one artifact or transaction across them, assign every source a distinct job, and test the claim by changing one actor, rule, platform or historical condition. Keep a revision log of the first inference that fails.