Discover published sets by community

Simplifying complex systems by modeling them at a more general level, omitting details.

A principle of extreme programming that states to not add functionality until deemed necessary.

Bundling data with the methods that operate on it, while keeping both safe from outside interference

The capability of a system to handle a growing amount of work or its potential to accommodate growth.

A measure of how interdependent software modules are.

The degree to which elements of a module belong together.

Property of systems that allow for multiple computations to happen simultaneously.

The process of restructuring existing code without changing its external behavior.

A linear sequential flow in which progress is seen as flowing steadily downwards through several phases.

A group of five principles for object-oriented programming and design: Single-responsibility, Open-closed, Liskov substitution, Interface segregation, and Dependency inversion.

Typical solutions to common problems in software design.

A set of practices that combines software development (Dev) and IT operations (Ops).

A software development practice where developers regularly integrate their code changes into a central repository.

A fast search algorithm with complexity of O(log n) that repeatedly divides the range of searched elements in half.

A principle aimed at reducing the repetition of software patterns.

Design principle that states most systems work best if they are kept simple rather than made complex.

Dividing a program into distinct features with as little overlap as possible.

A group of modern software development methodologies based on iterative development.

Design principle for separating a computer program into distinct sections.