It’s much simpler to write Rails applications when you don’t have any legacy data, applications or technologies to deal with, but many of us are not that lucky. Large Enterprises impose many constraints on us as developers, in this talk we’ll discuss our experiences working in a large enterprise that has a long history building big applications with few-to-no tests.
There is a lot of information locked away in large enterprise databases but its hard to work with. We’ll demonstrate a tool we developed to extract much of that information into your new Rails application. We’ll also demonstrate how to write tests for these old applications using the latest Ruby testing frameworks.
You will see example of:
Alex has over 15 years experience developing software for small startups and in the enterprise. In all contexts he strives to find simple, common-sense solutions to complex problems. Although he is a committed Rubyist he often has to find ways to coexist with legacy technologies and applications in the IT department at a large enterprise.
Pat is a Boston based Rails developer; at his day job Pat works at integrating Rails and other open source frameworks such as PHP/Drupal with large, legacy systems made up of a toxic mixture of vendor technologies such as WebSphere, Oracle (PL/SQL), Visual Basic, Lotus Notes/Domino, etc.
After struggling with legacy systems all day, in his free time Pat enjoys writing a blog on open source Ruby on Rails development ideas geared towards beginners.
Pat spends a lot of time with his wife and two kids. He is is fluent in Spanish and travels frequently with his family to Spain.
For information on exhibition and sponsorship opportunities at the conference, contact Sharon Cordesse at email@example.com
Download the OSCON Sponsor/Exhibitor Prospectus
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the OSCON Newsletter (login required)
Have an idea for OSCON to share? email@example.com
View a complete list of OSCON contacts