Ruby community pioneers.
We don’t stay in “Kansas” although there is nothing wrong with Kansas. Tradeoffs.
Great frameworks are extracted, not invented.
Rails driving vision is hyperlinked documents.
The web is the platform, not a delivery system.
Flash is a failure, flash clones are failures, apps will ultimately fail.
HTML and the web are the past, present, and future.
Speed is what is most important to users.
Speed is achieved via extensive, aggressive cacheing.
Russian doll approach.
How Shopify Scales Rails
Mostly above my head.
About scaling, of course, deployment, configuration. Tweaks.
Workers, Redis, Resque, Unicorn.
Good summary here: https://gist.github.com/naoyamakino/5505169
Talk here: http://www.youtube.com/watch?v=j347oSSuNHA
Nobody Will Train You But You
Disappointed with this talk.
Copy and memorize a good tutorial.
Memorization is undervalued.
Write on notecards what you look-up on SO.
Simple and Elegant Rails Code with Functional Style
This talk was utterly boring.
I remember literally nothing from this talk. Really excited by the topic title, but it did not live up.
Front-end Testing for skeptics
This was a good talk.
Epic full stack testing post: http://blog.mattheworiordan.com/post/4701529828/full-stack-integration-testing-with-rails-3-cucumber
Real Time Rails
Another good speaker.
This talk was mostly about deployment, which I’m pretty light on, so above my head for the most part.
Still interesting ideas.
Puma as a web server.
Building Extractable Libraries in Rails
Treat you lib directory like a temple.
Be ready to extract logic in lib to a gem at any moment.
Doman Context Interaction. Awesome.
Fake classes as test doubles. Or structs as test doubles.
Lame talk about how being a “Volatile” is good, being a “Stable” is bad, but not really, but yes really.
There is still need for server side processing.
Rails Vs. The Client Side
Very good talk.
Most current innovation is on the client side.
Where does the app live: client-side or server-side? Lines becoming meshed.
Don’t use Backbone.
The Magic Tricks of Testing
Very cool talk.
One of the most practically useful talks in the conference, along with the Pry talk.
Don’t conflate queries with commands.
Space capsule idea for object testing.
Do not test internal object messaging.
Do not test outgoing messaging.
Test incoming messages, receiver is always responsible for test verification.
Test interface only.
Avoid temptation to over-specify just because you can.
Test doubles should stay in sync? #need to look further into this
From Rails to the Web Server to the Browser
Not a fan of this talk. Pretty dull.
An explanation of Rack’s function, request-response cycle.
Other web servers.
What Ruby Developers Can Learn From Go
Pretty good talk.
Go has a very strong agenda.
Treats errors as normal.
Methods have multiple returns.
Encourages use of lots of well-defined packages and libraries.
Learning new languages gives you context for appreciating features in other languages.
Learning new languages allows you to abstract what’s common to all languages.
Ruby Libraries Important For Rails
This was a tutorial section with the great Michael Hartl.
This tutorial was way basic, for very new rubyist and it was hard to keep interest.
Pry – the Good parts
Awesome talk, really good.
Pry is a clear step up from IRB and print debugging.
My takeaway is I need to start using Pry now, get over the slight learning curve and use it.
James Duncan Davidson
Somewhat interesting talk, I guess, not really technical more about the possible unrecognized global impact of our efforts and his travels. Or something.
Firefighting on Rails
Really fascinating talk.
One programmer, who happens to be a volunteer firemen, taking initiative to develop a most basic app to upgrade the archaic system in place for alerting firemen of emergencies.
Emphasis here was it doesn’t have to be pretty to be useful, he built his system paying attention to only the most critical minimal requirements, all crushed together in one weekend, and it had a significant impact on his work, and the ability of firemen to respond to calls.
Really inspiring. I want to look into the repo and see if I can help.
Your First Rails Pull Request.
The speaker went over all the details necessary to make a pull request to rails, shared his particular story, talked about motivation for doing so.
Stressed how much he learned about rails by putting the effort into doing a pull request.
It’s not easy though, there are no easy issues.
If you do the work, your chances of getting accepted are high.
But you could get rejected.
But you still win by learning in depth about Rails.
You can also submit fix issues with one of the many supporting gems.
Use easy way set-up
Vagrant. Virtual Box.
DevOps for the Rubyist Soul
Good speaker. Interesting talk.
Deployment focused, so just tried to absorb what I could.
Puppet and Puppet Configuration.
How to Talk to Developers
By far the most awesomest talk, performance-wise, of the conference.
Mostly tips on public speaking.
Keep forearms at 90 degrees. One hand in pocket is okay, Two is not.
Better summary -https://gist.github.com/jamesgary/5504200
Singing Happy Birthday.
TDDing iOS Apps for Fun and Profit with RubyMotion
Really loved this talk.
Went through the steps of using RubyMotion to build a simple to-do list app
You get to use Ruby to build and iOS app (mostly). How cool is that?!
My big takeaways:
- I need to find out everything I can about cacheing.
- I should learn more about deployment.
- I want to attend RailsConf in 2014. Its a great way to get a glimpse at the state of the industry from the best minds.