RUG::B

".. and then cache the hell out of it!" This is usually how the talk ends when it comes to rails performance tips, but in reality it is where the fun starts. This talk goes way beyond Rails.cache, it explores layered caches, discusses the CPU cost of marshaling, the latency even Memcache adds and how to dodge the unavoidable stampedes that invalidating your caches will cause. This is the tale of how to survive half a billion requests per day with Rails and MySQL (hint: don't query it).

For many developers, design does not come naturally. Lucky for you, you have ME! (Congrats on your recent acquisition of my friendship and knowledge.) Let me be the first to tell you design isn't as complicated as it may seem. It all boils down to three basic strategies that we'll discuss in this session. First, we'll go over the fundamentals of grid structure. This will include how to set the content to maximize space allowance, and create an appropriate hierarchy to convey your content based on importance. Second, we'll take a brief trip down color-theory lane. Theory? Yes, there is theory behind all UI color choices and you'll learn what that means and why. Last, get ready, this is the big finale; we're going to talk type! Type is a huge part of design and is often neglected or simply thought of as the alphabet. Each typeface tells a story and you want to make sure you're picking one that's right for your message.

If all of this sounds over your head, fear not, I'll hold your hand and go slow. This session is for design beginners, people who have an interest in design, or just those of you who'd like to be able to understand your own designers better.

Refinements are an official part of Ruby now. They are pretty new and have some issues, so they hardly get used as of today. Let's take a look at some uncontroversial examples of syntactic sugar, which could easily be implemented using refinements.

I would like to tell the story of one of our(6Wunderkinder) recent database migrations. We were migrating from our own hosted PostgreSQL to AWS RDS PostgreSQL. I'm going to explain why we failed the first time we tried and what changed the second time. I'll show you the tools we've used to make sure we don't fail another time - I think they are pretty cool!