wroc_love.rb

Steve Klabnik

Steve is a teacher, aspiring digital humanities scholar and open source developer. He maintains the Hackety Hack project, which allows anyone to learn software development via Ruby. He was a Ruby Hero in 2011 and is involved with many Ruby-based open source projects. He's currently writing a book about APIs titled Get some REST.

Designing Hypermedia APIs

Rails did a lot to bring REST to developers, but its conception leaves the REST devotee feeling a bit empty. "Where's the hypermedia?" she says. "REST isn't RPC," he may cry. "WTF??!?!" you may think. "I have it right there! resources :posts ! What more is there? RPC? Huh?"

In this talk, Steve will explain how to design your APIs so that they truly embrace the web and HTTP. Just as there's an impedance mismatch between our databases, our ORMs, and our models, there's an equal mismatch between our applications, our APIs, and our clients. Pros and cons of this approach will be discussed, as well as why we aren't building things this way yet.

Piotr Sarnacki

Rails contributor (#17 by number of commits) who greatly improved Rails Engines during Ruby Summer of Code in 2010 and afterwards. Freelancer. As an enterpreneur he recently launched stoliczku.pl which is a Rails 3.1 application that allows you to book a table in various restaurants. It uses Sproutcore under the hood to run rich client that helps managers control their restaurant business. Working with Rails since 2005.

Rails: past, present and the future

Rails is getting older and there was a lot changes along the way, including The Big Rewrite from 2.3 to 3.0. Was it worth it? Where is rails heading now? In this talk I will try to address these and other questions connected with rails status and progress.

Jim Gay

Jim is the Lead Developer for Radiant CMS and is a prolific contributor to it and many open-source projects. At Saturn Flyer LLC he's built numerous Radiant sites, custom applications, and award winning graphic design. Jim is the author of Clean Ruby, a yet-unreleased book about writing better object oriented Ruby code and using the DCI architecture. He's been a co-host of the Ruby 5 podcast and has been professionally building Ruby and Rails applications since 2006.

It's Business Time

Discover a complement to your MVC ways that puts your business needs in plain view. Learn how DCI (Data, Context, and Interaction) allows you to keep your application architecture lean by turning your use cases into executable code. Make your application easy to read, easy to understand, and easy to reuse.

Roy Tomeij

Roy Tomeij is co-founder of 80beans in Amsterdam, where he takes care of front-end architecture using an agile approach. He loves front-end meta languages like Haml, Sass & CoffeeScript because they are DRY, produce quick results & lead to better maintainable code. Roy has nearly seven years of professional front-end experience in Rails projects.

Modular & reusable front-end code with…

Most Ruby developers use Rails for their everyday projects. Often they toy around with front-end themselves or outsource it, ending up tangled in a web of css-all-over-the-place.

Keeping your front-end code clean is hard. Before you know it you're suffering from CSS specificity issues and not-really-generic partials. Find out how to keep things tidy using the HTML5 document outline and modular Sass & CoffeeScript, for truly reusable code.

Piotr Szotkowski

Piotr Szotkowski is an assistant professor at Warsaw University of Technology (where he happily sneaks Ruby, EventMachine and newfangled database systems into the creaking world of twentieth-century academia), a Ruby developer at Rebased and an alumnus of Mendicant University.

He's also a long-time contributor to various open source projects for the civic sector and co-organiser of NetWtorek - monthly NetTuesday meetings of people from the NGO/non-profit and IT sectors, as well as SocHack - quarterly 48-hour hackatons for worthy causes, in coordination with Random Hacks of Kindness, Open Data Day and Open Education Week

Decoupling Persistence

‘When I open up a Rails project and the models dir is full of 100% ActiveRecord classes I shudder. Model ≠ Persistence.’ — Ben Mabey

From DCI to presenters, from Uncle Bob’s architecture talk and Avdi Grimm’s upcoming ‘Objects on Rails’ book to the proliferation of (competing? complementing?) database systems, it seems the time has come to seriously consider decoupling our objects’ persistence from the rest of the application.

This talk – after describing the general vices of strong object/database coupling and the all-too-usual rails g model-driven development – covers the various approaches to separating the objects’ persistence layer, along with their virtues (cleaner, simpler tests! backend independence! no RDBMS-related shortcuts impacting the design!) and potential vices (performance? perceived compexity? YAGNI?).

Piotr Solnica

When Piotr’s not writing great code, he’s writing awesome code. As an open source enthusiast, he has been working as a web developer for over 6 years, including more than 3 years of professional experience with Ruby-based technologies, working with many international agile teams. Piotr is an unobtrusive JavaScript evangelist, an HTML/CSS purist and a Linux geek, too. During his free time Piotr supports open source software. He is a DataMapper core team member.

DataMapper 2

I would like to describe all of the pieces that we're working on: new relational algebra engine, new model definition and introspection layers, new validation library and other things that will become part of DM2 (better migrations, UoW library, optimizer layer). The talk would be in the context of a better way of handling business logic in Rails apps.

Nicolas Barrera

DrummerHead is the lead Designer working at Cubox and has years of experience being a certified Expertologist. You can call what he does UX, UI, IA, Usability, Accesibility, Front end; or any other hyped acronym you want. In truth, he is just the bridge between information and humans getting what they want in the fastest and best way possible.

Whatever you do, if you do it with love and passion, it will come out fine and dandy!

Nicolas Barrera: Responsive Web Design

Responsive Web Design is all about having the same content visible in all devices, from tiny mobiles to huge monitors, preserving proper readability and adapting to the medium. It also entails a new way of creating content, in which interaction between designers and programmers is more important. In the Ruby world programmers generally feel proud of being "agile", however when you zoom out, you see that the interaction between designers and programmers is more waterfally than you'd want.

In the talk I will present the concept of responsiveness and teach with examples how to make a layout responsive with the one-two punch of fluid layouts and media queries. I will also show how to make the interaction between designers and programmers be truly collaborative and not just a pass-me-down PSD from the designer to implementors and programmers.

Piotr Szotkowski, Steve Klabnik, Nick Sutterer, Jim Gay

Rails vs. OOP

A lot has been said recently about the topic of Rails and OOP. We consider this issue very important in our community. This fight is all about the recent OOP movements in the Rails world. There are quite a few problems that people focus on and quite a few proposed solutions.

We want to cover topics like: persistence and domain logic separation, DCI, backend/frontend separation, "Objects on Rails", TDD and unclebob's "Rails is not your app". Each of this approaches tries to solve the problem differently.

We gathered a group of people that have some interesting opinions on this topic. We want to put them on stage and start the discussion. There will be questions prepared before the discussion, to ensure that we go through all of the important topics. Additionally, we’re planning to have questions from the audience.

Testing fishbowl

All you wanted to question about testing but was afraid to flame. In this heated debate where everyone can participate we may focus on the following discussion starters: cucumber vs. object oriented tests, tdd vs. bdd, full-stack vs. frontend/backend testing, steak vs. bbq, rspec vs. minitest or just no-tests drama.

Discussion will be conducted under rules of a Fishbowl.

Tim Lossen

Tim really enjoys talking about himself in the third person. Not. He lives in Berlin with his girlfriend and two lovely little daughters. Tim is deeply in love with Ruby and recently helped to organize Euruko 2011. He works as backend engineer at social gaming startup Wooga. At night Tim likes to go down to the basement and hack on secret hardware projects like Superglobe or Evercube.

Dirkjan Bussink

Dirkjan Bussink spends his working days between cows in the scenic country side of the Netherlands at Nedap. There he works on software and sometimes even plays with actual hardware devices. As one of his hobby's he likes tinkering with Rubinius and has been an active contributor for the last three years.

JRuby vs. Rubinius (Fight)

After breeze introduction of the aforementioned projects you'll witness fighters struggling in a combat of questions. Is it speed and performance that makes difference? Or tooling and extensibility that convinces judges? Maybe there'll be a KO on concurrency and production readyness?

Martin Sústrik

Martin Sústrik is an expert in the field of messaging middleware. He participated in the creation and reference implementation of the AMQP standard. He has been involved in different messaging projects in the financial industry. He is a founder and one of main contributors to the 0MQ project. Currently he's interested in integration of messaging technology with operating systems and the Internet stack. He lives in Bratislava.

ØMQ: A way towards fully distributed architectures

This talk covers ØMQ basics.

Nick Sutterer

Nick Sutterer is proud to be a member of the Ruby open source community. His Cells and Apotomo projects have been bringing increased view modularity and event-driven programming to Rails for years. He has enjoyed attending, and speaking at, Ruby conferences around the world. Buy him a beer sometime, and with very little prompting, he will tell you why there should be no such thing as a double-render error, why you should not confuse your models with your resources, and how to play a mean bass in a punk rock band.

It's All About Respect!

Open-Source is driven by innovation from the people. Controversial ideas often change the way software developers write software. It can be a tedious, awkward task to promote, develop and maintain such projects. But in the end of the day it feels just great, doesn't it?

Florian Gilcher

Florian Gilcher is enjoying the ruby community since 2004. After using Rails most of the time, he is now involved in the Padrino project. He contributes to the Ruby community by working on the german ruby website and by providing a german discussion board. During day, he runs a consulting company specialized in backend systems.

Fear of adding processes

In object-oriented programming, there is a well-known anti-pattern called 'Fear of Adding Classes'. It describes the fear of solving a problem by adding another class because of the (often wrongfully) perceived added complexity. With systems moving towards a distributed nature through the usage of external services, a similar pattern can be seen: the fear of adding dedicated components, mostly independent processes to the system, because of the fear of added management overhead through doing so.

Michał Taszycki

After leaving the corporate universe and developing a few computer games (like Motorstorm and Saints Row 2) for the PS3, XBOX and PC, he entered the Ruby World. Today, he is making delicious software at Applicake, managing projects and training fellow programmers during Code Retreats. He enjoys pushing people out of their comfort zones and into new rewarding experiences. He can talk for hours about how seemingly unrelated skills (such as running, dancing or juggling) can help you become a better programmer.

Programming Workout

Times are changing... Technology is moving forward... Command line tools are becoming obsolete... Programmers today don't need to touch type... Using mouse to copy and paste is perfectly fine... You can always look up those design patterns on the web... Your IDE can do a lot of things for you so you don't need to think... Can you feel that? Can you feel that this is TRUE? Then stop being UNPROFESSIONAL and think again!

In this talk I'm gonna convince you that learning seemingly obsolete skills can have huge impact on your productivity. I'll show you how those skills and other seemingly unimportant factors can impact your career. I will help you to find a way to improve them in order to become a better programmer. I'll also show you tools that can facilitate this process. You will either leave this talk with strong resolution to level up, or curl up in your comfort zone with your lovely mouse and IDE. I will show you how PROGRAMMERS WORK OUT.

Ralph von der Heyden, Georg Leciejewski and Jan Kus

Ralph and Jan are web developers at Railslove, Georg is working hard to revolutionise invoicing with SalesKing. All three have known each other for years and have worked on a wide range of projects. Along the way, they’ve gained extensive experience on all levels of web application development and how to found and maintain profitable web businesses, without disregarding the challenge to have some serious fun along the way ;) They love all things cool and nerdy, but their fields of expertise are API design, Ruby, Rails, project management, and payment solutions. As developers and business founders they've had their fair share of falling into the pits of application development and would now like to share some of the insights they've gained from past mistakes.

Get out of the trap!

In our talk we share some of the most interesting, absurd, or funny insights and moments we experienced in our past couple of years. As developers and business founders, we present the best of our own mistakes and show you how we got out of the pits we fell into. Believe us, we’ve been there as well and, hopefully, attending our talk will help you not making the mistakes we already made for you ;) It will be serious fun! The talk will cover both technical and other subjects.

Krzysztof Kowalik

Krzysiek is a 23 years old freak from Poland, easy to recognize by his strange hairdos. He is an Open Source contributor, BSD and Arch Linux enthusiast, and inline-skating addict. He lives in Montevideo and works for Cubox, crafting awesome Go, Ruby, Python, and C code, and implementing clever ideas. He plays with *nix systems since got his first computer being a typical optimization monster and The Unix Philosophy evangelist. Now his favorite pastime is MQ and distributed programming. Recently all his efforts goes into WebRocket project - a new scale, distributed and open source websockets broker.

Get out of the trap!

Oh gush! There's more and more people visiting your web app, what you gonna do! Many instances connected through single database or cluster! It may work... but you do it wrong! Don't message through shared data, share the data through messaging! During this talk you gonna find out how to design and build cloud-ready distributed web applications correctly, how to scale them according to your needs and finally how to test and deploy them fast and easily. You have to see this!

Michał Czyż

Michał Czyż has been working professionally as a web developer since 2007, and from the very beginning of his professional career, his choice is Ruby on Rails. In 2010 he became a team leader, helping his teammates to follow the path to improvement. These experiences gave birth to several open source, documentation and testing solutions, that are used with great success in Selleo, where he currently works. Michał helped organize code retreat in 2011 and he is also one of the core members of SRUG - a local Ruby users group community, where he is known for evangelizing best practices.

User perspective testing, using Ruby

I would like to share our team experience in testing and tell the story of "how we get there" - successive stages of evolution (not writing tests at all, rspec, rspec story runner, cucumber). I will show you how we are doing it now (rspec + capybara + our custom dsl) and why we took more object oriented approach, taking user's perspective for writing integration and acceptance tests. I'll also tell you how we integrate all of this in form of documentation in applications we make.