Once work is planned and assigned, you can sit down and start coding. As the developer, you need to remember all of the previous levels of the hierarchy as you introduce new code into your infrastructure. Often, as an SRE, your work will be looked to as a model for what the rest of your developer teams should be doing. If you skimp on a level, you may find the teams and developers you work with also skimping on it because of your example and hypocrisy.
A simple checklist for new software that you are writing based on our hierarchy framework is as follows:
Monitoring: Do you have basic metrics coming from the code that you are writing? Are they being collected and stored?
Incident response: Are you writing documentation on how to operate your service? Are there alerts that if they get fired, anyone who receives them will know what to do?
Postmortems: When your code has an outage, are you treating it like other code having an outage and writing a postmortem?
Testing and releasing...