Word Roots in IT

The Latin prefix "de-" is one of the most productive in IT vocabulary — recognising its "reversal or removal" meaning unlocks dozens of technical terms that would otherwise need individual memorisation.

IT terms with "de-" prefix and their decoding: debug (remove bugs from), decompile (reverse compilation), decompress (remove compression), decrypt (remove encryption), deprecate (remove from recommended use), dequeue (remove from queue), deserialise (reverse serialisation — convert bytes back to objects), detach (remove attachment), dereference (follow a pointer reference to its value). The prefix also appears in more subtle forms: dead code (code that has been de-activated or is unreachable), deadlock (processes locked in mutual removal of each other's ability to proceed). Understanding the root pattern prevents having to look up each term individually.

Key vocabulary:
• prefix "de-" — Latin origin; typically means reversal, removal, or undoing in IT contexts
• decompile — to reverse the compilation process; convert binary/bytecode back to human-readable source form
• deprecate — to mark a feature or API as outdated, with the implication it will be removed in a future version

"Micro-" is a remarkably consistent prefix in IT — it almost always means "small in scope or granularity relative to a larger counterpart," whether applied to architecture, hardware, time, or economics.

The micro- vs. macro- pattern appears across IT: microservices (small, focused) vs. monolith (large, all-in-one); microcontroller (minimal chip) vs. full CPU + RAM + storage system; micro-optimisation (small performance tweak) vs. architectural redesign; microsecond (one millionth of a second, 0.000001s) vs. millisecond or second; micro-frontend (small, independent UI component) vs. monolithic frontend. Understanding this pattern helps: when you see "micro-X", ask "what would the larger, less granular version of X look like?" and you'll understand the relationship. The opposite prefix "mono-" (one, unified) often appears as the counterpart: microservices vs. monolith, microcontroller vs. monolithic processor design.

Key vocabulary:
• prefix "micro-" — Greek mikros (small); in IT indicates small scope, scale, or granularity relative to a larger counterpart
• microservice — a small, independently deployable service responsible for a single bounded capability
• microsecond — one millionth of a second (10⁻⁶s); prefix "micro-" here indicates the SI unit scale, not scope

"Poly-" (Greek for many) is a highly productive IT prefix — understanding it unlocks polymorphism, polyglot architectures, polynomial complexity, and any new "poly-" term you encounter in the future.

IT terms with "poly-": (1) Polymorphism — the object-oriented principle that a single interface can represent multiple types (method overriding, duck typing); (2) Polyglot — using multiple languages (polyglot developer, polyglot persistence = using different databases for different data types); (3) Polynomial — O(n²), O(n³) time complexity classes; (4) Polycast — a networking transmission model sending to a group (less common, between unicast=one and broadcast=all); (5) Poly-repo vs. mono-repo — many repositories vs. one repository. The contrast with "mono-" (one): polymorphism vs. monomorphism, polyglot vs. monolingual codebase, poly-repo vs. mono-repo. Spotting this contrast helps understand both terms simultaneously.

Key vocabulary:
• prefix "poly-" — Greek polys (many); indicates plurality or variety
• polymorphism — a programming concept where one interface represents many types or behaviours
• polyglot — using or speaking multiple languages; in IT, a developer fluent in multiple languages or an architecture using multiple data stores

"Inter-" (Latin for between) is one of the most valuable prefixes in IT — it consistently signals that something operates across a boundary between two systems, components, or layers.

IT terms with "inter-": interface (the boundary/contract between components), interrupt (signal between hardware and OS), interoperability (ability to work between different systems), inter-process communication (IPC — data exchange between separate processes), interconnect (link between systems), internet (network between networks), interpreted (code executed between compilation and runtime — mediated), interlock (mutual dependency between two operations). Contrast with "intra-" (within, not between): intranet (network within an organisation, vs. internet = between networks), intra-process (within a single process). When you see "inter-X" in a new term, ask: "What two things are communicating or connecting here?"

Key vocabulary:
• prefix "inter-" — Latin inter (between, among); signals a boundary, connection, or communication between two or more entities
• interface — a boundary definition specifying how two components can interact; a contract between systems
• interrupt — a hardware signal to the processor requesting it suspend current execution to handle an urgent event

"Auto-" (Greek autos, self) is one of the most relevant prefixes in modern DevOps and cloud vocabulary — as infrastructure becomes increasingly self-managing, "auto-" terms proliferate and understanding the prefix unlocks all of them at once.

IT terms with "auto-": automation (self-acting processes), autoscaling (self-adjusting capacity), auto-provisioning (self-setup of infrastructure), autocomplete (self-completing text input), auto-rollback (self-reverting deployment), auto-discovery (self-finding services in a network), auto-healing (self-repairing infrastructure), auto-configuration (self-setting of parameters), auto-documentation (self-generating docs from code), autogenerated (self-produced content). The DevOps principle of "automate everything" is fundamentally about adding "auto-" to as many manual processes as possible. Understanding the prefix also helps evaluate automation claims: "auto-scaling" does automatically scale, but does it auto-provision the dependencies those scaled instances need? The prefix maps precisely to the question "does this happen without a human doing it?"

Key vocabulary:
• prefix "auto-" — Greek autos (self); in IT indicates a process that operates without manual intervention
• autoscaling — automatic adjustment of computational resources (up or down) in response to load, without manual intervention
• auto-remediation — automated detection and correction of infrastructure problems without requiring human response

The comment highlights modular design. 'Separation of Concerns' describes the principle of dividing a system into distinct parts, each addressing a specific aspect – this aligns with Sarah's suggestion. It's not about memory, debugging, or HTTP requests; it's fundamentally about structuring code for maintainability and clarity.

The explanation correctly identifies 'status' as referring to HTTP status codes. A '200 OK' response is a standard indicator that an API request was successful. The other options relate to different aspects of API responses (payload size, credentials, or request counts).

The question focuses on measuring performance under load. 'Throughput' specifically describes the rate at which a system processes requests – it's crucial for evaluating how well a system handles increased demand. The other options relate to CPU usage, data size, or concurrent users.

The explanation correctly interprets 'permission denied' in this context. It's a common security error related to access rights – often caused by misconfigured file permissions or IAM roles. The other options relate to network issues, system overload, or database connections.

The explanation accurately describes 'automated scaling.' It's about dynamic resource allocation based on metrics like CPU utilization – a key concept in cloud computing. The other options describe manual configuration, server restarts, or maintenance tasks.