Why Swarm: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
*Swarms are an effective way to teach collaboration | *Swarms are an effective way to teach collaboration | ||
*Rate of gaining wisdom (obtained by feedback from consequences) increases when progress is fast - which shortens the length of a feedback cycle. | *Rate of gaining wisdom (obtained by feedback from consequences) increases when progress is fast - which shortens the length of a feedback cycle. | ||
=Links= | |||
*[[OSE Discipline]] | |||
Latest revision as of 13:56, 21 February 2026
- Build instructionals take too long otherwise and are rarely done properly
- CAD takes too long, even with AI, and is otherwise not taken to completion
- Learning velocity increases by a factor equivalent to the speed increase factor
- Build is more pleasant and fun, as opposed to brutal work
- Civilization grade engineering requires perseverance, which is easier with a coordinated team
- Important problems are not solvable by a single person, but a large team can do it
- Swarms are an effective way to teach collaboration
- Rate of gaining wisdom (obtained by feedback from consequences) increases when progress is fast - which shortens the length of a feedback cycle.