Asynchronous Programming

Software Engineering

The systematic application of engineering principles to the design, development, testing, and maintenance of software.

Agile Methodology

An iterative approach to software development emphasising flexibility, collaboration, and rapid delivery of working software.

Scrum

An agile framework using fixed-length iterations called sprints for incremental product delivery with defined roles and ceremonies.

Kanban

A visual workflow management method that limits work in progress and optimises the flow of tasks through a system.

Waterfall Model

A sequential software development methodology where each phase must be completed before the next begins.

Technical Architecture

The design and structure of a software system's technical components and their relationships.

Design Pattern

A reusable solution to a commonly occurring problem within a given context in software design.

SOLID Principles

Five principles of object-oriented design promoting maintainable, flexible, and understandable code.

Domain-Driven Design

A software design approach focusing on modelling the business domain and aligning code with business logic.

Clean Architecture

A software design philosophy separating concerns into layers with dependencies pointing inward toward business rules.

Stress Testing

Testing a system beyond normal operational capacity to determine its breaking point and failure behaviour.

Technical Documentation

Written materials describing the architecture, design, APIs, and usage of software systems.

Automatic memory management that reclaims memory occupied by objects no longer referenced by the program.

A non-relational database designed for specific data models offering flexible schemas for modern applications.

A system that records changes to files over time so that specific versions can be recalled later.

A software practice where code changes can be released to production at any time through automated pipelines.

Restructuring existing code without changing its external behaviour to improve readability and maintainability.

Testing the interaction between different software modules or components to verify they work together correctly.

A design pattern where dependencies are provided to a component rather than created within it.

A programming construct that waits for and dispatches events or messages in a program.