As anyone reading this knows, the Ever Given was stuck in the Suez Canal for just over 6 days. It blocked a route that normally carried ~10% of the world’s trade. More importantly (at least for this post), it also generated more than 10% of the world’s memes.
A productive incident post-mortem is one that results in a change to the system or environment in which people work, that enables and supports the people within it to not make the same ‘mistake’ again.
Great read since it mentions not only what a post-mortem is, but also goes into useful tips on execution.
SRE interviews can be tougher to prepare for than some other IT jobs. It’s still a new-ish field and role in many companies, even if it has its roots in traditional IT operations as well as DevOps. It’s also a role where non-technical skills are just as important as tech IQ. IT prowess is only part of the job.
As bosses and managers inside organizations, no matter the industry, it is our collective responsibility to understand what is happening in the world and work avidly toward gender parity in our workplaces. Many of us want to do the work and make changes but – much like me and this article – we don’t know where to start. Some of us are afraid of doing or saying the wrong thing or that we lack the training to really tackle this massive problem fully and responsibly. A lot of us feel like we need to wait for the right moment, or until we’ve been at the table long enough, or until we have the funding to really make a difference.
Apache Kafka is optimized for throughput at the expense of latency and jitter, while preserving other desirable qualities, such as durability, strict record order, and at-least-once delivery semantics. When someone says ‘Kafka is fast’, and assuming they are at least mildly competent, you can assume they are referring to Kafka’s ability to safely accumulate and distribute a very high number of records in a short amount of time.
Most of us aren’t taught how to respond when someone shares with us a really heavy piece of information.
There isn’t really a one-size-fits-all solution. Things will always break. The real key is to stay self-aware, all the time, so you can identify those broken things and address them. Scaling is a constant process of reinvention.
Availability zone IDs are consistent across AWS accounts!
AZ IDs are new for me!
Individuals who believe their talents can be developed (through hard work, good strategies, and input from others) have a growth mindset. They tend to achieve more than those with a more fixed mindset (those who believe their talents are innate gifts).