Rails owes much of its popularity to how it has helped many startups
take products to market quickly. Using Rails and similar frameworks has
enabled many startups to compete with far larger companies who are
burdened with complex architectures and outmoded technologies, and
revolutionized the practice of web development.
But what happens when enterprises use Rails to compete with *startups*?
Can a framework born out of frustration with "the enterprise way" of
web development become a new standard for how large organizations solve
their web development problems? Is Rails an anti-enterprise partisan
framework, or does it want to increase the joy of developers regardless
of the nature of the organization for which they work?
I think the answers to these questions are important for the future of
both Rails and many complex enterprises that could benefit from the
Rails approach to web development.
I'll take a case study of Rails adoption within a larger company
(Getty Images) to talk about:
- How Rails fits into complex multi-application environments
- Arguing the case for Ruby in a Java/.NET dominated world
- Sane, lean architectures for managing change driven by different
parts of a business
- What the Rails community has to learn from the Enterprise
- Organizational patterns of adopting new technologies
- Using open source to help enterprises be more competitive
- Strategies for paying down technical debt as you go (without going