<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Julien Dorra on Medium]]></title>
        <description><![CDATA[Stories by Julien Dorra on Medium]]></description>
        <link>https://medium.com/@juliendorra?source=rss-bdfd5ce80297------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*roPbb0rFQ_9JAzjZ.png</url>
            <title>Stories by Julien Dorra on Medium</title>
            <link>https://medium.com/@juliendorra?source=rss-bdfd5ce80297------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 16:55:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@juliendorra/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Lab Surprise: building a game bundle store with 2 cloud functions]]></title>
            <link>https://juliendorra.medium.com/lab-surprise-building-a-game-bundle-store-with-2-cloud-functions-b5086bf038e4?source=rss-bdfd5ce80297------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5086bf038e4</guid>
            <category><![CDATA[vr]]></category>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[cloud-functions]]></category>
            <dc:creator><![CDATA[Julien Dorra]]></dc:creator>
            <pubDate>Mon, 03 May 2021 14:55:05 GMT</pubDate>
            <atom:updated>2021-05-03T19:26:54.057Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi everybody!</p><p>Here’s<a href="http://labsurprise.me/"> Lab Surprise</a>, a game bundle store built with just 2 Google Cloud Functions (and an integrated payment service API!).</p><p>The idea: Get a surprise bundle of 3 VR apps from 19 games (the more you reveal, the lower your discount). 19 choose 3: that’s 969 different bundles, with 4 discounts possible for each bundle 😂</p><p>VR Scout explain it nicely: <a href="https://vrscout.com/news/app-lab-bundle-major-quest-discounts/">https://vrscout.com/news/app-lab-bundle-major-quest-discounts/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DQJC3V4Ehx2zq-yslmWh4g.png" /></figure><h3>What is it?</h3><p>Mid-march, after a first <a href="https://uploadvr.com/waiting-for-app-lab-quest-game-bundle/">successful indie VR bundle with 12 games</a>, the idea of Lab Surprise emerged as an inclusive way of giving our now 14 very different games, in terms of price, gameplay, etc. an equal chance to be seen and bought by all players.</p><p>We couldn’t find any platform or store that would allow us to have the mix and surprise elements we wanted to have (we searched!), so… I build it over the course of a month, testing and iterating with the group 😅</p><p>I set up our own API endpoints with Google Cloud Functions, storing data using Firestore, and using the Paddle API to add a programmatically priced integrated checkout. The web front-end is very simple, basic HTML, CSS and a dash of JavaScript just doing requests to these custom APIs and replacing the elements as needed. I’m old and didn’t do browser work in a long time, so I just went straight to jQuery for DOM manipulation and JSON requests and, well, it works and the jQuery API still feel nice to me…</p><p>Now for the dirty, shameful secret: the first version of the drawing-and-revealing custom backend was actually built with a Google Spreadsheet and an App Script. It worked quite well for the ball of strings and glue it was! Moving to Cloud Functions helped remove<strong><em> a lot</em></strong> of specific code for Sheets, in addition to making requests <strong><em>much faster</em></strong>. Apps Script is actually fun to use and the web editor itself is really nice. Sheets are also a great way to <strong><em>sketch your data structure very quickly</em></strong> and change it as you prototype. There’s even a<a href="https://chrome.google.com/webstore/detail/google-apps-script-github/lfjcgcmkmjjlieihflfhjopckgpelofo"> hack/Chrome extension</a> to version you Apps Script with GitHub. But ultimately, it’s not good enough and it feel too cumbersome compared to Cloud Functions.</p><p>Tip: use Cloud Shell if you are new to Cloud Functions, it allowed me to get going in a minute without installing anything on my local machine.</p><h3>What are the parts that make it work?</h3><p>A key part of the flow is <a href="https://www.linkedin.com/company/2695021/">Paddle</a> and using the Paddle API in a dynamic way. Paddle is the merchant of record and manages the taxes worldwide, which would be a nightmare to manage ourselves 😱.</p><p>We are using the fact that Paddle can split a sale automatically between sellers to immediately route the money to the vendor account of each developer in a given bundle, calculating the split for each bundle. That means that we had to onboard all 19 developers into Paddle in a record time. It was a totally new use case for Paddle, and they were really open and helpful about it.</p><p>Technically, Lab Surprise is made of just 4 parts, all exchanging through web APIs and decoupled:</p><p>- The <strong>web page</strong> itself, the front (it’s not doing a lot really 😂 just updating the graphics and price on the page depending on the bundle and revealed apps)</p><p>- The<strong> drawing-and-revealing </strong>custom backend (one cloud function drawing a random surprise of 3 games, updating the reveal status of the surprise and sending back the price, discount and paylink)</p><p>- The<strong> Paddle service </strong>(Paddle does a lot here: checkout, reporting, tax remittance, emailing the keys we pass them to buyers, even first level support)</p><p>- The <strong>key fulfillment</strong> custom backend (one cloud function checking if keys are available and passing them to Paddle)</p><p>The custom backends are using a few collections and sub-collections in Google Firestore: games, promotions, keys, surprises… The Firestore API is not perfect, but simple and well documented.</p><p>There’s also a couple of other custom back-office functions: one function that handles adding a batch of keys for a given game (with a very simple form for devs to use) and one private function to generate the bundles for a promotion.</p><p>I’m very happy that I didn’t try to go the route of setting up a traditional monolithic web application.</p><p>Cloud functions force you to think in a decoupled way (even if there’s several ways that you can couple them via the data) and at this stage it allows for easier updates and explorations. For example it’s really easy to deploy just a variant of the draw function to test new features.</p><p>There’s also benefits in thinking the API-first way. I’m very senior as a creative and a prototyper, and I started programming when I was maybe 9 or 10, <strong><em>but</em></strong> I’m <strong><em>not</em></strong> a developer by trade. API-first design is helping me greatly in designing my architecture, by focusing on the relationships of the parts.</p><h3>The update puzzle</h3><p>This decoupling can make updates a multi-steps process: at some point after the launch of Lab Surprise, I had to update the way the game IDs were passed by the drawing function first to Paddle paylink API and then on checkout by Paddle to our fulfillment function. To update that message passing without breaking anything and without interruptions, I couldn’t just change both functions to the new message passing, as it could have led to a few buyers getting the message from the old version passed to the new version and then not getting their game keys.</p><p>I had to first make the fulfillment function accept both types of messages, old and new (and now in a more extensible way😅). Then I could create a new version of the drawing function, passing only the new message format, test it against the live, production fulfillment function, and deploy it once everything was tested. I can ultimately go back to the fulfillment function and remove the legacy code.</p><p>If both parts had been consolidated into a single app, I might have been able to update both of them in one go. But in many cases, you are not controlling the pace of updates of some parts of the system anyway, for example is you have a client app that your user download. It was an interesting update lesson, one that fortified my views on decoupled updates: we are going to have similar issues with <a href="https://pecopecogame.com/">our VR game Peco Peco</a>, and additive updates like that might be the way to go more often than not.</p><h3>What’s next?</h3><p>The system behind Lab Surprise is build in such a way that it’s really easy to add new games in Lab Surprise along the way: it was <strong>a major frustration</strong> during the Waiting for App Lab bundle when <strong>we had to say no to developers </strong>who asked to join (because of how the <a href="https://itch.io/docs/creators/bundles">Itch co-op bundle</a> system works), so this time we wanted to be able to say yes!</p><p>We were able to<strong> add 5 more games in the middle of Lab Surprise without issues or interruptions.</strong> We just created a new promotion and switched to it.</p><p>The way we built it, it is also easy to create evolutions: we could include all paid App Lab games if their developers were interested 😃. We could add an official Quest store games for a 2-days period as a special event… We could create a version with 6 games in the surprises, or 20, or just 1.</p><p>In term of business, we have gained some autonomy in terms of experimenting with marketing our apps. And I think this is good for the whole indie VR ecosystem, as it shows that we don’t need to wait for the stores to evolve, <a href="https://skarredghost.com/2021/03/12/app-lab-lessons-numbers-indie/">we can build our own experiments in terms of marketing</a>.</p><h3>OK, but why build a surprise machine instead of a classic bundle store?</h3><p>As a collective of indie developers, it’s really important to showcase the whole lineup of games, not just one or two games, to give players a way to explore and take a chance on games that they might not think of trying.</p><p>As our group grows, we need to find ways to reach out to players that don’t exclude or sideline one developer or the other. We don’t need to replicate what others are doing, we need to find new ways to market and sell our games that reflect our own position in the VR and indie game market.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5086bf038e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Twitter API journey: a glimpse back to the future of Twitter that never was, as laid out in…]]></title>
            <link>https://juliendorra.medium.com/the-twitter-api-journey-a-glimpse-back-to-the-future-of-twitter-that-never-was-as-laid-out-in-bafd1187e565?source=rss-bdfd5ce80297------2</link>
            <guid isPermaLink="false">https://medium.com/p/bafd1187e565</guid>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Julien Dorra]]></dc:creator>
            <pubDate>Fri, 07 Apr 2017 11:38:07 GMT</pubDate>
            <atom:updated>2017-04-07T11:38:07.225Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Twitter API journey: a glimpse back to the future of Twitter that never was, as laid out in 2009.</h3><p>In 2009 I interviewed <a href="https://medium.com/u/207a027138ba">Alex Payne</a>, then Twitter API lead. The interview was <a href="http://streisand.trollab.org/fr.readwriteweb.com/2009/10/21/a-la-une/alex-payne-twitter-api-nous-voulons-tre-bus-des-messages-du-web/index.html">published, in French, on now defunct ReadWriteWeb France</a>. It was never released in its original english version.</p><p>Following the publication of <a href="https://twitter.com/TwitterDev/status/850006245121695744">the new Twitter API roadmap</a>, and apparently much rejoicing from developers, it’s a good time to revisit the future of Twitter that was laid out in the interview. It was a future with the API becoming a central utility of the modern web, and a core value of Twitter itself. But of course we all know that since then, Twitter alienated many of the developers using its API by closing or limiting many uses initially fully allowed.</p><p>I hope the optimism about open web APIs, this optimism that Alex Payne showed back in 2009, can be brought back to the web — many developers and startuppers are now wary of web APIs, having had their code or product killed instantly when an API owner changed its policy without warnings. New optimism toward open web APIs would probably needs stronger, more binding commitments from organizations opening their APIs. A roadmap is a good start.</p><h3>Alex Payne, Twitter API lead: “We want Twitter to be the message bus of the web” [2009]</h3><p>Alex Payne and his team are changing the way you experience the web. They are adding more realtimeness to it.</p><p>(and yes, I’m amongst the pioneers that proudly use realtimeness as a word. There is <a href="http://www.google.com/search?q=realtimeness">only 18200 result on google</a> at the moment [2009], but expect that to increase. [nope.])</p><p>You don’t even have<em> to go</em> to twitter.com for that new realtimeness to reach you. You just have to use <em>something</em> that use the <a href="http://apiwiki.twitter.com/">Twitter API</a>. And today, that could be a plant — or a social platform about stocks.</p><p>The Twitter API team is one of the most effective at changing the web. Imagine: a little group of developers, invisible to everyone but other developers. On top of their invisible work, thousands can build new, realtime applications.</p><p>And thousands did it, are doing it and will continue to do it.</p><p>The Twitter API is the best case scenario in term of an Open Web API: useful, usable and actually used.</p><p>(In fact, I first got the idea to interview Alex because I had a client that needed help in defining its web API strategy. But that was too important to keep it for myself ;-)</p><p>So, let’s get to know Alex’s work a little more.</p><h3><strong>The message bus of the web</strong></h3><p><strong><em>Julien: </em></strong><em>What is the most surprising use of your API, the use that stroke you as “I would have never thought of that!”</em></p><p><strong>Alex: </strong>The most surprising to me has been the work that InSTEDD has done using Twitter as a cheap, pervasive communication mechanism for humanitarian work (<a href="http://instedd.org/twitterbots">http://instedd.org/twitterbots</a>).</p><p>I expected client applications, visualizations, data mining, and so forth, but seeing Twitter and our API used for disaster relief was certainly a pleasant surprise.</p><p><strong>Julien: </strong><em>It’s a very interesting use: Twitter as core infrastructure.</em></p><p><em>What I love here, it’s how it allows them to prototype the emergency communication process. Iterating is so rare when it comes to communication networks, it’s precious! (because we all love prototypes and iterations, needless to say:-)</em></p><p><em>But it’s a lot of responsibility for Twitter. And it seems people are asking more and more on that front (see the #nomaintenance meme that emerged just after the Iranian election — I suppose it won’t be the last time we see it).</em></p><p><em>How do you relate with that responsibility, being part of the team that built the infrastructure to support so many tools?</em></p><p><strong>Alex: </strong>It’s a lot to contend with, but we’re up to the challenge. We know that everything from emergency communication to essential business transactions are happening on Twitter.</p><p>And we’re doing our best to provide a stable, high-performance platform for those messages. We’ve made a considerable investment in our infrastructure, from an operational perspective, a software development perspective, and a talent perspective.</p><p><strong>Julien: </strong><em>How do you relate to this challenges as a person?</em></p><p><em>For example, how do you personnally feel API-wise about the </em><a href="http://www.google.com/search?q=site:twitter.com+no+maintenance"><em>#nomaintenance meme</em></a><em> [after the iranian election] or other signs of twitter becoming perceived as a public service?</em></p><p><strong>Alex: </strong>I think that’s what we want.</p><p>We want Twitter to be the message bus of the web, and I think our users and developers should demand the utmost of our service. We need that pressure to guide us.</p><p><strong>Julien: </strong><em>How do you think one can plan for “surprising uses” of an API ?</em></p><p><strong>Alex: </strong>Just provide as much data, as many methods, as much access as possible.</p><p>Let developers do everything a user can do, and great projects will emerge. Don’t treat your API as a second-class feature; always launch new features with accompanying API methods.</p><h3>The mistake you shouldn’t do</h3><p><strong>Julien: </strong><em>What are the errors you won’t make again, but see others do again and again ! I bring this question from those </em><a href="http://www.slideshare.net/al3x/designing-your-api"><em>older slides</em></a></p><p><strong>Alex: </strong>Versioning, versioning, versioning. I will never again design a web API without versioning from Day 1!</p><p>In this day and age, I also think it’s crazy not to provide OAuth from the get-go if you’re just starting from scratch.</p><p>We didn’t have that option when we started providing our API, but I think some sort of token-based authentication is the way to go.</p><p><strong>Julien: </strong><em>I can imagine no versioning leads to very uncomfortable situations for devs, because you change things and it breaks their apps.</em></p><p><em>How did it became more and more of a roadblock? Does or did it restrain you, the API team?</em></p><p><strong>Alex: </strong>It has became a roadblock as Twitter applications have moved from the web, for which upgrades and quick changes are easy, to phones and even embedded hardware devices, which in some cases can only be updated by re-flashing. The lack of versioning has definitely restrained us from making more drastic changes.</p><p><strong>Julien: </strong><em>But why was it not practicable to just add /1.1/ in the URL, fall back to a frozen version if not stated — and start versioning like that ?</em></p><p><strong>Alex: </strong>We want client authors to be explicit in their code about which version they’re using.</p><h3>About OAuth</h3><p><strong>Julien: </strong><em>As an user, I love OAuth. OAuth is a much better solution than give your login and password to a third party!</em></p><p><em>But the very basic auth process was part of the twitter API success, as it lowered drastically the implementation barrier to build authenticated app or data flows.</em></p><p><em>In retrospect, you were right to go dead easy first, and more secure second.</em></p><p><em>How do you find that balance?</em></p><p><strong>Alex: </strong>I think Basic Auth is certainly easier for developers (and, in some cases, users) to get started with.</p><p>We’re going to try to maintain that low barrier to entry by providing a Basic Auth to OAuth proxy for local development use, and by providing a web-based way to explore Twitter API methods (a test console).</p><p><em>[Note: a good example of this kind of console is the </em><a href="http://soundcloud.com/api/console">SoundCloud test console</a>]</p><h3>The developper community</h3><p><strong>Julien: </strong><em>Was it easy at first to gather feedback of the API users, AKA as the devs ?</em></p><p><strong>Alex: </strong>Yes, definitely. We had a much smaller developer community when I first started spending time on our API, but they were very vocal and active. The foundation of our API grew in response to their needs and preferences.</p><p><strong>Julien: </strong><em>What was the more surprising feedback/demand on the API?</em></p><p><strong>Alex: </strong>As we’ve grown, I’ve been surprised at how much our developer community has grown with us.</p><p>Two years ago, we never would have needed <a href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/98f4c4d13954e8bf">API methods that return huge denormalized lists of user IDs</a>, for example.</p><p>Developers could get by with a little bit of pagination. It’s been surprising and gratifying to see that our developers are “scaling up” with us.</p><h3>A tale of two APIs</h3><p><strong>Julien: </strong><em>The problem of merging two APIs is something you face with the Search API…</em></p><p><em>Planning for consistency, do you just iterate, or do you think there is a right way to integrate the Search API — and even converge with external-but-friend APIs like </em><a href="http://bit.ly/"><em>bit.ly</em></a><em>?</em></p><p><strong>Alex: </strong>I think that by providing consistent, well-documented APIs, we can satisfy everyone. The stronger our conventions, the easier it is to learn your way around our APIs.</p><p>That’s our goal, and we’re engaging our developer community whenever possible to be sure that we’re delivering what people want.</p><p>We’re pretty clear on what we need to do for the Search API. It’s a very powerful API, but thankfully it’s also pretty simple to use.</p><p>Integration, in this case, is mostly about ensuring that the data you get back is the same no matter which API you’re talking to.</p><p>In terms of integrating with external APIs, that’s mostly a matter of pointing people in the right direction. We generally do very little facilitation there; client authors find other APIs that work well with our APIs, and word gets around.</p><h3>We love REST</h3><p><strong>Julien: </strong><em>Was there times when you felt the </em><a href="http://en.wikipedia.org/wiki/Representational_State_Transfer"><em>RESTful</em></a><em> paradigm was a limitation (Over more complex/complete choices like SOAP?) ?</em></p><p><strong>Alex: </strong>No, not really.</p><p>We’ve had the occasional request to provide SOAP or another more heavyweight transport, but most developers seem happy to be working with a RESTful API.</p><p>If anything, our API is only going to get more RESTful as it evolves. We’re not taking full advantage of everything the REST model has to offer, at present.</p><p><strong>Julien: </strong><em>Critics frequently say that many web APIs are not true REST at all (similarly to the web app MVC debate/confusion).</em></p><p><em>Do you feel that the Twitter API is not really RESTful, but that your goal is to tend to a real RESTful implementation? Could you elaborate on that point?</em></p><p><strong>Alex: </strong>I think some methods in the Twitter API are closer to the academic definition of rest (in which resources are exposed as plural nouns which are modified by HTTP method verbs)</p><p>But many of the more recent methods are not.</p><p>Our goal is to normalize our method names around RESTful conventions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bafd1187e565" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The end (of programming) is near!! Or is it?]]></title>
            <link>https://juliendorra.medium.com/-38358562d424?source=rss-bdfd5ce80297------2</link>
            <guid isPermaLink="false">https://medium.com/p/38358562d424</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Julien Dorra]]></dc:creator>
            <pubDate>Fri, 07 Apr 2017 10:18:54 GMT</pubDate>
            <atom:updated>2017-04-07T10:18:54.470Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>We really *don’t want* to program computers using meetings and decks of slides.</h4><p>I categorized a new branch of code-denial.</p><p>When I published <a href="https://medium.com/code-adventures/bff7cd81d699"><em>Why we believe everybody must learn programming</em></a><em>, </em>the article got some very interesting reactions <strong>against teaching code</strong> to kids and adults.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*ed6-YK273R0ne-6bGWw3nw.jpeg" /></figure><p>We all know the argument that goes: <em>“Kids used to grow up just fine without knowing programming, thank you. Drawing and running is great”</em>. It generally comes from people that are fed up with the techno-utopian blind faith in technology (and most probably rightfully so) and mean well for the kids. As our common goal is for kids to grow empowered and happy, once that common ground is established, we actually can have meaningful conversations about creativity, activities and code with this group of code-doubters.</p><p>(Rarely, there’s also purely reactionary opposition: <em>“The good old education was, well, good. Don’t spoil it with those machines.” </em>Not much to say, here, apart that the Good Old Education never was that good for the majority of kids.)</p><p>But there is another, more intriguing argument coming from <em>tech believers</em>. It’s puzzling: <strong>they believe computer scientists are great and computers are mighty, and for that very reason, they posit that kids don’t need to learn computer programming, at all. Uh? How… what?</strong></p><p>So, their rationale is well summarized in these tweets:</p><blockquote>We believe every computer must learn the mother tongue of its users. Now, programs and computers are illiterate, not us!</blockquote><blockquote>Let’s computer spend years learning to write-talk! It’s what research in artificial intelligence try</blockquote><p>That’s not the first time since we launched <a href="http://codinggouter.org/">Coding Goûter</a> that I’ve stumbled upon this paradoxical idea. It is summarized like this: <em>“Artificial Intelligence will get so good that very soon we won’t need to program anything. </em><strong><em>Computers will program themselves! </em></strong><em>And we won’t need to learn those strange computer languages.”</em></p><p>Behind this view lay two common misconceptions about computer languages: first that programming languages are for computers, and second that structuring ideas to make them real is new to computing.</p><p>Let’s see how we can answer to these two misconceptions:</p><h4>1. Programming languages are for humans</h4><p>It’s a misconception that programming languages are the “native languages of computers”. Programming languages are very much human creations.</p><p>Programming languages are as much human as mathematical conventions for writing formulas are, or as geometrical conventions are. They are probably <strong>more</strong> human than some awful, incomprehensible, manually designed visualizations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*9rikdKzYHu62dZMj_zCmbA.png" /><figcaption>Selected for you by the <a href="http://wtfviz.net/post/71050926834/omni-channel">WTFviz Tumblr</a>. Many more failures of human communication over there.</figcaption></figure><p>So why do programmers write programs using programming languages, really?</p><p>A big part of the answer is: for humans to read it. Sometimes this human is the programmer herself, some weeks or months later. Sometimes it’s someone pair-programming with the programmer.</p><p>Programming languages are conventional ways of expressing thoughts, intent and expected results. They are used to articulate human intentions in a structured way.</p><p>They exist in many shapes and forms, to fit many problems. And new programming languages are created every year.</p><p>And this leads us to the fact that humans have created many structured conventions, long before the invention of computers.</p><h4>2. Structured communication predates computers.</h4><p>Other humans understand you perfectly well, and you <strong>still </strong>need to learn and write <strong>*many* </strong>varied forms of conventionally structured documents: invoices, specifications, science papers, answers to call for projects, etc.</p><p>Architects have plans and measurements, accountants have had book-keeping formats for centuries, manufacturers have bills of materials.</p><p>As humans, we are creating all kinds of complex and structured documents for other humans, when simple descriptive text doesn’t seem enough:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*ZfZn17ZoVpcNrYJeqqeiaQ.png" /><figcaption>An example of a diagram intented for other humans to understand.<a href="https://twitter.com/SoBookOnline/status/386990940428455936/photo/1"> Shared on twitter by @SoBookOnline</a></figcaption></figure><p>Notice how even when someone creates a seemingly free-form diagram, he use protocols and conventions. Here, <em>arrows</em> mean that things are connected via a causal relationship. We understand that because arrows are a convention.</p><p>Of course this kind of inter-human communication can turn bad, very quickly, especially when there is too much informations to fit in one single slide:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B6cl0yidt_MNcfKftpzhaw.png" /><figcaption>Slide made infamous via <a href="http://en.slideshare.net/thecroaker/death-by-powerpoint">Death by PowerPoint by Alexei Kapterev</a></figcaption></figure><p>In terms of complexity, these really are on the same level as simple programming. So we don’t even need to point to mathematical writing conventions to find examples of structured ideas, laid out for others to understand and act on them. We just have to look around at bad (and good?) PowerPoint decks.</p><p>Ultimately, <strong>programming is laying out your ideas using a convention between you and the other humans around you.</strong> It has meaning (if not purpose) even without a computer executing it.</p><p>That makes programming extremely important as a convention for expressing ideas. It’s generic and powerful. It’s a convention to express ideas that can then be run and work by themselves. And it’s a convention finding its way into all aspects of our lives.</p><h4>Star Wars meet PowerPoint</h4><p>It might be very true that, in a distant future, an AI would be able all by itself to compose clear plans of actions, to create texts, to structure ideas.</p><p>Let’s say an artificial intelligence understands us. Would it exempt us humans from clear communication of ideas using structured texts? Would it exempt us from designing and from solving problems? And more generally, would it exempt us of thinking?</p><p>If AI progress ultimately exempts us from structuring clearly our ideas –because it does the structuring for us– would it mean a text-less culture, as in the fictional Star Wars universe, <a href="http://www.tor.com/blogs/2012/10/most-citizens-of-the-star-wars-galaxy-are-probably-totally-illiterate">where apparently most people are totally illiterate</a>?</p><p>Then, it would probably mean having to talk and talk endlessly to the AIs so they can do what we want them to do…</p><p>… and that’s where the real nightmare behind the <em>programming-via-AI</em> dream starts.</p><p>In the future, <strong>you may very well have to schedule 5 meetings with your own AI computer assistant, spend hours creating a series of powerpoint decks it needs to understand what you want, and have dozens of back and forth conversations to iron out the details – just to explain what it has to, well, program for you.</strong> And it will of course end up with a communication mishap, because, hey, you weren’t that clear on slide 67. (Says the AI. But of course you keep insisting it’s all its fault and classic AI-programmer deflection.)</p><p>Learning Ruby to directly express your ideas doesn’t look so bad now, does it?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38358562d424" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Le problème avec les notes n’est pas celui que vous croyez]]></title>
            <link>https://juliendorra.medium.com/le-probleme-avec-les-notes-nest-pas-celui-que-vous-croyez-3e1fa2c2957e?source=rss-bdfd5ce80297------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e1fa2c2957e</guid>
            <dc:creator><![CDATA[Julien Dorra]]></dc:creator>
            <pubDate>Fri, 04 Jul 2014 15:17:28 GMT</pubDate>
            <atom:updated>2014-07-04T19:50:03.768Z</atom:updated>
            <content:encoded><![CDATA[<h4>Tout le monde les détestent, tout le monde veut les garder. Pourquoi ?</h4><p>Les notes. J’ai croisé de nombreux enseignants — depuis l’élémentaire jusqu’aux niveaux universitaires — qui trouvent que les notes sont un indicateur inadéquat comme reflet complet d’un élève et un outil de mesure peu efficace. Qu’elles sont génératrices d’angoisse et qu’elles détournent de la motivation intrinsèque de l’apprentissage au profit d’une motivation extrinsèque. Et qu’elles provoquent un effet pygmalion négatif (“je suis un cancre”).</p><p>Dans le même temps, les discours sur les notes continuent de leur trouver des vertus ad-hoc, et elles sont toujours ardemment défendues comme utiles dans un cas ou un autre.</p><p>Que se passe-t-il ?</p><p>Il se passe que les notes en sont arrivées à combiner en un seul chiffre de nombreux usages — j’en ai relevé neuf !</p><p>* Mesurer le savoir acquis sur un sujet<br>* Analyser la progression individuelle<br>* Classer l’élève au sein du groupe, et le groupe au sein d’ensembles encore plus grand.<br>* Sanctionner l’échec ou la paresse(le zéro ne mesurant rien, il sanctionne seulement)<br>* Servir de barrière au diplôme (brevet, bac, etc.)<br>* Évaluer l’implication de l’élève (en comparant les notes du contrôle continu par exemple)<br>* Déplacer la responsabilité de la non-acquisition du savoir sur l’élève (par opposition à un simple Acquis / Non Acquis où la responsabilité peut être portée par l’enseignant)<br>* Compenser entre eux des savoirs et compétences totalement différentes et créer ainsi un niveau moyen de l’élève (un 18 en math compense un 2 en français, et permet donc de passer à la classe suivante en masquant la non maîtrise)<br>* Évaluer de manière normative par rapport à un élève ou un étudiant moyen qui aurait autour de 10 à 12</p><p>Agglomérer ainsi autant de fonctions dans un seul indicateur, puis faire reposer tout le système dessus… est-ce une bonne idée ?</p><p>C’est certainement une erreur éducative aussi bien que statistique, et cela a plus à voir avec notre obsession collective de la mesure pseudo-scientifique qu’avec une intention pédagogique claire.</p><p>Puisque les notes servent à tout cela, il aussi est compréhensible que la discussion ne puissent se dénouer. Car quand quelqu’un nous parle « des notes », il nous parle de ces neufs usages, en même temps, séparément, ou dans toute combinaison possible.</p><p>Un discours clair sur les notes doit donc creuser en dessous, et se focaliser sur les différents usages amalgamés pour les analyser un à un.</p><p>Pour ma part, je prone l’abandon de tous ces <em>B+</em>, <em>12/20</em> et autre <em>8/10</em> qui détournent notre énergie et notre attention. Les notes nous empêchent d’imaginer de vrais indicateurs pédagogiques.</p><p>L’abandon « des notes » n’est pas l’abandon du suivi des élèves et des étudiants , bien au contraire. Un réel suivi pédagogique des élèves passe par la différenciation des objectifs de suivi, par la réflexion sur ce que nous voulons évaluer, par rapport à quoi, pour le comparer avec quoi.</p><p>PS: Nous pourrions commencer par remplacer les chiffres et les lettres et les échelles de valeurs faussement objectives par des mots qui ont du sens, des mots choisis en communs et expliqués à tous.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e1fa2c2957e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The pleasure of buying domains]]></title>
            <link>https://juliendorra.medium.com/the-pleasure-of-buying-domains-b95de06be11c?source=rss-bdfd5ce80297------2</link>
            <guid isPermaLink="false">https://medium.com/p/b95de06be11c</guid>
            <dc:creator><![CDATA[Julien Dorra]]></dc:creator>
            <pubDate>Tue, 04 Feb 2014 17:21:24 GMT</pubDate>
            <atom:updated>2014-02-05T19:25:51.438Z</atom:updated>
            <content:encoded><![CDATA[<h4>2000 new gTLDs coming! Let’s splurge.</h4><p>Domain names are about to change. Massively. Hundreds of new generic top-level domains — extensions like .club and .education— are to be released <a href="http://newgtlds.icann.org/en/program-status/delegated-strings">starting now</a>. It’s a good time to tell the tale of a indulgence inherited from the 20th century: buying domains for the sake of it.</p><p>Over the years I registered around two dozens of domain names: a few for projects and business use, and the rest just for the pleasure of it. I also leave most of them unused – I even let some of them drop back into the available pool. (I’m sure to be then grabbed by squatter-bots registering everything that was once registered.)</p><p>I buy domain names on two occasions:</p><p><em>for a dedicated project, event or community (that makes sense, isn’t it?).</em></p><p><em>for… well… because sometimes, I feel like spending 5 hours listing words, combining them, looking them up on </em><a href="http://domai.nr/">domai.nr</a><em>, </em><a href="http://ovh.com/">OVH</a><em> and all. Because it’s fun to list names. Because buying </em>words<em> is a guilty pleasure.</em></p><p>What does it feel to buy a new domain name? It feels like having a new idea. Buying a domain give you the same excitement, as if making the first step into a wide open valley of interesting possibilities. You list names, you try to be clever, and each one of these names could be something really interesting (or not).</p><p>Then, there is this feeling of having found an unearthed nugget — “what, nobody ever thought of registering <a href="http://ilovepuppies.io/">ilovepuppies.io</a>? It would be crazy to let this opportunity pass!” Oh, indeed it would. Land-grab feeling. I was first.</p><p>The other side of this land-grab feeling is <a href="http://en.wikipedia.org/wiki/Loss_aversion">the loss-aversion bias</a>. Loss-aversion is a mean trick our emotions does to our rationality. Marketers and landing-page designers believe it’s the key to selling you things you don’t really need.</p><p>And it just happens than I’m inclined to pay a small fee to ‘keep’ a domain I just found, because I fear I will lose it forever if I don’t. Which is totally irrational. You see, I never thought of this domain in all my life. Not before actively testing dozens of crazy combinations of words and TLDs.</p><p>But now, I don’t want to lose these words I summoned up from the ether. I want them to be mine for all eternity (I’ll let you insert the adequate pop culture reference here. There must be some).</p><p>A good name tells a story. A good domain name is both a way to give access to this story, and a fantasy of owning the story all for ourselves.</p><p>That’s what makes them so irresistible. It’s a quick and cheap way to feel like I created something great already. I have a title for it! It exists on the web! It exists then. I’m the original author of this. The rest can wait. Ah, one year already? Let’s renew.</p><p>What’s the most important domain I ever bought? That’s boring: it’s my full name as a dot com. What domain I regret not having bought? My last name as a dot com. How original.</p><p>Still, I’ll keep listing words, imagining projects, and buying improbable domains for non-existing web sites. It beats buying shoes. (<a href="https://domai.nr/betterthan.shoes">betterthan.shoes</a>, anyone?)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b95de06be11c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we believe everybody must learn programming]]></title>
            <link>https://juliendorra.medium.com/why-we-believe-everybody-must-learn-programming-bff7cd81d699?source=rss-bdfd5ce80297------2</link>
            <guid isPermaLink="false">https://medium.com/p/bff7cd81d699</guid>
            <dc:creator><![CDATA[Julien Dorra]]></dc:creator>
            <pubDate>Wed, 29 Jan 2014 13:22:14 GMT</pubDate>
            <atom:updated>2014-01-29T13:51:25.139Z</atom:updated>
            <content:encoded><![CDATA[<h4>Code education is about literacy, fun and freedom. And power.</h4><p>Awakened by your phone, you start the washing machine. Oh look, a new fully automated train in the metro. At lunch you pay with your credit card. In the evening you enjoy the timed lights on the Eiffel Tower. It’s an endless list. There is not an hour of your life (one minute?) without a programmer participating in it by writing… code.</p><p>Technologies surrounding us are <em>animated</em> by code. This is transforming society and our lives, in nearly every aspect. The examples of this transformation… well, <a href="http://www.google.fr/search?q=creative+destruction+technology">you’ll be able to find them by yourself</a>. You already know them, most probably.</p><h3><strong>The danger of de facto illiteracy</strong></h3><p>If I am illiterate in our society — if I can’t read and write— I find myself powerless and excluded in many situations. I am then very easy to manipulate, drowned in the omnipresence of text, rules and laws that I can’t interpret.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*_R8fcSdDdV_x6Vp9A8VFDQ.jpeg" /><figcaption>Even an ad can crash nowaday. Oh, and of course <a href="http://shitdigitalsignage.tumblr.com/">there is a Tumblr about such crashes</a>.</figcaption></figure><p>Similarly, as we are now in a completely computerized society, one who doesn’t master the culture of code will be more and more powerless, excluded, and manipulated when facing new technologies.</p><p>Is there such a thing as <em>code illiteracy</em>? The concept is appealing because code is just text. A text that is used to create a program, an app, a website. A special kind of text, since it acts directly on the world (and sometimes with obvious hostility, as when it <a href="http://www.monde-diplomatique.fr/2011/07/LAFARGUE/20788">controls the gates of the subway [in french, but worth it]</a>)</p><p>In the early 19th century, a minority could read and write. And an even smaller minority were mastering the dominant culture based on text, contracts, legal texts… (once again, <em>codes.)</em></p><p>Just as today only a small number of people can read and write computer code.</p><h3><strong>From invisible control to liberating creativity</strong></h3><p>The founders of Facebook, YouTube, Twitter, Google, are all coders. These web platforms have transformed society in just a few years.</p><p>In fact, they <em>scare </em>people. And maybe rightly. <a href="https://www.socialtext.net/codev2/part_two_regulation_by_code">Code is Law</a>. <a href="https://www.socialtext.net/codev2/part_two_regulation_by_code">Code is Power</a>.</p><p>The web and venture capital have transformed the skills of these programmers-entrepreneurs into a new,<strong> almost magical talent</strong>:</p><p><em>The talent of writing, from their rooms, new social rules that spread and are adopted in a few months.</em></p><p>This talent should not remain in the hands of an elite group of new scribes. We must actively spread it.</p><h3><strong>Read and write, once again</strong></h3><p>We all need, sometimes, to count; we all need, sometimes, to read and write; and now <a href="http://www.edutopia.org/programming-the-new-literacy">we all need, sometimes, to code</a>, without always realizing it.</p><p>If we want our children to be creative, independent — if we hope for them as adults to use technology for their own freedom — we must <a href="https://medium.com/p/ab8e937956ee">pass on the code culture.</a></p><p>But is that something all kids must learn? Yes, <strong>*all*</strong> kids must learn programming.</p><p>Because the kids we would leave aside would have to use tools they can’t modify. They would be subjected to rules they can’t decrypt.</p><p><strong>Also, also: they would miss all the fun.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*lVOw6Y53xbZmAydv-jQRlA.jpeg" /></figure><p><em>A first version of this post was part of </em><a href="http://ils.sont.la/taxonomy/term/17,21"><em>a short series of articles</em></a><em> published after the second Coding Goûter in 2011. This is a revised (better) edition for Medium.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bff7cd81d699" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Abusing the digital commons]]></title>
            <link>https://juliendorra.medium.com/abusing-the-digital-commons-1f0be43dc5c3?source=rss-bdfd5ce80297------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f0be43dc5c3</guid>
            <dc:creator><![CDATA[Julien Dorra]]></dc:creator>
            <pubDate>Sun, 26 Jan 2014 18:26:35 GMT</pubDate>
            <atom:updated>2014-03-26T00:29:32.804Z</atom:updated>
            <content:encoded><![CDATA[<h4>When building an open community, remember that free-libre licenses exist to protect user freedom, not author copyright.</h4><p>Free licenses are here to protect the end users, not the authors. Copyright already over-protects the authors.</p><p>A good license for open creative communities is a license that aims to protect the users *<strong>from</strong>* the contributors, not to protect the contributors from the users.</p><p>Because, in the end, the one with all the power is the author.</p><p>By licensing work under a free-libre license, an author willingly chose to give a broad, permanent protection to the user against the author’s own rights.</p><p>That’s what the GPL is all about. That’s what the CC-BY-SA is all about. (And, yes, the Share-Alike part actually does protect the users, from re-proprietarization that would limit their rights to derivative works).</p><p>And this great gift from authors create a virtuous circle of wide use, new contributions, and thriving ecosystems. It benefits users, community members, and the society as a whole, including, yes, profiteers.</p><p>Think about how an user of the Linux kernel, or the jQuery library, or Wikipedia, is protected from the arbitrary decisions of their (single and then numerous) authors.</p><h4><strong>The fear of abusive (mostly commercial) uses</strong></h4><p>When trying to set up rules for their open creative communities, many community founders are worried about the community contributors’ work being abused.</p><p>One thing community founders fear is outsiders using the work without ever contributing back. Or using the work to make money, and not contributing back adequately. It leads them to shy away from free-libre licences, and to seek licences that would protect the community authors from these abuses.</p><p>Selfish use of community-produced content is an important issue to address, of course. Is it morally right to use this community-produced content without giving back? Is it fair that someone uses it to make money?</p><p>Often, by focusing on fairness *for the authors*, we forget that open communities which create (digital) common goods must above all protect the users of these commons.</p><p>So, how to strike a balance between liberating the users from the tyranny of copyright where authors are the almighty dictators on their work, and the possible immorality of outsiders profiteering on the common work without giving anything back to the community?</p><h4><strong>Not owned by anyone, not even the community</strong></h4><p>Each community has to answer according to its goal. For Wikipedia, its goal is to create a global, universal encyclopedia, and it’s perfectly fine if someone uses Wikipedia without ever contributing back. Also, it’s fine to make money using Wikipedia content as long as you credit the use.</p><p>When you use Wikipedia content, you know as a user that you are protected from Wikipedia authors. No small print. Wikipedia is a commons because it is not owned by anyone, not even the community that is creating it.</p><p>The commons are by definition prone to abuse. This abuse is a drama in the scarcity-based material world. It becomes at worst a very impolite thing to do in the abundance-based digital world.</p><p>If an open creative community impose rules that protect the community contributors first, and the users second, we risk turning our communities into closed tribes.</p><p>In putting the users second we would lose sight of our greater goal: to create freely usable common goods in a world dominated by DRM, monetization, and arbitrary contracts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f0be43dc5c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>