<?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 Jorge Rybar on Medium]]></title>
        <description><![CDATA[Stories by Jorge Rybar on Medium]]></description>
        <link>https://medium.com/@JorgeRybar?source=rss-112bdeff9a96------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6mJHxPQuQwecxx5IhdRIvg.jpeg</url>
            <title>Stories by Jorge Rybar on Medium</title>
            <link>https://medium.com/@JorgeRybar?source=rss-112bdeff9a96------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:36:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@JorgeRybar/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[Learning to Code Should be More Like Playing Candy Crush]]></title>
            <link>https://medium.com/@JorgeRybar/learning-to-code-should-be-more-like-playing-candy-crush-13cc02340e0c?source=rss-112bdeff9a96------2</link>
            <guid isPermaLink="false">https://medium.com/p/13cc02340e0c</guid>
            <category><![CDATA[games]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Jorge Rybar]]></dc:creator>
            <pubDate>Mon, 22 Feb 2016 02:35:23 GMT</pubDate>
            <atom:updated>2020-02-20T21:29:53.637Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you wondered how your Aunt Sally learned to play Candy Crush? Think about it — she can’t even turn on the AC in her car. Isn’t it a mystery?</p><p>The secret, my friends, is in great game design. The most popular and highest-grossing games these days are easy to learn and hard to master. Games like Crossy Road and Angry Birds know how to progressively ramp up the difficulty for players to keep them stimulated as they learn to play.</p><p>However, in the world of computer programming, there is currently no way for people to learn on their own in this natural manner. This is a huge opportunity. Whoever can create a computer language that is designed to be picked up like a game will open the door for millions of people to become coders.</p><p>A game designer’s job is to teach people the rules of an imaginary world and make it fun enough that they’ll want to stay there (for example, by choosing to help Odus the Owl even if it means missing their bus stop and ending up in Koreatown). Incredibly, some of the best practices from game design have not been applied in the design of computer languages and IDE’s, even though everyone agrees that it would be beneficial if more people were exposed to coding.</p><p>One of the core principles of great game design is “easy to learn and hard to master”. Basketball, for example, is easy to learn (put the ball in the hoop) and super easy to start playing. Anyone with a ball and a hoop and some funky shoes can play. But basketball takes much time to become a master at. It takes tons and tons of practice. That’s really why it’s so popular: it&#39;s accessible to everyone but it never gets boring. Whether you are a pro or a newbie there is always a new challenge. You can increase your shooting precision, face better opponents, find more tricks to master and work on your mental game. Similarly, some of the most popular video games of all time (Candy Crush, Mario, <a href="https://medium.com/life-learning/your-life-is-tetris-stop-playing-it-like-chess-4baac6b2750d#.q6waf6y7h">Tetris</a>) also make it simple to start playing and to understand the rules but as you start moving through the world, challenges just get harder and harder. Not so with learning computer programming.</p><p>Most computer languages fall into the ‘hard to learn, hard to master’ category. It’s just too hard for non-programmers to simply start using them and to just ‘pick them up’ (even with languages that sound super non-threatening such as Python). There’s no way for a non-programmer that hasn’t had <em>some</em> instruction to download Python and instantly make something cool. It doesn’t work like that. <em>Some</em> education is always required, whether that be a university or online course, a book or a few minutes on W3Schools. At best, a newbie can start learning by using interactive tutorials like Code academy or Rails For Zombies. But the process is not self-guided. It does not follow the natural way that people learn. The reason is that serious computer languages today were not designed with non-technical people in mind.</p><p>On the other end of the programming landscape, there are languages that fall into the “easy to learn easy to master” category. In short, these are languages that <em>were </em>designed for newbies. <a href="http://scratch.mit.edu/">Scratch</a> is the best example I’ve seen. First of all, it’s super easy to set it up. You just go to the website. No downloads required. Then you start playing and it is so easy to get something happening on the screen (a ball bouncing, or a cat dancing). Scratch removes the need for its users to memorize any special syntax through the use of drag-and-drop. The puzzle pieces of code will only fit together if the logic works. Also, Scratch makes it unnecessary to search through the documentation by placing all the available types of pieces and functions and right there in a sidebar. There’s no guessing involved. If my 10-year-old cousin, Jake, wants a two-horned unicorn to bounce when it reaches the edge of the screen he just naturally searches for blocks under the “Motion” tab and stumbles on to the one that says “If On Edge Bounce”.</p><p>But what happens to Jake the day he hits 13 and decides that he is ready for more than just unicorns? Perhaps he wants to build a first-person shooter? The problem with “easy to learn easy to master” languages is that at some point people want to do more but they discover that these languages don’t offer enough functionality or speed. In my case, I wanted to implement A* path searching for my mini <a href="https://scratch.mit.edu/projects/92652931/">game</a> but found myself with no way to reference a specific instance of an object. Boy was it excruciating. I had to find a roundabout way of doing what I wanted, and it took many repetitive lines of code. When the same thing happens to little Jake he will have no option but to move to one of those ‘hard to learn hard to master languages’ to get hurt because those languages don’t offer any training wheels or helmets. Jake will find himself shivering in the cold world of compilers and debuggers and dependencies; and shuddering with syntax errors, logic errors and complex documentation. It would take a lot of persistence and luck in being found by some great mentors in order for him to keep coding.</p><p>Well, he does have another alternative: some very smart guys at Berkley created their own version of Scratch called <a href="http://snap.berkeley.edu/">Snap</a>! and it is a really smart tool. It extends Scratch to allow people to do pretty much anything they can do with a real object-oriented language. However like Scratch, Snap! can only run within its own IDE. So if Jake wants to use it to make an app to show off at school, he cannot. My impression is that other attempts like Lua’s Corona SDK, Visual Basic, GameMaker suffer from the same problem of being only useful for a few specific platforms or applications.</p><p><strong>So what if we had a language that was “easy to learn and hard to master”? </strong>What if we<strong> </strong>had a<strong> </strong>language that would be useful to both very beginners and the most advanced programmers? What would that look like? That is the question I pose to you today.</p><p>Now I’ll share are a few of my own ideas:</p><p>1. <strong>It progressively transitions from friendliness into speed</strong>. For example the input method starts as drag and drop, but then it shows you a keyboard shortcuts to control the drag and drop, and finally allows you to input text with all the protective features of modern IDE’s.</p><p>2. <strong>It progressively discloses functionality</strong>. Are you making a “game”? <a href="https://en.wikipedia.org/wiki/Progressive_disclosure">It adapts to your own project by only revealing basic functions that are relevant to you at that moment…</a> But if you want to dig deeper it offers an easy to navigate tree of categories and classes and functions that you always have at your side (like in Scratch). Once you start looking it is easy to delve in and find everything you need. You can always add new libraries of blocks to extend your environment and documentation is built-in right when you need it.</p><p>3. <strong>It looks cozy and friendly like Scratch.</strong></p><p>4. <strong>Naming conventions and readability</strong> are super important like in Python.</p><p>5. <strong>It can be used to make real applications</strong> for a multitude of hardware and platforms. It can be used to make games and also apps and websites and to program servers.</p><p>6. <strong>It is open source.</strong></p><p>Do you agree that this is the way that we have to design languages? Do you have any other ideas? Please do leave your comments below.</p><p>Jorge David — Game design, technology, and education enthusiast</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13cc02340e0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>