Repository with sources and generator of
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

thoughts.html 112KB

  1. {% extends "base.html" %}
  2. {% block lang %}en{% endblock lang %}
  3. {% block title %}Thoughts{% endblock %}
  4. {% block extra_head %}
  5. <!-- Canonical URL for SEO purposes -->
  6. <link rel="canonical" href="">
  7. {% endblock %}
  8. {% block content %}
  9. <h1>Thoughts</h1>
  10. <section typeof="schema:Blog">
  11. <article id="slowweb" typeof="schema:BlogPosting">
  12. <h2 property="schema:name"><a href="#slowweb" title="Link to that content" property="schema:url">Slow Web</a></h2>
  13. <div property="schema:articleBody"><p>Inspired by the <a href="">Slow Food</a> and more recent <a href="">Slow Science</a> movements, I decided to go back to what I call <strong>Slow Web</strong>. Enough of real-time distractions, enough of noisy notifications, enough of crappy web 2.0 "services" telling me intimate things about people I do not even know. Back to real reflexions, interesting discussions and passionate serendipity. In plain old HTML.</p>
  14. <p>I thought about it for a while and <a href="">my year in Japan</a> will be the perfect timing to switch:</p>
  15. <ul>
  16. <li>8 hours timezone lap with France and US, less real-time distractions ;</li>
  17. <li>about 2 hours a day of transports to just think, disconnected ;</li>
  18. <li>back to a salary job with less peripheral concerns.</li>
  19. </ul>
  20. <p>Here is what I did to slow down my attention and bring back my reflexion. Let me be clear, this is not a guide, just a testimony:</p>
  21. <ol>
  22. <li><em>Deleting all accounts with time consuming notifications.</em> LinkedIn is the perfect example, after a couple of messages I realized that all propositions were just bullshit and that you need to know people to find interesting jobs, not contacts.</li>
  23. <li><em>Reopening an aggregating system with few quality blogs remaining after the micro-reflexion crisis.</em> I thought that Twitter, the human sourced aggregator was enough but the signal vs. noise ratio is too bad even with a restrictive follow policy.</li>
  24. <li><em>Forcing me to write articles.</em> By forcing I mean taking the time to aggregate some thoughts and links to try to summarize my vision on the topic, not just transmitting/retweeting links without any context nor deep reflexion.</li>
  25. <li><em>Finding a good setup.</em> My 11" MacBook Air associated with Sublime Text 2 in Distraction Free Mode looks to be perfect. At the technical level, I just use a repository to store my writings generated in static, portable, almost perennial, troll proof HTML. This will be a one-page blog, be ready to scroll (and to link anchors).</li>
  26. </ol>
  27. <p>At the end of the day, the quality you produced matters. Be part of that Web and share the love :-).</p>
  28. <p>As a side note, I’m trying to write in English to force me to express myself with that language, please email me if there are mistakes. Same apply for Japanese, if any.</p>
  29. <p>PS: there will be no comments at all on this space but discussions are much more appreciated and manual trackbacks will be added, just find a place to publish. Don’t let me be responsible of your data, please!</p></div>
  30. <footer class="post-date">—
  31. <span property="schema:datePublished">Summer 2011</span>,
  32. <span property="schema:contentLocation">Arles</span>
  33. </footer>
  34. </article>
  35. <article id="geeksparano" typeof="schema:BlogPosting">
  36. <h2 property="schema:name"><a href="#geeksparano" title="Link to that content" property="schema:url">Geeks are paranoid</a></h2>
  37. <div property="schema:articleBody"><p>Because they/we are <strong>control freaks</strong>. And that’s the root of a lot of issues because geeks are creating and implementing systems for people who are not obsessed by pixel perfect rendering, exact version numbers or strongly typed stuff (Wait there are statuses between male and female, how can I implement that?! A FREE text field? Crazy you.). Let me saying it out loud: <em>PEOPLE JUST DON’T CARE</em>.</p>
  38. <p>This idea leads me to consider a very system familiar: <strong>the human body</strong>. Actually that’s one of the most complex systems that you can study very easily, try to enhance, feed randomly, drug at best. And that’s why I’m not surprised that more and more geeks I know are starting to do sports regularly (OK, at first it’s for the beer-effect phenomenon but then...), trying to figure out how that system works and finally control it. Of course. It’s interesting to compare running (the sport!) programs and Scrum’s process for instance, an iterative way to improve yourself in one sense.</p>
  39. <p>A lot of geeks are over-equipped (including me, I confess) because of that psychotic frenzy, thinking that you can only achieve yourself when all the environment is at his best. This is not about consumerism or having a better one than your neighbor, it’s probably more about ego actually: <em>I deserve the best to accomplish myself.</em> Somehow it’s wrong but so reassuring and challenging in the meantime because you <em>have to</em> give the best of yourself in this configuration :-).</p>
  40. <p>But trying to control an open system is pure utopia and it will only bring frustration. This frustration is turned into pessimism about society, human nature and so on. The only solution is to let it go, to rise above (do not stress, this parenthesis will never be closed but it’s a possibility and it’ll not make that world better nor worse, just breathe, no problem. You don’t know if that sentence is still in the parenthesis but that’s still OK. <em>Relax.</em></p>
  41. <p>Should we try to heal that mental disease? Good question. In one hand it standardizes the Worl^W^Web at an incredible pace with that control obsession in mind. On the other, the control must be performed in a perfect way and it slows down the process with endless discussions and <a href="">countless standards</a>. <strong>It’s always a matter of cursor.</strong> What about you?</p></div>
  42. <footer class="post-date">—
  43. <span property="schema:datePublished">Summer 2011</span>,
  44. <span property="schema:contentLocation">Arles</span>
  45. </footer>
  46. </article>
  47. <article id="aboutfeeds" typeof="schema:BlogPosting">
  48. <h2 property="schema:name"><a href="#aboutfeeds" title="Link to that content" property="schema:url">Feeds</a></h2>
  49. <div property="schema:articleBody"><p>Most of the feedback about that page was about the missing RSS feed. I got two technical remarks about that: as you probably noticed there is no date associated with posts <del>and a feed requires one</del> I was wrong, <a href="">the pubDate element of an RSS feed is optional</a>, I wonder how RSS tools deal with that and freshness though. Secondly, HTML 5 adds some (poor) semantic through tags (article, section, etc) so I wonder why we still need to duplicate the information in a feed while it already exists. <em>You are just reading some kind of content feed with that page,</em> interpreted by your browser.</p>
  50. <p>Now let’s consider a juridic point of view, the license for that page will probably be (still undecided):</p>
  51. <blockquote>
  52. <p>Creative Commons: <a href="">Attribution, Noncommercial and No Derivative Works.</a></p>
  53. </blockquote>
  54. <p>BUT, those conditions are far from being enough, you need to explain what you mean by <strong>Attribution</strong> or people will just put an hidden link somewhere or worse your name without any link and same apply with <strong>Noncommercial</strong>: is Google’s indexation a commercial use of my content with their contextual ads? What if your aggregator displays ads on top of my feed? What do you consider as a <strong>Derivative Work</strong>? Is an extract a derivative?</p>
  55. <p>The real question about feeds is: <em>Do I want to be eaten by robots?</em> Not yet. And I’m seriously considering the deindexation of that page from search engines too.</p>
  56. <p>PS: this page has only been announced on Twitter so you’re probably <a href="">following me</a> and will be notified for new content that way, at least for now! I agree that it’s not really <a href="#slowweb">Slow Web</a> compatible, just keep that tab opened if you’re an extremist :p</p></div>
  57. <footer class="post-date">—
  58. <span property="schema:datePublished">Summer 2011</span>,
  59. <span property="schema:contentLocation">Arles</span>
  60. </footer>
  61. </article>
  62. <article id="opendatacontests" typeof="schema:BlogPosting">
  63. <h2 property="schema:name"><a href="#opendatacontests" title="Link to that content" property="schema:url">OpenData contests</a></h2>
  64. <div property="schema:articleBody"><p>This article is a follow up of a discussion with <a href="" title="">Olivier</a> after the <a href="" title="">OpenDataGarage</a> event which took place in Marseilles last July. After the <a href=";generate=yes&amp;width=640&amp;current=0" title="">excellent keynote</a> of <a href="" title="">Simon</a> we were wondering if those contests are finally useful for citizens.</p>
  65. <p>Most of the contests are arguing that it allows data openers to have apps for a minimal investment. Ok. <em>Let’s try to find who’s fooled in that contest?</em> Extract from the <a href="" title="">Apps for democracy</a> website:</p>
  66. <blockquote>
  67. <p>The first edition of Apps for Democracy yielded 47 web, iPhone and Facebook apps in 30 days - a $2,300,000 value to the city at a cost of $50,000.</p>
  68. </blockquote>
  69. <p>2 million dollars. Incredible ROI, right? But it means that app developers worked for that amount of money without getting a penny back. <strong>And developers are citizens.</strong> At least for now because that’s my second point.</p>
  70. <p>One of the argument of that kind of contest is to develop local economy. But after a few contests this is not true anymore, most apps being reused across cities/countries: if you did an app for Ottawa public transports, will it be easier to adapt it to Paris or to write it from scratch?</p>
  71. <p>Last but not least, <em>most of the created apps during those contests <a href="">are not maintained</a> because the business model was just to win the first prize</em> and it’s of course not viable for the 47 involved companies (note that even the first prize is probably not enough to be profitable given the time spent building the app).</p>
  72. <p>How can we encourage innovation and creativity with released open data? First let’s <strong>ask citizens</strong>, I really like the way Ubuntu is involving users through their <a href="" title="">Brainstorm</a> and <a href="" title="">Neighborland</a> has a nice UI too. Once you’re sure to have potential users, be collaborative with other developers, raw data often requires to be refined to standard formats and that’s a boring/repetitive task. Third, start to innovate to build your awesome AND viable app. This is the only win-win scenario, there will probably be less apps at the end but more useful to citizens. We can even imagine a business model based on citizens’ donations based on a relevant idea if there aren’t enough potential users. <em>We should not focus on OpenData apps but on <a href="">OpenData communities</a>.</em> I want <a href="" title="">MyMajorCompany’s concept</a> applied to OpenData apps’ development. <strong>Communities will drive local development, nothing else.</strong></p></div>
  73. <footer class="post-date">—
  74. <span property="schema:datePublished">Summer 2011</span>,
  75. <span property="schema:contentLocation">Arles</span>
  76. </footer>
  77. </article>
  78. <article id="noosphere" typeof="schema:BlogPosting">
  79. <h2 property="schema:name"><a href="#noosphere" title="Link to that content" property="schema:url">Noosphere</a></h2>
  80. <div property="schema:articleBody"><p>Bernard Werber introduced that concept to me in his Encyclopedia, the <a href="" title="">noosphere</a> is the "<em>sphere of human thought</em>", it’s about ideas emerging in the meantime but in different places. With the Web, this is not anymore a matter of physical places but this phenomenon still happens.</p>
  81. <p>For example my latest article about <a href="#opendatacontests" title="">OpenData contests</a> has been written after 2 months of reflexion/maturation but I discovered that Hubert Guillaud wrote <a href="" title="">a similar article</a> <em>the same day</em> with ideas from articles written those 2 last months that I wasn’t aware of. Coincidence? I don’t think so ;-).</p>
  82. <p>I’m convinced that Twitter is a new step, some kind of neonoosphere, where the physical distance between places has turned to a social distance related to followers’ circles. Twitter is somehow the <strong>feed of human thought</strong> (about the "human" part, I’m a bit skeptical though, I’d love to know the ratio of content generated by bots on Twitter). It means that from an era of relatively slow confrontation of ideas we can turn this in an era of real-time collaboration. This is the theory.</p>
  83. <p>With <a href="" title="">geofences</a>, the concept developed by Flickr (see their <a href="" title="">researches</a> for interfaces), something interesting is happening: the concept of digital neighbor BUT in a physical space, a way to combine both approaches.</p>
  84. <p>Our history is a perpetual local/global/local circle, I think we’re currently going from global to local but this "local" is not anymore a matter of physical space. And in the meantime <strong>this digital local has a growing influence on our physical world</strong>: coworking spaces based on affinities, <a href="" title="">local food by digital cooperation</a>, web conferences encouraging proximity and so on. This is terribly exciting.</p></div>
  85. <footer class="post-date">—
  86. <span property="schema:datePublished">Summer 2011</span>,
  87. <span property="schema:contentLocation">Arles</span>
  88. </footer>
  89. </article>
  90. <article id="replacement" typeof="schema:BlogPosting">
  91. <h2 property="schema:name"><a href="#replacement" title="Link to that content" property="schema:url">Replacement</a></h2>
  92. <div property="schema:articleBody"><p>I’m reading <em><a href="" title="">The 100 thing challenge</a></em> book while doing my luggage for Japan and it’s quite inspiring:</p>
  93. <blockquote>
  94. <p>We buy things year after year, over and over again, in our pursuit of contentment. It has been my impression that these days, replacement is emblematic of our dreams more than ownership. This is a curiosity, for it is by endlessly acquiring the right things that we measure our distance from the good life. We are always getting, but never getting there.</p>
  95. </blockquote>
  96. <p>We are not anymore bound to objects, the beauty of an hand-made unique piece, the more we can do is being devoted to a brand. But that’s not the same, it implies to get the latest object from that brand, again and again, <strong>replacement as a way of life</strong>. Consumerism at best.</p>
  97. <p>Doing your luggage for a whole year is very different from doing it for holidays. You have to make choices about what you bring, what you keep, what you give, what you just trash. I decided to give as much as I can and to reduce what I keep to the minimum. If I’m not bringing it, who know if it’ll be useful a year from now? In this configuration, it’s hard to think at some things as "I’ll never buy that article again because it’s useless" vs. "I’ll replace it with a better/different one when I’ll be back". After all, if I didn’t miss it for a year, is that really useful? <em>How tempting is it to start a new consumer life?</em> Buying the latest replaced product :-).</p>
  98. <p>Ironically, we’re ourselves more than ever afraid of being replaced, as a husband, as a father, as an employee, as a client and so on. This leads to stress and our relations and lives are totally changed by that replacement approach. Is there any alternative? <a href="" title="">Contributors, not consumers, are what the twenty first century needs.</a></p></div>
  99. <footer class="post-date">—
  100. <span property="schema:datePublished">Summer 2011</span>,
  101. <span property="schema:contentLocation">Arles</span>
  102. </footer>
  103. </article>
  104. <article id="dequiring" typeof="schema:BlogPosting">
  105. <h2 property="schema:name"><a href="#dequiring" title="Link to that content" property="schema:url">Dequiring</a></h2>
  106. <div property="schema:articleBody"><p>I finished <em><a href="" title="">The 100 thing challenge</a></em>’s book before leaving France and I’m not convinced that’s the way I want to refrain myself.</p>
  107. <p>Having 100 things but <a href="#replacement">replacing</a> those regularly is still consumerism and your challenge is just an alibi. I propose an alternative to it or maybe more a complement: the "aquire only x things per month" challenge where "x" is personal. Because there is a marketing issue here, let’s call it <strong>The Dequiring Challenge</strong> (yes, I love neologisms). This approach focuses on quality and perenniality of your things while encouraging minimalism and reflexion.</p>
  108. <p><em>From now on I’ll experiment that challenge, starting with <code>x=3</code> this month (November).</em> I have no idea how hard it will be given that I’m still discovering my new life in Japan and being continuously tempted by Japanese gadgets! Anyway, I’ll keep you posted <a href="">on twitter</a>.</p>
  109. <h3>My dequiring challenge log:</h3>
  110. <dl id="dequiring-log">
  111. <dt>November 2011</dt>
  112. <dd>
  113. <ol>
  114. <li>Foldable bag to avoid plastic ones</li>
  115. <li>Lightweight hat for hiking this winter</li>
  116. <li>Barefoot shoes for running/trailing/hiking</li>
  117. </ol>
  118. </dd>
  119. <dt>December 2011</dt>
  120. <dd>
  121. <ol>
  122. <li>A classy pull-over with hot underwears</li>
  123. <li>A visor to have more options when I run/trail</li>
  124. <li>Scissors for homemade hair-cut</li>
  125. <li>Christmas gifts: a belt, two caps, running gloves</li>
  126. </ol>
  127. </dd>
  128. <dt>January 2012</dt>
  129. <dd>
  130. <ol>
  131. <li>A classy black trousers</li>
  132. <li>A polar vest</li>
  133. <li>Foldable chopsticks</li>
  134. </ol>
  135. </dd>
  136. <dt>February 2012</dt>
  137. <dd>
  138. <ol>
  139. <li>Speakers</li>
  140. <li>Bag dedicated to trail</li>
  141. <li>A camera</li>
  142. <li>Valentine’s gift: a japanese bauble, a towel</li>
  143. </ol>
  144. </dd>
  145. <dt>March 2012</dt>
  146. <dd>
  147. <ol>
  148. <li>2 pairs of minimalist shoes for road & trail running</li>
  149. <li>A leather jacket</li>
  150. <li>A lightweight sleeping bag</li>
  151. </ol>
  152. </dd>
  153. <dt>April 2012</dt>
  154. <dd>
  155. <ol>
  156. <li>A lightweight hammock</li>
  157. <li>A light polar vest</li>
  158. <li>Diving glasses</li>
  159. <li>Birthday gift: a camera lense</li>
  160. </ol>
  161. </dd>
  162. <dt>May 2012</dt>
  163. <dd>
  164. <ol>
  165. <li>A shirt</li>
  166. <li>Cool biz shoes</li>
  167. <li>Recovery legging</li>
  168. </ol>
  169. </dd>
  170. <dt>June 2012</dt>
  171. <dd>
  172. <ol>
  173. <li>A longsleeves running shirt</li>
  174. <li>A longsleeves comfort shirt</li>
  175. <li>Cardio watch</li>
  176. </ol>
  177. </dd>
  178. <dt>July 2012</dt>
  179. <dd>
  180. <ol>
  181. <li>A pink polo</li>
  182. <li>A classy t-shirt</li>
  183. <li>A funny t-shirt</li>
  184. </ol>
  185. </dd>
  186. <dt>August 2012</dt>
  187. <dd>
  188. <ol>
  189. <li>An hiking bermuda</li>
  190. <li>A rain jacket</li>
  191. </ol>
  192. </dd>
  193. </dl></div>
  194. <footer class="post-date">—
  195. <span property="schema:datePublished">Autumn 2011</span>,
  196. <span property="schema:contentLocation">Tokyo</span>
  197. </footer>
  198. </article>
  199. <article id="contentsstreams" typeof="schema:BlogPosting">
  200. <h2 property="schema:name"><a href="#contentsstreams" title="Link to that content" property="schema:url">Contents vs. Streams</a></h2>
  201. <div property="schema:articleBody"><p>I’m often asked — as a data/privacy freak — why <a href="">I use</a> Twitter daily. To me Twitter isn’t about contents but streams and it changes it all: <em>the value is the freshness of the information and the speed of the reactions, not the content in itself.</em></p>
  202. <p>I even created a script, a long time ago, to keep only recent tweets (maintained and completed <a href="">by Olivier</a>) because in one hand I don’t want a public history of that kind of discussions and the interest of a stream drops very fast with time. Things I tweeted 1 month ago are probably irrelevant/useless now. If Twitter dies tomorrow, I’ll regret it for daily discussions/informations, but not for the log in itself.</p>
  203. <p>Of course, it might have been better: decentralized for instance. <em>The problem isn’t decentralized discussions but decentralized notifications.</em> How to be able to aggregate all reactions in one place for a better reader experience? Trackbacks were a fiasco because of spam, because there isn’t any network of trust yet. That’s a huge unresolved issue for the Web.</p>
  204. <p>Another problem is <strong>universality</strong>: you need to create an account to take part of the discussion and that’s the most annoying part to me, some people I want to interact with are not part of the closed system. Again, there is a lack of notifications too, I can’t easily cc messages to an email address or a cell phone number.</p>
  205. <p>It might have been worse too. Hopefully this platform will remain independent but I doubt about that, sooner or later a Big One™ will buy this toy and kill it. And we’ll get back to IRC, as always :-).</p></div>
  206. <footer class="post-date">—
  207. <span property="schema:datePublished">Autumn 2011</span>,
  208. <span property="schema:contentLocation">Tokyo</span>
  209. </footer>
  210. </article>
  211. <article id="barefoot" typeof="schema:BlogPosting">
  212. <h2 property="schema:name"><a href="#barefoot" title="Link to that content" property="schema:url">Barefoot</a></h2>
  213. <div property="schema:articleBody"><p>There are two distinct things behind this term: a running technique that can be applied whatever the shoes (but democratized by barefoot runners) and the fact to actually run (almost) barefoot.</p>
  214. <p>The running technique (mid-step, no extension, etc) is well described on numerous websites. I’d like to focus on the experience to run barefoot. My first impression was how silent it is to run with minimalist shoes (I didn’t opted for <em>real</em> barefoot for now), you rediscover the sounds of your environment, you approach animals and people without any annoyance, I even kept my respiration for a while to be totally silent :D</p>
  215. <p>The second sensation is of course the one you have with the soil, from roads to trails, you can feel whatever you’re walking/running to. <em>Choosing each and every step placement is fun</em>, jumping like an animal from places to places, back to ancient instincts, barefoot running really changed my approach of running and hiking, more focused on sensations. It can potentially hurt but, being more careful, you can avoid any injury related to that quite rapidly. There are surfaces more critical than others but the same apply whatever the shoes, remember that the articulation of your foot is way closer to the soil and thus limits risks.</p>
  216. <p>I started all this as an experiment, because experimenting on your own body is probably the more exciting thing you can do, and I know that I’ll not look back for a while. <strong>This is all about sensations and (feeling of) freedom.</strong></p>
  217. <p>PS: note that you <strong>must</strong> start slowly, whatever your current running experience, it’ll take months to develop muscles in your foot. That’s frustrating, because you know that your body can continue but your calf just can’t. I had to stop running for 3 days because of my lack of humility, don’t make the same mistake ;-).</p></div>
  218. <footer class="post-date">—
  219. <span property="schema:datePublished">Autumn 2011</span>,
  220. <span property="schema:contentLocation">Tokyo</span>
  221. </footer>
  222. </article>
  223. <article id="projection" typeof="schema:BlogPosting">
  224. <h2 property="schema:name"><a href="#projection" title="Link to that content" property="schema:url">Projection</a></h2>
  225. <div property="schema:articleBody"><p>I realized lately, alone by night in an onsen (hot Japanese spa: best place ever for introspection), that I don’t have projects anymore. No geek related project, no photography project, no career project, not even sportive project. Ultimate freedom or lost wandering? Hard to say for now.</p>
  226. <p>Ironically, I tried the opposite approach a few years ago, by infatuating my mind with video games, useless projects and events. It worked quite well to stop thinking for a time but on the other side you feel always exhausted and it’s really hard to keep that pace of very short nights…</p>
  227. <p>That’s an interesting moment in my life, partly motivated by my decision to move from my comfortable home. Japan influences me in that way, it’s a good place to stop taking care of a lot of things (security, food, etc). Next steps? Nothingness, detachment and compassion to use Zen’s vocabulary. Shibumi, Iki and Wabi-sabi to use Japanese words that I don’t fully understand yet :-).</p></div>
  228. <footer class="post-date">—
  229. <span property="schema:datePublished">Autumn 2011</span>,
  230. <span property="schema:contentLocation">Tokyo</span>
  231. </footer>
  232. </article>
  233. <article id="jetlag" typeof="schema:BlogPosting">
  234. <h2 property="schema:name"><a href="#jetlag" title="Link to that content" property="schema:url">Jetlag</a></h2>
  235. <div property="schema:articleBody"><p>A few advices when you have to travel around the world to adapt your body to another timezone faster:</p>
  236. <ul>
  237. <li>do not think about your old time and even try to anticipate if possible (getting up earlier or try to stay awake later) ;</li>
  238. <li>take your meals at the new lunch times, as big as you can the first day, your body will be used to that new cycle ;</li>
  239. <li>expose your body to the sun (or at least lights) during days at your new location, here you can anticipate too darkening your room the day before you leave ;</li>
  240. <li>be exhausted, something I experimented for ParisWeb and that worked pretty well: it allows you to sleep in the plane (depends on your level of excitation and arrival time of course) ;</li>
  241. <li>do not go to sleep before it’s night at your new location, it’s hard but it’s a good investment, trust me ;</li>
  242. <li>on the contrary, if you can’t sleep on the evening, do sport as much as you can and then watch the most boring thing you can find on the TV at your hotel ;</li>
  243. <li>take care of what you drink, coffee and tea are well known for their properties. Drink water, a lot. Alcohol can make you sleepy in the plane but I prefer to be dressed warmly.</li>
  244. </ul>
  245. <p>Still to be tested: Anti-Jet-Lag Diet, even if I’m a bit skeptical about that idea. Any feedback?</p></div>
  246. <footer class="post-date">—
  247. <span property="schema:datePublished">Autumn 2011</span>,
  248. <span property="schema:contentLocation">Tokyo</span>
  249. </footer>
  250. </article>
  251. <article id="centralizing" typeof="schema:BlogPosting">
  252. <h2 property="schema:name"><a href="#centralizing" title="Link to that content" property="schema:url">Centralizing</a></h2>
  253. <div property="schema:articleBody"><p>I’m thinking about that for years now and the recent issues with the <a href="">APINC</a> motivated my laziness to regroup all my digital identities to a unique domain name: <strong></strong></p>
  254. <p>Creating both a single point of failure, but also a single point of trust: domain and DNS managed via <a href="">Gandi</a> and files hosted via <a href="">Alwaysdata</a> because they care so much about their clients and innovative technologies.</p>
  255. <p>Here will be the URI (this is still a huge work in progress, I’m so happy to have kept so many pages static!), all will of course be redirected:</p>
  256. <ul>
  257. <li>/ dispatching between members of the family</li>
  258. <li>/david/ the page of my identity (FOAF and so on)</li>
  259. <li>/david/biologeek/ the content of, probably as static html</li>
  260. <li>/david/pro/ the content of</li>
  261. <li>/david/code/ the content of</li>
  262. <li>/david/thoughts/ the content of</li>
  263. <li>/david/media/ the content of because Alexandre Buisse convinced me to publish photographs again</li>
  264. <li>/anakin/ (my black cat) and /yoda/ (my bonsaï) maybe one day :D</li>
  265. </ul>
  266. <p>Another big news is the switch to HTTPS only for the whole domain, something I’d like to do for a while is now becoming way easier/cheaper with a unique domain. It was way easier to set up than I imagined and I encourage you to do so: being sure of your source of information is so important (note that Gandi is offering an SSL certificate for each domain name). It will allow me to test <a href="">WebID</a> for real too.</p>
  267. <p>I’m also working on a new design to unify a bit all those pages with a topbar ala Twitter or Google. This is far from being finished, this is more a test actually and I’m still thinking about the mobile adaptation of both the navigation and the design. I’m trying new fonts served by Typekit, using the <a href="">Abril Text</a> and <a href="">Abril Fatface</a> ones.</p>
  268. <p>Those days, <strong>I try to focus on aesthetic, minimalism and links</strong>. Not only for this website but as a way of life. Drop me a line if you have any suggestion.</p></div>
  269. <footer class="post-date">—
  270. <span property="schema:datePublished">Winter 2011</span>,
  271. <span property="schema:contentLocation">Tokyo</span>
  272. </footer>
  273. </article>
  274. <article id="healthy" typeof="schema:BlogPosting">
  275. <h2 property="schema:name"><a href="#healthy" title="Link to that content" property="schema:url">Healthy</a></h2>
  276. <div property="schema:articleBody"><p>I decided to do some sport about a year ago, mainly to be able to complete a trek in Corsica that I dreamt of for years.So at first it was just about having enough muscles and endurance but the more I trained, the more I actually enjoyed it!</p>
  277. <p>First your motivation is essential, you need a goal. And even with a goal, there are chances that you’ll fail because sport is boring at the beginning. Really. And it hurts. And it takes time. You don’t need motivation but abnegation for the first 2-3 months. How to achieve that painful process?</p>
  278. <ul>
  279. <li><em>start small</em>: <strong>but often</strong>, 4*20 minutes per week is better than 3*30 minutes, it prevents injuries too ;</li>
  280. <li><em>routine</em>: decide rules with yourself, like "I’ll go running 3 times that week whatever happens" (and by whatever I mean weather, family, laziness, etc) ;</li>
  281. <li><em>diversity</em>: try to mix various sports during the week, running, hiking, biking, swimming, anything that motivates you ;</li>
  282. <li><em>everywhere</em>: you can always use your environment to do sport, from stopping to take lift/escalator to making tractions during your daily commute in the train, there is always a way to use that time efficiently.</li>
  283. </ul>
  284. <p>During those first months, you’ll learn a lot about you. I learned to breath, to drink, to eat, to stretch, to rest. Sometimes with advices, most of the time the hard way though. Probably because I did all the process alone, it can be interesting to do that with a group or a friend but I know that I better listen to (and motivates) me when I’m alone. <abbr title="Your Mileage May Vary">YMMV</abbr>.</p>
  285. <ul>
  286. <li><em>breath</em>: it’s all about rythm, that’s the first thing you learn and ironically that’s the last thing you need to improve, if you still have problems with respiration after a few iterations, you probably try to start too fast. Reduce your pace, there is no problem at being slow. Focus on endurance first.</li>
  287. <li><em>drink</em>: regularity, regularity and regularity. My rule is: one little mouthful every 10 minutes if you run, 20 minutes if you walk. You can drink less but your performances will drop very quickly if you are deshydrated, it’s up to you ! Adapt to the weather but remember that you always emit water so hydration is not an option.</li>
  288. <li><em>eat</em>: regularity, regularity and ok you start to understand :-) My rule is: one mouthful every 30 minutes. Never too much or your performances will drop too (forget about big meals during a picnic when only half of the hike is done for example).</li>
  289. <li><em>stretch</em>: I’m still learning a lot in this domain, from my experience you can hardly plan a sportive event on many days without stretching. Since my <a href="#barefoot">barefoot</a> transition it’s essential to stretch my calves many time a day but that’s a bit extreme.</li>
  290. <li><em>rest</em>: if you’re exhausted at the end of the week you’re doing it wrong (or you’re not training anymore), you know if you’re not over-training if you can repeat your iterations for 4 weeks without pain (nor injuries!). It’s OK to feel your muscles but plan days for recuperation.</li>
  291. </ul>
  292. <p>Note: when I talk about performances, it’s about enjoying your iteration and it totally depends on the context, adapt to your situation, it’s different when I go hiking with family vs. trailing alone for instance.</p>
  293. <p>Do not think that gaining muscles is fast, it’s not. If you focus on muscles, go to a gym club and eat a lot of proteins. That’s not my motivation. What I love about sport is enjoying the nature and reaching places that looked inacessible a year ago. There is some kind of animal instinct too when you’re jumping from stone to stone, it’s hard to describe but you "feel" to be part of your environment and you start to see previously "hidden" things. I met a lot of unusual animals during my runs:</p>
  294. <ul>
  295. <li>a chamois in the Luberon, I was in a descent full of rocks, he was jumping to go up. We both stoped at 6 meters and stared each others for a couple of seconds, astonished (it’s not usual to see a chamois there so I was probably the more suprised!) ;</li>
  296. <li>a fox crossing an alpine ibex crossing a marmot crossing… me, under an hailstorm, totally surrealist scene in the Alps ;</li>
  297. <li>a tanuki today at the Meiji Jingu Shrine, between Shinjuku and Shibuya (two of the most crowded places of Tokyo, and probably the world), I was very surprised to see an almost wild animal there of that size given the thousands of people processioning at that place 3 weeks ago for the new year celebration.</li>
  298. </ul>
  299. <p>Besides that, I learned to eat less fatty food (so hard when you work from home) and drink way less alcohol. Both leads to an annihilation of performances :D</p>
  300. <p>A japanese told me last month that I looked healthy. I smiled.</p></div>
  301. <footer class="post-date">—
  302. <span property="schema:datePublished">Winter 2011</span>,
  303. <span property="schema:contentLocation">Tokyo</span>
  304. </footer>
  305. </article>
  306. <article id="layers" typeof="schema:BlogPosting">
  307. <h2 property="schema:name"><a href="#layers" title="Link to that content" property="schema:url">Layers</a></h2>
  308. <div property="schema:articleBody"><p>There has been a lot of frustration lately about layered systems in computer science and especially the Web.</p>
  309. <p>First with <strong>HTTP layers</strong> and the creation of <a href=""></a>:</p>
  310. <blockquote>
  311. <p>Engineering clocks slow down because developers need to account for dependencies between API calls, and to arrange those calls to optimize overall latency. Implementing orchestration logic involves multi-threaded fork-join code, leads to code bloat, and distracts from the main business use case that the developer is striving to support.</p>
  312. </blockquote>
  313. <p>With <strong>architecture layers</strong> too and the cost of <a href="">load-balancing techniques</a> and their complexity:</p>
  314. <blockquote>
  315. <p>And really the frustrating part is there seems to have been no headway on any of this stuff in a decade. Same old open source options, same old techniques.</p>
  316. </blockquote>
  317. <p>And finally with <strong>operating systems layers</strong> and the way they’ve <a href="">originally been developped</a>:</p>
  318. <blockquote>
  319. <p>You program in a dynamic language, that runs on a JVM, that runs on a OS designed 40 years ago for a completely different purpose, that runs on virtualized hardware. Does this make sense?</p>
  320. </blockquote>
  321. <p>Now, if we go one step further, what about <strong>data layers</strong>? When you think about it, nowadays the data displayed to the end-user has been processed a crazy number of times! Let’s take the example of an architecture with a backend API and a classic SQL database:</p>
  322. <ul>
  323. <li>from disk to database ;</li>
  324. <li>from database to language object (ORM) ;</li>
  325. <li>from language object to JSON ;</li>
  326. <li>from JSON to language object ;</li>
  327. <li>from language object to HTML.</li>
  328. </ul>
  329. <p>And I’m oversimplifying here, your data is probably denormalized with parts from cache in memory, your HTML interacts dynamically with your data through JavaScript and so on. All this has a cost: development, maintenance, performances, hosting, bandwith, etc.</p>
  330. <p><em>Now imagine that you can remove those layers.</em> From <a href="">Boot to Gecko</a> to <a href="">CouchApp</a>, we are not that far of getting rid of some big layers in fact. Think about that today: <strong>what can I do to reduce the number of layers of my project?</strong> Degrowth applied to computer science (Plain Old HTML is valid too ;-)).</p></div>
  331. <footer class="post-date">—
  332. <span property="schema:datePublished">Winter 2011</span>,
  333. <span property="schema:contentLocation">Tokyo</span>
  334. </footer>
  335. </article>
  336. <article id="books" typeof="schema:BlogPosting">
  337. <h2 property="schema:name"><a href="#books" title="Link to that content" property="schema:url">Books</a></h2>
  338. <div property="schema:articleBody"><p>You maybe noticed that I’m not mentioning books on <a href="#dequiring">my dequiring challenge log</a>, that’s because I’m not considering stories as things you can own.</p>
  339. <p>To me a book, digital or not, is just a representation of a story, <strong>a way to transmit a message</strong>. I consider myself as a node when I got a book: I listen to the story and then I try to transmit it to a friend, like an interesting link shared on the Web. I don’t care about the physical book in itself, I don’t get any particular attachment to dead trees.</p>
  340. <p>That being said, I’m really concerned that a story can be lost. Of course a lot of stories are lost every days by lack of transmission, that’s what I call the Darwinism applied to collective knowledge. We can’t log and/or remember every story and the less transmitted ones disappear.</p>
  341. <p>The network of stories transmitted by books is acentered, like the Web. <strong>That’s a way to preserve knowledge</strong>, even if a node fails to transmit the story, there will be another way to find it. This is no longer the case with digital libraries which store stories in a centralized way, nodes are getting way too big and it’s really dangerous. Some are even considering disconnecting totally their nodes from the current network (I’m looking at you Apple!).</p>
  342. <p>If a node of that kind disapears, a lot of stories will be lost. Once and for all. This is not <a href="">the first time in history</a> but it’s really sad that it still happens now that we have the technology to avoid it. <em>Put your digitalized stories on the Web if you care about their perenialty.</em></p></div>
  343. <footer class="post-date">—
  344. <span property="schema:datePublished">Winter 2011</span>,
  345. <span property="schema:contentLocation">Tokyo</span>
  346. </footer>
  347. </article>
  348. <article id="ssl" typeof="schema:BlogPosting">
  349. <h2 property="schema:name"><a href="#ssl" title="Link to that content" property="schema:url">SSL</a></h2>
  350. <div property="schema:articleBody"><p>A few people asked me why I switched to <abbr title="Hypertext Transfer Protocol Secure">HTTPS</abbr> only on this domain. First about the <strong>only</strong>, that’s because knowing both the plain text <em>and</em> the encrypted text eases a cryptographic attack by comparison. Now about <abbr title="Secure Sockets Layer">SSL</abbr>’s pros and cons:</p>
  351. <p><strong>Please read the follow-up of this article <a href="#https">about HTTPS</a>, this thought contains mistakes.</strong></p>
  352. <h3>Pros</h3>
  353. <ul>
  354. <li><strong>privacy</strong>: any intermediary between you and my server will not be able to <em>analyze</em> the content you read because the message is encrypted, only the URI (meaningful, SEO-oriented URIs can be a threat for your users’ privacy, did you ever thought about that?) ;</li>
  355. <li><strong>security</strong>: any intermediary between you and my server will not be able to <em>alter</em> the content you read, this is <a href="">not exactly true</a> though but way better than nothing ;</li>
  356. <li><strong>identity</strong>: this is a requirement to play with <a href="">WebID</a>, to be able to log in <em>and</em> to exchange critical data with the third-party website (that information’s workflow part is what differs conceptually from <a href="">BrowserID</a>).</li>
  357. </ul>
  358. <h3>Cons</h3>
  359. <ul>
  360. <li><strong>performances</strong>: the negotiation at each request takes time, enough time <a href="">to be a problem on mobile apps</a> (or low connection access). Furthermore, I can’t have a subdomain for my assets without paying more and thus you had to send cookies for statics too, which impacts performances ;</li>
  361. <li><strong>one more point of failure</strong>: if your Certificate Authority (CA) is down, the user will not be able to view your website in a secure manner (same as HTTP + browser error) ;</li>
  362. <li><strong>price</strong>: it costs me 16$/year without taxes and I had to remember to update it each year or browsers will raise a certificate error too. Moreover, your web hosting need to be compatible (for instance I had to pay 66$/year more for an IP address on my mutualized server).</li>
  363. </ul>
  364. <p>That being said, is it worth it? Well, I do think so because I consider this domain as my <strong>digital identity</strong> but I understand that it can be overkill for the current content. <em>This is an investment for the future.</em></p></div>
  365. <footer class="post-date">—
  366. <span property="schema:datePublished">Winter 2011</span>,
  367. <span property="schema:contentLocation">Tokyo</span>
  368. </footer>
  369. </article>
  370. <article id="fear" typeof="schema:BlogPosting">
  371. <h2 property="schema:name"><a href="#fear" title="Link to that content" property="schema:url">Fear</a></h2>
  372. <div property="schema:articleBody"><p>I realized lately that French people are afraid. And that’s why they are so arrogant and embittered.</p>
  373. <p>Afraid of theft, afraid of being involved in a fight, afraid of loosing their job, afraid of being injured/rapted, afraid of the police(!), or just afraid of being fooled. It creates a very nasty environment to live in, a vicious circle of rejection of the others leading to all kinds of extremisms. The constant attention required by fear consumes a lot of useless energy. People are exhausted and they don’t even realize why.</p>
  374. <p>Let’s compare this situation to Japan. Of course. In Japan, the level of trust (I prefer that word vs. security or safety) is so high that you can even lost money and find it back. When you put your bag somewhere, you’re 99% sure to find it at the exact same place hours later (the remaining 1% is due to tourists :p). You’re <strong>never</strong> afraid of wandering by night. No one will ever tried to fool you when you stand in line for a restaurant or an exposition. So relaxing that you can’t believe it without actually living it. <em>It sounds incredible and it shouldn’t be.</em></p>
  375. <p>And yet, there are a lot of reason to be afraid in Japan, from natural to <em>not-so-natural-anymore</em> events you can hardly consider this country as a <em>safe place</em>. Japanese tends to adopt a pragmatic approach to this (may I say phlegmatic?) because nothing can be made against it, there is even <a href="">a word for that!</a></p>
  376. <p>So why do we — frenchies — inflict that mutual fear to us? Alternatives do exist. It’s up to you, to me, to <strong>us</strong>.</p></div>
  377. <footer class="post-date">—
  378. <span property="schema:datePublished">Winter 2011</span>,
  379. <span property="schema:contentLocation">Tokyo</span>
  380. </footer>
  381. </article>
  382. <article id="standards" typeof="schema:BlogPosting">
  383. <h2 property="schema:name"><a href="#standards" title="Link to that content" property="schema:url">Standards</a></h2>
  384. <div property="schema:articleBody"><p>People are complaining about the <abbr title="World Wide Web Consortium">W3C</abbr>’s standardization process for years. Is it a fatality?</p>
  385. <p>First things first, when I share a link <a href="">on Twitter</a> I try to quote the interesting part, the one that reflects my point of view. Most of the time it’s not the whole article otherwise I had to write it :D. That’s what happened with <a href="!/davidbgk/status/168266802734968832">the link to Dustin Curtis’ article</a> lately, note that I didn’t quote the sensational:</p>
  386. <blockquote>
  387. <p>The reason the -webkit prefix was necessary is simple: the W3C and the CSS Working Group are ineffective, failed organizations.</p>
  388. </blockquote>
  389. <p>On standards, what interest me is that simple question: <strong>is it possible to establish a consensual standard faster?</strong> After all that’s the main criticism toward the W3C. Standards take times for 3 reasons:</p>
  390. <ul>
  391. <li><em>endless discussions:</em> some thread are real caricatures of trolls, I sadly quit the WebID group for this ;</li>
  392. <li><em>lack of involvement:</em> probably because the standardization process looks boring from a developer point of view ;</li>
  393. <li><em>politics:</em> that’s the tough one, from egos to economical interests, objectivity is for sissies.</li>
  394. </ul>
  395. <p>The chairman has the role to put an end to endless discussions, that’s difficult but necessary. On the other side discussion is a requirement to consensus and the line between troll and well-founded reasoning is thin and not the same for all participants. I don’t know how to address the lack of involvement issue, maybe a way to collect web developers needs at a higher level can motivate future participations, a lot can be done in this area. Remains politics, <em>diversity is the only regulator to fight against extremisms and mono-cultural approaches</em>, not sure that it speeds up the process though. To answer my own question and please take the time to think about it too: <strong>it’s hardly possible.</strong> But I’d love to be proven wrong by W3C’s haters.</p>
  396. <p>Jacob Kaplan-Moss <a href="!/jacobian/status/169465798216261633">asked</a>:</p>
  397. <blockquote>
  398. <p>Let’s say that Mozilla and Microsoft both sign onto WebKit and ship it in their browsers. How would that hurt the web?</p>
  399. </blockquote>
  400. <p>It will not hurt the Web, it will not accelerate the pace of standardization/innovation either, the discussion will just move from W3C’s to Webkit’s mailing-lists and innovation to new proprietary layers on top of Webkit. The W3C is a Consortium, a group of people (mostly representing implementors) discussing how to build things in a standardized way to ease implementation for us: web developers. Opposing implementors and W3C is a nonsense, they <strong>are</strong> the core of the W3C.</p>
  401. <p>W3C should stand for World Wide Web Community too and that’s the current problem, web developers are not enough involved in those discussions and thus are frustrated because they don’t understand the standardization’s process. <em>We are the Web, we must be part of the W3C.</em></p></div>
  402. <footer class="post-date">—
  403. <span property="schema:datePublished">Winter 2011</span>,
  404. <span property="schema:contentLocation">Tokyo</span>
  405. </footer>
  406. </article>
  407. <article id="https" typeof="schema:BlogPosting">
  408. <h2 property="schema:name"><a href="#https" title="Link to that content" property="schema:url">HTTPS</a></h2>
  409. <div property="schema:articleBody"><p>I was almost totally wrong on my <a href="#ssl">previous article about SSL</a> so here are corrections thanks to <a href="">Alexandre Alapetite</a> and <a href="">Vincent Bernat</a>.</p>
  410. <p><strong>About privacy:</strong> the connexion is established via an IP address and port only (that’s <a href="">why I need a dedicated one</a> by the way). So your URLs, as meaningful as they could be, are not a threat as I previously stated.</p>
  411. <p><strong>About costs:</strong> you can get a free certificate via <a href="">StartSSL</a> or <a href="">CAcert</a>, in my case I prefer to trust my registar (Gandi) which provides a free one too. I know that I’ll have some support if I get into any trouble and it’s easier to manage domain name, DNS and certificates in one place.</p>
  412. <p><strong>About security:</strong> activating SSL is not enough, you have to take care of the configuration too. SSLlabs is an interesting tool to check that and <a href=";s=176%2e31%2e58%2e103">the result for this website</a> is not that good… if I was on a dedicated server. <a href="">AlwaysData</a> told me that they are aware of those issues and got protections against that, some evolutions are planned to improve that part.</p>
  413. <p><strong>About performances:</strong> you have to take care of caching more aggressively because browsers will consider that resources will not always be cacheable by default. On the other hand, the size of the key you use is crucial for the latency during the negotiation of the SSL connexion, mine is 2048 bits (<a href="">best compromise</a>) but Google for instance choose a 1024 one to speed up the process (less secure though but security is always a trade-off, <a href="">Mozilla and Microsoft updated their policies a year ago</a> on that topic).</p>
  414. <p><strong>About point of failure</strong>: if your Certificate Authority is down, <a href="">it will probably be ignored</a> considering you’re on a captive portal (which leads to issues with certificates’ revocation, read the article for the whole story).</p>
  415. <p>That’s what I love about bloging, learning new things when I write something on a subject, being proven wrong, discussing, iterating. Never hesitate to send me an email if I’m wrong. I must confess that I learned almost all my computer science knowledge while helping people on IRC and writing blog posts. <strong>Sharing is learning.</strong></p></div>
  416. <footer class="post-date">—
  417. <span property="schema:datePublished">Winter 2011</span>,
  418. <span property="schema:contentLocation">Tokyo</span>
  419. </footer>
  420. </article>
  421. <article id="caring" typeof="schema:BlogPosting">
  422. <h2 property="schema:name"><a href="#caring" title="Link to that content" property="schema:url">Caring</a></h2>
  423. <div property="schema:articleBody"><p>A follow-up of my precedent article about <a href="#fear">Fear</a>.</p>
  424. <p>Olivier Thereaux <a href="!/olivierthereaux/status/168690650458488833">reacted</a> <a href="!/olivierthereaux/status/168691026830176256">briefly</a> on Twitter:</p>
  425. <blockquote>
  426. <p>societies tend to fear the other more when differentiation (and inequality) are inflated. Class, sex, race, nationality…
  427. case in point, the Japanese fear neighboring countries, foreigners. etc. Just not each other, cos jp is still very homogeneous.</p>
  428. </blockquote>
  429. <p>There were a few reactions on <a href="">the extract published by Laurent Gloaguen</a> (in French) too.</p>
  430. <p>There is another aspect of Japan I need to discuss related to <em>respect and trust</em>. The concentration of people in Tokyo leads to that daily routine, everybody feeling "connected" with their smartphone and thus ignoring their environment and their neighbors, looks familiar? <strong>But</strong>, if anyone has any trouble, there is a huge difference in the astonishing devotion to fix it. I saw a person running to give a glove to another person running to give that glove to another person running to catch up a bike with the owner of the missing glove 60 meters away. Wow! This is just an example, I’ll not report the dozen of time Japanese people proposed to accompany us to the location we initially asked for help to find a place.</p>
  431. <p>The act of caring is so developed that they even created a complementary currency based on that to help seniors called <em><a href="">fureai kippu</a></em>: a way to exchange hours of service to an elderly person from one family to an other.</p>
  432. <p>What can we learn from that? First, when everybody is playing the game, it works. Second, beyond the fact of helping others, there is the one to feel concerned by the work of others (which for instance results in a cleaner city, really no one is eating in the street or littering whatever). Third, <strong>it creates an implicit solidarity to fight against adversity</strong>, it’s incredibly reassuring, even more being a foreigner. Fourth, barter can work at large scale and that’s a good reminder those days.</p></div>
  433. <footer class="post-date">—
  434. <span property="schema:datePublished">Winter 2011</span>,
  435. <span property="schema:contentLocation">Tokyo</span>
  436. </footer>
  437. </article>
  438. <article id="exercising" typeof="schema:BlogPosting">
  439. <h2 property="schema:name"><a href="#exercising" title="Link to that content" property="schema:url">Exercising</a></h2>
  440. <div property="schema:articleBody"><p>Each sportsman asks himself — and is often being asked — why does he inflict that to his body? Here are my personal reasons.</p>
  441. <p>First, I’m close to 30 and about a year ago I realized that my body was way older, I wasn’t able to complete a hike without being really tired with aches for a week. It was very hard to accept it and <em>I made the choice to change my sedentary way of life</em> (working from home for 3 years has physical consequences). I consider that I did half of the pathway and that’s extremely rewarding to reach that point!</p>
  442. <p>Second, <em>I want to be prepared for tough times</em>. Not that I’m particularly afraid of the future but I can smell that something is "evolving" and I want to be ready, both physically and mentally to… well… mind the gap. As a result, I didn’t feel sick for a year after 2 winters (maybe biased by face masks for the last 6 months in Japan but we live for one month in a very cold^W^Japanese apartment) .</p>
  443. <p>Third, <em>it reconnects me to my environment</em>, that’s why I refuse to run with music or any sports’ app yelling my distance and time each kilometer. I use that time to discover my city, to observe people, to listen to the nature, to just think and to stop thinking. Willingly. It offers me the time to make thoughtful decisions too.</p>
  444. <p>Besides all that, <em>it’s all about feeling good</em>. I’m not talking about endorphins here (even if it’s obvious that it’s stimulating too), but more about the sensations you can have when you take pleasure to do it. This weekend I was running in a snowy trail and I felt the same sensation that I had a few years ago while snowboarding, a combination of speed and flight and suffering and happiness.</p>
  445. <p><em>I feel <a href="#dequiring">lighter</a>, <a href="#healthy">healthier</a>, <a href="#slowweb">slower</a>, stronger.</em> <strong>Alive.</strong></p>
  446. <p>Recommended book: <em>Sun and Steel</em> by <a href="">Yukio Mishima</a>, merci <a href="">Karl</a>.</p></div>
  447. <footer class="post-date">—
  448. <span property="schema:datePublished">Winter 2011</span>,
  449. <span property="schema:contentLocation">Tokyo</span>
  450. </footer>
  451. </article>
  452. <article id="theorem" typeof="schema:BlogPosting">
  453. <h2 property="schema:name"><a href="#theorem" title="Link to that content" property="schema:url">Theorem</a></h2>
  454. <div property="schema:articleBody"><p>Inspired by <a href="">the CAP theorem</a>, my own experience shows that it is impossible for a web enthusiast to simultaneously obtain all three of the following guarantees:</p>
  455. <ul>
  456. <li><em>Fun</em>: technically and humanly</li>
  457. <li><em>Ethic</em>: self-accomplishment and generosity</li>
  458. <li><em>Profit</em>: sustainability and extras</li>
  459. </ul>
  460. <p>According to the theorem, a web project can satisfy any two of these guarantees at the same time, but not all three.</p>
  461. <p><strong>Discuss.</strong></p>
  462. <p><em>Addendum: if you only have one, it’s time to find a new job.</em></p></div>
  463. <footer class="post-date">—
  464. <span property="schema:datePublished">Winter 2011</span>,
  465. <span property="schema:contentLocation">Tokyo</span>
  466. </footer>
  467. </article>
  468. <article id="traceability" typeof="schema:BlogPosting">
  469. <h2 property="schema:name"><a href="#traceability" title="Link to that content" property="schema:url">Traceability</a></h2>
  470. <div property="schema:articleBody"><p>A few months ago <a href="#contentsstreams">I wrote</a>:</p>
  471. <blockquote>
  472. <p>the value [of the stream] is the freshness of the information and the speed of the reactions, not the content in itself [because] the interest of a stream drops very fast with time.</p>
  473. </blockquote>
  474. <p>It appears that Twitter found another value in this stream based on trends and customers’ satisfaction dedicated to marketing, they sold their <em>Firehose</em> to <a href="">DataSift and Gnip</a> since July 2011 in order to make money and I can perfectly understand that. It could have been worse.</p>
  475. <p>This anecdote reminded me that I worked for a company 5 years ago dedicated to traceability (in laboratories) and that there are many levels, from macro to micro, to make stories from data. Besides that, I realized that <a href="">a lot of information</a> contained in tweets are personal (from place to time to context and so on) and will be used on an individual bases. <em>This is just a matter of time.</em></p>
  476. <p>Given that I <a href="">rewrote my script</a> (no maintenance, no support, just <a href="">DBAD</a>) to keep tweets in text files and delete originals from Twitter. I control the meta information I keep and the one <a href="">I want to share publicly</a>. <strong>Take care of your webprints.</strong></p></div>
  477. <footer class="post-date">—
  478. <span property="schema:datePublished">Spring 2012</span>,
  479. <span property="schema:contentLocation">Kyoto</span>
  480. </footer>
  481. </article>
  482. <article id="cleverness" typeof="schema:BlogPosting">
  483. <h2 property="schema:name"><a href="#cleverness" title="Link to that content" property="schema:url">Cleverness</a></h2>
  484. <div property="schema:articleBody"><p>In his book <em>Introduction à la pensée complexe</em> published in 1990 (thank you <a href="">Thomas</a>!), Edgard Morin opposed the car to the human body as an example of an auto-organized system: the former composed by perfect elements that results in single points of failure of the whole, the latter made of lousy elements resulting in an auto-regenerating system.</p>
  485. <p>I think we reached that point on the Web with the cloud and all fail-over mechanisms we have now. <em>We don’t spend time setting up perfect components but rather try to create the more auto-regenerating architecture</em>, this is an important shift in the way we shape our services.</p>
  486. <p>The next step is to make those parts speaking one to each other, without a centralized monitoring component to rely on. The communication in our body is a peer-to-peer system, not that far from the original Web architecture after all.</p>
  487. <p><strong>Do not fight against failure, learn to deal with it. Cleverness is about adaptability, not perfection.</strong></p></div>
  488. <footer class="post-date">—
  489. <span property="schema:datePublished">Spring 2012</span>,
  490. <span property="schema:contentLocation">Hakone</span>
  491. </footer>
  492. </article>
  493. <article id="communities" typeof="schema:BlogPosting">
  494. <h2 property="schema:name"><a href="#communities" title="Link to that content" property="schema:url">Communities</a></h2>
  495. <div property="schema:articleBody"><p><em>Note: this article is a summary of my 12 minutes talk at <a href="">djangocong</a>.</em></p>
  496. <p>I’m in Japan for 7 months now and I thought that the harder times would have been to deal with the distance from family and friends. Actually, it’s not. Because those people can take a plane or give a Skype call, what is difficult is to be far from your communities.</p>
  497. <p>A community is a group of people (cum) sharing something (munus), this is all about sharing a common good and interacting with the other members of the group. I think we can go a bit further in that definition adding the notions of <em>vision</em> and <em>values</em> associated to that group. During that time in Japan I realized how important communities are, not only to interact with but because they define yourself. <strong>Your personal story is the sum of all interactions you have with your communities.</strong> (<em>Warning</em>: if you’re only defining yourself with one community, it’s probably a sect.)</p>
  498. <p>Initially, you probably started to ask for help as your first contact with the Django community but that was an transient state to both increase your knowledge and know cultural codes of this particular community, to be able to communicate, to feel part of it and to give your knowledge back. Unfortunately some people never reach that point and I think that it has to do with the size of the community. I highly recommend the reading of Clay Shirky, <a href="">A Group Is Its Own Worst Enemy</a> (<a href="/david/cache/2020/4d81a301bbb7936312cd16e6674f3ff6/">cache</a>) on this topic:</p>
  499. <blockquote>
  500. <p>And, finally, you have to find a way to spare the group from scale. Scale alone kills conversations, because conversations require dense two-way conversations.</p>
  501. </blockquote>
  502. <p>I identified 5 ranges of sizes from my own experience:</p>
  503. <ul>
  504. <li>1-5 people → <strong>Reflexion</strong>: <em>thinkers</em>, they share the same values (conflicts are very destructive in such a tiny group) and decide of the vision. This is the same schema as in a startup.</li>
  505. <li>6-15 people → <strong>Action</strong>: <em>doers</em>, they agree with the overall vision and feel emulated by the capacities of other members. This is the same schema as in a team (see <a href="">Daniel Herrero’s keynote</a> for the importance of 15 team mates in Rugby).</li>
  506. <li>16-50 people → <strong>Interaction</strong>: <em>talkers</em>, they like the initial vision and they can talk endlessly about it but nothing concrete is actually done. This is the same schema as in a non-profit association.</li>
  507. <li>51-500 people → <strong>Consumption</strong>: <em>consumers</em>, they don’t try to understand the vision, they are here for themselves. This is the same schema as in a company.</li>
  508. <li>501 people and more → <strong>Presence</strong>: <em>attendees</em>, they don’t even know about the vision, they are here because they have to. This is the same schema as in an administration.</li>
  509. </ul>
  510. <p>Those figures may seem extreme and too precise, that’s of course an approximation of the different patterns I identified. I’m not saying here that all participants from a group of more than 50 people are consumers, that’s just the limit where you <strong>start</strong> to see people joining the community with that profile (going to an event to look for a job, joining an IRC channel to finish a project, etc).</p>
  511. <p>Given those sizes, determine your involvement in each of your communities. Does it define what you would really like to be? Should you focus a bit more on this community? Is your help still valuable in this other? Your interactions with those communities evolve with time because you’re evolving too. There is no shame about that, just be clear on what you’re trying to do. This is all about communication, be honest with others, with yourself.</p>
  512. <p>Let’s focus on Djangocong, given the growing popularity year after year and the lack of new seats, it has been stated as an elitist event. I understand that it can be considered like that from an external point of view even if I regret it but that’s the price of the conviviality you can’t achieve with consumers. The solution is as obvious as the original title of the conference: <strong>Les</strong> rencontre<strong>s</strong> Django. Why is there only one event with such a title? Go on, create your own (local) event and benefit from the help of the community. <strong>You’re already a talker, level up and become a doer!</strong></p>
  513. <p><em>One thing I learned in Japan, is the importance of the group on behalf of the individual and how it can transcend a society. We should think a bit more about that in our more and more individualistic societies.</em></p></div>
  514. <footer class="post-date">—
  515. <span property="schema:datePublished">Spring 2012</span>,
  516. <span property="schema:contentLocation">Montpellier</span>
  517. </footer>
  518. </article>
  519. <article id="training" typeof="schema:BlogPosting">
  520. <h2 property="schema:name"><a href="#training" title="Link to that content" property="schema:url">Training</a></h2>
  521. <div property="schema:articleBody"><p><strong>When you are a geek and you discover a system as complex as your own body, you’re highly tempted to experiment</strong> with its capabilities, to push it to its limits, to see how it reacts to new solicitations. It opens an incredible new field with endless possibilities. A few months ago, I talked about <a href="#exercising">exercising</a> and I’m still considering that:</p>
  522. <blockquote>
  523. <p>Besides all that, <em>it’s all about feeling good</em>.</p>
  524. </blockquote>
  525. <p><em>but</em>, is it possible to feel good for a longer period? Definitely, but it requires training. Daily training, hard training, cross-training and more important: <strong>happy training</strong>. I set no goals, I know it will take time and I’m ready for this, the only requirement is that it still provides me fun, <a href="#healthy">crossing new animals</a> and landscapes, meeting new people.</p>
  526. <p>I started my own "program" 2 weeks ago and the results are quite good for now, I’m no longer feeling tired after the first 10 km of running <a href="#barefoot">barefoot</a> and I can even run a semi-marathon without being totally exhausted, a thing that seemed just impossible 2 years ago! As a counterpart, I started suffering from my knee, a sign that I trained <em>"Too Soon, Too Fast"</em> without enough recovery. Like a n00b :-).</p>
  527. <p>Today I bought a watch with heart rate monitoring capability, because <a href="">"the only unit of time that matters is heartbeats"</a> as said Paul Ford and I want to measure more precisely some reactions of my body, as an introverted <a href="">datasexual</a>. <strong>This is a turning point.</strong></p></div>
  528. <footer class="post-date">—
  529. <span property="schema:datePublished">Spring 2012</span>,
  530. <span property="schema:contentLocation">Tokyo</span>
  531. </footer>
  532. </article>
  533. <article id="switching" typeof="schema:BlogPosting">
  534. <h2 property="schema:name"><a href="#switching" title="Link to that content" property="schema:url">Switching</a></h2>
  535. <div property="schema:articleBody"><p>I changed my Nikon D3 for a Fuji X-Pro 1 three months ago and took a lot of photographs since then. Be ready for the only review without any picture ;-).</p>
  536. <ul>
  537. <li><strong>Mobility</strong>: I reduced the weight of my bag by 3 or 4. I’m not anymore reluctant to take my camera for the whole day and obviously <em>I take more photographs with a camera</em> so it’s a clear win. I can even bring it for my trails, yay!</li>
  538. <li><strong>Incognito</strong>: the first thing you realize is how silent it is when you take a photo, for instance I was able to take people in a museum without being spotted. You’re not anymore considered as a pro, just a random tourist taking pics and it changes a lot the way you can hunt and shoot people.</li>
  539. <li><strong>Quality</strong>: of the object in itself first, it’s clearly less durable than a DSLR and I’m now afraid of rain etc. Of the produced images, you can see the difference on a big screen when you know where to look at but this is way sharper than I expected even at the highest apertures and colors render better than the X100. The difference with a DSLR is hardly noticeable except for photogeeks.</li>
  540. <li><strong>Autonomy</strong>: I had to buy a second battery because I wasn’t able to finish the day with a single one… without taking any video, it really sucks. I’m trying to verify if the first one is deficient because that’s just not acceptable.</li>
  541. <li><strong>Performances</strong>: the autofocus is incredibly slow, I hope a firmware update will at least ease the verification of the focus as with the X100’s. <strong>Edit</strong>: that’s the case. It’s hard to discuss on exposition and tonality for now given that Aperture doesn’t handle RAWs from this camera yet (I don’t know which one of Fuji or Apple is responsible for this but that’s a shame!).</li>
  542. <li><strong>Liveview</strong>: I discovered how powerful it can be to do not have to put your eye on your visor for upper-crowd shots or very low point of views (I still lay down on the ground sometimes to remember good ol’ times). Bonus: reduces the wrinkle of the photographer :p</li>
  543. <li><strong>Happiness</strong>: probably the more important point, that switch brought me back the fun of taking photographs, I shot more those last months than the previous year. This is not about the quantity of course but more how inspiriting it can be to embrace new constraints. Moreover, I got rid of a bunch of photography stuff in the process, one more step on the <a href="#dequiring">minimalism</a> journey.</li>
  544. </ul>
  545. <p>To sum up, the switch is above my expectations and I’m quite happy. I’ve "lost" a lot of money in the process but it was definitely worth it. <strong>Next steps: printing and offering.</strong></p></div>
  546. <footer class="post-date">—
  547. <span property="schema:datePublished">Spring 2012</span>,
  548. <span property="schema:contentLocation">Tokyo</span>
  549. </footer>
  550. </article>
  551. <article id="japan" typeof="schema:BlogPosting">
  552. <h2 property="schema:name"><a href="#japan" title="Link to that content" property="schema:url">Japan</a></h2>
  553. <div property="schema:articleBody"><p>I’d always been reluctant to write about Japan, waiting to better understand this country, better understand these people. It never happened :-). Next month, I’ll come back to France once and for all (well, at least for a couple of years? months?). The decision was tough but it’s a good timing to make a stocktaking about the last 9 months in this country.</p>
  554. <p>Has Japan changed me? <em>Of course it <strong>does</strong> have.</em> Now is it relative to the travel or to Japan itself? Good question. I think I can try to separate the two, with things that changed in my life:</p>
  555. <ul>
  556. <li><strong>I do a lot more sport</strong>: the first six months I gain some weight in Japan even if there are less sugar and salt in food so the Japanese diet is probably not that ideal (at least when you continue to eat like a European), I lost 2 kg since I train harder and reduce my rice consumption. The lack of socialization probably influenced my switch from <a href="#exercising">exercising</a> to <a href="#training">training</a> but I have some fun playing with my heart now so I’m not sure which one is an excuse for the other ;</li>
  557. <li><strong>I own less things</strong>: living in 24 square meters probably helped but that change started before I left France while selecting stuff I decided to keep for that year and after, that’s more a personal reflexion about consumption and economy craziness. Living in the largest supermarket of the world (Shinjuku, Tokyo) probably speed up the process though ;</li>
  558. <li><strong>I care even more about environment</strong>: here again, maybe Japan influenced me with the waste of energy I can experiment daily or being conscious of what happened in Fukushima but that’s more part of my return <em>into the wild</em> thing while trailing and hiking.</li>
  559. </ul>
  560. <p>And things that changed because of/thanks to Japan (and I’ll miss, hardly):</p>
  561. <ul>
  562. <li><strong>I care more about people</strong>: by mimicking, obviously. I learned how rewarding it can be to be part of an ecosystem. This is not anymore about self-esteem but respect of others and at the end of the day it’s extremely relaxing ;</li>
  563. <li><strong>I realized you can live in a world without aggressiveness and fear</strong>: and in the meantime how aggressive is the French way to communicate, I’m done with that debate excuse to be arrogant and I’m sure this energy can be reused positively, calmly ;</li>
  564. <li><strong>I rediscovered how happiness is communicative</strong>: daily seeing a lot of people laughing, being amazed, smiling creates an indescribable atmosphere of positivity and safeness. That’s what I will probably miss the most.</li>
  565. </ul>
  566. <p>Coming back to France with such observations is hard because I know these are deeply entangled cultural values and you can’t change that within a lifetime. And <em>you can’t judge a culture either</em>, that’s something I learned during that year. There is often a good reason for that and when there is none that’s part of the singularity of this culture, what makes it unique and somehow desirable.</p>
  567. <p>That being said, how to combine all this in my "future life"? I’ll try to bring some of my learnings to France to see how it can fit, at least locally. I don’t consider this as a come back but more as a pursuit of the journey, in a place I (used to) know, with people I care about, with updated values, with upgraded me :D. <strong>I don’t regret any minute I spent in Japan and counting.</strong> I know I’ll come back, at least for that little place of paradise I found. One day…</p>
  568. <p>ありがとうございます気をつけて。</p></div>
  569. <footer class="post-date">—
  570. <span property="schema:datePublished">Summer 2012</span>,
  571. <span property="schema:contentLocation">Tokyo</span>
  572. </footer>
  573. </article>
  574. <article id="jobless" typeof="schema:BlogPosting">
  575. <h2 property="schema:name"><a href="#jobless" title="Link to that content" property="schema:url">Jobless</a></h2>
  576. <div property="schema:articleBody"><p>I spent the last year to build interfaces both for users and developers on top of a document-oriented database with a built-in search engine. I learned a lot of things, a few amongst others:</p>
  577. <ul>
  578. <li>developing an API and its Python client counterpart using the <a href="">HAL+JSON specification</a> to link resources in a truly RESTful way ;</li>
  579. <li>reducing the complexity of a dynamically generated search interface, not enough for my taste but already a huge step forward ;</li>
  580. <li>turning my relational background to a document way of thinking and its multi-valued fields ;</li>
  581. <li>automating continuous deployment against Amazon Web Services and Doing Things Right™ considering cache, rollback and so on.</li>
  582. </ul>
  583. <p>Unfortunately I ended up disagreeing with the founder on the vision of the product — which has an incredible potential by the way — that demotivated me and I quit last week.</p>
  584. <p>Now there are a few options I’ll consider within the upcoming months:</p>
  585. <ul>
  586. <li>taking the lead of a technical team, that means moving to a bigger city than I plan to (Arles) and I think I’m not ready for that. Note that I’m not sure there is a need for a team leader in a technical context and that’s why I prefer the <em>"Web Architect"</em> title when I refer to my job/skills ;</li>
  587. <li>starting my own product, after so many fail stories I’d been taken part of I optimistically (and wrongly :p) think that I can avoid common pitfalls (shipping early, reducing complexity, considering marketing seriously, making profits and so on). A few problems are currently <em>scratching my own itch</em> but I need more brainstorming ;</li>
  588. <li>collaborating with other people, I already did that with <a href="">Makina-Corpus</a> and it went extremely well (kudos to <a href="">Lauréline</a>, <a href="">Matthieu</a> and <a href="">Benoît</a>!), maybe it’s time to go a bit further and consider the association of talented people in a small dream team. Utopia? A few companies around the Web prove me not :) ;</li>
  589. <li>pursuing my freelance activity as I did before moving to Japan, the <em>easy and obvious</em> solution but I remember all the drawbacks of that approach: lack of technical skills update (too risky to sell something you’re not proficient at), lack of team emulation (celebrating daily victories is so important for long-term welfare), lack of challenges (you’re somehow constricted to basic projects given your manpower) to name a few.</li>
  590. </ul>
  591. <p>That being said, <strong>I’m open to all propositions.</strong></p></div>
  592. <footer class="post-date">—
  593. <span property="schema:datePublished">Summer 2012</span>,
  594. <span property="schema:contentLocation">Tokyo</span>
  595. </footer>
  596. </article>
  597. <article id="fujisan" typeof="schema:BlogPosting">
  598. <h2 property="schema:name"><a href="#fujisan" title="Link to that content" property="schema:url">Fujisan</a></h2>
  599. <div property="schema:articleBody"><p>A few things I learned during our attempt to reach the top of Mt. Fuji last night:</p>
  600. <ul>
  601. <li><strong>Humility</strong>: We made two (costly!) decisions that probably saved our lives, I’m a bit dramatic here but when something is going wrong at that altitude it can be dramatic. First, we switched from a 2300 meters trail to a 1200 meters one (ascent) which allowed us to do not spend the whole night hiking. Second, we reserved a hut at approximatively mid-distance to the summit to take some rest before reaching the top for the sunrise at 4 a.m. (initial plan). The Fuji’s staff made an awesome work informing us from dangers related to climbing that particular night, I’m against over-protection concerning mountain but in this case that was perfectly appropriated.</li>
  602. <li><strong>Patience</strong>. When we woke up at 1 a.m. the storm and the wind were so strong that we didn’t even open the door, the hut keeper said "Very bad, do not go" and advices from local people are pure gold. We made a second try 2 hours later when the storm stopped to realize that we were now in the cloud and the wind was still incredibly violent, enough to hardly stand up. Finally at 5 a.m. the hut crew woke up everyone to say that it was not possible to reach the summit that day. When we took the bus to return to the station, uprooted trees and destroyed roads made us realized how unusual was that storm.</li>
  603. <li><strong>Renouncement</strong>. Even if that date was highly symbolic to us, sometimes you must admit that you can’t fight the mountain, whatever your training, and just give up… until the next attempt ;-).</li>
  604. </ul>
  605. <blockquote>
  606. <p>Ô wise Fujisan, will you let us reach your top next time?</p>
  607. </blockquote>
  608. <p><strong>[Edit]</strong> : 3 days later, we did it in perfect conditions. Thanks!</p></div>
  609. <footer class="post-date">—
  610. <span property="schema:datePublished">Summer 2012</span>,
  611. <span property="schema:contentLocation">Tokyo</span>
  612. </footer>
  613. </article>
  614. <article id="stillness" typeof="schema:BlogPosting">
  615. <h2 property="schema:name"><a href="#stillness" title="Link to that content" property="schema:url">Stillness in motion</a></h2>
  616. <div property="schema:articleBody"><p>I had the chance to experience that state 3 times in my life for now, that’s the hardly descriptive feeling of being in movement (by yourself) without feeling it, better explained by this Taoist text:</p>
  617. <blockquote>
  618. <p>The stillness in stillness is not true stillness; only when there is stillness in movement does the universal rhythm manifest</p>
  619. </blockquote>
  620. <p><strong>The first time was at the finish sprint of my first and almost last race ever, 15 years ago.</strong> I was playing basketball at that time and we challenged ourselves with a good friend to run that 5 kilometers race without any specific training (for the story, we did the 10 kilometers the year after and it was a bit too much). It was still fun because the distance is easy if you’re doing some sport but painful enough to reach that <em>I’m-so-happy-to-end-this</em> state. And then a few meters from the finish line I sprinted and that was like flying, my vision focused on the finish gate, yells from the crowd were like marshmallows and that weird taste of iron come to my mouth but I only realized all that when I stopped trying to analyze what just happened. During that minute, probably less, I was just in another dimension, feeling the indescribable joy of being alive.</p>
  621. <p><strong>The second time was a couple of years ago while snowboarding in the Alps</strong>. There was a descent full of fresh snow between two lifts and I did it about 20 times with a lot of pleasure. But then, with no particular new element in the context, maybe fatigue, maybe anaerobic or hypoglycemia, anyway that particular ride was like surfing on top of a moving wave, my body was moving but my brain was elsewhere, both plainly conscious of the situation and somewhere on top of me (yes it’s close to <a href="">Near Death Experience</a> somehow), both having a lot of fun.</p>
  622. <p><strong>The third one was this spring during <em>Hanami</em>.</strong> I decided to go running just for a few kilometers from <em>Shinjuku</em> (via <em>Yotsuya</em>) to <em>Iidabashi</em> on the top of the canal because I knew there will be cherry blossoms at that place. The view was incredible and the joy of japanese people is so communicative during that period that you can’t feel bored. And then close to the end, a very soft wind made all petals falling from trees like snow and that instant was once again magic. Everybody looks up with a large smile (and some usual japanese interjections), I continued running going through that waterfall, almost literally diving into flowers. Time stopped and a child laugh brought me back to life.</p>
  623. <p>Lately, I discovered during <a href="#fujisan">Fujisan</a>’s descent that you can share that kind of orgasmic state with <a href="">somebody else</a>. <strong>Maybe the end of my sportive singleness :-).</strong></p></div>
  624. <footer class="post-date">—
  625. <span property="schema:datePublished">Summer 2012</span>,
  626. <span property="schema:contentLocation">Plane</span>
  627. </footer>
  628. </article>
  629. <article id="delegating" typeof="schema:BlogPosting">
  630. <h2 property="schema:name"><a href="#delegating" title="Link to that content" property="schema:url">Delegating</a></h2>
  631. <div property="schema:articleBody"><p>I used to think that <strong>religion is for weak people, people who prefers to delegate</strong> comfortably their thoughts and sometimes manpower to one central authority.</p>
  632. <p>It hits me lately that politic follows the exact same pattern, annihilating any self-consciousness and thus self-esteem. Electing a president at the head of a nation creates the feeling that you did your job as a citizen for the next X years but being a citizen is not a one-shot, it’s a daily challenge to find your place in the society not as a consumer but as an actor. Our societies are relying on one person with his government to drive our countries for a few years without any long-term vision, a scapegoat for our lack of thinking, our lack of acting, our lack of humanity. Where is your dignity when you can’t even think and act by yourself?</p>
  633. <p>In 1721, Montesquieu published his Persian letters and the 14th is very important to me, <a href="">here is an extract</a> (<a href="">in French</a>) but I recommend the whole reading:</p>
  634. <blockquote>
  635. <p>O Troglodites, what moves you to this; uprightness becomes a burden to you. In your present condition, having no head, you are constrained in your own despite to be virtuous; otherwise your very existence would be at stake, and you would relapse into the wretched state of your ancestors. But this seems to you too heavy a yoke; you would rather become the subjects of a king, and submit to laws of his framing-laws less exacting than your present customs. You know that then you would be able to satisfy your ambition, and while away the time in slothful luxury; and that, provided you avoided the graver crimes, there would be no necessity for virtue.</p>
  636. </blockquote>
  637. <p>Such an idealist! Nobody can live and work in this context today. Virtue, really? Almost a hundred of geeks at Github are proving that it’s possible, see that blog post from <a href="">Ryan Tomayko</a>:</p>
  638. <blockquote>
  639. <p>Telling people what to do is lazy. Instead, try to convince them with argument. This is how humans interact when there’s no artificial authority structure and it works great. If you can’t convince people through argument then maybe you shouldn’t be doing it. […] Essentially, I try to create little mini-managers, each responsible for managing a single person: their self.</p>
  640. </blockquote>
  641. <p>Confirmed by <a href="">Brandon Keepers</a>, working there for 6 months:</p>
  642. <blockquote>
  643. <p>Anarchy works wonderfully in a small group of individuals with a high level of trust. Everyone at GitHub has full access and permission to do whatever they want. Do great things and you earn respect. Abuse that freedom and you violate everyone’s trust.</p>
  644. </blockquote>
  645. <p>Marriage is another way of delegation, behind the love story that’s a way to state administratively (and sometimes religiously) that you’re forming a couple. Validating your love by a piece of sheet and a ring instead of daily attention, it surely deserves a huge celebration in our attention-deficient world.</p>
  646. <p><em>That’s why I’m agnostic. That’s why I’m a blank voter. That’s why I’m running my own company. That’s why I’m not married.</em></p>
  647. <p>The worst part is that by delegating, you can loose your knowledge too. Think about it in our geeky world of <a href="">Clouds</a>, <a href="">Proxys</a>, <a href="">Frameworks</a>, each introducing more and more opaque <a href="#layers">layers</a>.</p>
  648. <p><strong>We are Tailorizing the Web and soon nobody will be able anymore to put a service online without heavily relying on an uncontrolled — delegated — stack.</strong></p></div>
  649. <footer class="post-date">—
  650. <span property="schema:datePublished">Summer 2012</span>,
  651. <span property="schema:contentLocation">Arles</span>
  652. </footer>
  653. </article>
  654. <article id="broken" typeof="schema:BlogPosting">
  655. <h2 property="schema:name"><a href="#broken" title="Link to that content" property="schema:url">Broken</a></h2>
  656. <div property="schema:articleBody"><p>From 0 to 5, you’re encouraged to talk.<br />
  657. Above 5, you’re encouraged to shut up.<br />
  658. From 5 to 10, you’re encouraged to be independent.<br />
  659. Above 10, you’re encouraged to be addicted.<br />
  660. From 10 to 15, you’re encouraged to criticize.<br />
  661. Above 15, you’re encouraged to follow.<br />
  662. From 15 to 20, you’re encouraged to know.<br />
  663. Above 20, you’re encouraged to delegate.<br />
  664. From 20 to 25, you’re encouraged to be.<br />
  665. Above 25, you’re encouraged to have.<br />
  666. From 25 to 30, you’re encouraged to procreate.<br />
  667. Above 30, you’re encouraged to reproduce that loop.</p>
  668. <p><strong>This system is broken.</strong></p></div>
  669. <footer class="post-date">—
  670. <span property="schema:datePublished">Summer 2012</span>,
  671. <span property="schema:contentLocation">Arles</span>
  672. </footer>
  673. </article>
  674. <article id="cooperating" typeof="schema:BlogPosting">
  675. <h2 property="schema:name"><a href="#cooperating" title="Link to that content" property="schema:url">Cooperating</a></h2>
  676. <div property="schema:articleBody"><p>Some companies are inspirational: <a href="">37signals</a>, <a href="">LincolnLoop</a> or <a href="">Github</a> for instance. They pursue their vision, propagate their values through their culture, share their ideas. They can achieve this thanks to their <em>cooperation</em>, both internally and with their clients, considered as collaborators, as peers.</p>
  677. <p>Coming back from Japan, I knew that I’d like to <a href="#jobless">change my professional environment</a>, being solo was a really good experience (may I say experiment?) but it’s hard to do that for many years. Not socially (at least for me) but more in terms of <strong>knowledge</strong> (How do you progress when you’re in a comfortable situation? Can you take the risk to use a new technology for a client ?) and even more important in terms of <strong>values</strong> (it’s very hard to debate with yourself wether a client has crossed the ethical line or to arbitrate objectively a sticky situation).</p>
  678. <p>A few months ago, <a href="">Nicolas</a> contacted me with a project he shared with <a href="">Stéphane</a> and <a href="">Vincent</a> to create a framework to work together. Not a technical one, <strong>a legal and ethical framework</strong>. Creating a company based on values and principles, on cooperation and participation. <em><a href="">A company encouraging humanity before profit</a></em>. This proposition intimately resonated with the way I wanted to evolve, both as a professional and as a citizen. <em>I accepted the challenge.</em></p>
  679. <p>So far, I learned a ton of things. From administrative knowledge to humanist discussions, this is even more interesting than what I dreamed of. And this is just the beginning, it takes a lot of time to set up the foundations but it’s an incredibly valuable time to discuss our ideas and <strong>to feel confident in our shared vision</strong>. More on that later.</p></div>
  680. <footer class="post-date">—
  681. <span property="schema:datePublished">Summer 2012</span>,
  682. <span property="schema:contentLocation">Arles</span>
  683. </footer>
  684. </article>
  685. <article id="unplugged" typeof="schema:BlogPosting">
  686. <h2 property="schema:name"><a href="#unplugged" title="Link to that content" property="schema:url">Unplugged</a></h2>
  687. <div property="schema:articleBody"><p>I experienced an unusual situation in our rich countries last month: not having any electricity for a whole week due to my move from Japan and my switch to a non-nuclear electricity provider: <a href="">Enercoop</a>. During this period, completely scheduled on daylight which is in itself an interesting experiment, I discovered a few things.</p>
  688. <p>The first thing you realize in an unplugged home is the silence. All our technology produces a background noise that you don’t notice daily but only when it stops. In this situation, all other noises are amplified: a wooden beam cracking, an insect flying, yourself breathing. <em>Natural noises of the townsman.</em> <strong>You rediscover an inner world</strong>.</p>
  689. <p>Then you start to listen to your environment: the street, your neighbors, shops, tourists. Each one have their schedule and their habits. You consume electricity by procuration, listening accidentally your neighbors’ radio, TV or parties. <em>Social noises of the celibate.</em> <strong>You rediscover an outer world</strong>.</p>
  690. <p>Finally, you’re alone with your noisy ideas and you start to think, to read, to write, to do things, to care about people. After a few days, only when all batteries are empties, you’re able to proceed to an introspection, to question yourself about your place in this world. <em>Brain noises of the human.</em> <strong>You rediscover yourself</strong>.</p></div>
  691. <footer class="post-date">—
  692. <span property="schema:datePublished">Summer 2012</span>,
  693. <span property="schema:contentLocation">Arles</span>
  694. </footer>
  695. </article>
  696. <article id="sleeping" typeof="schema:BlogPosting">
  697. <h2 property="schema:name"><a href="#sleeping" title="Link to that content" property="schema:url">Sleeping</a></h2>
  698. <div property="schema:articleBody"><p>I bought an <strong>electric bed</strong> for my new home, the kind of bed you can find in hospitals with an engine to raise the head or your legs. That’s pretty expensive but the end-result is way above my expectations.</p>
  699. <p>Being in Japan, I realized that futons were definitely not adapted to my body, especially the curving of my back so I started to experiment different positions adding books under my legs, my knees, my head and <strong>I found a pattern similar to what you have in a hammock or a cocoon</strong> but with knees a bit upper to do not stretch your muscles. This way I was able to lay on my back without any pain.</p>
  700. <p>Back in France, I found the bed of my dreams, well… literally, for two people with two mattresses which is very important because we end up not using the same level of elevation. We’re using it for a month now and she changed her mind from <em>"Yet another useless geeky gadget"</em> to <em>"This is the best thing you bought EVER! &lt;3"</em>. My best reward :-)</p>
  701. <p>When you put in perspective the time you spend in a bed plus the pain you suffer for a few hours after being out of your bed, <strong>you don’t ever look (at your) back</strong>. <em>Bonus</em>: in recovery mode or for a little nap, having your legs above your body is very comfortable. <em>Bonus 2</em>: I spend way more time reading from my bed given the suitable position I can have.</p></div>
  702. <footer class="post-date">—
  703. <span property="schema:datePublished">Autumn 2012</span>,
  704. <span property="schema:contentLocation">Arles</span>
  705. </footer>
  706. </article>
  707. <article id="sharing" typeof="schema:BlogPosting">
  708. <h2 property="schema:name"><a href="#sharing" title="Link to that content" property="schema:url">Sharing</a></h2>
  709. <div property="schema:articleBody"><p>My only career management engine — and thus advice — is <strong>to share</strong>. I thought about it after reading <a href="">Mathieu’s article</a> on that topic (in French), it’s not really a planning involving ladders but the end result is far more rewarding. Why is that so powerful?</p>
  710. <ul>
  711. <li><em>By sharing you meet new people.</em> You have to find people to share your knowledge with, from going to conferences to taking the responsibility to train someone, it will definitely boost your career.</li>
  712. <li><em>By sharing you learn new things.</em> You have to dig into something to be able to share it, you have to be curious, you have to find new people, new ways of thinking. You’ll be more confident and proficient.</li>
  713. <li><em>By sharing you know when to quit.</em> The moment you stop being able to share at work should ring like an alarm bell. Hey wake up, your brain cells are doing boring &amp; repetitive stuff!</li>
  714. <li><em>By sharing you become valuable.</em> Both for your team and your company, your value is related to the way you explore, you synthesize, you create links between people and knowledge.</li>
  715. <li><em>By sharing you become humble.</em> You realize that you just know a very small part of the vast knowledge ocean and that your experience has to be confronted with others’.</li>
  716. </ul>
  717. <p><strong>Your value is proportional to the number of times you shared your knowledge, your experience, your ideas with others.</strong> This advice will make you richer every day, not only in money :-).</p></div>
  718. <footer class="post-date">—
  719. <span property="schema:datePublished">Autumn 2012</span>,
  720. <span property="schema:contentLocation">Arles</span>
  721. </footer>
  722. </article>
  723. <article id="opendata" typeof="schema:BlogPosting">
  724. <h2 property="schema:name"><a href="#opendata" title="Link to that content" property="schema:url">OpenData</a></h2>
  725. <div property="schema:articleBody"><p>I was at the <a href="">OpenDataHACK PACA</a> this last weekend and I ended up being quite disappointed and frustrated. <strong>Disappointed</strong> because I thought that a hackathon is about just having fun together and that event looks closer to a startup weekend with a final jury and questions about business models. <strong>Frustrated</strong> because after a few months without coding actively I was very motivated and most of the projects presented didn’t provide any line of code or even use OpenData (from PACA) <em>for real</em>.</p>
  726. <p>In hindsight, I discovered the discomfort I have with OpenData (at least in France): <strong>it’s hard to have fun for a developer</strong>.</p>
  727. <ul>
  728. <li><em>the nature of data</em> is very limited and you can’t do anything but a service about transportation or tourism.</li>
  729. <li><em>the quality of data</em> is so bad that you lost a lot of energy just being able to use it programmatically.</li>
  730. <li><em>the freshness of data</em> is incredibly inconsistent and can’t be predicted.</li>
  731. </ul>
  732. <p>That being said, here are some ideas for data providers:</p>
  733. <ul>
  734. <li><em>we reached the limits of public data, it’s time for companies to expose some of their private data</em> in order to make pertinent and various services, don’t forget the first-mover advantage here! (by private I mean internal, not data related to privacy of course).</li>
  735. <li><em>we need to work on the way providers open their data</em>, releasing files — whatever the format — is not an option anymore, developers used to work with APIs for a good reason. Take care of your data, that’s your responsibility.</li>
  736. <li><em>we invest time with your data, give us guarantees</em>, document your data, give informations about the releases’ frequency, future released data, interoperability with others’ data and so on.</li>
  737. </ul>
  738. <p>As a citizen, I want to be involved in the life of my city/county but <strong>I’ll need some help from your side, providers</strong>.</p></div>
  739. <footer class="post-date">—
  740. <span property="schema:datePublished">Autumn 2012</span>,
  741. <span property="schema:contentLocation">Arles</span>
  742. </footer>
  743. </article>
  744. <article id="democracy" typeof="schema:BlogPosting">
  745. <h2 property="schema:name"><a href="#democracy" title="Link to that content" property="schema:url">Democracy</a></h2>
  746. <div property="schema:articleBody"><p>Lift 2012 in Marseilles was a blast. The first afternoon was dedicated to conferences (more intimate than previous editions) about a lot of interesting topics, from <a href="">Biology 2.0</a> by Thomas Landrain to Gudrun Pétursdóttir, chairman of the Icelandic Constitutional Council, talking about the democratic process in Iceland after 2008’s crisis. But the most interesting part was the second day, a whole day of workshops entitled <em>"DIGITAL DISRUPTIONS" COLLECTIVE FORESIGHT</em>. You first have to choose one of the 20 "promises" explained as some kind of scenarios about a given topic. I picked the one dedicated to <strong>democracy: restored, enhanced, extended</strong> and I’ll try to sum up some of the insight in this session (there were about 10 people).</p>
  747. <p>First things first, when you talk about democracy you have to consider that not everybody wants to actively participate in it, it’s very frustrating but it’s interesting to analyze causes:</p>
  748. <ul>
  749. <li><em>lazyness</em>: it’s much more comfortable to let others do the hard work even if it’s not possible on the long term if you consider democracy as a daily implication ;</li>
  750. <li><em>hopeless</em>: one thinks that democracy is just a mirage that can’t be reached, they consider that we are not in a democracy ;</li>
  751. <li><em>disagreement</em>: I don’t think that democracy can scale (even using MongoDB :p) to the size of a country or even a city — or Humanity is just not ready for that — at best it should be possible in a community or a tribe. The only alternative I see (and we get back to small groups) is <a href="">Sociocracy</a> but I need to experiment that system of governance for real.</li>
  752. </ul>
  753. <p>The first part of the day was dedicated to past and present initiatives and we all felt a bit desperate after that observation. One of the conclusions is that the digital world, even if we can cite a few marginal examples, didn’t enhance nor extend democracy. But, it provides <strong>a new hope: the one to be technically able to reinvent the democracy</strong>. The Web gives people a way to educate themselves about citizenship and to somehow magnify their messages, to express their diversity. On the other side, it can be instrumentalized and didn’t invert any hierarchical relation.</p>
  754. <p>The afternoon were hopefully more encouraging, we talked about the future of democracy and even if it was hard to keep focused a whole day with intense discussions we ended up proposing some <strong>key actions to change for the better</strong>. Unfortunately I didn’t took the time to write notes down because of the rush but I’m impatiently waiting for <a href="">Hubert Guillaud</a>’s article on that topic given that he kept the poster :-).</p>
  755. <p><em>Note : I’m more and more frustrated about the lack of discussions about those unidirectional thoughts but I don’t want a clasic centralized commenting system, maybe I’ll finally code that DCVS fork/enrich/propose way of interacting…</em></p></div>
  756. <footer class="post-date">—
  757. <span property="schema:datePublished">Autumn 2012</span>,
  758. <span property="schema:contentLocation">Arles</span>
  759. </footer>
  760. </article>
  761. <article id="television" typeof="schema:BlogPosting">
  762. <h2 property="schema:name"><a href="#television" title="Link to that content" property="schema:url">Television</a></h2>
  763. <div property="schema:articleBody"><blockquote>
  764. <p>rules the nation. — <em>Daft Punk</em></p>
  765. </blockquote>
  766. <p>I had a television in my house for about a quarter of my life (7-9, 23-27) and thus I lost a bunch of so-called "TV references". What I gained instead is a capacity to focus on ads’ analysis, to choose wisely my programs, to be conscious of the time lost watching TV. Retrospectively, I’m not sure it was worth it given the popularity of childish 80s’ events though :p.</p>
  767. <p>Back from Japan, we decided to do not have a TV anymore. Since then, a few things changed in my life:</p>
  768. <ul>
  769. <li>I definitely sleep more (combined with sport) ;</li>
  770. <li>I read more, from magazine to books ;</li>
  771. <li>I almost cut myself from news and it’s quite relaxing, I realized how useless it is to care about extra-local things ;</li>
  772. <li>I’m listening to more music ;</li>
  773. <li>I choose what I decide to watch (TV series, documentaries, movies) ;</li>
  774. <li>I shocked people with a living-room not centered on TV.</li>
  775. </ul>
  776. <p><em>Things to improve now: more games, more love, more cooking.</em> <strong>Less screens.</strong></p></div>
  777. <footer class="post-date">—
  778. <span property="schema:datePublished">Autumn 2012</span>,
  779. <span property="schema:contentLocation">Train</span>
  780. </footer>
  781. </article>
  782. <article id="goodies" typeof="schema:BlogPosting">
  783. <h2 property="schema:name"><a href="#goodies" title="Link to that content" property="schema:url">Goodies</a></h2>
  784. <div property="schema:articleBody"><p>I refused the goodies’ bag at the last conference I attended (<a href="">ParisWeb</a>). The staff, always very careful about their attendees, asked me politely why I declined that "gift", here are some reasons in no particular order:</p>
  785. <ul>
  786. <li>I presume that most of the bags (and their content) were trashed within 2 days after the conference, ecologically that’s just crazy.</li>
  787. <li>Half of the bag used to be full of crappy goodies to promote brands I don’t care about (or worse).</li>
  788. <li>Most of the content is not adapted to me: I got an smartphone to read the program, the t-shirt is too large, I already have a pen and so on.</li>
  789. <li>I went to that conference without any bag and I’d like to keep that freedom during the whole event.</li>
  790. </ul>
  791. <p>I know how important it is for sponsors to distribute their goodies (and thus make the event viable) but I’m sure there is a way to let the attendee have that choice. That being said, maybe <strong>there is a better way for sponsors to promote their brand</strong>:</p>
  792. <ul>
  793. <li>Provide high quality goodies without an ostentatious logo, something that people will actually use (I still wear a beautiful t-shirt from DjangoConEu Berlin and I do appreciate the notebook offered to orators by ParisWeb last year for instance).</li>
  794. <li>Send people from your company to attend the conference or even participate (avoid product-driven keynotes, please), your employees are the best ambassadors of your brand <em>but</em> they have to be happy in their job to share their passion of course.</li>
  795. <li>Offer something valuable to the conference’s attendees and explicitly ask to be named for that, for instance <em>"This food is provided by FooInc who cares about the health of their actual and future employees"</em>.</li>
  796. <li>Think about ways to ease the integration and socialization of people during the conference, there is a lack of tools for that.</li>
  797. </ul></div>
  798. <footer class="post-date">—
  799. <span property="schema:datePublished">Autumn 2012</span>,
  800. <span property="schema:contentLocation">Arles</span>
  801. </footer>
  802. </article>
  803. <article id="transparency" typeof="schema:BlogPosting">
  804. <h2 property="schema:name"><a href="#transparency" title="Link to that content" property="schema:url">Transparency</a></h2>
  805. <div property="schema:articleBody"><p>We chose the transparency as a core value of <a href="">Scopyleft</a> because we wanted to share our little adventure and it’s incredibly hard.</p>
  806. <p>I used to publish code as an open-source process but when it comes to <a href="">administrative stuff</a> I feel way less confident and feel somehow reticent to publish drafts publicly or to edit values/principles from my side when it impacts 3 other people. I know (well, I hope) that it’s a way to improve myself on those topics like it happened for my code but the transition is quite brutal.</p>
  807. <p>Fortunately, your first messages and contributions are very positive and really encouraging. <strong>Thank you.</strong> The thing is we don’t know any "Open Company" publishing all the process of their creations to be inspired by so we try to do our best to share our <em>road to enlightenment</em> :-).</p></div>
  808. <footer class="post-date">—
  809. <span property="schema:datePublished">Autumn 2012</span>,
  810. <span property="schema:contentLocation">Arles</span>
  811. </footer>
  812. </article>
  813. <article id="endofpage" typeof="schema:BlogPosting">
  814. <h2 property="schema:name"><a href="#endofpage" title="Link to that content" property="schema:url">EndOfPage</a></h2>
  815. <div property="schema:articleBody"><p>I decided to switch from English to French as my blogging language so <strong>this post is the last one in English</strong> for a few reasons:</p>
  816. <ol>
  817. <li>I started to write in English to somehow extend my audience given that I went to Japan and only a very few Japanese people are reading French. <em>I’m pretty sure no Japanese at all ever read that page</em> so I can consider this as a failure, I realized way too late that integration is before all about working together in Japan :-).</li>
  818. <li>It looks like <a href="">Craig Kerstiens</a> is <a href="">the only one</a> reading English-only across my few readers (<em>thank you!</em>), probably because my vocabulary and grammar are so bad or my thoughts far from those of another country. Anyway, trying to think in English was a good experiment but now I need to improve myself via discussion, not unidirectional writing anymore.</li>
  819. <li>This page started to be a bit too large for my taste (even if performances are still not that bad), when I started it I wasn’t sure to write more than 3 posts. Well, there are 42 posts now — <em>Coincidence? I don’t think so</em> — and I’ll switch back to a dedicated page per article (coucou <a href="">Damien</a> !).</li>
  820. <li>I want to be involved locally, from OpenData to (micro)events, and to interact with my French peers. Moreover, I’m trying something new with <a href="">Scopyleft</a> and I’m sure that feedback about that adventure is more valuable for French people too.</li>
  821. </ol>
  822. <p><em>Je vous vois demain !</em></p>
  823. <p><strong>EOP</strong></p></div>
  824. <footer class="post-date">—
  825. <span property="schema:datePublished">Autumn 2012</span>,
  826. <span property="schema:contentLocation">Arles</span>
  827. </footer>
  828. </article>
  829. </section>
  830. {% endblock content %}