Schedule

Saturday, Tech Talks

10:30:00 10:40:00 Greatings
10:40:00 11:15:00 Gregory Man, Deployment with Chef
11:15:00 11:25:00 Coffee-break
11:25:00 12:00:00 Max Laphin, How manage 60 million request per day?
12:00:00 12:10:00 Coffee-break
12:10:00 12:45:00 Slava Dodatko, Model Fitness
12:45:00 14:00:00 Dinner
14:00:00 14:50:00 Jose Valim, Skype-conference(Jose Valim cann't come to Ukraine because of problems with visa. We apologize for such program changes.)
14:50:00 15:00:00 Coffee-break
15:00:00 15:35:00 Piotr Sarnacki, Mountable apps
15:35:00 15:45:00 Coffee-break
15:45:00 16:20:00 George Brocklehurst, Javascript and CSS in Rails applications
16:20:00 16:30:00 Coffee-break
16:30:00 17:10:00 Oleg Andreev, Building flexible UI with Ruby and JavaScript
17:10:00 17:20:00 Coffee-break
17:20:00 17:55:00 Pavel Mitin, Anti-patterns of unit testing

Sunday, Business Talks

10:00:00 10:40:00 Yaroslaw Lasor, Products DONE! Railsware Way
10:40:00 10:50:00 Coffee-break
10:50:00 11:30:00 Elliot Crosby-McCullough, Agile
11:30:00 11:40:00 Coffee-break
11:40:00 12:20:00 Hubert Łępicki, Measuring Agile Development Process with Ruby
12:20:00 12:30:00 Coffee-break
12:30:00 13:10:00 Gregory Man, How kill your start up during 7 days
13:10:00 14:20:00 Dinner
14:20:00 15:00:00 Slava Dodatko, Business by programmers
15:00:00 15:10:00 Coffee-break
15:10:00 15:40:00 Alexey Smirnov, Tahometer.com
15:40:00 15:50:00 Closing

Rails 3 mountable apps, Piotr Sarnacki

Over a year ago, when Rails 3.0 was announced, one of the great features on the roadmap was ability to mount Rails applications in other Rails applications. Although plans were changed and we will not see mountable apps in Rails 3.0, they're coming in next versions! Thanks to Ruby Summer of Code and help from the rails core team I can work on making it a reality.

Mountable apps are a great way to develop reusable components, no matter if it's just a login system or a full featured CMS. If you need a forum or a blog as a part of your app, you don't need to always build it from scratch. If you have several applications that share many components, you don't have to use advanced and hard techniques to keep all of them up to date.
In my talk I want to:

• describe what are the benefits of using mountable apps
• address some of the concerns that make people think that "components are evil"
• describe the new API for building and using mountable apps
• tell about mountable apps antipatterns - mountable apps are not a silver bullet and you must know when to avoid them

Piotr Sarnacki: I'm a ruby developer, working mainly with rails. I participate in Ruby Summer of Code 2010 in a project "Rails 3 mountable apps". Me on the web: http://piotrsarnacki.com

Title: Building flexible UI with Ruby and JavaScript, Oleg Andreev

We'll go back to 1985 when Jean-Marie Hullot designed Interface Builder for NextStep and steal his great technique for serializing objects today known as NSCoding in Cocoa. This will help us to build fun and powerful UI spreading model-view-controller design seamlessly across Ruby, HTML and JavaScript.

You will learn how to:

• transfer an object graph from one language to another
• completely get rid of tons of brittle glue code used to make HTML "dynamic"
• go from an ajax business application all the way to interactive programming in a web browser.

Oleg Andreev: Software developer at Pierlis company located in Paris. Develops web/mac/iOS apps. Creator of Gitbox
Twitter: @oleganza Blog: http://oleganza.tumblr.com/ About him on blog: http://oleganza.tumblr.com/post/73474045/about

Measuring Agile Development Process with Ruby, Hubert Łępicki

Hubert about talk: "In this speech I would like to share you my ideas and experience about improving agile development process (especially Scrum) in Ruby development teams. With Ruby.

My approach is to introduce metrics for the process and analyse them over time to find out if your development process is right. I will show variety of metrics that can be used and ways to collect them and analyse with Ruby. Choice of metrics should be left up to individual companies and teams, however there are groups of metrics you can easily collect from tools that you already use:

• SCM-related metrics (daily commits count, branches usage, average commits size, lines of code changed)
• test-related metrics (code coverage, success/fail ratio, code/test ratio)
• static code analysis metrics (ABC, cyclomatic complexity)
• backlogs-related metrics (user stories done, hours per story point, amount of work not ready at end of iteration, new bugs count, team velocity)

As Scrum is lean development process, it's essential not to introduce new tools and processes that would make developers' work harder or just disturb them. Used approach is totally based on existing tools and routines that all good development teams use (version control, issue tracking, automated tests).

Presented techniques could be also useful to find out answer to question why did particular project fail, fight development bottlenecks, find out when technical debt was introduced and adjust company practices to make future projects succeed. Finding out possible future problems is even more precious, as you can fight them before they occur. This talk is mostly business process related. However, all the tools I use are Ruby and analysed projects are all Rails. I will introduce audience to variety of tools they can use to collect and develop metrics for their Ruby projects."

Hubert Łępicki is running small software development house, AmberBit and they are doing some cool Ruby on Rails and mobile applications development for over 2 years in Białystok, Poland.