Fixing a bug is much cheaper than putting it in a tracking system. @wouterla#lascot
But … which team fixes the bugs?
Try as much as you can to directly root a big to the right team! @wouterla#lascot
But … we still have bugs!
Yes, you’ll have a fairly predictable amount of bugs.
But, once you have work under controle, you are not overwhelmed anymore.
And you can improve to have less bugs in certain components. @wouterla#lascot
• • •
Missing some Tweet in this thread? You can try to
force a refresh
we use information, both tacit and implicit, to inform our testing to uncover unknowns we are aware of (known unknowns) as well as the once we are not aware of (unknown unknowns)
X: Where do you get your amazing people at Netflix?
A Cockcroft: I get them from you.
It is not about hiring brilliant people.
It is about Netflix building an organisation, a management structure and leadership that enabled people to do their best and create outcomes effectively
The system is important!
If you hire good people into a bad system, you break the people.
> A bad system will beat a good person every time
>-- Deming
Another implication of Conway’s Law is that if we have managers deciding on teams, and deciding which services will be built, by which teams, we implicitly have managers deciding on the system architecture.
— @ruthmalan on Conway’s Law
Conway’s Law also kicks in if we take an initial guess at the system decomposition allocate subsystems to teams, and sally forth–the team boundaries will tend to become boundaries within the system.
Anything else will be a feat of architectural heroics; hard to accomplish, when architectural heroics have to compete with schedule heroics driven by the steady beat of integration clocks.