Debugging Teams: Better Productivity through Collaboration
Rate it:
Open Preview
Kindle Notes & Highlights
Read between August 21, 2021 - January 16, 2022
8%
Flag icon
The Genius Myth is the tendency that we as humans have to ascribe the success of a team to a single person/leader.
9%
Flag icon
Bus factor (noun): the number of people that need to get hit by a bus before your project is completely doomed.
21%
Flag icon
A good general rule around communication is to include as few people as necessary in
21%
Flag icon
synchronous communication (like meetings and phone calls), and to go for a broader audience in asynchronous communication (like email, issue trackers, and document comments).
23%
Flag icon
Let’s start with the most dreaded meeting of all: the standing meeting.
23%
Flag icon
absolutely be kept to basic announcements and introductions
23%
Flag icon
going around the room for a status update from every attendee (whether they have something important to add or not) is a recipe for wasted time, rolling eyes, and a burning desire to...
This highlight has been truncated due to consecutive passage length restrictions.
24%
Flag icon
Schedule time on your calendar in three- to four-hour blocks and label these blocks as “busy” or even “make time,” and get your work done.
24%
Flag icon
Try to schedule the meeting near other interrupt points in your day (e.g., lunch, end of day).
29%
Flag icon
Comments should be focused on why the code is doing what it’s doing, not what the code is doing.
47%
Flag icon
you need to provide team members with a combination of motivation and direction to make them happy
47%
Flag icon
and productive.
47%
Flag icon
There are two types of motivation: extrinsic, which originates from outside forces (such as monetary compensation), and
47%
Flag icon
intrinsic, which comes from within.
47%
Flag icon
Dan claims you can increase intrinsic motivation by giving people three things: autonomy, mastery, and purpose.15
50%
Flag icon
Have a visible mission statement, to keep you focused on both your goals and nongoals.
51%
Flag icon
Establish proper etiquette around email discussions. Keep archives, get newcomers to read them, and prevent filibustering by noisy minorities.
51%
Flag icon
Document all history: not just code history, but also design decisions, important bug ...
This highlight has been truncated due to consecutive passage length restrictions.
51%
Flag icon
What’s specifically at risk is your team’s attention and focus. Attention and focus are the scarcest resources you have. The bigger the team, the more capacity the team has to focus on building things and solving interesting problems —
51%
Flag icon
Lack of Respect for Other People’s Time
51%
Flag icon
Rather than spending a few minutes of their own time reading fundamental project documentation, mission statements, FAQs, or the latest email discussion threads, they repeatedly distract the entire team with questions about things they could easily figure out on their own.
52%
Flag icon
The point here isn’t about who is right or wrong, but whether a disagreement is guaranteed to come to a conclusion and whether it’s worthwhile to keep a debate going. Never stop asking yourself those sorts of questions; at some point
52%
Flag icon
you need to decide when it’s time to cut your losses and move on.
53%
Flag icon
Redirect the Energy of Perfectionists Once a good-enough solution is found for the original problem, point the perfectionist to a different problem that still needs attention.
54%
Flag icon
not let “the perfect be the enemy of the good,”
54%
Flag icon
This trick of redirecting energy also works on the overly entitled people who spend more time complaining and criticizing than helping out.
54%
Flag icon
Remember that your job is to build great things, not to appease every visitor or repeatedly justify your existence. The stronger your emotions are, the more likely you are to waste hours or days writing passionate replies to someone who doesn’t deserve such attention.
54%
Flag icon
If someone is complaining, listen carefully. Always start by giving the person the benefit of the doubt, despite the angry or rude language.
56%
Flag icon
Despite the short-term loss of your team’s attention and focus, do you truly believe the project will still benefit in the long run?
56%
Flag icon
Do you believe the conflict will ultimately resolve itself in a useful way?
56%
Flag icon
A strong culture based on HRT is irreplaceable, while technical contributions are definitely replaceable.
56%
Flag icon
genius is such a commodity these days that it’s not acceptable to be an eccentric anymore.
56%
Flag icon
it’s not worth compromising your culture for the short-term gains — particularly if it’s about a brilliant contributor who doesn’t acknowledge the importance of HRT.
56%
Flag icon
Never attribute to malice that which is adequately explained by stupidity.
57%
Flag icon
This kind of proactive, responsibility-seeking behavior reduces your manager’s workload because she has one less thing to worry about, and it shows that you’re capable of doing work beyond your current
58%
Flag icon
level.
58%
Flag icon
you are responsible for teaching people how to act and how to treat you.
58%
Flag icon
Happy families are all alike; every unhappy family is unhappy in its own way. Leo Tolstoy, Anna Karenina
59%
Flag icon
Fear of failure is one of the most common traits of bad managers.
59%
Flag icon
there is little opportunity for you to inject your own ideas into your product and you’ll usually wind up implementing (by rote) the product someone else designed.2
59%
Flag icon
By hoarding information and requiring that they be a conduit for information and communication, bad managers are also able to take credit for your successes3 and blame you for your failures (and sometimes, their failures as well).
60%
Flag icon
who is willing to sacrifice the health and sanity of the employees to meet the needs of the business.
60%
Flag icon
Typically you’ll see this directly in the form of unrealistic deadlines and lack of qualified technical people to get projects completed on time. You may have difficulty acquiring enough hardware to effectively run your product, or find your team spending weeks rewriting something when a hardware purchase costing only a few hundred dollars would have done the job. This is unfortunately typical of a company that doesn’t value engineers and treats them like “work
60%
Flag icon
units” or “resources,” giving them no voice in how the...
This highlight has been truncated due to consecutive passage length restrictions.
61%
Flag icon
Lastly, your company might lack important things like focus, vision, or direction. This is often the result of too many masters, or “design by committee,” which results in conflicting orders being sent down to the rank and file.
61%
Flag icon
If you focus on the way things should be in your organization, you’ll usually find nothing but frustration and disappointment.
61%
Flag icon
Instead, acknowledge the way things are, and focus on navigating your organization’s structure to find the mechanisms you can use to get things done and to carve out a happy place for yourself in your company.
61%
Flag icon
“It’s Easier to Ask for Forgiveness Than Permission”
62%
Flag icon
If you spend all your capital winning a bunch of battles that just don’t matter, you’re going to find that you have nothing left in your account when it comes to the important things.
62%
Flag icon
If You Can’t Take the Path, Make the Path
« Prev 1