<?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 Oscar Elizondo on Medium]]></title>
        <description><![CDATA[Stories by Oscar Elizondo on Medium]]></description>
        <link>https://medium.com/@oelizondo?source=rss-49563c4a8e26------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nZu6gad9IZc430xnEQCCzg@2x.jpeg</url>
            <title>Stories by Oscar Elizondo on Medium</title>
            <link>https://medium.com/@oelizondo?source=rss-49563c4a8e26------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:29:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oelizondo/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[In building Moato, and learning Rails.]]></title>
            <link>https://medium.com/icalia-labs/in-building-moato-and-learning-rails-57653f6e2c68?source=rss-49563c4a8e26------2</link>
            <guid isPermaLink="false">https://medium.com/p/57653f6e2c68</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Oscar Elizondo]]></dc:creator>
            <pubDate>Fri, 11 Sep 2015 22:37:34 GMT</pubDate>
            <atom:updated>2015-09-14T22:19:42.830Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AvdahZZ9Dpa_W_jUv8Q0aQ.png" /></figure><p>The day I started as an intern in <a href="http://www.icalialabs.com/">Icalia Labs</a> I was afraid, “You’re going to be a rails intern, and you’re gong to have fun”. That didn’t seem very fun, I say it because the first time I tried rails a few months ago, I didn’t like it at all. “You don’t need to know ruby to learn rails.”, they said. That wasn’t true so I had a bitter experience and moved on to JavaScript frameworks, like Express and Meteor. But this time I had no choice, it was rails and only rails. I want to say that I am completely in love with both Ruby AND Rails.</p><p>I must say I was impressed with the introduction my mentor gave me to the ruby language. First we did a API wrapper with CoffeeScript. It was confusing at first, but I picked up the syntax rapidly. Afterwards I learned ruby, but since I was familiar with coffeescript, it was much easier to learn, coming from more explicit and strucutred languages such as C++ and vanilla JavaScript. Learning and working with ruby was great, the syntax was pretty, the object-oriented programming I was executing felt right and clicked. I made the same wrapper but with ruby, but I was so comfortable with the language this time that I made it so much more deep, complex and and usable, I even published it on rubygems.org.</p><p>Next came Rails. I was afraid to be honest, I was called to go upstairs in the office, and sat down with my mentor, and he said: “It’s time to pick a Project so that we can work with it internally”. What. That was too soon, I had barely been there for a month, and these guys wanted me to pick a complete project so that they could use it as an internal day-to-day tool. That was kind of terrifying. I didn’t know Rails. And I been with ruby for only a few days. But still, I went with it because it looked interesting.</p><p>So I was presented with 3 ideas. And I picked what looked like the most interesting one. I didn’t know if it was the hardest or the easiest, and because I had no real back-end experience, I couldn’t measure the difficulty. A Styleguide generator, I didn’t know what that was, I knew what a styleguide was, but not how to generate them via-web.</p><p><strong>First Steps</strong></p><p>The first thing I did to learn Rails was reading the famous “Ruby on Rails Tutorial” by Michael Hartl. People told me to stay away from it because it was pretty advanced, but that’s not the case, it’s very friendly and easy to read. I spent about a week or two reading the whole thing and doing the app the book walks you through. I liked it but I wasn’t in love, what was happening? I felt like things didn’t click, I understood stuff but I didn’t feel right. But I went on with it and started the actual project here at Icalia, named <strong>Moato</strong>. And then it clicked. Everything made sense, except for a few things, but I was getting the hang of it, and it was hella fun. How could I have missed such an awesome framework?</p><p>The best part was pair-programming, because I could actually sit down with an experienced developer and see how he did things, how I did things, and how I could improve and refactor my code.</p><p>It was fun and I picked up the pace quickly, the logic and how the frameworks were easy to understand, at least for me. But there were many moments where I had my ‘Aha’ moment. Such as nested resources, production environment vs testing vs development, subdomains and namespaces. Those moments were amazing and really set my creativity free as to what I could do with rails.</p><p><strong>Rails, data and the front-end</strong></p><p>ActiveRecord is amazing. I really like the Object Oriented approach the framework has to dealing with data. I think that it even makes it more efficient to work this way, because you can make super minimal queries that translate into more complex ones. It’s just very developer friendly. The one thing that makes me think twice is the fact that it may be detrimental on the long run. For example, say the whole Rails hype goes away, and there’d be a problem where Rails developers switch to another framework, but don’t know how to handle a database because it doesn’t have that same ‘ActiveRecord’ feel.</p><p>The next thing was the front-end part. I had a conflict here, mostly because I <em>thought</em> I knew front-end, but I figured out I knew very little, and then again, I learned a whole lot. The first big challenge was working with a designer, especially picky ones. Every time I had a design review it took us about an hour or two just to move pixels around, but I guess that’s how they roll here. Second was the actual coding of the application. Picking a front-end framework, I had never used before, this being Furatto, using Sass extensively, and getting used to the CoffeeScript syntax. It was very fun, and learned the real power of Sass to make coding the front-end easy and painless. CoffeeScript however was a bit different, even though the syntax is very ruby-like, applying it to a jQuery / JavaScript ambient was kind of weird. Fun, still.</p><p>Deployment was weird. I liked it, but it was pretty strange dealing with the whole ‘key’ thing, and it was certainly not something that I was familiar with. I <em>had</em> deployed apps before, but this time the process was much more strict and solid, with database backups, image storage, and Heroku add-ons to keep track of the site’s traffic. This was weird but I’m used to it, and I’m in the process of deploying another app on my own. Certainly that wouldn’t be possible without the initial walkthrough I had with my mentor.</p><p><strong>Conclusion time</strong></p><p>Learning Ruby, Rails and front-end tools was amazing, but what I appreciated and loved most was the initial app design. I’m not talking about good looks, but functionality and planning. Planning what Users would do, how Projects behaved, the feel of the application, the wireframes, user stories. I think that’s the part that really adds value to a product or project. In pen and paper are literally where a project or product comes to life. Designing and Coding are things that are built on top of a product’s requirements, if there are no specifications or requirements then the designer and the coder will never make a product that’s as good as one that does have these elements.</p><p>I’m really excited to improve <a href="http://www.moato.style/">Moato</a>, add test and make it a useful tool for everyone to use when in need of a styleguide.</p><p><a href="http://www.twitter.com/oehinojosa">Óscar Elizondo H.<br></a>Aspiring web developer, currently focusing in Rails and Express. I like to look for new challenges and learn new things everyday.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57653f6e2c68" width="1" height="1" alt=""><hr><p><a href="https://medium.com/icalia-labs/in-building-moato-and-learning-rails-57653f6e2c68">In building Moato, and learning Rails.</a> was originally published in <a href="https://medium.com/icalia-labs">Icalia Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>