© Fullscript 2025. All rights reserved.
*These statements have not been evaluated by the Food and Drug Administration. These products are not intended to diagnose, treat, cure, or prevent any disease.
A reference guide for how to be a successful member of our dev team. It describes our culture, processes, and explains how we’ve gone about creating a platform that has taken the integrative health industry by storm.
Without expectations, there is no bar; if there is no bar, no one knows how they are doing
Done is better than perfect, but you need to ensure that it’s still great.
We’re a startup – and time matters! We move quickly and value delivering high quality products to our stakeholders as quickly as we can. Focus beyond just getting projects done as quickly as possible. All team members should strive to deliver work that will scale and can be iterated in the future.
Ultimately, whatever form your work takes, you should be proud to stamp your name next to it. If you are not, then you are introducing technical debt. And again, document your work to assist others with picking up where you left off, if necessary.
Leave it cleaner than you found it. The Fullscript codebase is our home and we want it to remain a place we enjoy living in for years to come! The expectation for all developers is to take care of it.
Ok, enough with the house metaphor. If it wasn’t clear, we are talking about technical debt. Sometimes taking on technical debt is a necessary requirement of software development. We want to ensure that everyone does their part in reducing technical debt when they encounter it.
While you should do everything possible to make sure your work is complete and accurate, you are not a robot and mistakes happen.
Even after code reviews and testing, things sometimes still fall through the cracks. If you realize that you have made a mistake, it’s your responsibility to own up to it as soon as possible. This can help us mitigate the effects of the error and avoid catastrophic emergencies. Once it has been fixed, learn from your mistakes and move on.
We are all about sharing responsibility: as a team we are responsible to our users, the company, and to each other to do the best job we can. It’s all about the small things, attention to detail, and ensuring that our work is the best it can be. We are a team – we succeed and fail as one.
Even after code reviews and testing, things sometimes still fall through the cracks. If you realize that you have made a mistake, it’s your responsibility to own up to it as soon as possible. This can help us mitigate the effects of the error and avoid catastrophic emergencies. Once it has been fixed, learn from your mistakes and move on.
We have chosen a technology stack that we believe provides a tool for every job, while also keeping our products approachable by other developers in the organization.
