Context switching

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

Context switching is the cognitive and operational disruption caused by repeatedly changing between different tasks, teams, or work contexts.

Context switching is the disruption created when people repeatedly move between initiatives, subdomains, teams, or modernization and legacy work. It increases cognitive load, weakens focus, and can undermine sustainable flow, motivation, and quality. section 11.1.5 section 16.3.5

Manage context switching by:

• Keeping team boundaries and owned subdomains small enough that their collective complexity fits one team’s cognitive-load capacity. section 11.1.5
• Avoiding routine allocation of one person across separate modernization and legacy teams; transfer legacy knowledge and reserve callbacks for emergencies. section 16.3.5
• Listening to the people involved before committing to a staffing or modernization arrangement. section 16.3.5

A developer divided between modernization and legacy work

A developer working three days a week on modernization and two days on legacy work may be pulled back by bugs and production issues. Part-time participation also hampers the learning modernization requires. A better arrangement transfers as much legacy knowledge as possible before the developer joins modernization, with return involvement limited to emergencies. section 16.3.5

Figure 11.2 Identifying potential high cognitive load on a Core Domain Chart

Use a Core Domain Chart to visualize team boundaries and identify subdomains where complexity and context-switching costs may create high cognitive load. section 11.1.5

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes

Explains disruption and mitigation through boundaries, knowledge handover, emergency callbacks, and staffing decisions, without prescribing a fixed process.

Examples

Uses a split-week developer arrangement and a Core Domain Chart to make disruption and overloaded boundaries visible.

What it assumes

Assumes familiarity with teams, subdomains, legacy work, and modernization while treating context-switching risks through concrete organizational examples.

What you can do after

Diagnose overloaded team boundaries and redesign staffing so modernization work receives sustained attention.

How it connects

Connects cognitive load with team boundaries, subdomains, modernization, legacy systems, knowledge transfer, and cost of change.

liveBookmanning.com

Read Architecture Modernization: Socio-technical alignment of software, strategy, and structure on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Learn Concurrent Programming with GoA context switch saves one task's execution state and restores another's so processor execution can move between tasks, threads, or goroutines.
• 

  liveBookmanning.com
  LatencyContext switching is the process of saving one execution context and loading another so multiple processes or threads can share a CPU core.
• 

  liveBookmanning.com
  100 Go Mistakes and How to Avoid ThemContext switching is the act of suspending one execution context and resuming another on a processor or runtime worker.
• 

  liveBookmanning.com
  C# Concurrency: Asynchronous and multithreaded programmingA context switch is the act of saving one thread's execution state and loading another thread's state so the processor can run it.
• 

  liveBookmanning.com
  Grokking ConcurrencyContext switching is the operating-system procedure of saving one task's execution state and restoring another task's state so execution can be transferred between them.
• 

  liveBookmanning.com
  The Creative ProgrammerThe shift from one active task, system, language, or conceptual framework to another, including the effort required to resume the original context.
• 

  liveBookmanning.com
  Software Design for Python ProgrammersContext switching is the operating-system or runtime operation of saving one thread's execution state and restoring another's so execution can alternate between them.
• 

  liveBookmanning.com
  Object-Oriented Software Design in C++Context switching is the operating-system operation of saving one thread's execution state and restoring another's so execution can move between them.

Compare how 9 books explain context switching →

Related concepts

• multithreadingused by · Multithreading is a concurrency technique in which multiple threads of execution operate within a program or process, with their work interleaved or running in parallel.
• threadused by · A thread is an independently schedulable sequence or context of execution within a program or process.
• operating systemused by · An operating system is system software that manages computer hardware and provides services and interfaces for application programs.
• schedulerproduced by · A scheduler is a system component that selects, orders, dispatches, or assigns execution resources to tasks according to timing, dependency, placement, or other scheduling criteria.
• multitaskingimplements · Multitasking is the concurrent or apparently concurrent management of multiple tasks by sharing, interleaving, or switching among execution resources.

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.