Work on things that you care about; define goals for yourself; define productivity for yourself; establish routine and environment; take responsibility for your work; take responsibility for human connection; practice empathetic review; Have self-compassion; learn to say yes, no, and not anymore; and choose correct communication channels.
99.995% uptime seemed like an achievement worth celebrating at Voice123 until they realized it a benchmark set with insufficient justification. The costs of the implementation were around 30 times the impact of having downtime!
The ability to instantly spin up compute and storage has enabled them to move quickly and meet the growing demands of their business. However, this can quickly be offset by cloud computing costs, unless the organizational capability to efficiently use these resources is developed.
Having experienced not-so-successful handovers, Aleksandra Gavrilovska was inspired to create a guideline that will help other teams do handovers differently. The guideline not only documents what they did at SoundCloud, but also provides a template for other companies to use when faced with a similar scenario.
As the number of services grows, developers start to specialize working with specific services. When it comes to troubleshooting, however, developers need to be able to find the source, understand the service and dependencies, and chat with the owning team for any service.
In this post, Ricardo Ander-Egg Aguilar explains a new deployment method he came up with to achieve the following requirements: simple, based on git tags, zero-downtime, and easy rollbacks.