Subroutine
In computer programming, a function is a callable unit of software logic that has a well-formed interface and behavior and can be invoked multiple times.
At a glance
Key signals
0% cross fields · reaches 0 more
- Computer Science
- Software Engineering
- Explanation
- Examples
- Misconception
- Sourced relations 3
- Attribution
Dependencies
What this concept builds on and what it makes possible — derived from the atlas’s dependency, causal and structural relations, not from every related edge.
Enables · leads to
Modular programmingdepends onSubroutineEstablished
modular programming depends on subroutine.
Mechanism: Modular programming rests on subroutines: breaking a program into small, named, reusable blocks makes it easier to build and maintain.
- Wikidata verifiedmoderate evidence
System context
Subroutineis part ofComputer programEstablished
subroutine is part of computer program.
Mechanism: A subroutine is a reusable part of a program: a named block of instructions that can be called from many places to avoid repetition.
- Wikidata verifiedmoderate evidence
Subroutineis aControl flowEstablished
subroutine is a kind of control flow.
Mechanism: A subroutine directs control flow: calling it jumps to a named block of code, runs it, then returns to where the call was made.
- Wikidata verifiedmoderate evidence
Structural role & consequence
Interpreted from the current atlas graph — what the connections mean, not just how many there are.
Currently dark in the atlas: no key date stored · 3 of 3 of its relations lack claim-level evidence.
atlas representation · Describes the current Thinking OS representation, not the state of the world.
Structural neighbourhood: 3 → 11 → 22 concepts reachable within 3 hops.
structural · Structural reach — being reachable is not the same as being understood.
All 3 of its relationships stay within its own discipline — a field-specific concept in the current atlas.
structural · Structural graph analysis — not a claim of importance, causation or history.
cross-field
3 within-field, 0 cross-field
Strengths & constraints
Constraints
- Evidence coverage currently thin in the atlas — few of its relationships carry claim-level evidence. atlas representation
- No dated history stored — the atlas records no key date for this concept. atlas representation
Conditions
- Read structurally — most of its relationships carry no external evidence yet, so claims here are graph-derived. structural
Dependency radial
What this concept builds on (left) and what it makes possible (right) — derived from dependency and causal relations.
What builds on this
1 concept build on this directly, 1 in total, across 2 disciplines.
Structural downstream reach along dependency edges — not a claim of historical necessity.
Seen through each discipline
How this concept sits in each of its fields — derived from its real connections in the graph, not asserted.
Through this lens it connects to Computer program, Control flow and Modular programming.
Through this lens it connects to Computer program and Modular programming.
Related ideas to explore
Concepts that look related but are not yet connected here — candidates for a connection to reason about, not established links.
This idea also appears in…
The same structure shows up in other disciplines. These are real recurrences drawn from the graph — a starting point for asking “what carries over, and what changes?”
Modularity7 disciplines · 8 concepts
Concepts
shares a mental model
shares a mental model
shares a mental model
shares a mental model
shares a mental model
shares a mental model
Mental models at work here
- Connects 3 other ideas across 2 disciplines.
- Most of its connections are of the “Kind & structure” kind.
- It exercises 1 reusable thinking pattern.
Derived from the graph’s real structure — observations, not a score.
Sources
- Wikipedia (English & German editions) verifiedmoderate evidence
- Wikidata verifiedmoderate evidence