The Practices section summarizes commonly used procedures that may help you and your team to increase Developers Experience.
Software documentation explains how the product works or how to use it. Different types of software documentation are created through the whole product development lifecycle.Read more
A Product Backlog is a breakdown of prioritized work to be done. It is a sorted list of changes your product needs. It is usually the Product Owner who is responsible for creating and updating the backlog.Read more
A Bus Factor measures the minimum number of team members who have to be hit by a bus to put the project in jeopardy. The goal is to increase your Bus Factor as much as possible.Read more
Starting on the journey of coding can be extremely overwhelming. But consistent efforts and determination will surely help you out in this journey.Read more
API-first approach to building products is rising, API first enables developers to innovate in ways that weren't before feasible and speed up the achievement of corporate goals.Read more
RESTful APIs are a popular choice for web-based applications due to their simplicity, scalability, and flexibility. By following the core principles of REST, the product team can create APIs that are easy to understand, develop, and scale.Read more
The .gitignore file is a text file that tells Git which folders or files to ignore in a project when sharing it through git. It helps to keep your code clean and secure...Read more
Cleaning the product backlog is essential to keep track of which key product features should be developed next.Read more
Total responsibility for failure is a difficult thing to accept, and taking ownership when things go wrong requires extraordinary humility and courage.Read more
What is good developer experience?
Learn what is good developer experience and why you might want it