Glosario para Desarrolladores

The systematic examination of source code by one or more developers to identify bugs, security vulnerabilities, and improve code quality before merging into the main codebase.

The process of analyzing source code without executing it to find potential bugs, security vulnerabilities, and code quality issues.

The implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer.

A surface indication in the source code that usually corresponds to a deeper problem in the system. Not a bug itself, but a sign that refactoring may be needed.

The process of restructuring existing code without changing its external behavior to improve readability, reduce complexity, and make it easier to maintain.

The process of running a program that analyzes code for potential errors, bugs, stylistic issues, and suspicious constructs.

Code that is easy to understand, simple to modify, and clearly expresses the intent of the programmer. A philosophy popularized by Robert C. Martin.

Existing code that is difficult to change due to lack of tests, poor documentation, outdated technologies, or original developers no longer available.

Un principio de desarrollo de software que establece que cada pieza de conocimiento debe tener una única representación autorizada en un sistema.

Un principio de diseño que establece que los sistemas funcionan mejor cuando se mantienen simples en lugar de complejos. La simplicidad debe ser un objetivo clave.

Un principio de Programación Extrema que establece que los programadores no deben añadir funcionalidad hasta que realmente se necesite, evitando características especulativas.

Código que nunca se ejecuta en tiempo de ejecución, incluyendo código inalcanzable, funciones no usadas y código oculto detrás de condiciones siempre falsas.

Static Application Security Testing — a method of analyzing source code for security vulnerabilities without executing the program.

Dynamic Application Security Testing — a method of testing running applications for security vulnerabilities by simulating attacks.

The Open Worldwide Application Security Project — a nonprofit foundation that works to improve software security through community-led open-source projects.

A regularly updated list of the 10 most critical security risks to web applications, published by OWASP as a standard awareness document for developers.

Un ataque que obliga a usuarios autenticados a ejecutar acciones no deseadas en una aplicación web engañándolos para que hagan clic en enlaces maliciosos o envíen formularios.

El proceso de verificar la identidad de un usuario, dispositivo o sistema. Responde a la pregunta "¿Quién eres?" (en contraste con autorización, que responde "¿Qué puedes hacer?").

La práctica de almacenar, distribuir y rotar de forma segura datos sensibles como claves API, contraseñas, credenciales de bases de datos y certificados.

Una debilidad de seguridad en bibliotecas o paquetes de terceros de los que depende una aplicación, que puede ser explotada para comprometer la aplicación.

Análisis automatizado de código para encontrar vulnerabilidades de seguridad, bugs y problemas de calidad de código, típicamente integrado en pipelines CI/CD.

An approach that integrates security practices into every phase of the DevOps pipeline, making security a shared responsibility across development, security, and operations teams.

A code injection technique that exploits security vulnerabilities in an application's database layer by inserting malicious SQL statements into input fields.

A security vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users, potentially stealing session cookies, credentials, or performing actions on behalf of victims.

The use of artificial intelligence and machine learning to automatically analyze code changes and provide feedback on quality, security, and best practices.

The use of automated tools to analyze code and provide feedback without manual human intervention, typically integrated into CI/CD pipelines.

Una arquitectura de IA donde múltiples agentes especializados colaboran en tareas complejas, cada uno enfocándose en un dominio específico como seguridad, rendimiento o calidad de código.

Continuous Integration and Continuous Delivery/Deployment — a set of practices that automate the building, testing, and deployment of code changes.

A set of practices combining software development (Dev) and IT operations (Ops) that aims to shorten the development lifecycle and deliver high-quality software continuously.

La plataforma CI/CD integrada de GitHub que permite automatizar flujos de trabajo de software directamente desde tu repositorio usando archivos de configuración YAML.

A practice of moving testing, quality, and security processes earlier in the software development lifecycle to find and fix issues sooner.

Scripts que se ejecutan automáticamente antes de crear un commit de git, usados para aplicar estándares de calidad de código, ejecutar linters y prevenir commits de código problemático.

A software testing method where individual units or components of code are tested in isolation to verify they work correctly.

A metric that measures the percentage of code executed during testing, indicating how much of the codebase is covered by automated tests.

Una metodología de pruebas que valida todo el flujo de trabajo de la aplicación de principio a fin, simulando escenarios de usuario reales incluyendo UI, APIs, bases de datos e integraciones externas.

A software development practice where tests are written before the actual code, following a cycle of: write a failing test, write minimal code to pass, then refactor.

Testing that verifies different modules or services work correctly together, typically testing interactions between components rather than individual units.

Un porcentaje mínimo de código que debe estar cubierto por tests, aplicado en pipelines CI/CD para asegurar que el nuevo código no disminuya la cobertura total de tests.

Una técnica para evaluar la calidad de los tests introduciendo pequeños cambios (mutaciones) al código y verificando si los tests los detectan. Las mutaciones no detectadas indican tests débiles.

A method of submitting code changes for review before merging into the main branch. Also known as merge request (MR) in GitLab.

A distributed version control system that tracks changes in source code during software development, enabling multiple developers to work together.

GitLab's term for a pull request — a method of submitting code changes for review before merging into another branch. Functionally identical to GitHub's pull request.

A snapshot of changes in a Git repository that records modifications to files along with a message describing what changed and why.

An independent line of development in Git that allows developers to work on features, fixes, or experiments without affecting the main codebase.

A branching model for Git that defines a strict branching structure designed around project releases, using dedicated branches for features, releases, and hotfixes.

A source-control branching model where developers collaborate on code in a single branch called "trunk" (or main), avoiding long-lived feature branches.

A software metric that measures the number of independent paths through a program's source code, indicating code complexity and testability.

Four key metrics identified by the DevOps Research and Assessment (DORA) team that measure software delivery performance: deployment frequency, lead time for changes, change failure rate, and time to restore service.

Five design principles for object-oriented programming that promote maintainable, flexible, and understandable code: Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion.

Una medida cuantitativa de cuán difícil es entender, probar y mantener el código, basada en factores como ramificación, profundidad de anidamiento y dependencias.