General Terms

A project management methodology emphasizing iterative development, collaboration, and adaptability to changing requirements.

A step-by-step procedure or formula for solving a problem, forming the foundation of computer programming.

Application Programming Interface - a set of rules and protocols that allows different software applications to communicate.

A mathematical notation describing the upper bound of an algorithm's time or space complexity as input size grows.

Code that is easy to read, understand, and maintain, following consistent naming conventions and single responsibility.

Specialized formats for organizing, processing, and storing data efficiently, including arrays, trees, and hash tables.

A programming technique that limits the rate of function execution by waiting until a pause in rapid events occurs.

A design pattern where objects receive their dependencies from external sources rather than creating them internally.

Reusable solutions to common software design problems, categorized as creational, structural, and behavioral patterns.

Don't Repeat Yourself - a software principle aimed at reducing repetition by abstracting common patterns into reusable units.

Testing that simulates real user scenarios across the entire application stack, verifying the system works as a whole.

A design pattern that defers loading of resources until they are actually needed, improving initial page load performance.

A version control strategy where multiple projects or packages are stored in a single repository, sharing dependencies and tooling.

The process of restructuring existing code without changing its external behavior, improving readability and maintainability.

Five design principles (Single Responsibility, Open/Closed, Liskov, Interface Segregation, Dependency Inversion) for maintainable OOP.

A development practice where tests are written before the code, driving the design through red-green-refactor cycles.

A technique that ensures a function is called at most once in a specified time period, regardless of how often the event fires.

Testing individual units of code in isolation to verify they work correctly, typically using frameworks like Jest or Vitest.

A system that records changes to files over time, allowing you to recall specific versions and collaborate with others.