<?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[Flatiron School - Medium]]></title>
        <description><![CDATA[learning to ❤ code - Medium]]></description>
        <link>https://medium.com/flatiron-school?source=rss----bb0d82a77870---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Flatiron School - Medium</title>
            <link>https://medium.com/flatiron-school?source=rss----bb0d82a77870---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:01:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/flatiron-school" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What does learning dance have to do with learning Ruby?]]></title>
            <link>https://medium.com/flatiron-school/what-does-learning-dance-have-to-do-with-learning-ruby-cfd706a8b7b5?source=rss----bb0d82a77870---4</link>
            <guid isPermaLink="false">https://medium.com/p/cfd706a8b7b5</guid>
            <category><![CDATA[flatiron-school]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[learn-to-love-code]]></category>
            <dc:creator><![CDATA[Benjamin Gadbaw]]></dc:creator>
            <pubDate>Fri, 12 Jun 2015 13:21:17 GMT</pubDate>
            <atom:updated>2015-06-12T17:03:28.633Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N7ouCEjWoiCVfS0JYh5jkA.jpeg" /></figure><p><em>Well, throw a bunch of programmers into a room with a professional house dance instructor in the middle out the afternoon and you’ll find out. That’s what Flatiron did to their web development class this week. It’s kind of their style…do it, fail, do better. I’m no stranger to prototyping, but usually I’m the one running the prototype. Now I’m like…the user. This post is about a few things I learned from the experience.</em></p><p>I came to programming from design, thinking it was going to be very logical and clear cut and there would only be one right answer. So far that’s turned out to be true and not true.</p><p>I don’t dance outside of weddings and when friends drag me to clubs, but my perception of dance is the opposite. It’s all about self expression and is really flexible. It’s loose. It’s…whatever. So there’s really nothing in common between learning the two. Not so fast.</p><p>Here are a few things similar between learning to dance and learning ruby. Note, this is after 1 week in programming and a half hour with the amazing John Doyle of the Harlem Dance Club.</p><h3>John Clayton Doyle on Twitter</h3><p>This is my obsession. https://vine.co/v/bV7PVDOWEBA</p><h3>1. Both learning Ruby and learning to dance benefit from embracing vulnerability</h3><p>Interrupting 27 programmers in the middle of their day to dance, tearing them away from more than enough to work seemed like a recipe for awkwardness…not to mention the lack of any social lubricant.</p><p>We started the class with a simple breathing exercise — fill your lungs completely as you take a step forward, then release your lungs as you take a step backward. Then repeat the process, except take two steps forward, and two steps back. Repeat this process up to ten steps. This is a very natural transition from sitting at a computer, because it has a logic and an iteration. You could almost write it into a program. In fact you could almost use a conditional like “until” to describe the process.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/daa09065c74f55f80c92c0e3b1739718/href">https://medium.com/media/daa09065c74f55f80c92c0e3b1739718/href</a></iframe><p>So for dance you’d define an ending condition (10 steps) and create a procedure (walking and breathing), and then iterate over that procedure starting with one step and incrementing it by 1 until you you met the condition.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5d550f14b9a2c81171aedad0f1f4fe42/href">https://medium.com/media/5d550f14b9a2c81171aedad0f1f4fe42/href</a></iframe><p>It’s actually more complicated, but you get the point.</p><p>So first we had rigid rules. Then we were told that some rules actually require expression and movement that we’re not used to. And then we were told to just self express without rules. The process was one of incremental exposure to vulnerability. Who would have guessed that after half an hour we would be in circles dancing in the middle of the afternoon in a hot carpeted classroom?!</p><p>In learning programming, it’s important to feel comfortable where you are. For example, if you’re sitting at a table not understanding how to find a vowel in a string and your teammates are refracting a program to scrape data from Spotify, that’s cool. There will always be someone ahead and behind you. It’s like the New York Marathon. If you kept staring ahead or behind you to see what place you were in, you’d trip and fall. When learning sometimes it helps to focus on process over outcome; to stay in the moment and breath and take each step at a time whether it’s a line of code or a complex dance routine.</p><h3>2. Both build on rules</h3><p>I always thought the people that were best at dancing were just more comfortable in their skin; getting out there and shakin’ it. Dance like ballet is really choreographed, but even social dance has rules. For example, if you are going to <a href="https://youtu.be/vBYvWPdUOHM?t=50s">dance to house music</a>, you better be moving your upper torso or you’re going to look like you’re in a barn doing square dance and that’s weird.</p><blockquote>“In house there’s there’s the jack. Best described as your heartbeat.” — John Doyle</blockquote><p>Just like Ruby has built in modules like the Enumerable and Comparable that have specific methods to apply to objects, dances like House have elements like “<a href="http://en.wikipedia.org/wiki/Footwork_(dance)">Footwork</a>”, “<a href="http://en.wikipedia.org/wiki/Jacking">Jacking</a>”, and “Lofting”. The more you understand the rules, the better you can dance or program. The same goes for other arts forms, like painting. Historically, painters spent years with charcoal before they were allowed to use paints. Picasso painted very realistic portraits and landscapes before moving on to cubism.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qjnym9fqGpkqt0-Dohkfsg.jpeg" /><figcaption>Compare Picasso’s cubist work like “Weeping Woman with Handkerchief” from 1937 to his earlier work like “Portrait of the Artist’s Mother” from 1896 when he was just 15 years old.</figcaption></figure><h3>3. Rules are just the beginning (i.e. learning Ruby is more like learning dance than learning math)</h3><p>Ruby is actually surprisingly approachable. As apposed to LISP programming languages, Ruby is pretty simple because the syntax (more or less the alphabet and grammar of the language) are simple. Avi Flombaum puts it well, “The entire Ruby language is approximately 43 words…that’s the weird thing about programming; if you memorized every one one of those keywords and what they did you still wouldn’t know how to program. Sort of like if you learned the 26 letters of the alphabet you can’t necessarily write Shakespeare.”</p><blockquote>Programming is the art of composition and the science of operations. So you’re not trying to memorize 43 keywords; you’re trying to understand how those keywords are building blocks — are the components with which we can put together a larger and bigger and more complex program, in fact invent our own program, our own language. — Avi Flombaum</blockquote><p>In other words, learning the syntax is just the beginning.</p><h3>4. Understand the specs so you’re not a slave to them</h3><p>A good definition of “specification” is “a detailed description of the design and materials used to make something.” Guess who makes specs. People. People are imperfect and diverse. So to master Ruby, it’s important to understand specs, just like it’s important in dance to understand the patta barrette (sp?)…basically the three step.</p><p><a href="http://blog.teamtreehouse.com/an-introduction-to-rspec">Rspec</a> is a testing library for Ruby that helps with TDD (test driven development).</p><p>It’s really annoying at first, because sometimes you’ll build an application that works and the test will fail. Even worse, you’ll build a program that doesn’t work and the test will pass. For example, say you wanted to write a simple method like follows:</p><h4>Write a method that will evaluate a string and return the first vowel found in the string, if any.</h4><p><strong>The RSpec</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d4755a22ef31718e9b7bc96eef77bff4/href">https://medium.com/media/d4755a22ef31718e9b7bc96eef77bff4/href</a></iframe><p><strong>The code to pass the test has fewer lines than the test itself.</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f4e1ad8cb9ebf09fe0004f826f468c28/href">https://medium.com/media/f4e1ad8cb9ebf09fe0004f826f468c28/href</a></iframe><p>But if you look closely, the code won’t actually “evaluate a string and return the first vowel found in the string, if any” for any situation. In fact, to pass the first test, it only uses one word.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xgppVGivwmVn448-4ksAUg.jpeg" /></figure><h3>let(:word_with_vowel) { “taco” }</h3><p>It will break if you use any word that has a vowel before an a, like burrito, or enchilada. To account for this the test suite has to be more robust.</p><p>To deliberate about this is kind of a waste of time. Because the lab is an exercise to teach something. In the real world, we would have much bigger problems than burritos and enchiladas to worry about. How do we even localize taco to situations where the roman alphabet system isn’t used like arabic (تاكو) or chinese (塔科)? What happens when we express vowels as emojis? So focusing on passing the RSpec builds the technical skills to solve broader challenges.</p><p>It alludes to something a little more profound about TDD and object oriented design which is well articulated by Sandi Metz,</p><blockquote>Part of the difficulty of design is that every problem has two components. You must not only write code for the feature you plan to deliver today, you must also create code that is amenable to being changed later. For any period of time that extends past initial delivery of the beta, the cost of change will eventually eclipse the original cost of the application. Because design principles overlap and every problem involves a shifting timeframe, design challenges can have a bewildering number of possible solutions. Your job is one of synthesis; you must combine an overall understanding of your application’s requirements with knowledge of the costs and benefits of design alternatives and then devise an arrangement of code that is cost effective in the present and will continue to be so in the future.</blockquote><blockquote>Taking the future into consideration might seem to introduce a need for psychic abilities normally considered outside the realm of programming. Not so. The future that design considers is not one in which you anticipate unknown requirements and preemptively choose one from among them to implement in the present. Programmers are not psychics. Designs that anticipate specific future requirements almost always end badly. Practical design does not anticipate what will happen to your application, it merely accepts that something will and that, in the present, you cannot know what. It doesn’t guess the future; it preserves your options for accommodating the future. It doesn’t choose; it leaves you room to move.</blockquote><blockquote>The purpose of design is to allow you to do design later and its primary goal is to reduce the cost of change.</blockquote><blockquote>– <a href="http://poodr.com/">Practical Object-Oriented Design in Ruby</a></blockquote><p>Tests are written by people so they will probably fail to forecast all the use cases, and more importantly tests are written in a moment of time, but the universe is not static so tests are inevitably out of date.</p><h3>5. Letting go of and diving into reality</h3><p>There’s a saying that a lot of dance is “dance imitating life.” For example, Michael Jackson made famous, the skate (imitating rollerskating…old school style with two wheels and a brake on the back). Lesser know moves are the old man (imitating a drunk old man) and even the pimp.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJp7GtXQGOMI%3Ffeature%3Doembed%26start%3D187&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJp7GtXQGOMI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FJp7GtXQGOMI%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a3b5382536d5e59bf41beacdac48f5a2/href">https://medium.com/media/a3b5382536d5e59bf41beacdac48f5a2/href</a></iframe><p>Learning ruby is the same. As Alan Kay famously said, “I thought of objects being like biological cells.”</p><blockquote>“I thought of objects being like biological cells.” — Alan Kay</blockquote><p>He designed Object Oriented programming the same way neurons communicate, with modularity and independence between each other. Throughout evolution this allowed for mutations to create new species with iterations rather than destroying them.</p><p>But what does this have to do with letting go of reality? Well, there’s a move in dance called the paper bag. It’s similar to other dance of Caribbean origin in that it has airiness to it. It doesn’t mean you dance with a paper bag on your head, or even that you dance to the Fiona Apple’s “Paper Bag.” It means you pretend that you have a light paper bag that’s floating and guiding you. So you have to give up your concept of paper bag dance.</p><p>In programming we come with a lot of concepts of how our computers are organized — in folders inside folders, with buttons, etc. But these are all GUI inventions to make computers more accessible to use. But to create applications we have to give these up. Web pages are just strings (characters contained inside “” marks), and a lot of data we use like folders are documents are just lists arranged with specific key/value relationships.</p><h3>6. Both start with and end with people</h3><p>I thought of programming as very cold and analytical, like math. But get this, computers and code were invented by people! It’s kind of a duh and a whoa at the same time. Yukihiro Matsumoto released the first version of Ruby on December 21, 1995. It’s younger than most of us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0TBm5QPJ2ylpIsdWmWPHOA.jpeg" /><figcaption>Yukihiro Matsumoto</figcaption></figure><blockquote>Often people, especially computer engineers, focus on the machines. They think, “By doing this, the machine will run faster. By doing this, the machine will run more effectively. By doing this, the machine will something something something.” They are focusing on machines. But in fact we need to focus on humans, on how humans care about doing programming or operating the application of the machines. We are the masters. They are the slaves.</blockquote><blockquote>— Yukihiro Matsumoto “<a href="http://www.artima.com/intv/ruby4.html">The Philosophy of Ruby, A Conversation with Yukihiro Matsumoto, Part I</a>” by Bill Venners on 2003–09–29 (Artima Developer).</blockquote><p>Furthermore, he is designing for programmers. As programmers we are designing for end users. So Matz is simply passing on the language for us to write the music for people to dance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nkeNkh4asqsq-bZNI03ovw.jpeg" /><figcaption>Flatiron students doing the paper bag.</figcaption></figure><h3>In summary</h3><ol><li><strong>Both learning Ruby and learning to dance benefit from embracing vulnerability</strong></li><li><strong>Both build on rules</strong></li><li><strong>Rules are just the beginning (i.e. learning Ruby is more like learning dance than learning math)</strong></li><li><strong>Understand the specs so you’re not a slave to them</strong></li><li><strong>Letting go of and diving into reality</strong></li><li><strong>Both start with and end with people</strong></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfd706a8b7b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/flatiron-school/what-does-learning-dance-have-to-do-with-learning-ruby-cfd706a8b7b5">What does learning dance have to do with learning Ruby?</a> was originally published in <a href="https://medium.com/flatiron-school">Flatiron School</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>