We are proud to announce
-
Konstantin Haase
As current maintainer of Sinatra, Konstantin is an Open Source developer by heart. Ruby has become his language of choice since 2005. He regularly contributes to different widespread projects, like Rubinius, Rack, Travis, Rails and MRI. He currently holds the position of "Berry Sparkling Lord" at Travis CI.
We don't know HTTP
Everyone knows HTTP! Well, that's not entirely true. There are large parts unknown to most web developers, well, even browser vendors, as it seems, and the wheel is invented over and over again to fix issues we wouldn't even have, if people would make use of their toolbox. There are two options to fix this: You can reading RFC 2616 over and over again or you can listen to this highly opinionated talk exploring facets of HTTP that most developers are probably not too well aware of and how to make best use of it. -
Yehuda Katz
Yehuda Katz is a member of the Ember.js, Ruby on Rails and jQuery Core Teams; he spends his daytime hours at the startup he founded, Tilde Inc.. Yehuda is the co-author of the best-selling jQuery in Action, Rails 3 in Action, and is a contributor to Ruby in Practice. He spends most of his time hacking on open source--his main projects, along with others, like Thor, Handlebars and Janus--or traveling the world doing evangelism work. He blogs at yehudakatz.com and can be found on Twitter as @wycats
-
Bryan Liles
Bryan Liles
-
Elliott Kember
Elliott Kember is a Rails/JS/CSS developer, based in Bath, England. I wrestle helicopters and fly crocodiles
Rails and Crew
Rails is rad. Rails plus other things can only be more rad. Join Mad Cap'n Kempers on a wild ride across the oceans in search of treasure. Hoist the Node sails, weigh the Mongo anchor, and... something something Backbone, or whatever. -
Steve Klabnik
Steve Klabnik
-
Jim Weirch
Jim Weirch
-
Adam
Adam is a professional yack-shaver at Mint Digital, but he's supposed to be a Rails developer. From dotfiles to dev tools, there is nothing that diverts his attention quite like fixing something that wasn't really broken in the fist place.
Bug Requests and Pull Reports
Getting people to contribute to open source can be hard. This talk looks at Powder, a simple Ruby gem, and some of the ways we tried to to turn bug reports into pull requests. -
Phil Nash
Phil is a developer living and working in London. He's been writing HTML since the <font> tag was cool. He plunged into the world of Ruby and Rails 4 years ago with Mint Digital, and in between app development wishes he had more time to spend on open source. Away from the computer he plays rugby, drinks beer and loves music festivals.
JavaScript in the next generation
JavaScript, once a "toy" language is now driving the interfaces of the most popular sites on the web. We've come a long way from snowflakes drifting over a site around Christmas time, now creating powerful client side applications. But JavaScript can do more for us than taking the heat off the server. There is a new generation of interfaces emerging in our browsers that will allow us to do even more interesting stuff in the client side of our apps. This talk will cover some of the interesting integrations between browser and device that are becoming available to us through JavaScript. From existing APIs, such as Geolocation, to bleeding edge stuff like the Battery API (woo!) or getting input from cameras or microphones with getUserMedia, we'll discover how browsers in the near future will shape users' interactions with our apps. -
Piotr Sarnacki
Passionate Ruby developer from Poland, [rails contributor](http://contributors.rubyonrails.org/contributors/piotr-sarnacki/commits) and open source lover. I'm working at Mixbook.com, and I co-founded Polish table reservations startup Stoliczku.pl. I was participating in Ruby Summer of Code 2010 with "Rails 3 mountable applications" project.
Using Rails without Rails
Rails got much more modular after 3.0 rewrite. But do you know how to use specific rails elements outside Rails? What if you would like to use ActionView with some other library (like webmachine)? Have you ever needed to render view with layouts outside of the rails stack? Or maybe you wanted to build some kind of system that fetches templates from database rather than from files? Router anyone? You know that you can use it outside rails too? In this talk I will dive into Rails internals and will show you what's there and how you can use it outside rails. Although I will focus on using those parts standalone, this knowledge will most likely help you also build your apps if you ever need something sophisticated that requires modification of regular rails behavior. -
Peter Berkenbosch
Peter is an early Spree adopter, launched a SpreeCommerce web-shop for a client back in 2008, and wrote a number of extensions. Static Content was the first and the most popular one. It's even an official Spree extension now. Currently he is the owner of PeRo ICT Solutions, a agile web-development company that is focusing on Spree implementation and development. Early 2012 he launched [SpreeCasts](http://spreecasts.org) where he is sharing Spree knowledge through screencasts.Spree from the trenches
his talk will try to give you some insight in a day at the office while implementing a custom SpreeCommerce web-shop. Showing the tools of the trade and discuss choices made while implementing designs and developing extensions. Utilizing the powerful SpreeCommerce eco-system and show you how to implement designs, extend default behavior using custom extensions and avoid some pitfalls.
The following subjects will be addressed:
- Theme development using Deface (or not)
- Test Driven Extensions
- Pitfalls to avoid
- Spree Best Practices -
Bartlomiej Niemtur
Passionate programmer who dabbles in many arts. Likes TDD and doing things the right way. Enjoys front-end and design too. Experiments with Haskell and pure functional programming. Known to play clarinet.
Better State Management
My talk description has run away to vimeo https://vimeo.com/41094993 So I will use this space to tell you of my other hobby, which is going to conferences. Last year I've been to Euruko, NodeCamp, onGameStart and RuPy; I've noticed a pattern, there are more and more functional programming references. This is why I'd like to hear a talk that would wrap up the topic of functional programming. -
Corey Donohoe
Hacks and Operations at GitHub.
The Amen Break
The Amen Break is one of the most widely sampled drum solos ever. Our Amen library is named after it and used for sampling all sorts of metrics around GitHub. In the talk I'll dive into how we use amen to map to something like Coda Hale's Metrics Library from ruby. It will also cover how we dumbed everything down so adding new metrics is trivial. I'll also cover how we store it in graphite and the SaaS landscape around doing similar things.
-
Aleksander Dabrowski
Aleksander Dabrowski is a Ruby developer and advocate. He has worked in a variety of start-ups and in a marketing agency. He co-organises Warsaw's Ruby User Group. Aleks is also the author of rubysfera.pl, the leading Polish blog focused on Ruby and Rails. He likes to speak at Ruby developer events and is very passionate about sharing his knowledge with others. Along with using and contributing to open source software (recently mostly travis-ci.org), Aleks particularly enjoys deleting ugly code, and in his spare time repairs cars.
Sinatra autopsy
Sinatra is dead, as a dead fish. We killed him during abordage. Now we can investigate his body, see his guts, and check what he has inside. Since medieval, autopsy of dead corpse was the best way of learning how human body works. We will use the same technique, examinating Sinatra, to learn how to write better code. With its 1740 lines of code, this piece of software is great example of Ruby application. We will see what jewels are hiding in its chest, notice some good practice, but also we will take a look at bad and stinky parts. Since Aleksander's only commit to Sinatra was concerned documentation, he is the right person to lead the autopsy. He will look at Sinatra with the fresh eye. Konstanin Haase won't get any hurt (probably).
-
Julien Biezemans
Julien is a fervent BDDer who loves writing code, building well-crafted conducive software as well as sharing knowledge and techniques with other passionate people. He’s been freelancing for more than 8 years in Belgium, mostly developing web applications in Ruby, PHP, Perl and – more recently – JavaScript. Julien is also a member of the Cucumber core team. He is the lead developer on Cucumber.js, the JavaScript implementation of the famous BDD tool. * Github: jbpros * Twitter: @jbpros * jbpros.net
Cucumber.js: Cuke up your JavaScript!
We're now living the golden age of JavaScript. An increasingly number of people are seeing it as a complete programming language. Therefore, agile development practices are now being adapted and applied to JavaScript code production.
Behaviour-Driven Development is a second-generation agile methodology with a strong focus on communication. In BDD, specifications are expressed through examples in the form of scenarios.
Originally written in Ruby, Cucumber is popular a tool for automating and validating a system against its scenarios.
A year ago, native JavaScript BDD solutions similar to Cucumber were almost inexistant. Yet the need for it was manifest. It didn't take me long before I started hacking on a port of the virtual cucurbitaceae and joined the Cucumber core team.
Cucumber.js is a native JavaScript implementation of Cucumber. It is a strict and robust port that can run on any JavaScript environment. It runs on Node.js as well as within any browsers, making it virtually serviceable against everything producing JavaScript and HTML (Node.js, Ruby on Rails, PHP, .Net, etc.).
This is an introduction to Cucumber.js. After briefly exposing the history and goals of the project, I'll demonstrate how to write features and scenarios, step definitions, hooks, support code, how to invoke Cucumber.js from both Node.js and browser environments. And of course, you'll see how to integrate it with your Ruby and Rails projects, because - yes - it works well with them.
-
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.
Persist, Little Objects!
Object persistence in Ruby is a tricky subject – everyone knows how to do it (‘simply use an ORM, plug it into a relational database and you’re done!’), most know the drawbacks (‘well, sure, you need to use a document database for the more schema-less cases… or serialise the variable parts… and, of course, object references need to be handled separately…’), but few experiment with alternatives.
This talk, after recalling the popular database-driven persistence solutions, concentrates on the less known, but more interesting and often quite useful approaches – from file-based PStore (ideal for small apps), through Candy’s out-of-the-way magic, to MagLev’s true cross-process transparent object persistence.
-
Ryan Stenhouse
Ryan’s a Ruby fanatic with a love of languages, programming and otherwise. He’s well travelled and has worked on projects of varying complexity for companies you’ve probably heard of. He’s also a little bit nuts when it comes to communication and has a burning passion for getting groups of people together to solve their problems. He also really hates describing himself in the third person and has only recently gotten over his aversion to tofu.
Cultured localisation, or 'how not to offend 1 billion people'
This talk isn’t really about localisation or internationalisation (add a ‘z’ if you prefer!) – it’s about culture and understanding. It’s about how we should all be approaching localisation challenges as people problems and to give good examples of how to get it right and where you can go so very wrong.
Your framework and tool of choice is the easy part – understanding the people you’re wanting to each out to is oh-so-very hard and too often seen as only just a translation problem – a simple matter of swapping one string for another.
I’ll talk about how people communicate across cultures, even when they are so different. Drawing on my experience as a teacher of english as a foreign language and my own travels and struggles to absorb another people’s language and culture, I hope I’ll change how you think about solving these problems in future.
Hell, I’ll even make you laugh. I hope. The most important thing though, I’ll provoke a discussion, given the diverse multilingual background of the attendees here; it could be a very good one.
Stay in the loop
The blabbering blog
Twatter on twitter
@ryanstenhouse sorry for that, fixed it.
Follow us