Rails Israel presented by People and Computers Israel, posted on YouTube by Raphael Fogel, not produced by Confreaks, LLC.
Large software projects stand a slim chance of ever being finished. Compared to work created in other fields, the ones that do survive lead very short lives. It's not uncommon for a building to stand well over a hundred years. Music is still relevant hundreds of years after it's created.
Even automobiles provide decades of use. But as software developers, we're extremely lucky if we create something which doesn't have to be replaced within five to ten years. How do we as software developers create software that can survive? What can we learn from surviving artifacts in other fields?
ֿThis talk will explore the idea that, like living organisms, the key to a long lasting system is that its components are constantly replaced.
This talk explores numbers in Ruby: integers, arbitrary-precision integers, floats, arbitrary-precision decimals, and rationals.
We are going to cover implementation in MRI and relate some abstract mathematical properties of numbers to the their concrete counterparts in Ruby, with understanding and emphasis on limitations and caveats.
What happens when you not only ignore every coding advice you've ever got but willingly do the opposite. Go against every guideline you have encountered, write code that pretends to work.
* Prepare for the strangest code slides yet.
It took a while, but Rails 4 finally got out the door earlier this
year. Rails has never been a project to rest on its laurels, and X.1 releases always have tons of new goodies.
In this talk, Steve will give you a sneak peek at what's been going on with Rails lately, as
well as some ideas as to where it may go in the future.
The story of the quest to make `bundle install` faster; in which Rubyists around the world inadvertently DDoS rubygems.org, witness its ignominious death, and vow to rebuild it from the ashes stronger than it was before.
Then, a tour of the changes; why is Redis so much slower than Postgres? Marvel at the gorgeous metrics and graphs used to measure and optimize; gasp in delight as we track, live, exactly how many Heroku dynos are needed. Finally, a happy ending: today, the server responds to requests TWO ORDERS OF MAGNITUDE faster than it did before.
Infrastructure as Code has been a popular industry buzz-phrase, but our initial investigations left our head spinning with so many terms and concepts. Eventually we settled on using Chef, but it wasn't as easy as we initially thought.
The purpose of this talk is to highlight what sorts of problems we were hoping to solve with Chef and how we started with small concepts and iterated on them to come out feeling like we were Master Chefs. By the end of this talk, you should feel comfortable enough with Chef to go home and start cooking.
Learn and develop yourself and your team through side projects, week-end projects & random hacks. How to get the most of these kinds of projects and how the RoR community can help you create beautiful stuff.
Ruby applications are becoming more complex and unwieldy (think MonoRails). An increasing number of us are trying to address this by separating our apps into gems without knowing best practices on how to write APIs or how to manage dependencies and versioning. The discussion we often have around good APIs should not stop with Ruby OO design, but should also consider the public APIs of gems.
This talk is intended for gem authors and users. It will share though many practical examples using the Ruby driver to MongoDB 1) Principles of good gem API design, 2) How to make your gem API optimal for users and how to best use the API of a gem, 3) Guidelines for introducing and anticipating gem API changes and managing dependencies.
The story of all the pitfalls we had while transferring FTBpro.com from the good old web to a Backbone single page application... and all the great solutions we've came up with
All you need to know to supercharge your Rails application using various levels of caching.
The pursuit of losing weight is something that people always try to achieve; the same thing happens with web apps so I'll show a plan to reduce that extra fat on the browser that we always left there.
I'm gonna explain a couple of effortless rules to make your views faster from good code practice for views to write better CSS and JS, how to load them correctly and 2 or 3 tricks that I found particularly attractive. And last but not least all of this will end in a clean code structure with happy Dev team who will do any change effortless. There's a lot of things devs may think know, but there's a lot fat to cut off.
Historically, many Ruby on Rails applications used MySQL. But over the last few years, thanks partly to Heroku and partly to the politics of MySQL/Sun/Oracle, more and more people have been using PostgreSQL in their projects.
This talk is an introduction to PostgreSQL from the perspective of a Rails user. What is different? What new capabilities can I enjoy? How do I use PostgreSQL's advanced transactions, server-side functions, custom data-integrity checks, and other features to make my Rails app more expressive and efficient than would be possible with MySQL?