HandbookFullscript 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.
Processes
Some sound principles that the development team follows at Fullscript
Prioritization and Tracking
Effective prioritization and tracking is an essential part of being a technical resource at Fullscript.
The development team is constantly juggling a high volume of projects. As a result, effective prioritization and tracking is essential. If you are in danger of missing a deadline or unsure of how to prioritize your tasks, it is your responsibility to communicate this with your team lead as soon as possible. They can help you reprioritize and communicate implications to the necessary stakeholders.
Documentation
Effective documentation of projects is a must for members of the Fullscript development team.
Your approach to documentation should adhere to the “Won the Lottery” rule: if you were to win the lottery tomorrow and stop coming to work, would another member of the team be able to understand your workflow and pick up your projects where you left off? This means that you should be documenting as you go. Not only will this make sure you don’t forget anything, it will also make the task of documentation much quicker and less tedious.
Deadline
Soft deadline
Most often used for projects at Fullscript. These are set by the team to ensure that the company is keeping on track with our longterm goals. They set constraints on feature sets and require us to distill the product down to what can be accomplished within a given timeframe.
Hard deadline
These are used only when absolutely necessary. This means that the company will have some serious repercussion if this timeline is not hit. At these times we may ask developers to pitch in some extra effort to ensure that we safely hit the deadline.
Emergencies
Of course by this we mean emergencies pertaining to the Fullscript platform – for real emergencies call 911, duh!
Emergencies can come in many forms – a broken deploy, a failing third party dependency, and all manners of other things. If the issue is important but non-urgent – email & slack are usually good enough. If it is an urgent issue do not hesitate to call the CTO, your team lead, or the devops team. Phone numbers can be found on Slack profiles, as well as the company directory.
Note: An incident report should be generated for the event and mailed to the devops team & CTO for historical purposes.