Developer experience
Developer experience is the overall quality and effectiveness of developers’ interactions with the tools, systems, resources, and workflows involved in building and maintaining software.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
Developer experience is the overall quality and friction of a developer's interaction with the tools, technologies, processes, and workflows involved in delivering software.
- How it is used
- Positions DX as reducing extraneous work so independent value streams can deliver product enhancements continuously.
- How deep it goes
- Defines DX and examines lifecycle friction and platform choices, without prescribing one interface or platform implementation.
- Examples
- Contrasts HMRC’s self-service application setup with an Austrian company’s configuration burden on development teams.
- What you can do after
- Evaluate/understand it by examining application setup, local development, deployment, production support, and the workload shifted onto platform engineers.
React in Depth
Developer experience is the overall quality and efficiency of developers' interactions with a software project and its development processes.
- How it is used
- Frames productivity-tool choices and evaluates how styling decisions affect collaboration on React projects.
- How deep it goes
- Breaks styling DX into practical evaluation criteria and illustrates formatting costs, without specifying a single implementation procedure.
- Examples
- Uses a large team editing one CSS file and Prettier making inconsistently formatted code uniform.
- What you can do after
- Evaluate/understand styling approaches against team friction and use consistent formatting to reduce collaboration costs.
Effective Platform Engineering
Developer experience is the quality of developers' interactions with the tools, resources, workflows, and platforms involved in software development.
- How it is used
- Improves developers’ interactions with platform tools, resources, workflows, and services through product-oriented engineering decisions.
- How deep it goes
- Connects DevEx to abstraction, self-service, standardization, roadmaps, feedback, and metrics, but does not specify implementation technologies.
- Examples
- Uses Backstage-style portals, starter kits, pipeline resources, contract testing automation, feature flags, metrics, and the Epetech platform scenario.
- What you can do after
- Evaluate platform investment and apply self-service, abstraction, standardization, and measurement to improve developer productivity and trust.
Read how Effective Platform Engineering explains developer experience →
Automating API Delivery
Developer experience is the overall ease, effectiveness, and satisfaction developers have when discovering, learning, using, and integrating with software products and APIs.
- How it is used
- Guides API teams in making products discoverable, learnable, testable, and practical for intended consumers.
- How deep it goes
- Details documentation, onboarding, sandboxes, SDKs, and community support, while leaving implementation choices to API philosophy and governance.
- Examples
- Uses documentation, authentication onboarding, sandbox testing, client SDKs, token renewal, and API consumer journey planning as concrete examples.
- What you can do after
- Apply SDKs, documentation, onboarding, sandboxes, and publication practices to reduce friction for API consumers.
Read how Automating API Delivery explains developer experience →
Design for Developers
The quality of a developer's interaction with a product and its development-related interfaces or workflows.
- How it is used
- Extends user experience design to APIs, tools, documentation, and workflows used by developers.
- How deep it goes
- Defines documentation and design considerations, then illustrates implementation costs; stops short of framework-specific procedures.
- Examples
- Uses API documentation, undocumented legacy code, custom HTML form controls, and an iterative web project process.
- What you can do after
- Apply developer experience principles by organizing documentation, clarifying APIs, and evaluating implementation choices against user needs.
Read how Design for Developers explains developer experience →
Platform Engineering on Kubernetes
Developer experience is the quality and usability of the tools, workflows, and interfaces through which developers build and deliver software.
- How it is used
- Uses developer experiences as an organizational platform layer that enables teams to build complex systems and continuously deliver software.
- How deep it goes
- Connects developer experiences to services, standards, integrations, and workflows, but stops short of prescribing a concrete interface or implementation.
- Examples
- Illustrates developer experience through organization-specific layers and Kubernetes ecosystem tools that simplify development workflows.
- What you can do after
- Evaluate platform choices by how effectively they reduce tooling and integration concerns for development teams.
Read how Platform Engineering on Kubernetes explains developer experience →
Related concepts
- client libraryproduced by · A client library is reusable software that provides programmatic interfaces for an application to interact with a service, platform, or system.
- microservice architectureproduced by · Microservice architecture is a software architectural style that organizes an application as independently deployable services with focused responsibilities that communicate through defined interfaces.
- user experiencekind of · User experience is a person’s overall perceptions and responses resulting from interactions with a product, service, or system.
- internal developer platformproduced by · An internal developer platform is an organization-provided system of self-service interfaces, automation, abstractions, and reusable capabilities that supports software development and operation.
- developer experience metricmeasured by · A developer experience metric is a quantitative measure of how effectively tools, processes, platforms, and teams support developers in accomplishing their work.
- developer productivityproduces · Developer productivity is the value or amount of useful software work produced relative to the time, effort, and resources required.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.