Amdahl's Corollary, for Teams
Metadata
- Author: monospacedmonologues.com
- Full Title: Amdahl's Corollary, for Teams
- Category: articles
- URL: http://monospacedmonologues.com/post/170069322435/amdahls-corollary-for-teams
Highlights
- Better to have 10 people working on 5 problems and doing a better job than it is to have 10 people working on 10 problems.
- Yes, meetings and other collaboration enhancers are boring. But they’re necessary. Just make sure you never lose sight of their purpose: to build a shared vision and style of work so that the team (or the organisation) works as one unit.
- Legacy code, bottlenecks in the development pipeline, and re-work caused by misunderstandings all contribute to decreasing the potential parallelisation of our jobs.
Amdahl's Corollary, for Teams
Metadata
- Author: monospacedmonologues.com
- Full Title: Amdahl's Corollary, for Teams
- Category: articles
- URL: http://monospacedmonologues.com/post/170069322435/amdahls-corollary-for-teams
Highlights
- Better to have 10 people working on 5 problems and doing a better job than it is to have 10 people working on 10 problems.
- Yes, meetings and other collaboration enhancers are boring. But they’re necessary. Just make sure you never lose sight of their purpose: to build a shared vision and style of work so that the team (or the organisation) works as one unit.
- Legacy code, bottlenecks in the development pipeline, and re-work caused by misunderstandings all contribute to decreasing the potential parallelisation of our jobs.
Amdahl's Corollary, for Teams
Metadata
- Author: monospacedmonologues.com
- Full Title: Amdahl's Corollary, for Teams
- Category: articles
- URL: http://monospacedmonologues.com/post/170069322435/amdahls-corollary-for-teams
Highlights
- Better to have 10 people working on 5 problems and doing a better job than it is to have 10 people working on 10 problems.
- Yes, meetings and other collaboration enhancers are boring. But they’re necessary. Just make sure you never lose sight of their purpose: to build a shared vision and style of work so that the team (or the organisation) works as one unit.
- Legacy code, bottlenecks in the development pipeline, and re-work caused by misunderstandings all contribute to decreasing the potential parallelisation of our jobs.
Amdahl's Corollary, for Teams (Readwise)
Not found
This page does not exist
Interactive graph
On this page
Amdahl's Corollary, for Teams
Metadata
Highlights
Amdahl's Corollary, for Teams
Metadata
Highlights
Amdahl's Corollary, for Teams
Metadata
Highlights