How to dodge vanity metrics and measure the right service level indicator and why?| blog.alexewerlof.com
A Mental Model to Assess Existing SLIs and Evaluate New Ones. We discuss 2 dimension: fidelity shows how closely your SLI is measuring the user experience, granularity shows how many parameter are measured by your SLI| Alex Ewerlöf Notes
Visualizing the service consumption and measurement topology while avoiding the most common SLI/SLO pitfalls| blog.alexewerlof.com
Overengineering, premature optimization, resume-driven development, hype-driven development, gold-plating, cargo-culting, etc.| blog.alexewerlof.com
Demystifying the most common misconception in Service Level jargon| blog.alexewerlof.com
Intro to both tools, why they exist, how they overlap and pragmatic tips how to use them and when| Alex Ewerlöf Notes
The pragmatic alternative to technical committees| blog.alexewerlof.com
What signs to look for and how to increase productivity with all-round skillset| blog.alexewerlof.com
Why the Staff+ archetypes are counterproductive and what to do instead?| blog.alexewerlof.com
Useful questions to get a head start as a newly hired Staff, Principal, or Distinguished engineer| Alex Ewerlöf Notes
A mental model to detect and prevent optimizing the wrong thing, at the wrong time, or for the wrong reasons| Alex Ewerlöf Notes
Using generators and promises to control backpressure| Alex Ewerlöf Notes
You should always generate more value than the perks the company puts on the table.| Alex Ewerlöf Notes
An invitation to intellectual humility, scientific curiosity, and collaborative exploration.| Alex Ewerlöf Notes
Holding engineering leadership accountable for the reliability of engineering artifacts| Alex Ewerlöf Notes
Why engineering maturity models are counter-productive, what are the real questions we should be asking, and how to lead the tech to a better place?| Alex Ewerlöf Notes
Breaking free from interpretation, time, environment, and exaggeration| Alex Ewerlöf Notes
When do you need a Staff Engineers? What's the accountability model with or without?| Alex Ewerlöf Notes
How value dominance, shallow understanding, and imitation hurts software, systems, and organizations| blog.alexewerlof.com
Why SMEs and specialists should be an exception and generalists the default?| blog.alexewerlof.com
The insult to any self-respecting software engineer| blog.alexewerlof.com
How a cost-cutting strategy led to the greatest collaboration effort of all time| blog.alexewerlof.com
Applying ideas from computer performance optimization and reliability engineering to improve organizational productivity| blog.alexewerlof.com
Smart use of digital tools to reduce the need for meetings| blog.alexewerlof.com
How vertical/horizontal organizational distance impacts the quality of information network, decisions, execution and deliveries?| blog.alexewerlof.com
When to separate accountability from responsibility and why it usually doesn't matter?| blog.alexewerlof.com
The 2 most common organization architectures, their key characteristics, pros, and cons with an example| blog.alexewerlof.com
The importance of organization design on service design and why consumer journey is the key to improve system reliability| blog.alexewerlof.com
See the about page for information about this site and target audience.| blog.alexewerlof.com
What is a “service” in the context of service levels (SLI/SLO)?| blog.alexewerlof.com
Introduction to Service Level Objectives and their relationship with error budgets| blog.alexewerlof.com
Non-Functional Requirements vs functional requirements| blog.alexewerlof.com
Introduction to the SLA in relation to SLI and SLO| blog.alexewerlof.com
The landing page for your curious neighbor| blog.alexewerlof.com
And the reverse: you should take control of what you are responsible for| blog.alexewerlof.com
Different hats that SRE's wear in the industry: Admin, Architect, Toolsmith, and firefighter| blog.alexewerlof.com
Analyzing what does it mean for other companies| blog.alexewerlof.com
Advice I wish I had when I lost my job| blog.alexewerlof.com
What to think about when deciding on the so-called SLO window?| blog.alexewerlof.com
For every 9 you add to SLO, you’re making the system 10x more reliable but also 10x more expensive.| blog.alexewerlof.com
Introduction to SLI, examples, counterexamples and tips| blog.alexewerlof.com
Some call it "Senior Staff", some "principal", others "technical director", but what comes after Staff Engineer? What are the challenges and toolset to handle higher complexity across a larger organization?| blog.alexewerlof.com
How to use the definition of "good" in the service level formula to focus the optimization?| blog.alexewerlof.com
Move the meetings next to each other to open up space for focused work| blog.alexewerlof.com
Why does this book exist?| blog.alexewerlof.com
What are the similarities and differences? What are the criteria for promotion? And some tools and techniques that come in handy.| blog.alexewerlof.com
In the ownership trio, we discussed 3 elements: Knowledge, Mandate and Responsibility. This article digs into various broken ownership scenarios where 1-2 of those elements are missing, what are the common symptoms and how to fix them.| blog.alexewerlof.com
The difference between valid and total in SLI| blog.alexewerlof.com
One of the most important decisions about SLI| blog.alexewerlof.com
Why did a friend of mine decline the chance to join a so-called "digital transformation"?| blog.alexewerlof.com
What is it? How does it work? When to use it and when not to use it?| blog.alexewerlof.com
What is it? How does it work? When to use it and when not to use it?| blog.alexewerlof.com
Why don't the high performing teams stop at the "run" level?| blog.alexewerlof.com
Set a cap on how much time goes to meetings in a period| blog.alexewerlof.com
Why and how we continuously invested the team bandwidth to pay back tech debt and what were the results?| blog.alexewerlof.com
