A little context
Words builders
throw around.
Plain-language definitions, with published stories where you can explore the ideas.
14 terms
API
An application programming interface defines how one piece of software can request data or actions from another. An HTTP API exposes those operations through web requests.
Cache
A stored copy of a result that can be reused instead of recomputing or fetching it. Cached results need an expiration or invalidation strategy when the source changes.
Component
A reusable piece of a user interface with its own structure and behavior. Components can receive inputs and compose into larger screens.
Git
A distributed version control system that records snapshots of a project. Its history makes it possible to compare changes, work on branches, and combine work.
Idempotency
The property that repeating the same operation has the same intended effect as performing it once. It helps make retries safe when a response is lost.
Open source
Software released under a license that permits people to inspect, use, modify, and redistribute its source code under the license’s terms.
Prototype
An early implementation used to learn whether an idea or interaction works. It may deliberately leave out the reliability and completeness needed for ongoing use.
Rate limit
A restriction on how many requests or operations a client may perform in a time window. Clients often need to wait and retry when the limit is reached.
Refactoring
Changing the internal structure of code while preserving its observable behavior. The aim is often to make future changes easier to understand and test.
SaaS
Software as a service: an application operated by a provider and accessed over a network. Users generally do not manage the application’s server installation themselves.
Static site
A website whose pages are generated before a visitor requests them. Browser-side JavaScript can still add interactive features to those prebuilt pages.
TypeScript
A language that extends JavaScript with a type system. Type checking can catch mismatched assumptions during development; types are not runtime input validation.
WebSocket
A persistent connection that lets a client and server send messages in both directions. It is often used when an interface needs timely updates.
Workflow
A repeatable sequence of steps used to accomplish a task, such as building, reviewing, testing, and releasing a software change.