IT Suffixes

-tion / -ation / -isation turns a verb into a noun representing the process or result

• serialise → serialisation ("JSON serialisation", "object serialisation")
• configure → configuration ("the configuration file", "a valid configuration")
• authenticate → authentication ("OAuth authentication", "two-factor authentication")
• authorise → authorisation ("role-based authorisation")
• virtualise → virtualisation ("virtualisation layer", "server virtualisation")

Note: British English uses "-isation" (serialisation); American English uses "-ization" (serialization). Both forms are correct. In code, American spelling typically dominates in APIs, identifiers, and documentation regardless of where the team is based.

scalability — the suffix "-ity" creates a noun expressing a quality or capacity. Key IT examples:

• scalability — (capacity to scale)
• availability — ("five nines availability" = 99.999%)
• reliability — ("high reliability system")
• maintainability — (quality of being easy to maintain)
• interoperability — (systems working together)
• vulnerability — (security weakness)
• durability — (in databases: the D in ACID)

The pattern: adjective ending in "-able" → drop the "-le" → add "-ility": scalable → scalab- → scalability.

validatable — the suffix "-able" creates an adjective meaning "capable of being [verbed]".

• validate → validatable ("validatable input")
• configurable — can be configured
• deployable — can be deployed ("a deployable build")
• scalable — can be scaled
• testable — can be tested ("testable code")
• debuggable — can be debugged
• maintainable — can be maintained
• parsable — can be parsed

Usage: "Write testable code" means write code that can be unit tested (no side effects, dependency injection, etc.). The suffix communicates potential, not current state — "deployable" means it CAN be deployed, not that it HAS been deployed.

-er creates an agent noun — the person or thing that does the action

• bundle → bundler — a tool that bundles (Webpack, Rollup, esbuild are bundlers)
• lint → linter — a tool that lints code (ESLint, Pylint)
• compile → compiler — a tool that compiles source code
• route → router — a component that routes requests
• manage → manager — a person or system that manages (package manager, state manager)
• load → loader — a component that loads data (Webpack loader, data loader)
• dispatch → dispatcher — a component that dispatches events or jobs

The "-er" suffix is extremely productive in software vocabulary — nearly every tool has a one-word "-er" name.

-less = "without" — "stateless" means operating without retaining state between requests.

IT "-less" words:
• stateless — no client state stored server-side; each request is self-contained (key HTTP/REST principle)
• serverless — without managing the server infrastructure (AWS Lambda, Vercel Functions — misleadingly named, as there ARE servers, just managed elsewhere)
• passwordless — authentication without a password (biometric, magic link)
• lockless — concurrent programming without locks (lock-free algorithms)
• keyless — encryption approaches without traditional key exchange

Contrast with stateful:
• Stateful services maintain context between requests (WebSocket connections, database connections, sessions). "Stateless vs. stateful" is a core design decision in service architecture.

Option A — "resourceful" is a real word meaning inventive, having many resources. However, it is important to note the distinction:

"-ful" in tech is relatively rare compared to "-less" and "-able". Common IT uses:
• helpful (documentation, error messages)
• powerful (a powerful tool, a powerful query)
• meaningful (meaningful variable names, meaningful error messages)
• successful (successful deployment, successful build)
• graceful (graceful shutdown, graceful degradation)

The term "graceful" is particularly important in systems: "graceful shutdown" means the service finishes in-flight requests before stopping cleanly — the opposite of a hard kill. "Graceful degradation" means reducing functionality smoothly when part of the system fails, rather than crashing entirely.