recentpopularlog in

leadership

« earlier   
Humility – Codecraft
A humble engineer (or architect, or any other role on a technical team) listens to the ideas of other team members and then restates them, without skew or value judgment, to validate his capture of a different viewpoint. He regularly sees others nod and hears them say, “Yes, that’s a fair summary of my perspective.” Notice how this contributes to designs that balance many considerations.

A humble engineer is not overly territorial. He doesn’t suffer from NIH syndrome.

A humble engineer doesn’t exaggerate estimates, bug impacts, feature creep, or technical debt.

A humble engineer likes to compliment. She can probably give you a long list of things she’s recently learned from team members. Notice how this dovetails with learning voraciously.

A humble engineer is quick to admit inadequacies of her code, design, or experience. She is proactive about raising questions and concerns in her own work product, so that everyone can learn faster.

A humble engineer is fact-driven, not authority-driven. Perhaps he learned long ago that technique A is “better” than technique B. Perhaps he considers himself an authority on the issue. He may suggest that his experience argues for technique A, but he suggests this always remembering that past experience may not apply perfectly to new circumstances. If his suggestion is not accepted immediately, he is ready to engage based on data and facts rather than his own prestige or another’s lack thereof. He doesn’t try to “game” the data; he just allows truth to be its own witness. Regularly pursuing facts without a hidden agenda makes it safe to put a stake in the ground, because people believe it will be moved if need be.

A humble engineer does not blame others when things go wrong. This is not because a humble engineer is relentlessly trying to convince herself that others aren’t blameworthy; it’s because she knows that blame is not helpful. Instead, she sees problems and asks, “What can I do that would prevent this in the future?” She may also offer ideas about how others could contribute to the solution. She may be blunt. But she remembers that it is the problem, not other people, that are the enemy. This shows in the way she communicates.

A humble engineer cheerfully tackles mundane tasks, not just exceptional ones with lots of glory attached
humility  leadership 
yesterday by da5is
How Giannis Antetokounmpo and the Bucks plan to take down the Warriors
That evening, he'll leave the facility for a couple of hours to check in on Alex and make sure his class load will track him for college eligibility. Then it's back to the gym for what the Bucks call night school.

"We call it 'No fastballs,'" Kidd says. "Fastballs kill us. We talk about it all the time. 'No one can throw a fastball. No one can throw a strike.' If someone throws a strike, it puts us in harm's way."

The Bucks define a fastball, or strike, as a pass delivered to an opposing player in the optimal spot at the optimal speed at the optimal moment. More than ever, the league's best offenses subsist on a healthy diet of catch-and-shoot bombs born out of drive-and-kick attacks or quick passes within a motion offense. A defense that can reroute those passes or delay them can degrade the quality of those shots.

"We actually measure air time," Kidd says. "We need a hang-time pass. We need a pass that is a ball and not a strike. If that's the case, we win."
Kidd imported the routine from Dallas, where players would voluntarily return for a little more work, including individual film sessions with the staff. Coming back and putting in reps after practice isn't a novel phenomenon, but the Bucks have formalized it as a staple of their routine.

Though there's no hard-and-fast schedule, the session usually starts with some light shooting drills or individual work on the floor. If there are enough guys present, assistant Sean Sweeney might conduct a sneak preview of a walk-through for the following night's game. Then they'll cool off and head inside for some film tutorials.

With a core group so inexperienced, Kidd puts a premium on watching tape.

"Our biggest question for a young guy is, 'Can you read?'" Kidd says. "If they're coming down the floor at you, what are they trying to do? If you can tell me, then we're doing something right. For young players, they don't have enough experience of seeing the action. You watch your habits. Night school is a way to educate a player about how to adjust the next time you see a situation. 'Can you read the action?'"
NBA  coaching  leadership 
yesterday by abemaingi

Copy this bookmark:





to read