Discipline focused on optimizing developer productivity, satisfaction, and effectiveness through well-designed tools, processes, and environments.
Developer Experience (DX) is a developer's total experience using tools, APIs, frameworks, and processes. Good DX reduces friction, accelerates the feedback loop, and makes work more satisfying.
| Metric | Framework | What it measures | Target |
|---|---|---|---|
| Onboarding time | SPACE | Days to first productive PR | < 1 week |
| Local build time | DORA | Minutes of feedback loop | < 2 minutes |
| Deploy frequency | DORA | Deploys per day/week | Multiple per day |
| Developer satisfaction | SPACE | Periodic survey | > 4/5 |
| Lead time for changes | DORA | Commit → production | < 1 day |
Developer experience determines the velocity and satisfaction of engineering teams. Slow tools, outdated documentation, and bureaucratic processes are frictions that multiply across every developer and every day. Investing in DX is investing in organizational productivity.
Set of technical and cultural practices that implement DevOps principles — from Infrastructure as Code to blameless post-mortems. The "how" behind the philosophy.
Code organization strategy where multiple projects coexist in a single repository, sharing dependencies, configuration, and build tooling.
Structured process for new developers to become productive quickly, from environment setup to understanding team architecture and processes.
Centralized platforms providing developers with documentation, APIs, tools, and service catalogs in one place.
Recommended, pre-configured paths for common development tasks incorporating best practices, reducing cognitive load for teams.
Continuous Integration and Continuous Delivery/Deployment — practices that automate code integration, testing, and delivery to production. Foundation of modern software engineering.
Discipline encompassing every aspect of a person's interaction with a product, system, or service, aiming for usefulness, usability, and satisfaction.
Practices, tools, and metrics for maintaining readable, maintainable, testable, and defect-free code over time.
Terminal-style design system with Matrix and TRON themes, Konami code integration, and micro frontend support. Published on npm as @jonmatum/terminal-ui.
Slidev presentation on 10 reasons to adopt a serverless-first architecture. Deployed on GitHub Pages.
Web platform for organizational maturity assessment with a simplified 3-level scoring system, customizable frameworks, and real-time visualization.
Principles for designing development kits that are intuitive, consistent, and facilitate service integration across multiple programming languages.
Discipline designing and building internal self-service platforms so development teams can deploy and operate applications autonomously.
Application of open-source development practices within an organization, allowing teams to contribute to other teams' projects with transparent processes.
Specification for defining reproducible development environments in containers, eliminating 'works on my machine' problems and accelerating onboarding.
Collection of reusable components, patterns, and guidelines ensuring visual and interaction consistency in digital products at scale.
Principles for designing intuitive, consistent, and productive command-line interfaces that developers enjoy using.
Spotify's open-source platform for building developer portals, with service catalog, templates, and extensible plugin system.
Practices and tools for documenting APIs clearly, interactively, and maintainably, from OpenAPI specifications to documentation portals.
Tools using LLMs to help developers write, understand, debug, and refactor code, from autocomplete to agents that implement complete features.