Urgent.News

What's breaking now, across thousands of outlets.

Tech

Ownership is not PR. It's not leaving the problem just in your head.

Ownership não é o PR. É não deixar o problema só na sua cabeça Pessoal, tem um padrão que eu vi demais em time que já sabe entregar. O erro está no board de observabilidade há meses. Alguém já comentou no canal. Suporte eventualmente reclama. Nunca virou card. Um dia vira incidente. Aí a pergunta aparece, desconfortável: de quem era a responsabilidade? Eu costumava responder errado. Ownership,…

Translated from Portuguese Read in Portuguese

The article discusses the concept of "ownership" in software development teams, specifically in relation to problem-solving and incident management. The author argues that ownership is not just about fixing a problem, but about taking responsibility for ensuring that the issue is addressed and does not recur. The author proposes a framework for ownership that involves four steps: SEE (perceiving a problem), UNDERSTAND (assessing its impact), EXPOSE (gathering data and evidence), and OWN (taking responsibility for resolving the issue).

The goal is to create a healthier system where team members feel responsible for identifying and addressing problems, rather than just relying on individual heroes or waiting for tasks to be assigned.

Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The LCU Trap: Why Your Load Balancer Bill Has Nothing To Do With Bandwidth

` Most engineers assume load balancer costs scale with throughput: "We push 2 Gbps, so our bill should reflect 2 Gbps." That intuition is wrong. AWS doesn't bill ALB or NLB by throughput.

  • Load balancer costs based on Load Balancer Capacity Units (LCU), not bandwidth.
  • Optimizing non-LCU factors has no impact on load balancer bill.

More from Thursday 27 August →