Campus AI Development AI-assisted development

The continuum Band 02

02

AI-assisted development

The human writes; AI suggests. The human remains the primary author.

Also called: AI pair programming, code completion

01Definition

A developer writes the code and an AI assistant suggests completions, explanations and edits inline or in chat. The human accepts, edits or rejects each suggestion and remains the author of record. Every line still passes through a person who understands it.

02Origins

The name borrows from pair programming, a practice popularized by Extreme Programming in the late 1990s, where two developers share one keyboard. GitHub launched Copilot as a technical preview in June 2021, billed as “your AI pair programmer” and built on OpenAI’s Codex model. ChatGPT, released in November 2022, added chat-based explanation and debugging.

Early evidence came from a 2023 controlled experiment in which developers with Copilot completed a set programming task 55.8% faster than those without. Later field studies found smaller and more varied gains.

03How it works

Person AI
01Write code
02Suggest completions
03Accept, edit or reject
04Review and test
  1. 01The developer writes code in their editor.
  2. 02The assistant suggests completions inline, or answers questions in a side chat.
  3. 03The developer accepts, edits or rejects each suggestion.
  4. 04The code goes through the team’s normal review and tests.

Typical tools: GitHub Copilot, Cursor, JetBrains AI Assistant, Gemini Code Assist, general chat assistants.

04Profile across the dimensions

How the work is done

Human role
Author; AI suggests
Unit of work
A commit
Source of truth
The code
Agent autonomy
Suggests only
Lifecycle coverage
Build and test

How you know it’s right

Code read by a person
Every line
Verification
Code review and tests
Traceability
Commit history
Delivery automation needed
Version control

Fit and risk

Upfront investment
Low
Durability
Maintainable
Data and risk ceiling
Internal data, under existing review rules

Compare all five bands

05Lifecycle coverage

Plan
Design
Build
Test
Deploy
Operate

Solid: AI does core work · Hatched: partial or informal · Dashed: done by people. Compare all bands

06When to use it

Good for: Production work in an existing codebase; coursework with learning goals

One personSame as working without AI, only faster.
A teamFits normal practice: each developer uses their own assistant, and code review stays the same. Agree on shared prompts and conventions so suggestions follow team style.

Less suited to

  • Large, repetitive or multi-file changes, where reviewing every suggestion is slower than delegating the task
  • Courses where the learning goal is writing the code yourself

Signs you’ve outgrown it

  • Tasks routinely span many files
  • You find yourself pasting the same instructions every session
  • The team wants to hand off whole tasks, not lines

07Development environment

Where it runs: The developer’s usual editor (VS Code, JetBrains) with an assistant plugin, plus existing version control.

Data
Whatever the project already allows
Credentials
Unchanged from normal development
Key setting
Enterprise tier with training on university code turned off
On campus
Duplicate-code filtering on where offered; licenses through central IT

Compare environments across bands

08Minimum controls

  • Personal space or sandbox only
  • No real or institutional data
  • Throw it away, or rebuild it properly before sharing

Risks

  • Automation bias: accepting plausible suggestions without checking them.
  • Provenance: suggestions that closely match licensed code.
  • Skill atrophy: learners skipping the practice that builds judgment.
  • Review fatigue: more code to review, with the same reviewers.

09On campus

10Sources

  1. GitHub, “Introducing GitHub Copilot: your AI pair programmer,” June 2021
  2. Peng et al., “The Impact of AI on Developer Productivity: Evidence from GitHub Copilot,” 2023
  3. Besser, Jensen & Katz, Open Research Europe, 2026