From b443b959c1d8889a5bcf988914c5452187000548 Mon Sep 17 00:00:00 2001 From: Alexandre Dulaunoy Date: Wed, 21 Dec 2016 08:17:45 +0100 Subject: [PATCH] Roots some ideas --- SUMMARY.md | 2 +- chapter1.md | 3 --- roots.md | 16 ++++++++++++++++ 3 files changed, 17 insertions(+), 4 deletions(-) delete mode 100644 chapter1.md create mode 100644 roots.md diff --git a/SUMMARY.md b/SUMMARY.md index a29b1fa..b018de6 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -1,6 +1,6 @@ # Summary * [Introduction](README.md) -* [First Chapter](chapter1.md) +* [Roots](roots.md) * [Acknowledgements](acknowledgements.md) diff --git a/chapter1.md b/chapter1.md deleted file mode 100644 index c0e22c6..0000000 --- a/chapter1.md +++ /dev/null @@ -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. diff --git a/roots.md b/roots.md new file mode 100644 index 0000000..dac16a2 --- /dev/null +++ b/roots.md @@ -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