The throughput of an entire system is dictated by the most narrow bottleneck. When prioritizing improvement work, start with this bottleneck.
Search
- Alerting
- Alertmanager
- Baseline testing extension for k6
- Chaos Monkey
- Data Visualization
- Infosec
- k6
- Logs
- Measuring Reliability
- Metrics
- Monitoring
- Observability
- OP5
- Performance Testing
- Prometheus
- Promtail
- Service Level Agreement
- Service Level Indicator
- Service Level Objective
- Somewhat Reliable Engineer
- Telemetry Types
- Traces
- Using k6 for Distributed Tracing
- Agile Methodology
- Automation is one of the most effective ways to resolve bottlenecks
- Cast of The Phoenix Project
- Change Advisory Boards are useless
- Change Management
- DevOps
- Discussing gender is a crucial component in challenging the status quo
- Don't let great get in the way of good
- Encouraging experimentation by getting rid of blame
- Engineering MANAGER vs ENGINEERING manager
- If you are the smarters person in the room, you are in the wrong room
- IL Recycling
- In case of ideas, break glass
- Inbox Zero
- Increments are useless until they have been released
- Kanban
- Lean
- Methodology
- Onboarding new colleagues by making them users
- Optimizations should be made at the bottleneck
- Prioritize work that removes bottlenecks
- Scrum
- Scrumban
- Servant Leadership
- Setting boundaries is an act of kindness
- Strong opinions, weakly held
- The difference between doing the right things and doing things right
- The Four Types of Work
- The Phoenix Project
- The Three Ways of DevOps
- The Unicorn Project
- Theory of Constraint
- There are no indispensable team members
- There is a difference between 10 years of experience and 1 year of experience 10 times
- Building Computers
- COS Lite Machine Sizing Calculator
- Multi-User Dungeon (MUD)
- SvenskMUD
- Articles
- Uses