BC Observatoryunofficial, made by waldo
community postAL Developmentcommunity - not Microsoftreviewed - checked by Opus

A Practical Mental Model for Using GitHub Copilot in AL Development

A mental model for using GitHub Copilot effectively in AL development, focusing on when to use each of five modes (Plan, Agent, Edit, Ask, Chat) to maintain control and predictability rather than treating Copilot as magic.

Open in Claude7402.md

post think about IT

Steven Renders · 2025-12-27 · 671 words · about 3 min

"Most frustration comes from using the right tool at the wrong moment."
Show the post hereRead on think about IT

Key points

  • Copilot has five complementary modes - Plan, Agent, Edit, Ask, and Chat - each supporting different intents in development.
  • Using the right mode at the wrong moment causes most frustration; effectiveness comes from intentional combination rather than individual features.
  • Success requires clarifying intent and architecture upfront before asking Copilot to implement, keeping design decisions explicit.
  • Copilot amplifies structural concerns around logic placement, responsibility separation, and how extensions evolve over time.

Quotes

  • “Most frustration comes from using the right tool at the wrong moment.” (Identifies the core issue - Copilot modes are complementary but must be applied in the right context, not interchangeably.)
  • “Copilot works best when it supports how you already think about software.” (Frames Copilot as an accelerator for existing thought processes, not a replacement for experience or design thinking.)

Context

  • Features: Copilot Chat mode, Copilot Ask mode, Copilot Edit mode, Copilot Agent mode, Copilot Plan mode

Source: think about IT - Steven Renders, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.