Get the latest tech news
On Writing Well
document is surprisingly hard. That is not because of the skill to tell a story.
Granular details of system characteristics during the outage Granular details on specific set of changes done LearningsThings that folks on team will already know list of services what do they do …ExecutivesImpact in terms of customer experience Monetary impact Likelihood of repetitionArchitecture diagram, call graphs, etc. BeforeAfterAs our company starts to diversify itself into more and more businesses in the transactional & financial services ecosystem, it has become imperative that we build a host of central capabilities which can be used as a repository of solutions which can be redeployed and reused primarily in a business agnostic way.As our company expands into more financial services, it needs to create reusable solutions that can be applied across different business areas.Given how we would often end up being the conduit point for a host of future building efforts for a lot of the CXOs, we may often end up in resource constrained zones and will end up in one of the following 2 scenarios.As we become a key resource for many CxO’s future projects, we may face resource limitations, leading to one of two situations: Replace adjectives with data or details. Hopefully, we fixed the main problem really quickly.10,400 customers couldn’t complete a purchase for 2h13m, due to a server failure introduced by a code change, resulting in an estimated loss of $50 000 (+/- 4%).
Or read this on Hacker News