Fullscript Developer Handbook
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.
Culture
Enabling employees to do the best work of their careers
Code Reviews
Reviewing code is an essential part of our process.
It’s an opportunity for education for both the author of the code and the peers reviewing it. It acts as a gatekeeper for quality within the codebase. Receiving criticism on your work can be difficult. It is easy to become attached to your code or view it as a reflection of yourself. It’s important to remember that you are not your code. We all have off days, or patterns and tricks we haven’t learned yet. Code reviews help us all become better in our field. Use them as an opportunity to give and receive knowledge.
Proposals
Writing proposals allows your teammates to provide feedback on your ideas, ensure that technology & processes are well thought out, and have buy-in from the team.
If you have ideas for new technology, changing a process, or how we can build better software – proposals are the best way to introduce your ideas to the team. This can be anything from coding conventions, all the way through to what we should use for message passing between applications.
Knowledge Silos
Share the knowledge, educate others, and don’t be afraid to tackle problems that are outside of your domain.
Just because Jane built checkout does not mean that she should be the only developer in charge of working on it. Similarly, just because Joe built a report does not mean that only Joe can make changes or fix issues with it.
