<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>rails on Senior Software Engineer Learns Functional Programming</title><link>http://llcawthorne.github.io/tags/rails/</link><description>Recent content in rails on Senior Software Engineer Learns Functional Programming</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 Jun 2017 00:00:00 +0000</lastBuildDate><atom:link href="http://llcawthorne.github.io/tags/rails/index.xml" rel="self" type="application/rss+xml"/><item><title>AWDWR 5.1 - 03-05 - Theory</title><link>http://llcawthorne.github.io/posts/awdwr51-03-05-theory/</link><pubDate>Mon, 05 Jun 2017 00:00:00 +0000</pubDate><guid>http://llcawthorne.github.io/posts/awdwr51-03-05-theory/</guid><description>&lt;p&gt;Chapters 3 through 5 focus on a little bit of theory before we get to
building the tutorial application.&lt;/p&gt;
&lt;h3 id="chapter-3---the-architecture-of-rails-applications"&gt;Chapter 3 - The Architecture of Rails Applications&lt;/h3&gt;
&lt;p&gt;Chapter 3 jumps into explaining MVC.
It&amp;rsquo;s a pretty simple concept. MVC stands for Model, View, and Controller.
The &lt;em&gt;model&lt;/em&gt; is responsible for the state of the application, often the data
you store in a database. It&amp;rsquo;s also more than data; it enforces the business
rules that apply to your data. The model is both a gatekeeper and a data
store. The &lt;em&gt;view&lt;/em&gt; is responsible for generating some type of user
interface. The view&amp;rsquo;s job is done once the data is displayed.
Multiple possible views of the same data are a common case. The
&lt;em&gt;controller&lt;/em&gt; orechestrates the application. Controllers receive events from
the outside world, interact with the model, and display the appropriate
view. The book provides a simple diagram:&lt;/p&gt;</description></item><item><title>AWDWR 5.1 - 02 - Instant Gratification</title><link>http://llcawthorne.github.io/posts/awdwr51-02-instant-gratification/</link><pubDate>Thu, 18 May 2017 00:00:00 +0000</pubDate><guid>http://llcawthorne.github.io/posts/awdwr51-02-instant-gratification/</guid><description>&lt;p&gt;First I&amp;rsquo;ld like to say sorry the images are a little big. Not used to
screencaps on this retina Macbook.&lt;/p&gt;
&lt;p&gt;So, I fixed my mistake from last time. I had originally installed ruby via
homebrew, but now that I&amp;rsquo;ve read up on rbenv, it seems a lot nicer than the
old rvm, and I might want multiple versions of Ruby on my home PC. So I
uninstalled Ruby 2.4 and went with &lt;code&gt;brew install rbenv&lt;/code&gt; and then used
it to install the latest Ruby. I see why the book authors prefer it over
RVM now. It&amp;rsquo;s a lot less invasive than the old RVM.&lt;/p&gt;</description></item><item><title>AWDWR 5.1 - 01 - Introduction</title><link>http://llcawthorne.github.io/posts/awdwr51-01-introduction/</link><pubDate>Tue, 16 May 2017 00:00:00 +0000</pubDate><guid>http://llcawthorne.github.io/posts/awdwr51-01-introduction/</guid><description>&lt;p&gt;So, what do I have to blog about? I&amp;rsquo;m always trying out new stuff and reading
books, so I figure I&amp;rsquo;ll talk about that. I happen to have just gotten a
beta copy of
&lt;a href="https://pragprog.com/book/rails51/agile-web-development-with-rails-5-1"&gt;Agile Web Development with Rails 5.1&lt;/a&gt;
and since my Ruby and Rails
experience from my résumé is a little rusty, I figure I&amp;rsquo;ll
read that and blog about the experience. Starting this site using Jekyll
has made me think about Ruby lately anyway. It&amp;rsquo;s been many years since I&amp;rsquo;ve
read &amp;ldquo;Agile Web Development with Rails&amp;rdquo;, and I think it was the version that
covered Rails 1.2, so this should be a pretty new experience for me; both a
great refresher and an introduction to what is new in the Rails world these
days.&lt;/p&gt;</description></item></channel></rss>