<?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 Patrick Miller on Medium]]></title>
        <description><![CDATA[Stories by Patrick Miller on Medium]]></description>
        <link>https://medium.com/@pjmiller823?source=rss-126e4fe3d142------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*4fIblNbxmDnIBgcx.</url>
            <title>Stories by Patrick Miller on Medium</title>
            <link>https://medium.com/@pjmiller823?source=rss-126e4fe3d142------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:27:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pjmiller823/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[It’s time to get to work]]></title>
            <link>https://medium.com/@pjmiller823/its-time-to-get-to-work-b48cfb454b71?source=rss-126e4fe3d142------2</link>
            <guid isPermaLink="false">https://medium.com/p/b48cfb454b71</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[benefits]]></category>
            <category><![CDATA[the-iron-yard]]></category>
            <dc:creator><![CDATA[Patrick Miller]]></dc:creator>
            <pubDate>Wed, 26 Apr 2017 22:40:34 GMT</pubDate>
            <atom:updated>2017-04-27T13:56:30.692Z</atom:updated>
            <content:encoded><![CDATA[<p>While watching the many wonderful speakers at the Front End Design Conference I began to wonder what kind of talk I would give were I ever given the opportunity. I bounced a couple of different topics around in my head but it quickly became obvious that there is something that I truly feel a need to say. I believe that the tech industry puts far too much emphasis on building up an attractive work culture, or at least is putting that emphasis in the wrong areas.</p><p>Let me explain. I fully understand and support the need for a great work culture. Between a commute and lunch, most adults spend more time at work than they do at home and it is important for them to be in a space where they feel comfortable and productive. Doing otherwise will drive employees to change companies at the first possible chance, and they will be hard pressed to give their best work. But some of the benefits I’ve seen listed on job listings are borderline ridiculous.</p><p>I don’t think that a startup needs to spend it’s precious resources on keeping a beer fridge stocked, a ‘bags’ set, or cling boards, and I don’t need a theater room or a sushi chef that comes in twice weekly (although that one doesn’t sound too bad…). You would be hard pressed to convince me that perks of this variety actually result in more work for the dollar. Personally, I think that there are far superior (for both the employee and the company) benefits to offer employees, and I don’t think I’m the only one who thinks so.</p><p>For me, work is something that I want to enjoy doing, put in my best work into every day, and then go to spend time with my family that I love. They’re the ones I’m going to work for. I don’t need games to play or social hours at the local pub, all of these things just extend the amount of time it takes to finish a project. And while a sushi chef would be great (honestly it really would), I would rather that the company hire another janitor, or pay the current one more. I think that a majority of people would list more PTO, or the ability to work from home as their ideal benefits. I know providing those are easier said than done, but there are smaller alternatives that you can implement while you’re building up to that point that make a real difference.</p><p>You might ask, “So guy who’s never owned a company before, where do you think the emphasis of culture should be placed?” Well, I would humbly suggest that all of these fancy benefits don’t actually build a culture. Put your dollars, effort, and emphasis on mentorship, hiring and building up junior developers (says the junior developer), or working to make sure that you have a space where hard questions can be asked. If the emphasis is placed in this direction your employees will actually enjoy working there. Or at least I would. And I would bet money that a company who places their emphasis on these types of practical cultural practices will beat out the company that buys all of their employees Segways in employee satisfaction every day of the week.</p><p>I know I have used a lot of hyperbole here, but it is a topic that has been digging under my skin since I’ve started to look at the tech industry as part of my future. This has been taken way overboard. And while I really love that everyone is trying hard to make all of their employees happy, I think it might be time for the tech industry to just sit down and get to work.</p><p>Patrick James Miller</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b48cfb454b71" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Felt After the Introduction of Ruby on Rails]]></title>
            <link>https://medium.com/@pjmiller823/how-i-felt-after-the-introduction-of-ruby-on-rails-ef6274113e72?source=rss-126e4fe3d142------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef6274113e72</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[the-iron-yard]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <dc:creator><![CDATA[Patrick Miller]]></dc:creator>
            <pubDate>Mon, 10 Apr 2017 22:32:38 GMT</pubDate>
            <atom:updated>2017-04-10T22:32:38.959Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week we made the transition from Ruby to Ruby on Rails. We went from having to spend a few hours writing all of the classes, methods (<a href="https://medium.com/@pjmiller823/how-classes-and-methods-work-in-ruby-51c4459bc0af">see previous post</a>), databases, the correlations between the databases, and every other tiny bit of code needed to start a project; to having all of that written for us in a handful of terminal commands. And I think it’s beautiful. To me there are two major keys to work satisfaction: efficiency and organization. My introduction to Rails has fully embodied both.</p><p>Don’t get me wrong, I’m happy to have spent the last four weeks building up a foundation in Ruby. As Josh Waitzkin says in his book “<a href="http://www.joshwaitzkin.com/the-art-of-learning/">The Art of Learning</a>” depth beats breadth any day of the week. I know how important it is to focus on the building blocks of a subject when you are beginning to learn, but it feels nice to take what feels like kid gloves off and really start to get to work.</p><p>For those of you who don’t know, when running a rails app you can ‘scaffold’ different objects into reality. When you run this, it will set up all the files that you will need for a very basic web app and pre fill in those files with functioning code. This allows you to invest your time in growing your app into something that is a little more complex. It’s beautiful. You can already see where the efficiency comes into play, by choosing to run your app with rails you’ve cut off a solid hour plus previously just spent getting to work. But the real beauty comes in the the organization. If you can allow yourself to follow the naming conventions that Ruby suggest for you (I certainly can), everything begins to connect together. Our instructor Gavin likes to call this automagically, and I’m beginning to see why. I’m excited to work within the Rails framework in the future, and you can keep reading about what I learn and my experiences right here. Thanks!</p><p>-Patrick Miller</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef6274113e72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Classes and Methods Work in Ruby]]></title>
            <link>https://medium.com/@pjmiller823/how-classes-and-methods-work-in-ruby-51c4459bc0af?source=rss-126e4fe3d142------2</link>
            <guid isPermaLink="false">https://medium.com/p/51c4459bc0af</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[the-iron-yard]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <dc:creator><![CDATA[Patrick Miller]]></dc:creator>
            <pubDate>Tue, 04 Apr 2017 17:52:05 GMT</pubDate>
            <atom:updated>2017-04-04T17:52:05.556Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m starting my fourth week at The Iron Yard and am going to use this space to rephrase some of the concepts I’ve learned in a unique and (hopefully) helpful manner. In this first blog I am going to explain how I choose to look at how classes and methods work within Ruby.</p><p>First I would like to quickly discuss the way that The Iron Yard works for those of you who are unfamiliar with the company. The Iron Yard offers programming classes at 15 different campuses at different times each year. I am currently a member of Cohort 7 at the St Petersburg/Tampa campus, and am spending 12 weeks learning Ruby on Rails. The program is immersive and therefore it is taking us from little to no knowledge of how programming and Ruby work to being able to enter the job market as a junior developer.</p><p>Now because one of the ways that I learn best is to teach or reframe some of the broader concepts within an area of study I’m going to explain how I have come to view how Classes and Methods work in Ruby:</p><p>I view code as a sort of factory filled with incredibly literal and slightly stupid gremlins. These poor little guys can only follow really basic instructions and have such short attention spans that every work station has a series of instructional books on the wall. To me, these books are our classes. Then each chapter of the books, and all of the instructions therein, are our methods. Let me explain.</p><p>Let’s say we are writing a program that is used to manipulate a personnel database. You want to be able to know what a person is, create a new person, view all people in the database, view a single person in the database, delete them, search for them, and edit them. All of these are different tasks that will be run through your ‘factory’. For the sake of this example, we’ll say that there is only one little gremlin working in your factory, and he is tasked with doing everything needed for that day. If it makes you feel better, you could imagine that all gremlins working in the factory are able to complete every task and that they’re just waiting around for a job to do, but I am going to stick with the first scenario.</p><p>For this scenario, you have will have most likely made two classes which might be named something like <strong>People</strong> and <strong>Database</strong>. The People class is fairly simple and only includes some methods that define all of the characteristics of a person. The Database class holds a method for every task associated with the manipulation of the database (edit, delete, add, etc). So now our gremlin (let’s call him Hank) has two books at his station. One is a thin one called people, and the other is a slightly larger book called Database.</p><p>Hank gets a job handed to him (this is our code that runs the program and is outside of our classes) telling him that someone needs to see a list of all personnel in the database. Because Hank is a slow little gremlin, the job has a section listed below that tells him exactly which book and chapter he needs to reference to get the job done. In this case, he reads his job sheet and it tells him to grab his Database book (class) off of the shelf. He references the job sheet again and flips to the chapter titled listing all personnel (method). Hank is now looking at a step by step instruction for how to present a list of all personnel in the database that Hank’s little brain can handle. He then follows those steps and in a short amount of time a full list of all personnel is rolling out of his station and presented to the end user to view.</p><p>This is handy, because no matter how many different ways or reasons Hank has to print off a list of all employees, he only needs to have his one book with its very helpful chapter. The same concept applies for any other task that he might have to do at his station. This really cuts down on the length of the individual job sheets (again, our actual code) that come to his station.</p><p>Now I understand that as you progress you begin to see less and less of what actually is actually happening inside all of your classes and methods, especially when you start working through separate frameworks that are doing some of this work for you. But there will always be a factory, and Hank and his gremlin buddies will still be slaving away in the background of your code. That’s why I felt it was important to cover Classes and Methods in my first mini lesson. I know it helps me to write it down, and I hope that it helps you. Thank you for reading!</p><p>-Patrick Miller</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51c4459bc0af" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>