Developer Experience

Knowledge Base

An open source knowledge base that stores articles related to developer experience.

Motivate Your Team

Lower the Fluctuation

Meet the Deadlines

Development

62 practices

12 problems

After clear boundaries of the project are established and riskiest assumptions are answered in the previous steps, the development phase begins. This phase also includes process definition, architecture design, and proper tools selection. Good practice is to break down the development into smaller functional units and direct involvement of the client. Your client can “keep an eye” on what has been done during development.

Practices 62 All Practices

A Agile Events
Agile Events, (formerly Agile Ceremonies), are several types of meetings prescribed within Agile frameworks.
Apache Kafka
Apache Kafka is used as a high-available messaging queue.
Automated Deployment
Automated Deployment is a practice that allows you to ship code fully or semi-automatically across several stages of the development process - from initial development right through to production.
C Code Coverage
Code Coverage (CC) measures how many, and which specific source code lines are being tested by automated tests (for example, unit or integration test).
Code Review
A Code Review is a software quality assurance practice in which developers check each other’s code, usually before merging the code.
Commit Naming Rules
Commit messages have become a crucial part of the development process.
Continuous Delivery
Continuous Delivery is a practice that enables you to release new product changes to your customers at any given time.
Continuous Integration
Continuous Integration (CI) is a practice of integrating code changes on a daily basis.
D Design Thinking
Design Thinking involves developing design concepts that are user-centric by applying cognitive, strategic, and practical processes.
Devops
DevOps is a set of practices that combines the work of two teams: software development (Dev) and information technology operations (Ops).
Dockerizing
Dockerizing is the process of packing, deploying, and running applications using Docker containers.
Documentation
Documentation in a software project is a manual that describes the architecture of the software and provides helpful instructions to the users.
Documentation Testing
Documentation testing is a few processes of continuous feedback gathering and documentation improvements based on feedback.
E Epics
Epics are a helpful way to organize your work and to create a hierarchy.
Extreme Programming (XP)
XP is a software development methodology that emerged from the agile movement in the late 1990s.
G Git
Git is one of many VCS that are there in the market but it simply is the most popular among the developers.
Git Flow
Git Flow is one of many styles of Git workflows - a branching model set for Git.
Good Developer Experience
The Developer Experience (DX) describes the experience developers have while using or working on your product.
H Handover
A handover is a process of transferring the roles and responsibilities of a project from one team/individual to another.
I Icebreaker
An icebreaker is an activity or game designed to "break the ice" between attendees in a meeting.
Infrastructure as Code
IaC is a principle (or process) of provisioning and managing your infrastructure through machine-readable definitions instead of using physical hardware configuration.
Integration Testing
Integration Testing is a web development terminology used to test the software modules.
J Javascript Front-End Build Tools
As a JavaScript programmer, you can use multiple build tools for front-end development.
K KISS
KISS is a principle standing for Keep It Simple, Stupid (sometimes written as Keep it stupid simple or Keep it simple and straightforward).
Kanban
Kanban is an agile method similar to Scrum but it is less structured (no specific timeframe) and it is based on a list of items to do.
L License in Repository
When you publish your source code repository, make sure to include a license.
Linting
Lint, or a Linter, is a very useful tool for automated analyzing of your source code to look for bugs and stylistic errors.
Lock File
Many people decide to ignore the lock files and they do not commit it to Git.
M Meaningful Meetings
Meaningful Meetings are spin-off on the classical, endless, and pointless meetings all people know and dislike.
O Objectives and Key Results (OKR)
Objective and Key Result (OKR) is a group goal-setting tool used by corporate and individual businesses to set goals and measure the expected results.
Operations Logbook
Operations Logbook allows you to collect, store, and share data in real time and dig your historical data easily.
P Package Management
Package Managers are tools for automating the installation, upgrading, configuring, or removing of programs in a consistent manner.
Pair Programming
Pair programming is a practice of two programmers working together on the same task at a single computer.
Product Backlog
A Product Backlog is a prioritized list of work.
Product Backlog Refinement
Product Backlog Refinement is an act when the Product Owner (PO) in collaboration with the Development Team prioritizes the backlog items and adds details and estimates.
Proper Bug Reporting
Bug reports are descriptions of bugs found by testers - they help to understand where the product lacks its functionality or performance.
Pull Requests
A pull request is a practice of getting feedback from other programmers and deciding to "merge" or "do not merge" the code before it is merged into the main codebase.
R README
A README is a text file that introduces a product to a user.
Refactoring
You can see Refactoring as a controlled technique used for improving the design of existing code.
Release Management
Release management is the process of going through the necessary steps to deploy a software build through different stages and environments; in preparation for its release.
Respectful Code Reviews
Code review helps you to improve the quality of software projects.
Responsibility
Response + ability, these two words combine to form a well known word Responsibility.
Retrospective
A retrospective is an opportunity for the team to inspect itself and create a plan for improvements to be included in the next Sprint.
Risk Analysis
Risk analysis is the process of defining your risks, analyzing their probabilities, and determining what impact they could have on your project.
Runbook
A Runbook (also referred to as a playbook) is a compilation of procedures and operations that describe how to run a computer system or network.
S SMART Goals
SMART Goals is a tool that can be used to plan and achieve your goals – both personal and work ones.
SOLID Principle
SOLID stands for five object-oriented design principles that together (when used with judgment) make your code more bug-proof, easier to understand, nicer to maintain, and simple to expand/scale.
Scrum
Scrum is a framework focused on a productive and creative delivery of complex products with an emphasis on the highest possible value.
Semantic Versioning
Semantic Versioning (SemVer) is the most popular system of versioning unique states of the project.
Software Development Kit (SDK)
A software development kit (SDK) is a set of tools that allow developers to write or use an existing framework to develop applications for a given platform.
Software Documentation
The software documentation is a written text or an illustration that covers comprehensive information of the product.
Software Portability
Portability in high-level computer programming is the usability of the same software in different environments.
Staged Rollout
A Staged Rollout is a method of updating your application, while reaching only a certain percentage of users.
Story Points
Some work has to go to every story in the product backlog.
U UX Prototyping
As mentioned above it's a model, a simplified version of a system meant to test or present specific aspects of it.
UX Strategy
A UX Strategy is a plan that supports the overall Business Strategy.
Unit Testing
Unit testing is a way to test units - the smallest components of your software, the smallest piece of code.
Updating the Dependencies
Updating dependencies should be a regular part of your job.
User Stories
A User Story (US) is the smallest chunk of work in an agile framework.
V Vision
A vision's purpose is to unify and motivate people and teams towards achieving an ultimate goal.
W Waterfall
The Waterfall methodology is a linear project management approach where customer's requirements are collected at the beginning of the project.
Y YAGNI Principle
YAGNI is an extreme programming principle (XP) which states that you must not implement features that you assume as significant in the future.

Problems 12 All Problems

D Demotivated Team
Demotivated team can be a disaster for the business - the team members produce less and less work.
Disconnect Between Business and IT
Disconnect between business and IT means that the companies do not consider long term IT innovation in their business plans for a fiscal year.
L Long Feedback Loops
Long Feedback Loops mean that the delay between actions and reactions increases and the team becomes frustrated and demotivated.
Low Bus Factor
How many people need to get hit by a bus for the project or team to stop functioning? What are the ways how to increase this number?.
M Meaningless Work
Meaningless work can be a feeling that the work I am doing has no meaning or it can mean that the product I am working on is not valuable.
N Not My Problem Mentality
One of the very dangerous approaches to a team work is “Not My Problem” mentality and it is an opposite to a healthy team collaboration.
P Poor Code Quality
Poor code quality describes buggy code or code with high coupling and low cohesion that is difficult to maintain.
S Sunk Cost
Sunk costs is a commonly used term for any form of a resource, invested attempting to reach future gains, that is not possible to gain back in any form, regardless of the investment outcome.
T Toxic Team Culture
Spreading like a virus, consuming the team spirit - toxic team culture should be dealt with as soon as possible.
U Unhappy Clients
No matter how good you are at what you do, sooner or later you'll come across an unhappy client.
Unnecessary features
Necessary features are those adopted, useful, and loved.
Unsuccessful Product
About one-third of new products turn out to be unprofitable.