An event that requires the team's attention and response.
In every team, there is a "shaman" - a person without whom everything comes to a halt. There's always a line to him, he's called to every meeting, and not a single release happens without him. From the outside, he looks like a super expert. In practice, this is a single point of failure, disguised as competence. Let's explore why knowledge turns into currency and how to fix it.
There are engineers who complete tasks in days. And there are those who spend weeks on the same thing. The difference between them is not in their knowledge of frameworks or typing speed. It's in one question that the former ask before opening the editor: "Is it even necessary to write this?" It sounds like laziness, but it's engineering maturity. Let's examine specific techniques.