Roots some ideas

This commit is contained in:
Alexandre Dulaunoy 2016-12-21 08:17:45 +01:00
parent ce035439e9
commit b443b959c1
3 changed files with 17 additions and 4 deletions

View file

@ -1,6 +1,6 @@
# Summary # Summary
* [Introduction](README.md) * [Introduction](README.md)
* [First Chapter](chapter1.md) * [Roots](roots.md)
* [Acknowledgements](acknowledgements.md) * [Acknowledgements](acknowledgements.md)

View file

@ -1,3 +0,0 @@
# First Chapter
GitBook allows you to organize your book into chapters, each chapter is stored in a separate file like this one.

16
roots.md Normal file
View file

@ -0,0 +1,16 @@
# Roots
Building an incredible successful team with a flat organizational structure is not coming from nowhere.
In our team, the background of the members is very disparate. The management experience has been sometime
an enlightenment but often it was a painful or disturbing experience for the vast majority of our team members.
Creating a model of well-being and success in an organization lies into a successive layer of evolution with
a strong feedback-loop. One of the most common model that we were used to was the free software community.
An open source community is built on different social rules but the most common is "release early, release often".
Having early feedbacks on a practical experiment is often the most meaningful input that is nearly impossible
to get in a committee-review approach.
Some team members were used to hackerspaces and especially close to the principles behind the hacker ethic[^1].
[^1]: http://www2.fiu.edu/~mizrachs/hackethic.html