✳flâneur — a map of the web's best reading

Development Philosophy | Sentry Developer Documentation

develop.sentry.dev · 1,667 words · saved by 1 readers

This document sets guidelines for how we approach software development at Sentry. This is the result of more than 10 years of history of what worked for us, what did not work and how our understanding evolved. As new developers get acquainted with the codebase, having this context will be valuable to understand how to approach things. This guidance only partially applies to SDKs, where slightly different rules prevail. For that, please refer to the SDK Philosophy and Design Principles document. We’re all engineers, we take pride in our creation. But we are not artists where the act of creation satisfies the observer. Our work is there to solve customer problems. The tidiest looking code does not win us any prizes. That means as we work towards solving problems, our way of thinking should be towards our ability to stay nimble while delivering a stable and high quality product. It can be challenging to make the right call between an abstraction and a duct-tape solution and you might need

Development Philosophy Skip to content Getting Started Philosophy Inclusive Language Engineering Practices Application Architecture Development Infrastructure Backend Frontend Services Integrations Ingestion SDKs SDK Setup Wizards Self-Hosted Sentry Code of Conduct User Documentation Home Sentry Developer Documentation Philosophy Copy page Development Philosophy This document sets guidelines for how we approach software development at Sentry. These guidelines are the result of more than 10 years of history of what worked for us, what did not work and how our understanding evolved. As new devel

Explore this link on the map →

saved by

related reading