/home/michael

A few thoughts on student use of AI

1 min read

Post

Tim Fawns recently posted some of his thoughts on student use of AI and most of it really resonated with me, so I’ve formatted it into a one-page PDF that’s easier to save and share.

The 17 points that Tim raises push back on the assumption that students using AI are cheating or avoiding learning.

Download as PDF · Original LinkedIn post

Tim Fawns' 17 points on student use of AI — a one-page reference card covering assessment, learning, trust, and the limits of product-based judgement

Fawns, T. (2026). A few thoughts on student use of AI. LinkedIn. bit.ly/4tXifaf

Continue reading

  • Building a CPD app with Claude Code

    Most CPD tools are built for compliance, not development. I wanted something that started from the gap; what am I missing, and what would close it? I couldn't find the tool I needed so I built one called Path instead. It describes what I think professional development should look like, and what two weekends with Claude Code produced.

  • What software engineers can teach us about AI in doctoral research

    PhD students are using AI across their doctoral work, but current policies focus on permission rather than specification. Drawing on how software engineers solved a structurally identical problem, this post introduces the research harness: a seven-part operating context that makes AI contributions visible, traceable, and supervisable. The harness addresses drift, offloaded thinking, and attribution failures — not by restricting AI use, but by specifying what the agent can and cannot do within the work.

  • The research harness: a framework for bounded AI use in doctoral work

    Current responses to AI use in doctoral research locate the problem either with institutions through policy, or with students through judgement and AI literacy. This essay argues that neither response addresses the structural source of the difficulty. The characteristic problems of AI use in doctoral research are not problems of policy or capability; they are problems of working with an agent in the absence of a defined operating context. Drawing on software engineering practice, it develops the concept of the research harness: a structured specification, negotiated between researcher and supervisor, of what an AI agent is doing in a doctoral project. The harness has seven components — knowledge base, interpretive permissions, tools, authority, scope register, process record, and amendment protocol — and can be entered at a minimal level and developed iteratively alongside the work.

Graph View